Who does science in imperial units?! Thats what crashes stuff and people into hard objects.
Well, then again, they use kcal, instead of Joule. Which has conflicting definitions by a small percentage. And usually, the kilo-part is hidden. Making some calcuations off by a factor of one thousand.
First of april is not now. So I will seriously discuss the idea:
IMHO, some level of linting should be required.
I would often have to reject lengthy and excellent pull requests (PRs), just because autoformat was not pressed and three instead of four whitespaces are in kotlin code. That annoys everyone.
Python does that right, code won't compile with the three version whitespace, which is easily spotted before the PR.
In Visual Studio I turn on the feature to see whitespaces and non visible characters, just because every now and then, for some ungodly reason, someone in the project, somewhere, in every C# project I've ever worked on, will somehow open the file differently (seriously wtf? we all use Visual Studio!) and goof up a file somewhere, or there's people who instead of hitting tab, will manually insert spaces in a way that doesn't match Visual Studio's own format.
I’ll use Visual Studio when you pry my cold dead fingers off of my Vim keyboard. Since Ogg used square rock and Eagg used triangle rock to carve messages we’ve fought over editors. I fall into the camp a of formatter should do the presentation. But I also fall into the { } would be nice for Python.
Might be a criminal or state behaviour, to chose exposure to germs as a method to hurt or kill someone.
But that as far as we know is not corporate style.
A car bomb, to deter other would-be whistleblowers, is more like the typical MO. As has happened with the original Panama Papers reporter on Malta.
B. Plenty of killings that we know of do not follow your typical MO. For example, the killing of Litvinenko by polonium which can only be created in a nuclear reactor (still the most overkill death of a whistleblower ever known).
C. In which case, is it possible you think that's the MO, because the others didn't get caught? And the corporations are now realizing a car bomb is too predictable?
Bacterial infection, grammatical inflection, both natural causes of death [According to uncyclopedia Wiki probably? Don't ask me, I am not germ-anist here in germ-any]
Go is less complex than Rust, imo. As someone who has used Go and Rust for about the same time (5-6 years), it's not as less complex than it seems, though. Namely i found a odd type of complexity emerge in Go where by every individual unit was simple, but the whole was so spread out and poorly abstracted that it it spread out the complexity. So if you squinted, everything was simple. If you zoomed out, it felt convoluted.
Rust on the other hand drastically simplifies a lot of the complexity i dealt with in Go. However depending on the type of work, it's of course got plenty of complexity to dig into should you need it.
The challenge with Rust imo is to know where to use that complexity. Lots of rope to hang yourself with. On average i find myself with code that to me is simpler in Rust, because it's easier to reason about larger blocks of logic. However i still wouldn't ignore the extra rope of the whole language and call it "simpler" than Go.
The golang language spec is very sparse on implementation details in comparison to something like the java spec. I don't think the length of the lang spec is a great metric for language simplicity.
The Java specification is bigger because it has to define the entire Virtual Machine where a compiler can target already defined architectures. I'm also not seeing much in the way of "implementation details" in their specification. Can you point out what you mean?
Arguments are like
"In OOP, every programming task is solved in a distributed system, adding a layer of complexity". So for the simplest of problems, avoid OOP patterns. Or, if having a complex problem, think about whether adding this layer helps or hinders.
And, perhaps the main subproblem arises about OOP [^1]:
state and identity get mixed up, if state is mutable. Then again, Scala seems to be fine with distributed systems, as many problems even add the actor pattern on top to handle messaging (perhaps not called messaging, that term might be more objective-C-ish) between entities.
------------
1: According to at least Scala's author
