Just to expand on the “behavior” bit, there’s a truckload of little things that native AppKit apps get you that nothing else will, not even other “native” toolkits like Qt. Things like Option-clicking a disclosure triangle in a nested list expanding/collapsing all children recursively, which one comes to use frequently and misses when absent. Foreign toolkits have spotty coverage of that kind of thing if they implement any at all.
As much as visually fitting in is important, behavior is perhaps bigger. Anybody who’s working on the Mac port of a cross platform toolkit would do well to replicate those little bits.
People care about the tools they are using a lot and spend a great deal of time on finding the perfect knife, the perfect editor, the perfect scissors.
People who care about their tools. If I have to stare at it all day, being pleasant on the eyes is a feature. If every time I grab my tool I think “urk, this is so ugly”, it affects my flow.
I've been using Migadu for a low-moderate throughput inbox (within their micro tier limits) in the US and the IMAP4 performance is kinda awful sometimes. I'm not sure why :(
Android's too. For some reason, it randomly changes plurals into possessives by adding apostrophes from time to time with no rule I can infer and avoid, but often enough to be annoying.
No, two of those are some pretty fundamental complaints about how GP wants to use their device. Just because you don't have those complaints doesn't make them any less fundamental.
Ultimately the disagreement is primarily on the fact that Apple goes very far out of their way to hide the concept of a file and filesystem from the user.
It's easily solvable with a case. I agree that it's silly that Apple does it this way, but I struggle to see how it rises to the level of being a fundamental flaw like file management is.
The wobble actually factors onto my device choice as well. It's just annoying to live with for the life of the phone if you can't find a case that widens it, which many don't.
As always, there's a balance. Communities (and individuals) generally need the ability to moderate and manage access to both membership and interactions with the community. Algorithmic-driven open platforms are sorta mutually incompatible with that idea
From what I can gather, the event happened in 2008. At the time gentoo had no official wiki, it was an unofficial wiki that died or went offline for a significant amount of time.
I agree with this, but as someone who occasionally shoots film I'm still very sad about it. There's still reasonable demand for film, I can walk into my local Target and pick up Fujifilm Fujicolor Superia 200 for $10 a roll. It's just really hard to scale down a business without imploding, but I firmly believe Kodak could have had a future as a boutique film supplier if they wanted to. It just wouldn't be super profitable.
Semi related, but a decent search engine like Kagi has been a dramatically better experience than "searching" with an LLM. The web is full of corporate interests now, but you can filter that out and still get a pretty good experience.
Go discouraging abstracts is sorta just... wrong anyways. Go doesn't discourage building abstractions, it discourages building deep / layered abstractions.
That is a key point in my opinion. A typical stack trace of a Spring (Java) application can easily be 1000 to 2000 lines long. That is not so common in Go, as far as I know (I'm not a Go expert ...).
Not really, it's more like it encourages "wide" abstraction (lots of shallow abstractions) that get pieced together vs heavily nested abstractions that encapsulate other abstractions. It's a very imperative language.
reply