1,665 karma · joined April 21, 2010
Just an anecdote: my grandmother was born as Sámi, so I could officially have the Sámi status as well (but my kids not anymore), although I don't speak the language nor have much connections with the culture.
Which "Linux" desktop are you referring to?
That's basically what happens in private mode (incognito), I guess. Would be nice if browsers used private mode by default, and you could "whitelist" certain sites you trust / want to remember your login.
Also, having too many extensions slows down the browser (because they need to parse/manipulate DOM) and extensions themselves are also a security/privacy risk and finding the good ones for every browser can be tedious.
Besides, my mom has no idea what's "a browser extension".
The naivety of this approach almost makes me laugh. I mean, it's good intention, but really we cannot just trust the "bad" party. Active client-side measures are needed (e.g. as Safari does).
(From a hobby perspective it's a bit sad that some of the older APIs such as dispmanx/openvg are being phased out IIRC, because those are extremely powerful and useful for embedded-style applications, i.e. running something else than a destop.)
It's high-quality time for you & kids (no screens!), and also teaches the kids to think complex sequences (or combinations of the future) in their mind, and patience in general.
That's a valid point!
It was one-off project for dedicated purpose, not a desktop replacement, but I will probably build another one and see if it's any usable as an actual workstation, because I merely need anything else than browser & terminals. (Well, probably also a dedicated headless server running docker for heavier stuff.)
(Context: I've been a die-hard Mac user since 2006, when I ditched Linux desktop, which I had used exclusively since 1998.)
The fact that there are "JS land" and "CSS land" is one of the problems. There should be better integration between the two, eliminating the need for "hacks" such as replacing stylesheets by JS styling (popular with React, for example). Writing variable-based dynamic CSS is too hard. SASS and other variants don't solve the problem because they are compile-time, not runtime technologies.
But, often the problems are also non-trivial. The web platform is really diversed, there are user-agents everywhere from mobile phone to smart tv and everything between, with extremely varying input methods (touch, mouse, etc), resolutions, pixel densities, performance, etc. Some of the devices are never updated, running a decade old browser. I don't think any other technology faces similar challenges. Actually it's amazing that things work as good as they do.
Oh? There are the old-school e.offset{Top,Right,Bottom,Left} etc methods for measuring the DOM stuff, and there's Visual Viewport API (experimental) for more advanced use cases:
https://developer.mozilla.org/en-US/docs/Web/API/Visual_View...
CSS transforms are really just an visual effect, not affecting the layout. That's why they are super fast (typically HW accelerated by GPU), but not suitable for defining the layout.
Managing the DOM in JS may be order of magnitude slower but is still fast enough, actually surprisingly fast. It's common to implement 60 FPS animations e.g. in React. Of course the performance heavily depends whether the manipulation causes a layout reflow etc, but generally speaking, DOM is pretty fast nowadays, and most sites/apps are not _that_ performance critical (such as games). Yes, it's not uncommon either that a complex JS app becomes slow, but that's mostly because of inefficient programming / generally bloated app, not because the layout is done by JS instead of pure CSS.
Browsers already have "alternative" APIs to make totally non-DOM interfaces, such as canvas (2D) and WebGL (3d). Nothing prevents to come up with alternative layout/UI libraries written on top of them. I'm sure such a libraries exist. Why it's really rare to utilize non-DOM UIs is probably due to many reasons, i.e. compatibility issues with exotic/older user-agents, devs being more familiar with DOM based solutions, etc.
After all, I think DOM works pretty well even for app-style UIs. Actually, many "native" technologies don't offer as easy responsive layouts, user-settable font-size, etc, which comes almost for free with DOM. There's lof of beauty in the DOM, despite its document-oriented origins.
(Oh, I just typed out some mind flow of mine, maybe a bit off-topic.)
There could be a standard header such as cookie-privacy-policy which would point to url containing the policy in standadrd format (html?) and the browser could show it in standard way (by user's settings). Personally I would be happy with just a little "privacy policy" icon in url bar, similar to https lock icon and reader view icon (in Safari).
The real problem of course is that the web specs itself have become too complex and expensive to implement. But a stripped-down version of browser could point out why we need to reboot the whole technology. It would be a long shot, I admit.
Battery life has always been very top priority for Apple. That's the reason why Apple stopped supporting Flash and basically killed it (thank gosh).
Built on top of KHTML foundation, it then became webkit and later the most successfull engine. It was the first to implement full ES6 support, and basically invented CSS transformations/transitions (really amazing stuff back then but not really used until all major browsers caught up years later), was the first to ditch Flash support, has argueably the best privacy policy, has superb font rendering, etc.
That being said, English is already unofficial common language between most Europeans. E.g. it's very common for Finns and Swedes to communicate in English, despite Swedish being one the official(!) languages in Finland (also taught in elementary school), simply because many Finns have much stronger English than Swedish skills (and Swedes speak typically more neutral (clear) English than native speakers).
Actually, because English is native language only in UK, that makes it excellent lingua franca for the rest: when both parties speak it as 2nd langauge, the communication is more easily kept in the same level (i.e. not speaking too fast, using exotic words, etc).
That's just how the world works nowadays, e.g. in tech English vocabulary is extremely pervasive. Even in Finnish every-day talk in tech related areas we often use direct loan words from English ("Finglish").
Personally I think the only downside of English is its irregular prononcing, i.e. relatively weak correlation between written and spoken language.