Common lisp because it's lisp all the way down which makes debugging in slime is better then clojure. With CL you can just have a buffer and start writing code, evaling snippets through slime. With clojure you have to have a project structure set up on disk first, it feels very java enterprisy , made for suits.
There is no cure. The best solution is to feed the addiction. Buy as many monitors as you can then display as many subreddits on the screen as you can. Then develop your ability to read multiple reddits simultaneously. At night make sure you have text-to-voice software to read reddits for you while you sleep.
When neuralink comes out, make sure you implant it into your brain. It will make you multi-threaded, enabling you to double the number of monitors you can simultaneously keep track of
If you are are already familiar with apple software you'd be crazy not go with the new M1. Super power efficiency without compromising on power? Yes please. It's the first big advancement in a while. It's priced very well for what you get.
The only reason I'm not jumping on the M1 train is I'm die hard linux. I also prefer desktops and never work outside of a home/work office. So I can get the same/better performance with AMD Ryzen and not need to care so much about power/battery.
Deciding between Debian/Arch is mostly about the package system. Debian locks in to package versions for stability. You don't need to worry about updating package A changing it's API and breaking package B. It's sort of a professionally managed package system. The downside is you might miss out on cool new feature of package A since you're locked in to an old version.
A lot of the big moving and shaking in Arch has already come to pass, so it's not likely you will brick your system from an update.
So if you are really into the latest versions of things, then Arch. If you prefer to remove the risk of breaking your system and limit updates to security patches then go with Debian.
Both. Tabs up to the current level of indentation. Then spaces after that for alignment. Spaces never come before a tab, only after and only for alignment purposes.
Everyone likes to take a dump on mixing tabs/spaces. But it solves all problems with both. Everyone can view the indentation width they prefer; 2, 3, 4, 8, whatever. And alignment is always correct no matter what width you prefer. An auto format tool can remove the need to manually deal with anything.
Indent width is a visual effect that should not be mandated. You wouldn't mandate a color scheme for your code base, so why would you mandate indentation width?