> for example allowing to specify environment variables in manifest.scm files.
There is already .envrc or .dir-locals.el? And manifest is just - well - manifest. By definition it has to be 'plain'. I mean, there are already a million ways to load env vars so why'd you want guix to do that too and from manifest.scm of all places?
Because instead of distributing two files (channels.scm and manifest.scm, or flake.lock and flake.nix), you have to execute monstruosities like `guix shell --container -m ./manifest.scm -- bash -c 'GUIX_LOCPATH=$GUIX_ENVIRONMENT/lib/locale LC_ALL=fr_FR.utf-8 exec jekyll build'`, which is how I build some websites I have.
To me, that's not ok from an user experience point of view.
not do the job for you? (For a single development command—for deploy 'nix build' should be set up to do the right thing, including setting LC_ALL if necessary; and to enter a dev shell just 'nix develop' should work. Nixpkgs installs glibc with a full complement of locales by default, which has its downsides size-wise but should prevent any troubles when setting LC_ALL=fr_FR.)
Or, for an automatic setup,
cat > .envrc
use flake
^D
or, for an automatic setup with caching[1],
cat > .envrc
if ! has nix_direnv_version || ! nix_direnv_version 2.2.0; then
source_url "https://raw.githubusercontent.com/nix-community/nix-direnv/2.2.0/direnvrc" "sha256-5EwyKnkJNQeXrRkYbwwRBcXbibosCJqyIUuz9Xq+LRc="
fi
use flake
^D
(I don't have nix-direnv installed systemwide because it ignores the --no-write-lock-file flag I need to pass sometimes. If you put some of your config in default.nix or shell.nix or whatever, you’ll need to watch_file resp. nix_direnv_watch_file those.)
Probably means "our laptops only run Windows, which infamously has performance issues with git because of different filesystem semantics (something about caching metadata?), but Linux filesystem drivers don't have that problem".
That's fair, I would recommend a MacBook, Chromebook or iPad to senior folks, even though I loathe the companies, they're perfectly fine for those who do not want to tinker.
Sure. We'll just believe that ProtonMail locks accounts randomly, for no reason. Or was spam the reason? If that was true, everyone would be locked out because, well, everyone is getting spam.
A quick Google search returns tons of results from ProtonMail's subreddit of people complaining that ProtonMail locked them out of their account for unknown random reasons.
The post you've linked doesn't say that it was some unknown/random reason just the fact that the person is locked out of the account, not that the account itself is locked, which may be for variety of reasons(losing 2FA, forgetting password, else?). It's more about that support is slow. The person reached out and the issue was eventually resolved.
> The post you've linked doesn't say that it was some unknown/random reason just the fact that the person is locked out of the account, (...)
Fair enough. You can google though. There's a wealth of complains of people seeing their accounts locked.
If you don't have time to run a Google search, you are free to read ProtonMail's own docs, specially how they describe how they lock accounts based on heuristics and how they recognize the occurrence of false positives.
Trying to contact support? Their response? Ultimately figuring out the real reason? When faced with an issue I usually try to figure it out first. After all, accounts can get flagged wrongly on outlook, gmail and other services as well. And the linked reddit thread does not relate to your case. To me, the very theory of account locked just because someone sends a spam email to said account is, honestly, ridiculous.
> They are by a long way the worst experience I ever had with a provider of any online service, so much so that I’ve since moved my own e-mail that was there back to outlook before some arbitrary spam caused the same thing to happen to me.
Well, I misunderstood you here. Wrongly assumed you meant it happened to you again.
I contacted support, but they simply refused to assist at all.
The account was just.. gone. That's what was so shocking about it - I realised pretty much immediately at the time that there would be no way to recourse a locked account because any means by which you could prove the account would be yours (other than having the password, which we still did, but which was not acceptable to unlock the account according to PM) is inside the inbox itself. More than that - they weren't asking for more information. They simply said it was permanently locked and nothing could be done.
This has happened to others too, as has been posted elsewhere in the thread.
Yeah, I get it. ProtonMail bad. I'm glad that your Gmails and Outlooks still work. Thumbs up. I'm also glad you've created this account just to reply to me, really honored.
You're being really dismissive here - no-one's saying PM bad/others good. I was pointing out an experience with ProtonMail and others have corroborated with their own experience.
All of that said, if it says nothing else it at least suggests that larger providers seem to have a better grasp of how catastrophic being locked out of one's own e-mail can be - PM really don't seem to understand the responsibility they bear being a provider of such critical infrastructure. If this were happening in this same way at larger providers like Google and Microsoft, I'm quite certain there would be heavy regulations by now.
Making an account is really quick, no need to feel honored by such simple act. It's basic privacy - don't keep your identities too long, especially if you're going to tie them to the set of services you're using.
Yes, we will, since it happened to others of us. What kind of evidence would you like? My account is inaccessible. Should I tell you the password so you can try yourself or what?
> I can use Nix at work, at home, with family, with vendors, with binary blobs, on macOS.
I'm using Guix for work, at home, my wife has Guix on her gaming laptop with nvidia card, playing games on steam.
Nobody has any problems with enabling rpmfusion repo on Fedora, using aur on Arch, adding backports repo for kde or whatever on ubuntu. But as soon as it's nonguix channel it's suddenly a problem. Huh. It's literally just a channel and ultimately it is still same Guix.
"What's that? NONGUIX? Hell no, I ain't having Guix working on my hardware! I don't want a better experience using Guix! Not in a million years!"
And then:
> Guix has truly noble goals (in classic GNU fashion) but they're ultimately misguided.
> Actually useless.
Which are really big claims with nothing to back them up.
> The standard encouraged response to "Hi I'm a new Guix user and I was wondering how I can run steam?" is roughly equivalent to "Go fuck yourself" and I'm just amazed by that.
Look, if you can't figure out how to `guix install flatpak' and then flatpak install com.valvesoftware.Steam, then... well, I've nothing to say actually.
That's definitely better than "go fuck yourself". "If you don't have something nice to say, don't say anything at all" and all that.
Tbh, I've seen the "go fuck yourself" attitude in almost every Free Software community I've spent time around. It's really just a matter of whether it's encouraged, tolerated, or actively rejected by the project maintainers and influencers.
I would hope that someone writing a blog post this positive would be one of the "actively rejecting" folks, but I really don't know anything about Guix (hadn't heard of it until this post).
I will say that I run NixOS on my primary home server, and while there's definitely a learning curve there, the community I've experienced is largely very helpful, friendly, and positive. Now that I've got most of it working the way I want, I don't see myself moving to something else any time soon (it's absolutely rock solid).
If you've turned to a system based on everything being perfectly declarative and reproducible, why would you then add an imperative autoupdating system on top of that? Of course you can, but if you're fine with that kind of system, why would you have turned to guix in the first place? It's not like it's just the popular default and you want to do something else on top, it's a super niche thing based specifically around this and you're breaking the core philosophy
The OS is called "Guix System". Without the system part it's just "Guix".
Both variants are very similar. The Guix tool comes with a "guix system" command, which lets you build Guix System containers, container images, system images, qemu VM images, qemu VM scripts, etc. The only command that won't work on a "foreign" distro is "guix system reconfigure" --- but that's only a "guix system init /" away ;)
There is already .envrc or .dir-locals.el? And manifest is just - well - manifest. By definition it has to be 'plain'. I mean, there are already a million ways to load env vars so why'd you want guix to do that too and from manifest.scm of all places?