I often hear the argument of savings in printing and postage.
Having seen all the over budget, years delayed or completely failed IT projects in the public sector, I wonder whether there are any savings at all in the end.
(Perspective from a couple of EU countries at different degrees of digitalization)
While composing a reply to recipient B leaking some details that it "learned" when reading a mail from sender A, which you did not want to share with B. I have no idea how they organize sessions, indexes and whatever they use. But if no "side-channels" existed, I would be extremely surprised.
Of course reading generated text remains the sole responsibility of the user before clicking "Send". We all know that reading drafts can happen more or less carefully, especially when being in a hurry.
There is no reason kids should use so called smart devices, except making certain companies richer. Kids have had a healthy development without such crap for thousands of years. We don't discuss what percentage of alcohol should be allowed in beer and wine for kids.
Except from being cool, we can do it, are there any benefits? Benefits for me would be avoiding interactions with the oligarchies and generally executing code on my machine that I don't need to consume Web content.
Hello. This is a bridge that connects Emacs to modern usage of the http protocol, for better or worse.
It makes your chromium experience programmatic, via the Emacs + CDP integration, now you can use a project like this to automate chromium with an Emacs user-friendly human interaction layer.
Sounds like a bunch of words. Here's a real example:
We added yesterday a gpg based password manager vault feature that is emacs-native: it pulls a password out from some local vault file and can inject it straight to a a web form.
That's just a simple example. But for someone who would prefer not to keep all their logins and passwords in a cloud. And for someone who uses and enjoys Emacs. But wants to have a modern browser controlled by Emacs, with all the familiar Emacs binds working the same in the Chromium. It might make sense. :)
One flow I'm considering, is making eww the default browser, to stay pure and text-based in my day to day, code documentation and simple html-only websites etc. all tends to work very well with eww.
And then connecting eww's fallback browser button '&' to this embr project. Then when eww is not capable to do what I need it, use this headless chromium approach.
Then at this point, I dont even need to install firefox or chromium or anything as a system package, and while it "still sucks" at least my browser experience is contained and minimized to a self-contained headless chromium, and i get to control it with Emacs keys.
It feels like a win to me. That's my mindset while putting this all together. And it's also why I used as many eww keybinds as I could for embr.
I don't like snap and have always uninstalled it in the past. However, that gets more difficult in newer releases, so probably not a sustainable path. Still searching for the distro I could install instead of Xubuntu for friends and family who don't want or need the latest and greatest.
The main reason for my dislike is the closed source nature of snap distribution.
App isolation is important and not easy. That bugs will happen and be fixed there is natural. Happens with every other system that was supposed to increase security, too.
Me too. Switching my home system from Ubuntu back to Debian was influenced a lot by snap. I don't get how they could fumble that one so hard. It goes against everything they used to stand for. If I want a bloated, slow, closed-source, proprietary app store with unclear security ramifications, I'll install MacOS or Windows. It also feels like app developers at least care a little bit about those stores. Mozilla for example still officially recommends installing their Debian package rather than through snap on Linux, despite shipping via snap by default on Ubuntu now.
Pop!_OS is basically Ubuntu without snap. Debian is fine, but for some reason it is ugly. Like, you can style and configure it with a thousand options, but simply fails to have a nice theme and UI out of the box.
I love multipass. It is a simple no BS virtualization solution and probably the best thing to come out of Ubuntu after LXD.
But I can't use it. You know why? Because despite being open source Canonical wont tell you how to compile it and install it as a standalone program. Instead all their documentation says "install via snap"... even if your are on fedora or debian or arch:
I think pointing end users to use the end user packaged app is fine, as is to trust people who are comfortable with building from source to find the build docs from the repo.
I worked in a company where reviews took days. The CTO complained a lot about the speed, but we had decent code quality.
Now I work at a company where reviews take minutes. We have 5 lines of technical debt per 3 lines of code written. We spend months to work on complicated bugs that have made it to production.
Having seen all the over budget, years delayed or completely failed IT projects in the public sector, I wonder whether there are any savings at all in the end.
(Perspective from a couple of EU countries at different degrees of digitalization)
reply