I agree, this is an anti-pattern for me.
Having explicit throw
keywords is much more readable compared to hiding flow-control into helper functions.
I agree, this is an anti-pattern for me.
Having explicit throw
keywords is much more readable compared to hiding flow-control into helper functions.
Yeah, idk, ive never actually used win 11 and have barely used win 10. It just a meme.
That’s right. Let’s return to basics, to the first programming language we learn as developers: Pascal. Well at least I have, I assume everyone does too.
/s
That’s a valid argument, but a very weak one. If we are not completely sure something is an improvement in all aspects are we just to dismiss it altogether?
Maybe search for this on kaggle? Or scrape Wikipedia?
This is the major reason for me. I really liked yaml, because it is way more readable to me than JSON. But then I kept finding new and more confusing yaml features and have realized how over-engineered it is.
Yaml would be great language if it had its features prunned heavy.
They’ve lost potential revenue, but that is not the same as if amazon would come to their house and had stolen their only rucksack prototype.
Potential revenue is not your property.
It still sucks though.
Documentation should be generated from code imo