In GrapheneOS, che vuol dire esattamente che le Google Apps sono "sandboxes"?
Uncategorized
1
Posts
1
Posters
11
Views
-
In GrapheneOS, che vuol dire esattamente che le Google Apps sono "sandboxes"? Per avere efficacia devo per forza creare dei profili diversi in cui relegare le applicazioni che per funzionare hanno bisogno dei servizi Google per preservare la privacy e non regalare i miei dati? Che differenza hanno con le MicroG? #mastoaiuto
-
undefined alsivx@livellosegreto.it shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@Uilebheist @muffa @NicholasLaney @leodurruti subacquei
-
@genehack @ludicity the good news is there's very little shit in Go, IMHO. It's a simple-ish language missing some fancy features, but it's not missing anything I really feel the loss of, especially for the simple problems I'm making web apps for.
Of course, as much as I like it, I'm not using it for anything other than web stuff. Even my current large-ish Go project has as much Python for the data import tools, just because it was easier to write and deploy/performance don't matter.
-
@genehack @ludicity I'm willing to believe it, but I've struggled quite a bit with Rust. To be fair to Rust, I've been dealing with it in a desktop app context, and I may have made poor choices (I switched from Qt to Slint for a C++ app because I thought maybe it'd be nicer to build and package, but Slint is also a nightmare). I've never built a web app in Rust, but maybe I'll give it a go at some point. The build times are pretty gnarly though. Go builds much faster than most Node.js apps.
-
@swelljoe @ludicity all that said, yes, if deployment process was a primary concern (and ...when is it not?), I would put up with a moderate to large amount of shite to get Go's deployment story.
-
@swelljoe @ludicity to be fair, Rust kinda has this same deployment story. I agree it's a huge selling point, but also, if you're deploying true lambdas to AWS, you also kinda get this for any supported runtime? (N.b., not "run a container as a lambda", like ...actual old school Lambdas.)
-
@ludicity it's just a bonus that it's an order of magnitude faster, has a standard library that's so good you barely need anything else (and what you do bring in from third party libs is mostly made by grownups who write clear, concise, no bullshit, code), and has a memory footprint that's dramatically smaller.
It's such a low bullshit language, I can't imagine using anything else for web services and web app backends.
-
@liberotoncello premetto che pur auspicando un boicottaggio USA, io voglio mollare WA per il suo disprezzo per la privacy. Signal è americano, ma ciò non toglie che al momento sia il miglior compromesso, perchè serve a poco avere un'App super etica se poi non la usa nessuno.
Consiglio alcune letture
https://www.lealternative.net/2025/04/08/perche-usare-signal-al-posto-di-whatsapp/
https://aboutsignal.com/it/blog/critiche-di-signal-e-come-signal-risponde/
Evidenzio in foto un passaggio
-
@ludicity deploying large mostly Python (but also Node.js, and others) apps in a ridiculous variety of places has been a huge part of my job for the past...well, forever, and I'm really good at it. I'm the person everyone asks for help when they can't make it work and when ChatGPT can't make it work.
All of my web projects for the past two years or so are in Go, and I'm slowly migrating old stuff to Go, too. The deployment story alone is enough to make it worth the effort.
