8 ms·
"cross-platform compatibility" isn't guaranteed on the web either, yet somehow "cross-platform compatible" websites exist. It isn't a problem that's so difficu
by krapp 5y ago
"cross-platform compatibility" isn't guaranteed on the web either, yet somehow "cross-platform compatible" websites exist.
It isn't a problem that's so difficult it requires wrapping a 60Mb runtime around every individual app instance.
- kitsunesoba 5y agoI’ve always felt that engine inconsistencies in electron-alikes are a bit overblown, particularly now with the old IE-based webview out of the picture (modern Windows uses a Blink-based webview). They’re all capable of the basics, and the greatest inconsistencies will be found in newer features. Stick to a slightly older well supported set of features and you’ll be fine. There are some significant differences between engines when it comes to things like local file access, but that’s what the native component of electron/tauri/etc is there for.
- awestroke 5y agoEveryone is basically using Chrome or Safari nowadays - so WebKit. Very little incompatibilities to consider compared to writing something that works on different WebView implementations
- ben-schaaf 5y agoWebKit and Blink have many significant differences, especially when it comes to supporting newer features. In terms of incompatibilities they're about as different as Gecko is from Blink, if not more so.
- capableweb 5y agoNot sure how familiar you are with the history of browser engines, but Blink and WebKit are definitely more similar than Gecko and Blink. Gecko comes from the heritage of Netscape. Blink comes from the chain of KHTML > WebKit WebCore. They don't share any points, while Blink probably wouldn't have existed without WebKit. But yes, today there are differences between WebKit and Blink.
- lillecarl 5y ago"In terms of incompatibilities they're about as different as Gecko is from Blink, if not more so." > Not sure how familiar you are with the history of browser engines, but Blink and WebKit are definitely more similar than Gecko and Blink. I see we interpreted parent poster differently, he wasn't talking about the history of rendering engines, but rather compability with the various web specs. Since Chrome forked WebKit quite a long time ago now and Blink has been reworked quite a bit they have deviated from eachothers implementations. Since everyone is trying to follow an open spec it might be that in certain areas FF and Chrome implement more of the same API's than Safari, which doesn't have anything to do with codebase history. You might and probably will feel more comfortable in the WebKit codebase if you're a Blink developer or vice versa in comparision to Gecko, but that is if you're writing the engine itself and not pressing the pedals (targeting it).
- elpescado 5y ago> as different as Gecko is from Blink As someone who has been playing with some web dev in early 2000s, that sounds funny. Gecko, WebKit and Blink seem very consistent to me. I remember dealing incompatibilities between IE6 and "standards-compliant" browsers (mainly Firefox/Mozilla Suite back then). And don't get me started on dealing with "classic" Netscape! `<layer>` tag anyone?
- Semaphor 5y agoLuckily, that is not the case. In Germany, FF still has 20% on Desktop and 10% total (and I wonder if those numbers are maybe too low, as FF blocks those trackers by default).
- gefhfffh 5y agoThat means that there are about 8 million people using Firefox in Germany. The world has more than 3 billion internet users
- jcelerier 5y agoI don't understand why this relative metric matters. Past the size of a small city it just shouldn't matter how many more users the competition have. There are more firefox users today (~200M) than there were total internet users in 1998 (~150M), and surely you would agree that it does not make sense to discard that, any more than it makes sense to discard, say, UK or France from diplomatic relationships because they have ~70M inhabitants while India and China account for almost 3 billion.
- gefhfffh 5y agoHmm it matters because when everyone basically uses competition, it doesn't matter if a few people use something else
- brnt 5y agoJust because only 17M people live in the Netherlands, does not mean it's OK to block them. Just because people in wheelchairs don't wall, does not mean we don't need to build streets such they can get around too. Just because some people use the Greek script, does not mean ASCII is enough. It's called accessibility, and it's a very good thing.
- gefhfffh 5y agoYou are arguing against a straw man
- roblabla 5y agoWebKit, WebKitGTK and WebView2 are all webkit-based too currently. WebView2 was always chromium-based afaict, I think the old trident-based edge had a separate control. Also, on the web, firefox still exists.
- sanxiyn 5y agoSorry, I am using Firefox.
- FooBarWidget 5y agoI'm not sure why downvoting is needed. What's said is true: on the web we already have to deal with different browsers and versions. It should be a fact of life for web developers. And things today are still infinitely better than back in the IE 6 days: many modern features work on all major targets. Why do people insist so much on engine consistency for "desktop web apps"?
- schwartzworld 5y agoMost cross compatibility issues have been resolved in browsers. Firefox and Chrome are pretty much at parity, Edge is chrome and Safari is the exception. Web views are less standardized though and require more finesse.
- dmitriid 5y ago> Firefox and Chrome are pretty much at parity, Edge is chrome and Safari is the exception. Firefox and Safari are very much at parity. Chrome ships ~40-70 new "standard" APIs every month or so: https://web-confluence.appspot.com/#!/confluence https://web-confluence.appspot.com/#!/confluence
- tekknik 5y agoIn my experience it’s Chrome that does weird things. I write for Safari and it works great in FF. Chrome and Edge will require some tweaking of CSS to make it look correct.
- wokwokwok 5y agoI mean… fair, but is the 60MB runtime the issue? I really don’t care if my hello world UI is 60MB to download, I care that it consumes 1 GB of my precious ram to run. How is running js with a rust backend any better than running js with a C++ backend? I guess your “backend” is rust here, which is nice (because I <3 rust), but tell me this won’t sit there guzzling all the memory it can get it’s hands on for the UI? Ie. really, do you get meaningful benefits from using this over say, literally just using https://github.com/webview/webview https://github.com/webview/webview?
- jraph 5y agoOne can hope that the code of the engine will be shared across apps in memory, thanks to shared libraries, and that the engine itself will use shared things too, by virtue of being distributed with the OS. ... if you happen to run other browsers and apps using this WebKit / libwebkitgtk / webview. and that embedded apps won't be obese frontend code with bazillion npm dependencies and a heavy, all too widespread framework, of course. Hopefully, developers turning to Tauri will have some sensibility to lightness.
- nine_k 5y agoThe code size is usually epsilon compared to the amounts that the JS heap, DOM, and JIT consume. These are not shareable.
- rebolek 5y ago> I really don’t care if my hello world UI is 60MB to download lot of people cares, they may have a slow connection, must pay per MB and so on. There is no reason why hello world UI should be 60MB.
- heurisko 5y agoI can remember using 56k dialup and downloading ISOs around 650MB. A 60MB download would have been fine. Indeed, with the annoying habit of proprietary software to install "Download managers" that download the actual software, I would be happy for just a 60MB runtime for the actual program itself.
- usrusr 5y agoYeah, and large fraction of the dev appeal of Electron is that a concern that has haunted web development for a quarter of a century is completely out of the picture when you do Electron. You're not even concerned with possible differences between past, present and future versions of the engine because your code runs with exactly the version you bundled. Sure, if your app is just a faux-native variant of something that is developed for the browser anyways nothing is lost, but if it's an offline first application that just happens to use web tech for UI the difference is huge.
- fragmede 5y agoChrome is the new IE6, and guarantees cross platform compatibility everywhere it uses its own renderer though. (Basically !iOS.) It's a strong reason for choosing to Electron for your "native" app.
- pjmlp 5y agoNice IE reference, helping Google to spread ChromeOS is exactly one reason not to package Electron everywhere, besides the bloat to have multiple copies.