I think a lot of people are stuck in 2023 when thinking about AI quality. It's gotten so much better that it's basically a totally different product now.
A couple of days ago we had these flow of Rust based "reimplementation" of Adobe and Microsoft applications. A lot of people couldn't get past the "yeah but it's full of bugs, it's just SlopWare" opinion.
These people couldn't see the forest. The writing is on the wall, that Slopware is the WORST it will ever be. 1 year ago that was unimaginable. Next year, the quality of the developed software will be way better.
Selling "code" or "apps" is dead. My wife works in Workday and I've told her to sell as much stock as she can, because there will be an "inflection point" where ALL software based companies will collapse. The same way as Silicon Graphics, Sun , DEC and similar companies collapsed (along with a bit of IBM and HP, who pivoted) with the rise of PC power. Salesforce, SAP, Workday and all smaller companies that sell generic software will fall down.
Yep. The reality is that as a single developer I'm able to produce a) more code and b) at a higher quality in a year than all of _Google_ did in it's entire existence up until ~2023. One man shops are literally replacing full software suites that were maintained by _thousands_ of engineers, often the highest paid in the entire industry. I can't wait to see what the future holds.
Google's codebase as of ~2023 was, IIRC, ~10 billion lines of code, and fairly high quality. You're able to produce 10 billion lines in a year. At high quality.
I think the contributing factor is people who make software but have no idea what they're doing. They want to make photoshop, but they have no knowledge of photo manipulation or how photoshop works, or any software engineering/development practices. And then we wonder why slop still exists. I am of the opinion that it will always exist: people just have no idea what they want to make let alone how they want to work. "Reimplement photoshop" is a nice end-goal, but you have to actually know to a decent degree how photoshop actually works! Not to mention the reverse engineering knowledge you need
> But this is not to tell every Safari user that they are irrational or wrong in any way for using Safari over Chrome (or any other browser, for that matter). Does Safari use more battery than Chrome? In these tasks it sure seems to, but it’s not by a massive amount, potentially costing you about 0.5% of your battery life every hour. Is that enough for you to switch browsers if you prefer Safari’s UI or reliability or privacy options? I suspect not.
The point is moreso that Chrome being a battery hog is a myth.
Safari is less private than Brave and does not have the breadth of extension that Chromium browsers (and Firefox) do. So again, the only reason to really choose Safari is if you're completely in the Apple ecosystem.