This seems not necessarily very hard to me? All you have to do is keep yourself honest by actually trying to reproduce the results of the notebook when you're done:
1. Copy the notebook
2. Run from first cell in the copy
3. Check that the results are the same
4. If not the same, debug and repeat
What makes it hard is when the feedback loop is slow because the data is big. But not all data is big!
Another thing that might make it hard is if your execution is so chaotic that debugging is impossible because what you did and what you think you did bear no resemblance. But personally I wouldn't define rising above that state as incredible discipline. For people who suffer from that issue, I think the best help would be a command history similar to that provided by RStudio.
All that said, Marimo seems great and I agree notebooks are dangerous if their results are trusted equally as fully explicit processing pipelines.
Arch exists for good reason, and if you’re not comfortable with the complexity of setup just use another distro?
Fedora, Mint and Ubuntu both exist if you want a simpler installer. I’ve started using Bazzite on more machines too and couldn’t be happier with the results.
Genuinely I think most people just confuse distro with desktop environment. If you don’t actually need arch just go with another simpler distro and set up the DE you need.
Nevertheless, he is probably right. Only the people who went through working on Windows, Linux both on cheap and expensive machines while dealing with all the "baggage" these environments bring can tolerate MacOS with leniency. I will never come back to anything else until I see a competitive offer from just anyone because what Apple offers is:
* Fast, silent, extremely energy efficient devices with excellent screens and audio.
* The font rendering. I honestly can't believe people who professionally work with text all their lives never mention it here. MacOS had and continues to have the best fonts and font rendering that is.
* Solid build that lasts (I own MacBook Pro and MS Surface Book 2 both from 2019 so I see how they age).
* A device that is ready to work when you open a lid or touch a keyboard button without any "waking up from sleep/hibernation" or freezing due to buggy video drivers and inability to work with GPU in hybrid mode OUT-OF-THE-BOX in 2025.
The above-mentioned is more than enough for me to tolerate any MacOS issues and the ones mentioned in the article are just laughable.
Apple offers you the full package that allows cross-device integration while Win/Linux users still rely on the Google stack or other third party "workarounds". Yes, no surprises here -- owning the hardware and software stack is a massive advantage.
What I really liked going through though are project euler and 4ever-clojure problems. It's subjective but I suspect it's because you don't need to read through paragraphs of text before starting to write a solution. It's the opposite, the small problems with clear goals leave you with more space for creativity and urge you to write more code in the end. I personally found the hours spent on such problems to be more productive.
confirmed it by looking at the site just now.
I've been using SQL on CSV and JSON lately as it's mostly easiest for me, but I can think back a few times where I've used an *awk for a specific need, AND had to deal with CSV parsing at the same time.