The majority of GDPR fines are avoidable, if the websites would just use GDPR-compatible tracking banners, but they decided to break the law => Consequences
1,264 karma · joined February 23, 2021
The majority of GDPR fines are avoidable, if the websites would just use GDPR-compatible tracking banners, but they decided to break the law => Consequences
This should be enough to render text-based sites. E.g. HN or news sites. But the reality is, that basically no side is able besides HN is usable at that internet speed. Soo much content out there could be accessible at that speed. Sure no videos or images. But everything text based should still work.
There are probably a lot of tools in the webdev-toolbelt that would allow to allow even e.g. image heavy news-sites to be usable during images and scripts load.
I frankly haven't found an ecosystem in which I feel more comfortable than the one from C.
Yes, C has its vulnerabilities, but for my own projects I do in my own time, I will use any language I have fun with, even if it has huge problems.
Another pro is that I can use git for tracking changes
I think it is the fault of the network stack of one those two devices, otherwise I can't explain that. Maybe that the devices receive/send data faster than they are able to process. (Is this even possible?)
But I could be awfully wrong
Regarding your edit: That's a good idea, but I never attempted that. I can't test that, because I'm in a Wifi where no device is allowed to talk to another :(
I agree with your comment, except here: Doing layout in GTK is much easier than using HTML. Especially using Blueprint[0] you don't even have to touch .ui files. And constructing the GUI using code is possible, too.
At least the few things I did in HTML were a lot more difficult than they would have been in GTK.
- Static linking of everything
- Big dependency trees that somehow remind me of npm
- Slow compilation, it should reach at least the average speed of C compilation
- Big binaries because of static linking
Before this is solved, I frankly wouldn't even consider touching rust again for personal projects, did it once, and it was an awful experience with too long compile times, as my style of development depends on fast compile-run-test cycles and having to wait around a minute to recompile for a small program is just too much.
I used it in school for making a game during my A-Levels for my scientific seminar (W-Seminar in german). While the concept is good, the editor is really not that good for anything bigger. You e.g. have no package support in Greenfoot (Or I was not able to find it), and e.g. if you restart a so called "scenario", the JVM does not get reset. Sure I did maybe go to the limits of Greenfoot with my game, but nevertheless it was really fun to work with
The Linux from "Linux Smartphones" e.g. fosters an open, user-first ecosystem, as opposed to the often very closed and locked Android Smartphones. Another examples are e.g. Safetynet or the Google Play Integrity API. Those primarily don't server the users. Or apps that either complain or even stop working on rooted phones. We have admin/root on normal PCs and nobody is complaining there.
Discord was - last time I used it on the desktop - awfully sluggish and basically even worse than in a browser.
We can just extend it to non-electron toolkits (E.g. Java Swing):
- Splash screen (E.g. I've rarely/never seen a native Libadwaita/GTK program that used one, they may exist, but are really rare in the linux world, examples: Teams, Mediathekview)
- Custom notifications (E.g. in teams, if you download a file, you get undismissable - at least for me ^^ - notifications that stay always on top)
- Weird custom things (E.g. Teams draws on close and minify buttons, that makes no sense)
- Order of the buttons in e.g. boxes (Is it Yes-No or No-Yes?)
That's how I measure "native-ness"
I never found an electron application that was even remotely "decent" or "native". The best one I used was Element (Matrix), any other way somewhere between "somewhat usable, but not good" (Webex) and "mv program /dev/null" (Teams)
The only way to get a good native experience, is to write native apps, using the native Toolkit.
Faster compiler than rust, smaller binaries, easier syntax, good GUI as defacto library (GTK)
With a bit of luck, this will cause site operators to reduce their usage of unnecessary JS, so maybe this has positive impacts :)
That is not true. WebKit is opensource, there are other browsers that use it (GNOME Web), it is used in a lot of other applications, like GNOME Builder, Devhelp.
Yes, opening browser engines would be good for the competition. But you missed one point: You assume all players will play fair in the competition. If all browser engines would be allowed over night, what would happen: Google will probably play really unfair. E.g. sadly the layout of Google will be messed up in Safari, youtube videos stutter/have lower resolution, everything is a lot slower, the performance will be sabotaged, but on Chrome everything will be working fine. There was even a precedent for something similar: [1]
This will probably come alongside with "Try it in Google Chrome", a lot of users would probably switch, thus the monopoly of Chromium would be unstoppable by pure market forces.
Yes, having only one browser engine is bad for the choice of the user, but it does have significant downsides.
Damned, if you do, damned if you don't
[1]: https://www.theverge.com/2019/5/4/18529381/google-youtube-in...
Simply make the DNT-Header a legally binding thing. If the user sends it, it means that only technically necessary cookies can be used.
This would require no UX from the side of the website, thus defeating all dark patterns at once
Is it possible to use TabNine without using the random executable from https://update.tabnine.com/3.2.28/x86_64-unknown-linux-musl/... (Or is there the source available?)
Are there any instructions on to make it work with any other editor (GNOME-Builder in my case)? Is there Vala support?
Edit: Found this: https://github.com/codota/TabNine/blob/master/HowToWriteACli...