I recently upgraded to Pop_OS 24.04 because I was sick and tired of being stuck with an outdated base.
But after trying the new Cosmic desktop, I basically ran screaming back to Gnome/X11 (with a couple of extensions to give me the old desktop experience from 22.04).
Once 26.04 drops, along with Cosmic Epoch 2, I may give it another serious try. Or I'll just go to KDE6/Wayland and see how that goes. (I do use KiCad from time to time, so I wonder how usable it'll be on Wayland down the line.)
(For reference, my biggest gripe with Cosmic right now is how it can't seem to figure out how to manage window focus. Modal dialogs can lose focus to their base window, and sometimes become covered by that base window. And focus-follows-mouse hasn't been done right ever. Both have issues written up, I just hope they get attention. Meanwhile, throngs of people seem to "swear" it "works fine for them.")
Do I struggle to keep them organized for later reference? All the time.
Do I use Obsidian? No.
I actually use Joplin, which I switched to after deciding I needed to dump Evernote. And before then (and somewhat simultaneously with), I used a pile of disorganized text files (sometimes shared via DropBox).
That’s a really clear split: “actions are fine, reference organization is the pain” — and Joplin/text files is a very real workflow.
If the goal is later reference (not task generation), the most useful thing to validate for me is: what “organized” means in practice for you. Is the biggest failure mode:
1. you can’t find it because you don’t remember the right keywords, or
2. you remember it exists but it’s scattered across too many places/notebooks, or
3. you find it but it’s missing the surrounding context?
Details in my HN profile/bio if you want to see the angle I’m exploring (it’s not only Obsidian-specific).
Mostly some version of 2.
Or more specifically, I have a lot of top-level note documents with somewhat clear titles and organizations. And then there are a lot of "thing to remember" snippets that frequently have no obvious place, and are often related to the greater topic of multiple note documents.
One pattern that may help (without heavy re-org) is to treat those snippets as first-class items with a stable home, and only link them out:
- keep an “inbox / snippets” note (or a single folder) where every orphan snippet goes
- give each snippet a short, searchable handle (one line title)
- add 1–2 lightweight links: related topics, and optionally “why it matters / when I’d need this”
Then when you’re in a top-level doc, you can embed/query “snippets linked to this topic” instead of trying to decide the perfect location for each one.
In your case, are those “things to remember” mostly time-bound (follow up, renew, schedule), or more like evergreen reference (commands, ideas, reminders)?
And I'm reading this article while sitting at an EMC/EMI test facility monitoring the test for one of my products. Certainly an interesting, and somewhat on-topic, read.
I still think there's a benefit to sticking with EVs from companies that are actually "all in" on EVs. Otherwise you're buying the product that the company (or really the sales/service channel) really doesn't want to sell you.
In this space, Tesla does have competition (e.g. Rivian and Lucid), but nowhere near as much as they should.
I'm very happy that the "base model" of cars now has a lot of the modern tech. Not because I'd personally buy a base model, but because its what you get whenever you travel and need to rent something.
In the past, when traveling, I'd be shocked at just how bare the rental cars were compared to my normal home experience. Fortunately that's no longer the case.
Its also useful for developers to have a way of bypassing customer support to have direct visibility into what issues the actual users are experiencing. This can come in the form of browsing tickets, online forums, or social media.
Often something that's easily brushed off by a support rep will ring a bell in the mind of a developer who has recently worked in the area of the code related to the issue.
The last time I worked on a project that actually had all these roles, "architect" basically meant someone who sat in meetings all day and played very little role in the actual software development of the project.
There were plenty of times where it would have been useful to have someone providing real architecture/design guidance, but no such person functionally existed.
The Seawolf was kinda the first attempt at a next generation attack sub while we were still figuring out the technology, making it far too expensive. But it led to the Virginia class, which has gone into mainstream production.
In some ways there's a similar situation with the F-22 vs F-35, though those two may have a bit more of a difference on roles and requirements.
This might be an unpopular opinion, but I'll take a car infotainment system that doesn't need CarPlay/AndroidAuto to be usable (and lacks it) over one that requires a phone attached via CarPlay/AndroidAuto to be usable.
I use Android Auto on rental cars all the time.
My daily driver is a Tesla (Model S /w MCU v2) that doesn't have it. And doesn't need it to provide a usable experience.
If the software has the same library as your phone, then I could why you see it as on par.
Android Automotive has a much smaller library than Android Auto, so the selection for audio apps, such as podcasts and music, are much more limited. The options for map software is smaller too. Also Android Automotive doesn't necessarily use your phone's existing internet connection. Depending on the maker, you have to subscribe to a separate data plan.
I've only rented Teslas but I can see how most people would consider CP/AA to be unnecessary given the quality of their integrated software. But for me, the two things Tesla can't do (and CP/AA can) is
