Apple has been required by the DMA to accept non-webkit browsers in the EU for 2 years now. But in practice no one has built one. There are some claims about malicious compliance on Apple's part (what else is new), but it seems equally likely to me that no one wants to maintain 2 rendering engines for the same app (1 for EU and 1 for the rest of the world).
The argument is based on one of these companies hitting the singularity, making it impossible for any other company to catch up ever. I still think it's way more likely we'll see a typical S-curve where innovation starts to plateau. But even a small chance of it happening in the future is worth a lot of money today.
There's a massive thinking gap in this singularity thinking. We ARE the singularity. It has been exponential all the way back to the big bang. First the stars, the solar system, life, consciousness, language, computers, the internet. Yes it is speeding up and that is exciting, cause we are going to experience a lot in our lifetimes. We have a lot of exponential growth to go before progress becomes instant. There are physical limits, too. Power generation for example. I can't believe on what dumb shit people bet the world economy on.
You should distinguish between residents and visitors. In Belgium, and I believe in many other European cities, street parking for residents is extremely cheap or free.
I'd argue that LLMs are not yet capable of the last step, and because most sufficiently large AI-generated codebase are an unmaintainable mess, it's also very hard for a human developer to take over and go the last mile.
So what is the “last step”? I have one shotted a complete AWS CDK app to create infrastructure on an empty AWS account and deploy everything - networking, VPC endpoints, Docker based lambdas, databases, logging, monitoring alerts etc.
Yes I know AWS well and was detailed about the requirements z
God yes. For some reason, I automatically scroll in such a way that I always keep what I'm reading at the very top of the screen. Which means that every time I want to reread a sentence I first have to scroll past the header.
I'm building web-based CAD software for woodworkers. Not a plugin, I'm starting from scratch. I'm aiming for it to be intuitive for non-technical users (think SketchUp), while also offering some of the more powerful tools of "proper" CAD tailored for woodworking: simple parametric workflows, cutting layout optimization, built-in tools like chamfers and joints,...
If you are using webpack, see if you can make the switch to turbopack. It cut my build times from ~1 minute to 15 seconds, incremental builds are down from 10 seconds to 2. Memory usage is down a ton as well. But if you rely on webpack plugins this may not be an option for you.
I've been pushing our apps at work in this direction and it's definitely worth it.
If you're relying on webpack plugins heavily, I'd consider that a liability either way. It's going to seriously hamper your portability to other frameworks and build tools and even new versions of the current ones.
You can easily run turbopack for development / preview environments and webpack for production(-like) ones btw. as long as you don't rely on custom magic.
For me, the answer to this question is: parts that involve no architectural decisions, and that won't need to be extended or built upon significantly in the future.
When I'm working on a greenfield project that I intend to build out further (which is what I am currently doing), I find that there's not a lot of work that fits those criteria. I expect that can change drastically when you're working on something that is either more mature, or more narrowly scoped (and thus won't need to be extended too much, meaning poor architectural decisions are not a big issue).
reply