8 ms·
...and ideally, we should also encourage the use of the "lesser" browsers like Dillo, NetSurf, and all the text-based ones. They can't really run "web apps" and
by userbinator 9y ago
...and ideally, we should also encourage the use of the "lesser" browsers like Dillo, NetSurf, and all the text-based ones. They can't really run "web apps" and the like, but will be fine for viewing the "long tail" of content-focused sites out there (including this one.)
What has become quite obvious to me within the past few years is that the whole "move the Web forward" thing seems to be really about coming up with and implementing as many complex features as possible (and advocating for their use in new sites), making it harder over time for smaller efforts at creating independent browsers to produce anything useful.
- baddox 9y agoI wonder: who could even feasibly introduce another browser today? The task seems almost impossible.
- nrhk 9y agoWell you could also fork Chromium I guess.
- colehasson 9y agoAnd with Puppeteer/Devtools programmers can stay in text editors.
- Vinnl 9y agoExcept that that doesn't really broaden the ecosystem, unfortunately.
- rlanday 9y agoGiven enough time, it does. People used to talk about a “WebKit monoculture” on mobile back when both Safari and Chrome were built on WebKit (although, they enabled different features and used different JavaScript engines). After Google forked WebKit to create Blink, WebKit and Blink started to diverge with different development priorities resulting in different improvements being made and different features being implemented. So as time goes on, and code gets added, removed, and rewritten, much of the commonality eventually disappears over time.
- jopsen 9y agomozillia research is sort of doing it with gecko. But yeah, from scratch is hard... Google didn't even do that, they started from webkit.
- mercurial 9y agoWith Gecko ? It's their original engine. You probably mean Servo (the experimental Rust engine).
- erikbye 9y agoI guess it's not wrong to call it their original engine, just remember it's a two-decades-old development that started at Netscape.
- gsnedders 9y agoWell, arguably started at DigitalStyle.
- robin_reala 9y agoCan you expand? I thought I had a good grasp of Mozilla’s history but this is the first time I’ve heard of them.
- dev_tty01 9y agohttps://en.m.wikipedia.org/wiki/DigitalStyle https://en.m.wikipedia.org/wiki/DigitalStyle
- gsnedders 9y agoSo my understanding is following Netscape's acquisition of DigitalStyle, the decision was made to replace Netscape's existing layout engine with something based on what DigitalStyle had in their editor (which, unlike Netscape's existing one, supported things like reflow), and it was this combination that was open-sourced. Notably, it was only really the layout engine that was replaced: the HTML parser and the JS VM survived unchanged, hence the name NGLayout for what became Gecko.
- captainmuon 9y agoI would first target a subset of HTML, for example static documents instead of web apps. You would have a specification like AMP which restricts what elements you can use. If a document used the full spec, I would fallback to another engine (e.g. WebKit). You could have full documents in iframes inside limited documents (but cross-frame scripting might be hard to get right in that case). Also, I would try to make it as modular as possible. E.g. layout engine, css engine, js engine etc. as libraries, use the system codecs instead of bundling own codecs, and so on. And it would help to have an extensive test suite, which you could take from other browsers.
- krapp 9y agoThe difference between static web documents and web apps isn't the set of HTML they use, it's just that the latter are designed to deeply integrate javascript (and/or, to futureproof this comment, WebAssembly) into their UI, rather than do all of the logic on the server between requests. The only way to ship a browser that doesn't render "web apps" would be to simply not support scripting of any kind. That would permanently break much of the web unless you offered a way to opt in to scripting the way current browser users who run script blockers can. But then you just have a regular browser with script blocking turned on by default. Having different engines for "static" and "web app" documents, and defining a proprietary standard for the former as a restrictive subset of HTML would be unnecessarily complex and hostile to web developers.
- captainmuon 9y agoThere is a subset of web pages that only use a subset of features - Hacker News is an example, but better examples would be Wikipedia, many news sites, documentation of all kinds, and so on. You have basically static HTML, and use JavaScript for 1) progressive enhancement and decoration (what used to be called "DHTML"), 2) ads, and 3) more and more for client side rendering. You can't do much about 3 right now, but I would offer support for 1 and 2. I would definitely offer scripting, but just not all features. You could autodetect a "lean html" site, or you could use a marker such as "<html lean>" like AMP does. I don't think this is hostile to developers at all, unless AMP is already hostile. You would have a subset of the web platform, yes, but if you only use that you are likely to have a faster and leaner website - even without a new engine. I would view it as a guideline or a best practice, rather than a restiction. Side note: I think the co-mingling of documents and apps is the source of a lot of problems today. Why can ads inject arbitrary javascript into my website?! On mobile, I am regularly redirected to annoying ads that proclaim my phone is infected, and make my phone vibrate and make noise. A news article shouldn't be able to do that!
- adventured 9y agoAmazon and Facebook could both launch entirely new browsers. Spotlight it constantly on Amazon.com or across Facebook's properties as with Chrome on Google.com. Facebook already has far more cash and profit than they know what to do with. $38 billion currently, rapidly climbing. They'll add ~$20 billion to that in 2018. They could do a new browser just for kicks if they wanted to, and they have the vast global reach to generate some uptake. Whether either could claw meaningful share away from Chrome is an entirely different question. Samsung, Tencent and Alibaba all have the resources to launch entirely new browsers if it made sense.
- rwmj 9y agoAlibaba already have their own browser of a sort (https://en.wikipedia.org/wiki/UC_Browser https://en.wikipedia.org/wiki/UC_Browser). As I understand it, it's some kind of thin mobile browser which renders on the server side.
- kinlan 9y agoThere are multiple versions of UC browser. My understanding of it is: - uc mobile on Android now uses the blink engine, it used to use Webkit. - uc mini ( I think that's the name) has server renderer but it's "uc engine" is a derivative of gecko (not checked recently)
- nojvek 9y agoHiring talent to build browsers is not as easy as throwing money. The bottleneck is engineers who have the know how to build it. Building your own browser could be a shitty business decision if you can't compete with Chrome for ad dollars. A browser makes sense if you can bundle it with an OS. Android : chrome, ios: safari and Windows: Edge Facebook makes a shit ton of money from ads people click on chrome.
- Mountain_Skies 9y agoAmazon sort of has their own browser called Silk. It's based on Chromium so it's not a built from the ground up endeavor but has been customized on their Fire devices to 'enhance' the browsing experience in a way that seems to benefit Amazon.
- deleted 9y ago[deleted]
- Vinnl 9y agoThe thing is that that, in turn, is somewhat of a reaction to people using native apps instead of the web, creating lock-in for other ecosystems.
- ksec 9y agoSorry if I sounded like a Hardcore Apple Fans, but if there is anything Steve Jobs taught us that lifted Apple from near Bankrupt to the World most valuable company, is that User experience matters. Native Apps provided better UX, easier access on the Home Screen, and is generally 10x faster. What the web responded, or in your words a reaction to people using Native Apps, were to put more Ads, Creepy Ads, more JS tacking, more JS that many had no idea what they were doing, web notification pops up every time you visit a page, mandatory cookies notification, and all sort of other things that makes people no longer wants to consume anything on the Web anymore. I will have to admit, even without those problem it will be a hard battle against Native Apps, but not only are they not improving the web, they are making it worst. A Steve Jobs phase constantly pops up in my head when i see this, "The only problem with Microsoft is they just have no taste." It is true for the majority of the web as well.
- Jyaif 9y agoA couple of things about native iOS apps. These are all a result of Apple controlling the walled garden and wanting to increase its revenue: -Apple limits what your app can do, e.g. apps can't spawn processes (FU Apple, this is bad for security/pricacy), can't do JIT compilation, can't download code, etc... -Apple rejects apps that compete with their own. -Apple removes apps that some governments want to have removed. These are all things an open web avoids. Now the fun thing is that nothing prevents Apple from turning the web into a walled garden since they don't allow any other rendering engine other than their own. The iOS ecosystem is really a beauty.
- inapis 9y agoI really disagree with your argument - > -Apple limits what your app can do, e.g. apps can't spawn processes (FU Apple, this is bad for security/pricacy), What's the issue with that? Why would I want some random no-name devleoper randomly spawning processes on my device killing my battery life? How is it exclusively better for privacy? What prevents them from executing privacy-invading code as the separate process? > can't do JIT compilation, What's the advantage when all the devices, your apps are supposed to be running on, share the same OS, platform, ABI etc? What's the point when the hardware is already limited in scope compared to alternative platforms >can't download code, etc... Again, why would you want some random developer be able to download extra code? What prevents them from not misusing it for nefarious purposes? Even assuming that the developer is not malevolent, what prevents a third-party from compromising the developer's "update" servers and pushing malicious code? >Apple rejects apps that compete with their own. This is from a bygone era. For every native app on my iPhone, I can list an alternative - - Apple Photos -> Google Photos/Plex Photos - iMessage -> Whatsapp, Telegram - Facetime -> Skype, Allo, Duo - Mail -> Outlook, Spark, Airmail - Apple Music -> Spotify, SoundCloud, Wynk, Gaana - iBooks -> Kindle, Blinkist, Kobo - Files/iCloud Drive -> Dropbox, Tresorit, Google Drive - Apple Maps -> Google Maps, Waze - Keychain -> 1password, lastpass, minikeepass - Notes -> Evernote, Simplenote, Bear, Ulysses, Notion - Calendar -> Fantastical, Vantage - Clock/Timer -> Klok, Timeglass - Reminders -> Todoist, Due, Things 3 - Video -> VLC - iTunes U -> Coursera, Udacity - Camera -> Halide, Camera Plus, Retrica - Weather -> Dark Sky, AccuWeather - Podcasts -> Overcasts, Pocket Casts - iTunes Store -> I'm not sure there's a perfect alternative but I can purchase music and movies from non-apple services as long as they provide it (and give apple their cut) - Settings -> Do we even need an alternative? - Voice Memos -> Recordium, Just Press Record - Pages/Numbers/Keynote -> Word/Excel/Powerpoint, Google Sheets/Slides/Docs - Apple Health -> I haven't gone looking for alternative but a lot of apps maintain their own data sources. I'm not sure what really prevents them from sharing data across or maybe they just don't want to? In any case I, sure as hell, trust only Apple with a centralized data source when it comes to my health tracking - iMovie -> Videoshop - Stocks -> Stock Tracker Do I need to go on? Some apps, which are indeed competitors to native apps, have been rejected but "is a competitor" doesn't appear to be the exclusive basis for rejection. >Apple removes apps that some governments want to have removed. True. Agreed > they don't allow any other rendering engine other than their own I am a developer and as much joy it would be to have Blink/V8 running on iOS, I'm totally fine with the decision apple made. In the absence of strong disincentives, companies and developers would try to get away with as much shenanigans as possible. I would absolutely not be happy if Google pushes a battery-killing update. Sure Apple has its fair share of problem but out of all the big tech co's they are, by far, the best when it comes to preserving privacy, security and the least likely to pull shenanigans or gotcha's on their users.
- ggvhbbhh 9y agoCan you stop “talking” “in” “quotes”? It’s extremely annoying. Either own up to what you say, or don’t say anything.
- agumonkey 9y agodillo for static documentation is neat, you can have twenty tabs and still using only 32MB total.
- groovy2shoes 9y ago> What has become quite obvious to me within the past few years is that the whole "move the Web forward" thing seems to be really about coming up with and implementing as many complex features as possible (and advocating for their use in new sites), making it harder over time for smaller efforts at creating independent browsers to produce anything useful. Yeah, it's enough to be infuriating. I've recently been thinking about what it would take to implement a lynx-like browser that had a better understanding of layout and could deal with the modern web. Hurdle number one is that there's no "Web standard", but rather a great many interrelated standards. At a bare minimum, you need HTTP K₁, SSL/TLS K₂, HTML K₃, XHTML, DOM N, CSS K₄, and ECMAScript K₅. Several of those standards are actually multiple standards, so you'll have to do some digging. That's the easiest hurdle to overcome. Number two is that a few of the standards (including some really fundamental ones like the DOM) are maintained as "living documents", making them moving targets; even the—uh—"dead" documents are subject to speedy revisions (for example, there have been 3 new ECMAScript revisions in the last 3 years). Number three is all the up-and-coming experimental stuff that isn't standardized yet, but if at least one browser supports something, some website somewhere is already using it. Between two and three, you'll need to keep a finger on the rapid pulse of the Web. And on top of all that, you have to support legacy bullshit, deal with malformed documents, and be ever hyper-aware of security threats. Allowing for off-the-shelf components like libcurl and duktape, I'm sure it's still doable by a single person, but it's a lot of work (much of it frustrating).
- roca 9y agoThe alternative to a "living document" is "we have a bunch of updates and errata, and you're going to have to piece together the current version yourself from many sources". If you really need an unchanging version, download some version and use that.
- userbinator 9y agoNo, the alternative is a versioned document.
- 9y ago
- sidlls 9y agoI think what you describe is a side effect of the "move the Web forward thing". I see the motivation for moving the Web forward as a cost-savings measure for software developing companies, which they believe will be achieved when "write once, run everywhere" is achieved. This time that particular Holy Grail is thought to be achievable through browser-based development. They essentially want the browser to become something very like a full VM running on a host OS. The natural consequence of this is increasing complexity.
- csallen 9y ago> we should also encourage the use of the "lesser" browsers like Dillo, NetSurf, and all the text-based ones. They can't really run "web apps" and the like, but will be fine for viewing the "long tail" of content-focused sites out there Perhaps this is a knee-jerk reaction on my part, but I'm against initiatives that resist technological progress, including those that rail against modern web applications. Not only do these initiatives seem doomed to lose against the nearly unstoppable forward march of technology, but they are coming at the problem from the wrong direction. If it's too hard for independent efforts to succeed, we should not be fighting in vain to hold back progress. Instead we should be working on efforts to increase the abilities of independent contributors. We should be making it easier for anyone to build a modern browser. That's something that more technologists could actually get behind. Further, while there's nothing wrong with a little nostalgia, let's not forget how far things have come. Many instances of modern web applications are certainly flawed, broken, misguided, overkill. But the web as a platform today is unfathomably better today than it was in the 90s. The applications built on top of it have massively empowered individuals and augmented our productivity. And I'm happy that I can build for the web instead of for Windows. The fact that some websites do a poor job using the new tools available is a small price to pay.
- loup-vaillant 9y ago> I'm against initiatives that resist technological progress I dispute the notion that the evolution of the web is at all progress. It has nice things, but so far the main effects are ever increasing bloat and centralisation. There are simpler ways to do this stuff, we're just too caught up in path dependence to see or invent possible alternatives. > we should be working on efforts to increase the abilities of independent contributors Unless you mean to make them less independent (say by providing common libraries and rendering engines), then the only way forward is to increase everyone's abilities. This is already an ongoing effort, just see how many programming languages and methodologies are popping up every year. > the web as a platform today is unfathomably better today than it was in the 90s The web wasn't even a platform the 90's, of course it's a better platform now. However, it only became a platform by accident. This reminds me of C++'s accidentally Turing complete templates, which later spawned template meta-programming madness. If a platform was design from the ground up as a platform, it would all be much simpler, perhaps even more capable. But no, we had to piggy back on whatever the market favoured at the time. --- Here's what I think: a web-ish platform written today wouln't need more than 0.1% of Firefox's 35 million lines of code, or about 30 thousand lines. Or maybe 10 times that amount, to account for optimisation and long tail functionalities —that's still under 1%. This even has been done. The STEPS projects at http://vpri.org http://vpri.org is only 20K lines, including the compiler collection and editing tools. It even runs at acceptable speeds on a laptop. That would be progress. That would spur the independence of contributors. Too bad the market just isn't ready for this. It probably never will be.
- dingaling 9y agoBrowsers like Dillo and Netsurf are also excellent for browsing Facebook, who maintain a remarkably functional HTML-only version at mbasic.Facebook.com The big advantage of such browsers being the zero-risk of JavaScript doing sneaky things ( like keylogging )
- danblick 9y agoYeah, "moving the web forward" sounds a lot like building barriers to entry. On the other hand, these browsers are open source software, so I'm not sure that's a great argument.