The stone-age called, they want their languages that need header files back!
(I use Rust btw.)
The stone-age called, they want their languages that need header files back!
(I use Rust btw.)
I also think it’s more descriptive. Just like blocklist and allowlist.
Hey! Don’t remove the context menu key, I use that! The alternatives are 1. using the mouse (no!) and 2. Alt+F10 which is awkward.
I think you could even get rid of the iter()
and the collect()
since it’s a small fixed size array.
Unfortunately that support would be worthless if only firefox does it.
Python is actually mostly strongly typed. Strongly (e.g. can’t use a number as a string without explicitly converting it), but dynamically (can change type of variable at runtime). You probably would prefer a statically typed language and I agree.
PHP is a shit language, but far from dead. There are too many legacy killer apps that are used A LOT and won’t be rewritten in a different language anytime soon. E.g. Wordpress, Mediawiki (The engine behind wikipedia and other wikis), Nextcloud, Typo3, …
The JS one is not surprising at all. There’s no other loosely typed multi-paradigm scripting language where such insane shitloads of money and developer time have been spent for optimizing its execution (by some of the largest tech companies). Kinda funny considering that the language design is complete horse shit.
Your 2nd point is really quite surprising. I also wouldn’t have thought that java would beat Go in both energy and time by that margin!
Wow, a proprietary quasi monopoly changes their business model into something extremely exploitative and hostile. I am totally surprised! Shocked even! Blimey!
Seriously, why spend years of your life learning to work with some technology that can at anytime be made instantly obsolete or impractical to use when some random asshole you don’t know decides something dumb. If there’s a FOSS alternative, always prefer that.
It’s actually not that hard to use async libraries in sync context. I rarely need that but if I do, I just pull in an executor and write a little extension trait for futures that lets me call .block() instead of .await.
In the large yearly stack overflow survey it has been the “most loved programming language” for the past 8 years in a row and at the moment its admiration is only growing. I don’t see anything stop this streak anytime soon. For good reasons.
Yes, but he’s doing it because he values the technological advantages of rust as a systems programming language, not because he likes to punish coders. In fact, rust has been the most loved programming languge for 7 or 8 years in a row now according to the big stack overflow survey, so it doesn’t make much sense for the purpuse of punishment.
This satiric picture resonates with a certain community of conservative and overconfident C-programmers. It has been created by bryan lunduke, who is a reactionary dumb fuck.
Probably spez in a pathetic attempt to shit on the lemmy platform :-P
I didn’t even know the origin of that term. That’s kinda sad, thanks for the info!
I’d say at 1000 lines it usually makes sense to extract some parts into other files. But sure, I guess most obscurities have positive aspects. On the other hand, nothing is stopping you from writing a separate file with only function signatures next to your python scripts. It’s just not required, because why would it ;)