3 ms·
You should check out his browser hacking videos. It's pretty shocking how much they have already and how fast it's improving. I have no doubt they will eventual
by seti0Cha 3y ago
You should check out his browser hacking videos. It's pretty shocking how much they have already and how fast it's improving. I have no doubt they will eventually be able render the vast majority of websites correctly. The real question is whether they will ever be able to make it performant enough that people who don't care about browser hacking will choose to use it. That's where a lot of the engineering hours in browsers goes.
- munificent 3y ago> It's pretty shocking how much they have already and how fast it's improving. My experience with large software projects is that there is an 80/20 effect where the first 80% happens really fast and easy and then the last 20% gets harder and harder and harder. Most of the challenge of software engineering is dealing with the scale and complexity of the codebase itself. So greenfield development is always going to be faster at first because there's simply less code to go around. But as you keep pouring code in, you are creating the complexity that makes software development hard. I definitely wouldn't do a linear projection of their current velocity and assume the whole project will keep moving that fast.
- seti0Cha 3y agoAll very good points. Still, I hope they pull it off for the shear inspirational value.
- phil917 3y agoI say something similar to my friends and colleagues all the time regarding my “professional” software projects. It takes 20% of the time to do 80% of the work. But that last 20% of the work takes 80% of the time. Essentially the core functionality doesn’t take very long to build out. But the final polishing, details, edge cases, and bug fixes soak up a huge amount of time.
- tcbawo 3y agoI suspect that the momentum behind the project is having a group of core developers (Kling foremost) that have complete knowledge of all the moving parts. This allows a small team to make changes quickly while keeping the whole cohesive and without the slowdown of deliberative bureaucracy. Maybe it’s like the human organizational equivalent of L1 cache. It’s like riding a wave, a situation that can’t last forever. I have been part of teams that did the work of much larger teams. It’s great when that happens. The last mile might be less fun, but this entire OS is a labor of love.