| ▲ | Bez: Generating a browser engine from specs and tests(tangled.org) | |||||||||||||||||||
| 51 points by nerdypepper 2 hours ago | 11 comments | ||||||||||||||||||||
| ▲ | Alacart 42 minutes ago | parent | next [-] | |||||||||||||||||||
This makes a ton of sense to me with the huge corpus of web standards that exist. In theory we should be able to generate a browser from those specs, it just took a massive amount of effort before. Maybe if things like this get some traction, some of the human time spent implementing the spec could be spent on creating more/better specs, allowing for even better generation too. Edit: replies are making good points about AI capabilities and where the effort really goes. Let’s just say that I meant this in an aspirational sense, rather than where the rubber actually meets the road today. | ||||||||||||||||||||
| ||||||||||||||||||||
| ▲ | fouc an hour ago | parent | prev | next [-] | |||||||||||||||||||
I'm looking forward to the day when we have fully functioning web browsers that we have full programmatic control over in all aspects. With luck all chromium/blink-based browsers will go the way of the dodo bird. | ||||||||||||||||||||
| ||||||||||||||||||||
| ▲ | mircerlancerous 42 minutes ago | parent | prev | next [-] | |||||||||||||||||||
This is a neat idea. It opens up a whole new way to make a web app into a native app, while also adding native features not available in web views | ||||||||||||||||||||
| ▲ | trencedamp 7 minutes ago | parent | prev | next [-] | |||||||||||||||||||
But can it dance | ||||||||||||||||||||
| ▲ | helpprotactiniu 34 minutes ago | parent | prev [-] | |||||||||||||||||||
Is this named like Jev intentionally? Or is this just a new naming convention that I haven't been watching? | ||||||||||||||||||||
| ||||||||||||||||||||