Using Sailfish OS is just trading Android for another proprietary OS. Why even bother going to all that effort and still end up back in the same place?
We have real mobile linux distros like postmarket OS and actual open source desktop environments like Phosh or plasma/gnome mobile.
Hell yeah. Next, they can get a cut of every dollar made! Or a subscription service with strict usage limits and add-ons to re-enable disabled functionality. It's one or the other.
Well damn, I wouldn't have expected that average arch users needed to know how to assess pkgbuilds given how enthusiastically arch users have been trying to sell the distro to first time linux users and other newbies.
Is thr solution truly to tell people to read the build instructions and decide if a package is safe? I'm not an arch user, but I've used nixos and assessing nixpkg before installation gets old real quick real fast. Somehow I really doubt telling an average user to assessing pkgbuild on their own will be very effective.
Graphene is insanely good. It's even better than classic custom roms, since you can actually easily install google play. I'm avoiding Google's stupid crackdowns, getting additional security, all while having most of my stuff still work.
Most apps just work. My games and paid apps still work. Google wallet doesn't work, but I just used my physical cards. McDonald's app doesn't work, but that might've been a benefit to my health.
Overall, couldn't believe a security focused product had such good usability.
Do your todo apps, sudoku solver etc. Simple problems are fine. Don't look down on them, don't tell yourself that they're too simple for you. There is always more complexity that you first expect once you start tackling it seriously.
Also, every self respecting tutorial ought to have exercises after every chapter. Don't skip them either.
It's a possibility with chromebooks because of the google ad network, but I can't see why consoles, linux, mac, even windows tbh, has any incentive to support this. At best, they might make it an option, but there's nothing in it for them. It actively makes their content look worse, while an ad supported OS like windows already has capability to place ads anyway.
Of course this is just a theoretical exercise. Technically, there's nothing in a QR code's algorithm or the mathematics that prevents it from scaling infinitely. The error correction algorithm even allows up to 30% of the code to be damaged and still retrieve the data.
Practically though.. Well, given the QR code is smaller than bacteria, paper looks more like a tangled forrest of plant fibers at that scale. Paper just doesn't support that kind of resolution.
However, I'm inclined to believe humanity can print that QR code on silicon wafers like we do with chips.
I assume you could deactivate an account without pruning if the account is legitimately human, just a very obnoxious one?
No way it's C. The average student will go home and find that they can't do much of anything they like, with the level of C they know. Even printing a string is famously hard in C, they'll hate it. Nothing drains their interest in programming faster than segfaults.
The average students wants to build games, websites, discord bots etc. Javascript makes it easy, none are easy in C.
My personal rule of thumb is that if it interacts with the OS or filesystem deeply, native is probably better. E.g. IDEs, cli programs, browsers, Steam etc.
Apps that do a simple things are likely to work perfectly fine on flatpak.
But the problem is that there are outliers in each case. You should pick one and be ready to switch if things don't work properly.