3 ms·
Software is hard. Chrome had this in 2008. Firefox had to be rearchitected 14 years for this.
by oblio 6y ago
Software is hard. Chrome had this in 2008. Firefox had to be rearchitected 14 years for this.
- nfoz 6y agoBrowsers are too big and the web is too complex. Engineering failures all around. As engineers, we should not accept this status quo; we should replace it. We need a new web and new software.
- MaxBarraclough 6y agoSee Gemini and Gopher. https://news.ycombinator.com/item?id=23042424 https://news.ycombinator.com/item?id=23042424
- approxim8ion 6y agoGopher is the opposite of new. Gemini is interesting for sure, but it's not an alternative to the web as they fully admit. It's an alternative to a subset of the web. Let's call it the document web. Blogs and articles and so on. But as entertaining as it is, it is a very very small subset.
- sfink 6y agoThat's the point. If you want the web, you need today's browsers. If you want a subset of the web, your "document web" for example, you can get away with something simpler.
- MaxBarraclough 6y agoRespectfully, you're failing to engage with the purpose of the project. > it's not an alternative to the web Right. You can't have a lightweight drop-in alternative to the web, pretty much by definition. Any platform capable of everything modern browsers are capable of, is by definition enormously complex. > it is a very very small subset That's not a flaw, it's a design goal. It isn't meant to be a half-baked portable GUI toolkit the way the modern web platform is, it's meant to be a simple and minimal format, stable and easy to implement. There are other formats somewhat like this in common usage, like man pages and, of course markdown.
- approxim8ion 6y agoI don't disagree with you at all. I like Gemini and think it is a very worthwhile pursuit.
- pmontra 6y agoGopher is from 1991. I've been using it back then but HTTP won quite easily.
- staticassertion 6y agoWhat's wrong with the web and browsers? It's honestly pretty incredible - we have a system where we can load and execute arbitrary code from any number of third parties near-instantly and it actually works and isn't a complete security disaster. Seems pretty cool tbh
- takluyver 6y agoPeople object to the massive effort it takes to create or maintain a browser engine which can practically browse the modern web. We're down to 3 players now actually trying to do this (Mozilla, Google, Apple). It conflicts with the idea that you can fork software if you dislike what it's doing, because even starting from existing code, it would be a lot of work to keep up with changes so you don't get left behind. So people imagine splitting off a simpler web, where the main focus is on reading documents, rather than interactive applications, and browsers could be much simpler. But it's pretty hard to see how this could actually work in practice.
- yakubin 6y agoThere are many distinct PDF readers. Making a document browser shouldn't be more complicated than making a PDF reader. PDF readers is how it works in practice.
- takluyver 6y agoI guess the issue is that a modern web browser is a sandboxed application runtime which also happens to function as a document browser. It's been going in that direction for a long time (since webmail became common), and there are real advantages of the browser as a platform for applications - it's cross platform by default, and it has pretty good sandboxing. So probably the most you can hope for is that we split the document part of the web from the application part, so that it's easier to make a viable document browser. But it's not clear what advantage this offers for anyone who's not trying to make their own browser. Security is probably much simpler for the document browser, but the logins and sensitive data you care about securing are probably in the application browser anyway. And we've spent the last 20 years blurring the lines between documents and applications (think of a Github issue page, for instance), so even if it was possible to access information as a pure document, there would be advantages to looking at it in an application browser.
- pabs3 6y agoA recent post about that: https://dustri.org/b/the-web-browser-im-dreaming-of.html https://dustri.org/b/the-web-browser-im-dreaming-of.html Gemini might be a good replacement for the web: https://gemini.circumlunar.space/ https://gemini.circumlunar.space/
- tristan957 6y agoThis is factually untrue. Site isolation wasn't enabled by default in Chromium until v67 in 2018. https://www.chromium.org/Home/chromium-security/site-isolation https://www.chromium.org/Home/chromium-security/site-isolati...
- oblio 6y agohttps://www.google.com/googlebooks/chrome/big_04.html https://www.google.com/googlebooks/chrome/big_04.html http://www.scottmccloud.com/googlechrome/ http://www.scottmccloud.com/googlechrome/ In early-mid 2008, I created a comic book for Google explaining the inner workings of their new open source browser Google Chrome. If I'm mixing this up with https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis, that's still 10 years.
- tristan957 6y agoChrome was a new project, and didn't have to deal with the legacy of being built on top of the same source code as Netscape Navigator. I do not understand why you are trying to make this out to bash Firefox like they aren't as competent by taking ~10 years to implement multi-process browsing after Chrome. Legacy software and patterns are truly painstaking processes to iterate on. But yes Electrolysis is the initiative that you should have referred to in the original comment.
- oblio 6y ago> Software is hard. Chrome had this in 2008. Firefox had to be rearchitected 14 years for this. How is this bashing? :-) It literally starts with "Software is hard." ...
- staticassertion 6y agoChrome didn't have this until 2018, as the parent link shows. This is not about multi-process architecture. Firefox is < 3 years behind, not 10, not 14.
- 6y ago