3 ms·
The problem is that nobody can create anew browser engine because you not only need to implement all the standards you also need to make your browser work with
by simion314 6y ago
The problem is that nobody can create anew browser engine because you not only need to implement all the standards you also need to make your browser work with broken html and work in the same way Chrome and Firefox work.
IMO we would need 2 split the document part from the application part. Have a set of elements and a document format just for blogs and news websites , and more complex components and APIs for application websites. Then you could have a browser that would be more simple that will be enough to browse blogs,forums and news sites and a more complex browser for SPA applications.
- BlueTemplar 6y agoThat first part is the Web, while the second part are native programs with Internet connection.
- simion314 6y agoI think you could have web rich documents with basic interactivity and as an option web application that are "native app like" , with tons of APIs for camera/microphone , bluetooth, canvas, 3d , complex sound APIs. We have to admit that rich web application can be very usefull, even during Java or Flash days we known that sometimes you need an animation or a simulation on a page to better present some content. Though it makes you think if we had an 100% open source Flash, then you could have used it for complex SPA like Figma while keeping all the bloat into an optional plugin , if the plugin was optional developers would not be tempted to use it unless is needed and it it was needed they would have use something like Flex (a Flash GUI tookit) and not reinvent the wheel constantly.
- BlueTemplar 6y agoSure, canvas is appropriate for basic animations/simulations.