Comments by "Anony Mousse" (@anon_y_mousse) on "everyone is coding like yoda. (should you?)" video.

This is one of those few things that Pascal actually did better than C. In fact I opted to copy that for my own language, := to assign, = to compare shallow, and == to compare deep. Well, copy and amend. As it turns out, I do assign variables at times in condition headers, and it would be quite annoying to give up that ability or make it a warning/error. The solutions that people come up with often make no sense. Like in Java, "gee, using goto is problematic if you don't know what you're doing", "we'll just delete it from the language and it'll be fine." Turns out that sometimes your code looks worse without it and is even more spaghetti-fied. The same could be said for Yoda notation which wouldn't catch if ( a = b ) errors, if it's not intentional.
5
@yjlom That's GNU style. I personally use Allman style, but I find that I'm nearly alone in that. Most these days use K&R, even people writing code in Go and Rust. Go actually enforces it too, as in it's an error to not use K&R. I actually hate K&R style which is why I hate Go with a fiery passion.
2
@CD4017BE Yeah, labelled continue and break, with try/continue/finally to fill in most of the rest of the gaps. Thing is, exceptions are slower than return value checking. What we need is a new idiom for a lot of things that are done the Java way, or for that matter the C++ way. Reasonable programmers do these things, but they're still inferior to how we should be doing things. And goto was just an example as there are other things that other languages remove as features because they deem them to be bad when they aren't.
2
I'm in a gang of one and "we" only use Allman style.
1
Kudos for actually using F# in any capacity.
1
@abcdef-fo1tf You can use any language as long as you've got either the compiler for it to generate .dex files or can use a stub and FFI the code you write.
1