

The biggest thing I’ve heard people suggest (and I’ve been using) is to install distrobox. I use it to install some fussy apps that otherwise would have been a dealbreaker. Maybe that helps?
Many fall in the face of chaos, but not this one, not today
The biggest thing I’ve heard people suggest (and I’ve been using) is to install distrobox. I use it to install some fussy apps that otherwise would have been a dealbreaker. Maybe that helps?
Congrats!
I concur, I went with bazzite for my daily driver and it’s been the best yet, I prefer it over the others I’ve tried: Arch, SteamOS, Fedora, Ubuntu, Mint, and OpenSuse.
It’s got downsides, but I just really like it.
Whoa whoa, what do you want to do, crash the entire US stock market over here?! Our whole economy is propped up by the story that AI is the future and will replace all jobs forever. We’ve got MS paying OpenAI paying Nvidia, and that’s making the line go up.
So let’s be cool with throwing around “numbers” that “prove” the emperor has no clothes. Because, like, we gotta pretend he does at least until the next thing that needs every video card ever.
F# is such a fantastic language.
I’d not hesitate a second to use it (and Fable) for my own startup. I’m very comfortable with Ruby, Clojure, Haskell, Perl, PHP, Python, Java, Typescript, and C#. Yet I would pick F# over all of those in a heartbeat.
F# has great type safety (but not forced into monad transformer chaos like Haskell). You need about 1/3rd less code than C# and Java, and the compiler will find more bugs than in those languages.
A few favorites:
Let’s be real, Witcher 3 is just a Gwent launcher.
Also I’ve definitely played more Pazaak than KOTOR.
I’m sure someone will be like “um akchuly” to my explanation. But for me it’s good enough to think if it that way.
I’ve worked in Haskell and F# for a decade, and added some of the original code to the Unison compiler, so I’m at least passingly familiar with the subject. Enough that I’ve had to explain it to new hires a bunch of times to get them to to speed. I find it easier to learn something when I’m given a practical use for it and how it solves that problem.
In practical terms, it’s most commonly a code pattern where any function that interacts with something outside your code (database, filesystem, external API) is “given permission” so all the external interactions are accounted for. You have to pass around something like a permission to allow a function to interact with anything external. Kind of like dependency injection on steroids.
This allows the compiler to enhance the code in ways it otherwise couldn’t. It also prevents many kinds of bugs. However, it’s quite a bit of extra hassle, so it’s frustrating if you’re not used to it. The way you pass around the “permission” is unusual, so it gives a lot of people a headache at first.
This is also used for internal permissions like grabbing the first element of an array. You only get permission if the array has at least one thing inside. If it’s empty, you can’t get permission. As such there’s a lot of code around checking for permission. Languages like Haskell or Unison have a lot of tricks that make it much easier than you’d think, but you still have to account for it. That’s where you see all the weird functions in Haskell like fmap
and >=
. It’s helpers to make it easier to pass around those “permissions”.
What’s the point you ask? There’s all kinds of powerful performance optimizations when you know a certain block of code never touches the outside world. You can split execution between different CPU cores, etc. This is still in it’s infancy, but new languages like Unison are breaking incredible ground here. As this is developed further it will be much easier to build software that uses up multiple cores or even multiple machines in distributed swarms without having to build microservice hell. It’ll all just be one program, but it runs across as many machines as needed. Monads are just one of the first features that needed to exist to allow these later features.
There’s a whole math background to it, but I’m much more a “get things done” engineer than a “show me the original math that inspired this language feature” engineer, so I think if it more practically. Same way I explain functions as a way to group a bunch of related actions, and not as an implementation of a lambda calculus. I think people who start talking about burritos and endofunctors are just hazing.
So much gardening!
Here’s my starts!
KATAMARI DAMACYYYYYY BUM BUM BUM BUM
At work Rider, at home Emacs. Also trying out Zed at home.
Bravo this advice is excellent
They are both my creepy weakness and my allies who eat worse things
Memes that lie?! On the internet?! Someone call the Internet police
I always find that last fellow intentionally hilarious. Just avoiding the gaze then he’s just got a full on blindfold
Final fantasy tactics
The saddest clown, trapped by his success.
It’s worth a try, you should be able to run an Ubuntu image in distrobox to install the ollama tools