I 100% agree. It's been incredible for velocity and the capabilities and accuracy of the models I've been (mostly from Anthropic) have improved immensely over the last few months.
I’ll start off by saying that the model Y is one of the best mid-level cars I’ve driven so the issues I mention below are worth the tradeoffs to me.
In my experience, Tesla navigation can be pretty bad when navigating my large urban city. During peak traffic times it often tries to send me down roads that are notoriously known for traffic backing up. Most times when I end up following those suggested routes, my ETA essentially becomes meaningless.
I’ve found Google, Waze, and Apple maps to be a lot better in this respect.
I do miss having CarPlay. That’s not to say I think the music integration you mentioned is bad, but I find the overall UI in my model Y to be a bit confusing - and the lower icons seem to sometimes randomly change from what I have them set as.
Same. I love the tesla model y, but it's not perfect. The screen UI is pretty good for the most part, enough that I don't think about carplay too often.
But I do tend to stream audio from my phone more than from the tesla UI, and so I do miss carplay when I think about it.
From the article: "What I find really interesting about this change on Apple’s part is how it seemingly goes against their own previous human interface guidelines..."
Welcome to Apple of the last decade. As an avid user of many Apple products, this has been extremely frustrating to experience. Hopefully Alan Dye's departure will see at least partial return to obeying Apple's own HIG.
The author is criticising 2025 macOS for not following the 2005 HIG. This is not reasonable criticism, the HIG are not set in stone and they have changed many times in the past 20 years.
> Don’t display an icon if you can’t find one that clearly represents the menu item
> Not all menu items need an icon. Be careful when adding icons for custom menu items to avoid confusion with other existing actions, and don’t add icons just for the sake of ornamentation.
> Instead of adding individual icons for each action, or reusing the same icon for all of them, establish a common theme with the symbol for the first item and rely on the menu item text to keep the remaining items distinct
And if you go do the work of tracking down newer HIG versions, they say the exact same thing.
2014:
"Avoid displaying an icon for every menu item. If you include icons in your menus, include them only for menu items for which they add significant value. A menu that includes too many icons (or poorly designed ones) can appear cluttered and be hard to read."
Newer versions seem to have escaped being properly archived anywhere, so Apple can gaslight us all into believing the HIG has never changed, that we have always been at war with East Asia, that giving a bad icon to every single menu icon has always been good, and that rule was never arbitrarily changed at the whims of a cardboard box designer and his liquid glarse aesthetics.
It works out though because it does give me ammo when people use these guidelines to thoughtlessly defend poor design as if they are axiomatic rules. For 20+ years having lots of icons in a menu was bad...but now...it's good! Why? I dunno! It just is!
Yes, the newer generation is used to computers being an inconsistent mess and slow. Only the the technically interested people know that it doesn't need to be this way. (And thus don't feed up with this and use Linux or *BSD :-) ).
yearning for old apple and order, current times and genz are more chaotic. not sure if it's generational, old apple was obsessed about design, now HIG is mostly optional. they now even use hamburger on websites which was a big no in the past.
On an Apple TV with first gen Homepods connected it is incredibly laggy. Specifically rewind and fast forward take sometimes up to 10 seconds to respond. And even then they never seem to get me to the correct location. It’s pretty maddening.
I went public schools growing up and never imagined homeschooling as an option when I eventually had children of my own, but my kid was not the same in their school after the pandemic. Coupled with how ideologically focused the public schools in my state have become over the last few years, homeschooling them was an easy decision.
Apparently it's also shit. There was a discussion about it a few days ago that contains multiple project maintainers pointing out deepwiki didn't get their repos at all https://news.ycombinator.com/item?id=45884169
To each their own. This syntax actially resonates with some people, which is why template-based frameworks like Vue and Svelte are also popular. In fact, at first glance this reminds me a lot Vue in some of its approach and syntax.
BTW - with Vue you can use entirely JSX of you dislike HTML component syntax (I don’t know enough about Svelte to know if it allows the same).
This is often the real driver in these decisions. A previous company I worked at had an API written in modern PHP with Laravel. Traffic wasn’t very heavy on most days and we could autoscale when it was required. It worked great and we hadn’t encountered business problems that couldn’t be fairly easily solved within the ecosystem. However, one of the execs on the business side knew some other exec at a big tech company who told our guy that “PHP can’t scale”. So then we get questions if we should we consider rewriting, if we’re using the “best” language for our needs, etc. They wanted to plan for some theoretical future that they couldn’t even define from a business sense.
Sure, it’s good to be aware of future business needs so that we, as technical people, can be asking the right questions to prepare for what that future may look like, but that almost never means a decision about language x over language y. It’s much deeper than that.
reply