- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
Personally I wouldn’t abuse a language like that. If you want to write Python, write Python. Don’t pretend some other language is Python, because it isn’t. The braces need to be in the “correct” place, i.e. { at the end of a line or on a line on its own, and } on its own line, with both braces indented correctly for the code they contain. Braces are important visual and logical indicators in C-like languages and are critical in understanding the flow of the code.
That said, if this is some silly little noddy program that only you will ever see then you can write it however you want. Don’t expect to be taken seriously as a competent dev though if this is going to be part of your public profile.
The last line is peak
For a moment I wondered why the Rust code was so much more readable than I remembered.
This would make a nice VS Codium plugin to deal with all the visual clutter. I actually like this.
I wish I could do this with every IDE. Get rid of all the semicolons and most curly braces and replace them with structural whitespace. You could even save the files with the punctuation and compile that to whitespace when editing.
I’m screaming internally and externally.
Kill it with fire
Looks neat, except for the rightmost column. Delete that and try again.
On a serious note, how hard is rust if I know python?
I don’t like this type of question. In my experience knowing one language has little impact on learning another. What matters much more is understanding the underlying concepts.
If you grok OOP it doesn’t matter if you go from Java to C# or from C++ to Python. Yes, there are differences, but they’re mostly syntactic in nature.
So assuming you got the hang of imperative programming and maybe had some exposure to functional programming, too, the concept you’re likely to struggle with the most is ownership. Simply because it’s a concept that’s fairly unique to Rust.
Having come from Java, via C++ and Python and having dabbled with Haskell a bit, I feel like The Book does a decent job of explaining Rust in general and its oddities in particular.Appreciated.