Similar story here. Loong time Apple fan, but as they say.. "trust arrives walking, but leaves on a horse". I'm real mad!
I installed tahoe in a virtualbuddy VM to see how it was before running on my main system... and.... I will be definitely be keeping Sequoia for a while (at least a year, probably).
If the situation does not improve in the meantime, I will probably switch to a framework laptop running cosmic desktop or something like that.
I recall it being slow, with frequent downtime, poor mardown support, and having very poor (or nonexistent? can’t remember exactly) first party non-web clients. I vaguely recall some third party apps picking up the slack (pun!), but integration was pretty basic (they did their best).
It basically stagnated like it was abandon, and then hipchat (atlassian bought and killed it) and later slack just ate its lunch.
> The fanaticism and cult of personality seems unusual for a living figure though.
Covid, both the disease and/or the isolation of lockdown, did some weird things to several people I know -- they just didn't come out the other side the same person. Coupled with social media and what seems like a global rise of nationalism fervor, the outlook doesn't seem good.
There's a growing amount of research on cognitive changes/decline following even mild covid infections. I think the realization that governments were so incompetent in handling a crisis and also fully willing to let people die for nothing didn't help either. Especially in those people who tend to be more fearful and less trusting in general. Fear and insecurity don't lead to people making the best choices.
Nitro does not declaratively handle service dependencies, you cannot get a neat graph of them in one command.
You can still request other services to start in your setup script, and expect nitro to wait and retry starting your service when the dependent service is running. To get a nice graph, you can write a simple script using grep. OTOH it's easy to forget to require the shutdown of the dependent services when your service goes down, and there's no way to discover it using a nitro utility.
It sounds[1] like this was an issue with assumptions regarding header stability. Hopefully as people update their installations things will improve for us end users.
I installed tahoe in a virtualbuddy VM to see how it was before running on my main system... and.... I will be definitely be keeping Sequoia for a while (at least a year, probably).
If the situation does not improve in the meantime, I will probably switch to a framework laptop running cosmic desktop or something like that.
reply