When I actually tried to write a project in coffee script, the results were the opposite of what I expected.
The code was harder to read, harder to modify, harder to understand, harder to reason about.
There's something about removing stuff from syntax that makes programming harder. My hypothesis is this: your brain has to spend extra effort to "decompress" the terse syntax in order to understand it, and this makes reading code unnecessarily difficult.
So I fundamentally disagree with the underlying premise of these projects, which seems to be based on PG's concept of "terse is power".
My experience suggests the opposite: there's power in being explicit. Type declaration is an example of such a feature: it makes explicit something about the code that was implicit.
Type declarations add more to the parse tree, and require you to type more, but they actually give you more power.
The same can be said about being explicit in the language constructs.
There of course has to be a balance. If everything is way too explicit (more so than needed) then your brain will do the opposite of what it needs to do with terse code: it has to spend more effort to remove the extra fluff to get to the essence of what the code is doing.
Being terse is good, up to a point. Same with being explicit.
Languages that try to bias too strongly towards one extreme or the other tend to miss the mark. Instead of aiming for balance, they start to aim for fulfilling some higher telos.
The fact that you ask that question suggest you already code enough during work hours and you need to do something else after work.
Did you used to code for fun before it was your work? Then maybe it's a good idea to accept that you are not going to find in fun as long as your job is mainly coding (but it might become fun again if you don't mainly code as a job)
Did you drink the kool-aid that a developper is supposed to code for fun after work? Then maybe it's time to question that belief. A lot of professionnal developer that used to do that came to term with the fact that they'd rather do something else from their free time after coding all day.
After 10 years coding professionally, the only times I'm going to consider coding after work is as a mean to an end. There has been some occasions, but I wouldn't consider it "coding for fun". I wanted the results badly enough to dedicate some of my free time to getting that done despite not really enjoying the actual "coding" part.
Most of my free time is now used for anything but coding and I'm cool with that.
I would be very careful with this sentiment. Pretty much any creative endeavour consists of parts that are not strictly fun. Coding in particular is filled with difficulty, tediousness, deep and wide thinking, etc. It's also the best creative tool that I know of, deeply engaging, very intelectually stimulating and fulfilling and lets you create things of extreme sophistication with very little limits. It's easy to rationalize your lack of motivation or discipline with a statement like: "I don't feel like doing it so it must not be something that I like" but creating an environment and a mindset to pursue fun, creative projects is not easy.
[1] https://www.youtube.com/watch?v=h-eEZGun2PM [2] https://replicate.com/p/qr4lfzsqafc3rbprwmvg2cw5ve
It seems every online community these days is full of people hyping up a crypto project for financial gain.
I tried to curate my sub Reddits and still can’t escape it in the comment threads.
Even Product Hunt is just a launching ground for NFT projects these days, crowding out interesting other product launches…