It's all the AI bloat for me. It keeps getting shoved in my face and they _really_ want me to use it. But I neither want nor need it. The product itself was so good that it doesn't need this whole guessing-machine-layer on top of it.
I also agree that the nav, structure, and defaults changing keep being un-intuitive and are making it harder to find the things that I use and that matter to me and my orgs.
They've been using AI to shove a lot of AI into their product and trying to force everyone to use AI. I really don't understand the why of any of it. The product was working great for what it needs to do. I don't need AI to make guesses about data for me and I especially do not want _yet another product_ trying to write features in my codebase (which is their latest push).
Zen has been working as a full replacement for Arc for me since the Atlassian acquisition. There are only minor things that I miss from Arc ("development mode").
I agree with a caveat: Default date pickers on mobile devices are very good. But on desktop browsers they are terrible. They break design continuity in a very ugly way and have quirks between browsers and systems. And personally, the popup calendar they provide just too small. If the system took over the date picker on desktop like it does on mobile devices instead of forcing the browser to handle it, I feel like we could get somewhere better.
> Having needled her repeatedly over the past couple years about AI’s environmental, political, and economic implications, I brushed all that aside on a recent Sunday and drove to her house. After a little tibia talk, I opened her computer and began emitting vibes.
So the author had a moral, environmental, political and economic stance and then just threw them all in the bin.
This is sad to me because I have all of these stances and more. I just cannot bring myself to give in and use a technology wrought with so many systemic problems. And I cannot understand how anyone could feel so strongly about anything to the point of preaching it to others, only to just sort of … ignore them(?).
This is a weirdly unpopular opinion here when it comes to HTML & JS, but there's a time and place for everything. This is a neat small example, but hardly worth the effort of changing something that was already working fine.
With the change, I now need another roundtrip network request to get new sizes of the same content on the current page that would have been able to be done in just a couple hundred bytes of JavaScript.
Edit: also there is still no view-transition support on Firefox.
Seems like they went through a bunch of vibe coding only to come up with a half-baked copy of Astro. And why not just use Astro? It's got the exact features that they've built, many more, and a large and bustling community.
Thanks for pointing this out. I had no idea it existed. The other options in the comments just didn't quite work the way I would like.
- The main topic requires me to pull python dependencies, build, run manually on Mac
- All others can't reassign the button below the scroll wheel on the MX Master 3/4
I assume it's because they would need to re-wire electrical and retrofit plumbing on a massive scale to accommodate kitchens and bathrooms for separate units. They end up needing to gut the entire building and cut through floors and ceilings without damaging any structural and load-bearing parts. It doesn't sound easy nor cheap.
This has nothing to do with NodeJS or NPM. The code is freely distributed, just like any open source repo or package manager may provide. The onus is on those who use it to audit what it actually does.
The code is literally right there for you. It doesn't matter what ecosystem or package manager. Someone could distribute the same thing anywhere — it's up to those pulling it in to actually start auditing what they're accepting.
I also agree that the nav, structure, and defaults changing keep being un-intuitive and are making it harder to find the things that I use and that matter to me and my orgs.