Hacker Newsnew | past | comments | ask | show | jobs | submit | noisem4ker's commentslogin


The provenance that is lost is the original base.

No, the original base is in the commit history. It's just not relevant any more after rebase. It's like your individual keystrokes before a commit are not relevant any more after a commit. They're not lost provenance.

The European Commission has recently put WhatsApp under scrutiny in terms of the Digital Services Act, and forced them to open up allowing interoperability with other messaging applications.

Perhaps we'll see a return of apps like Pidgin soon.


We've never left. https://pidgin.im/

WSL. Android app support (for the little while it lasted). Recall.


For Chrome and Firefox.


Because he didn't say Firefox so he deserves downvotes?


Odd response to attaching additional, valuable information to an existing comment.


That the first result is clearly marked as an ad is an opinion. One I don't agree with.


It’s not an opinion, the law states that ads must be “clearly” labeled as such, so if you disagree and think Apple is breaking the law, feel free to report them to the FTC and see how far you get.


Google's Gboard completes "i want t" with "to" and "the" for me.


Which is the better option now. But the one he's talking about is the OG windows phone swipe keyboard which would predict next word almost like from a LLM these days. For that reason, you can swipe like a maniac but it'd still type the correct thing.

Apple keyboard is shit. Swype (the one Microsoft bought) is better but still shit. Gboard is ok. But none of them are close to that windows phone keyboard. I still miss it.


Google's keyboard is okay for English. It's a complete tire fire for two other languages I use (both popular and with a very large training data set).

Suggests words that make no sense, preferring rare words to much more widely used and obvious matching picks. Has the vocabulary of a poorly educated five year old idiot savant — fails to complete many words you use fifty times a day, but sometimes surprises you by suggesting something you'd hear a couple times per decade. Doesn't know other forms of the same word, forcing you to correct it manually over and over again, often failing to remember the word until you type it in four or five times.

Yes, I've downloaded all the dictionaries, tried it on many phones, and my friends are of the same opinion: it really is just bad.


I write in English and Spanish on it, and it seems the shittiness gets multiplied when you use a bilingual instead on monolingual layout. I've tried switching languages manually, but that sucks even more when writing Spanish with English technical terms sprinkled.

This is a patent case where IA made a function worse instead of better, yet companies clinged to it for some reason.


Never used the Windows Phone keyboard but after Swype fixed its worst error ("me" was very often rendered as "nee", as in the term for a maiden name) it was fantastic. The last time I was able to use it was ca. 2016 when my Nexus 6P suffered the dreaded battery-goes-to-worthless-one-night-and-never-recovers problem. The editing keyboard allowing precise cursor placement, the Swype-X/C/V shortcuts, Swyping above the keyboard to indicate capitalization - WHY WHY WHY were they dropped?

The swiping keyboard from Apple simply refuses to do "and" for me. I get "abs" (I'm not a gym rat; I don't talk about that) or "Abbas" (the only one I know is the Palestinian president, and I don't talk about him either) almost every time. I hate the autocorrect-something-five-words-back problem, but not being able to recognize one of the most common words in the language is unacceptable crap.

I'll give Swiftkey another try.


The S23 too was Snapdragon only, allegedly to let the Exynos team catch some breath and come up with something competitive for the following generation. Which they partly did, as the Exynos S24 is almost on par with its Snapdragon brother. A bit worse on photo and gaming performance, a bit better in web browsing, from the benchmarks I remember.


The container runs a virtual machine using the host kernel's KVM device. Windows is then automatically installed inside said virtual machine.

https://github.com/dockur/windows


Ah, that makes more sense (and learned about KVM today, thank you.)

So more accurately, it's Windows in a VM, and the VM host running in a container.


You might find the StackOverflow surveys more representative: they crown Windows as the most used OS, with a solid margin.

https://survey.stackoverflow.co/2025/technology/#1-computer-...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: