I live in the Netherlands
I live in the Netherlands
For me it’s not the time spent at the checkout that matters, it’s the time spent waiting at the checkout. Also over here cashiers don’t bag your items for you, so you have to do that anyway
Also also, they have these really handy hand scanners over here so I can already bag my items while I’m walking through the store, and then the only thing I have to do at self-checkout is hand in the scanner and pay for the groceries. That is genuinely a lot faster than normal cash register shenanigans.
As a nix user, guix looks legit nice but it took me until 2 days ago to actually find community projects made for guix(https://whereis.みんな/) . Sometimes I just wish they used the same store and daemon as nix so that nix packages can work as guix dependencies and vice versa.
(Also major thing stopping me from using guix is I don’t get service types at all, let alone how you’d define your own service :( )
What are you on about? The open letter was specifically advocating against sponsorships and advertisements of the Military Industrial Complex. I.E. private companies who specifically try to turn a profit from countries going to war. Companies that literally earn money over people’s dead bodies. I think the people that wrote the open letter were very aware that being sponsored by the military was something that is hard to avoid. However there is a clear difference between being sponsored by a military and being sponsored by, like, literal death merchants
Hate to be that guy, but all those articles are 5 years or older. Have people had more recent complaints about systemd or did that movement that complains about it kinda move on?
Would it be fair to say that Neovim attempted with Lua to bridge that gap and also make it a lot more accessible?
I think so? Tbh I’m not very involved in the modern version of neovim but I don’t disagree with them moving to lua
I don’t think you did, but I’m already aware. I even have some concerns regarding its sandbox 😅. Would you happen to know more regarding this?
EWW (short for Emacs Web Wowser) is very basic, only really working with the HTML and not so much the css, and definitely not JavaScript. Don’t expect anything fancier than a blog post to work :P
Would you happen to know to what that is attributable?
Not sure but I suspect it’s 2 things:
So people have a need to change their editor, and a good configuration language to do it in. Moreover, emacs secretly comes with a bunch of built-in features, not enabled by default. It also helps that emacs is not terminal-based, allowing users to do stuff in emacs that you aren’t able to do in a normal terminal (like viewing images, or searching for images on the web. Did I already say that emacs has a built-in (primitive) web browser?) and generally means that emacs users “live” in emacs, as they already have access to so many features.
If you compare this to vim
Did I understand you correct in that customizing Spacemacs is a completely different beast?
Correct.
So knowledge acquired related to it doesn’t translate well to Vanilla/Doom Emacs and vice versa?
I wouldn’t quite say that. It is more that you are probably going to need some prerequisite emacs knowledge to make the best use out of spacemacs’ layer system. To figure out how spacemacs works, you first need to have a basic idea of how emacs works. Doom is a bit closer to the metal, so you need to know less in order to properly customize it
Oh! Emacs fanboy here!
I think that one of emacs’ surprising great points is that there is a plugin for a lot of smaller languages. If you’re working with a language that has no special text editor love at all you’re likely better off using vim but if the language authors made a plugin for their language, it’s likely either going to be for emacs or vscode.
As for distribution vanilla emacs Doom emacs. Spacemacs has a bespoke customization system involving layers that is not all that friendly towards copy & pasting code from the internet. Doom emacs customization leans more to the vanilla side which can help if you need to solve a problem in your workflow.
(Obviously vanilla emacs works best in that regard, but I can understand not wanting to start with default emacs straight away)
I think that when it comes to functional programming with effect systems, unison is currently the closest to showing how it is actually done. Koka and languages like Effekt are of course very nice, but they don’t show much going for them besides the example nondeterminism and exception effect. Verse, that language that was going to be used as Fortnite’s scripting language, also plans on adding these effect systems a la Koka.
Overall, I think one of 2 things will happen:
This Arch story reminds me a lot of a r/talesfromtechsupport story that went remarkably similar but had a less happy ending for the Linux enthusiast, where he basically disabled the TPM and couldn’t access the company network because the network seemed to only allow trusted machines.
Can’t find it right now but maybe I can do some digging once I’m on a computer
Isn’t there usually a yellow pop-up on the top of the screen showing microphone and webcam controls if they are active? I think that’s how you control it. Now this isn’t per-tab control, but it’s better than no control at all I guess
ah I think that’s where I’m at odds with a lot of lemmy NixOS users then 😅, since I am and have always been pretty hesitant to recommend NixOS to anyone in particular. I find the upfront costs of NixOS too big for me to recommend the OS to anyone who wasn’t already looking into it and knows its downsides and upsides.
I do agree however on the fact that using nix is purely beneficial. It doesn’t hurt if you just add a .nix file to your project, since it doesn’t do any harm to an already existing project. It can just install your build tools and then consider itself done, and if you don’t happen to like nix after all, the new installer makes uninstalling easier than ever. There is pretty much no downside to downloading the package manager, something I can’t say about the OS.
Having said that, I don’t think nix should be the end-all be-all standard in package management. I’m sure there will be other package managers that will be better than “nix but with yaml sprinkled in”, and are capable of improving the state of the art. At least, that’s something I hope to happen. For example, I have reservations about using a full-blown programming language for doing my project configuration (see people’s problems with Gradle for why you might not want that). I think a maven-style approach (where you’d have just limited config options, but can expand the package manager’s capabilities by telling it to install certain plugins (in the same config file!)), could be worth looking into, and I’d be lying if I said I wasn’t on the look out for a potential better nix alternative
I mean seeing how people here act after having been on nixos for a few weeks I would say it’s an apt comparison. I swear we weren’t that obnoxious when I started using the distro in 2019 D:
Alright as someone who likes Haskell and has dabbled in unison before, I believe I can answer all these questions for you:
- Why is
helloWorld
there twice?
It is common in languages like haskell and ocaml to first mention the type of a function, so in this case:
helloWorld
is '{IO, Exception} ()
. That is it’s type signature (important for later)helloWorld
is \_ -> println "Hello, World!"
- What’s the
'
for?- What are the
()
for?
Here is where I have to get into the nitty gritty of how unison actually works. Unison has what programming language researchers call an effect system. The type signature of helloWorld
indicates that it can perform the IO
and Exception
types of side effects, and these need to be handled. (in this case, they are handled by the compiler, but other types of side effects can be handled by the programmer themselves)
However, for reasons Unison does not like dealing with eagerly evaluated non-function values with side effects. For this reason, there is '
. Essentially, what it does is turn a value into a function that accepts ()
as it’s argument. We could therefore say that the type signature of helloWorld
is also () -> {IO, Exception} ()
. The last ()
indicates that, next to it’s IO
and Exception
side effects, it also returns ()
as a value. This is because, in functional programming languages, all functions need to return values (or run infinitely, but that is for another topic)
Now I’ve been used to functional programming for quite a while now, so things that seem natural to me can be absolutely woozy for anyone not used to this paradigm. So if anything still feels vague to you feel free to comment
Yes but it would have been nicer to have a transition period in which both methods are supported for a little while so that you don’t literally break every extension in existence up to this release
Idk I don’t tend to look at the clock when I fall asleep, but I do know that whenever I accidentally fall asleep while watching, say, a PBS spacetime video, I pass out for no less then about an hour
Also I have no clue how the other people here figure out how long it takes them to go to sleep, because as far as I know, looking at the clock just keeps you awake for longer
Netherlands :)