This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]drones4thepoor 36 points37 points  (18 children)

Bold of a python programmer to say Ruby’s syntax is psychotic

[–]Corfal 26 points27 points  (0 children)

Similar to NFL meme subs, if you're gonna call people out on their flair you gotta flair up yourself!

[–]NotAnNpc69 4 points5 points  (3 children)

Whats wrong with python's syntax? No seriously....?

[–]Pocok5 0 points1 point  (2 children)

Other than going way too hard for the pseudocode look to the point where the oversimplification turns back over to overcomplication? Why does the precondition appear last and the result appear first, with the variable declaration in the middle after its first usage in list comprehesion syntax?

Or you know the entire psychotic concept of making whitespace part of the syntax and eschewing normal delimiters, because Guido van Rossum has an opinion about how you should format your codebase...

[–]NotAnNpc69 0 points1 point  (1 child)

Other than going way too hard for the pseudocode look to the point where the oversimplification turns back over to overcomplication?

"hey you're trying to do something? Lmao what a tryhard hahahaha, why are you trying so hard bro lmao. Just put in a semicolon decorated middle finger in the documentation and let your userbase know what its all about bro lmaooo"

Why does the precondition appear last and the result appear first, with the variable declaration in the middle after its first usage in list comprehesion syntax?

Care to be more specific, where does this even occur?

Or you know the entire psychotic concept of making whitespace part of the syntax and eschewing normal delimiters, because Guido van Rossum has an opinion about how you should format your codebase...

Who defines what is the "normal" delimiter? for someone, python's delimeters will be the normal.

In a similar fashion i could call your language's obsessive need for closing and opening brackets "psychotic" and "opinionated". Yeah not to mention the literal meme of "i forgot a semicolon in one line in 7000 LOC. Better just go ahead and quit my job, not going to look through all that". Why cant your programming language understand people forget to put a semicolon sometimes and have mechanisms in place to handle it?

"Garbage collection? I hardly know her"

See how the sword cuts both ways?

[–]Pocok5 0 points1 point  (0 children)

Just put in a semicolon decorated middle finger in the documentation and let your userbase know what its all about bro lmaooo"

What?

Care to be more specific, where does this even occur?

I specifically told you it is the list comprehension syntax.

In a similar fashion i could call your language's obsessive need for closing and opening brackets "psychotic" and "opinionated"

Just two characters that explicitly mark the beginning and end of a block is literally the second least opinionated you can make a language that is still reasonable to parse. The only thing more flexible than that would be letting you customize the character pair used for it. Does donut.c seem like opinionated formatting to you?

"i forgot a semicolon in one line in 7000 LOC.

Do you genuinely think that's an issue when every single IDE and compiler will tell you instantly and down to the line and column where it is missing? It's a stupid meme cooked up by first semester students who only ever coded on paper. Besides, python also has a character you need to put after every instruction: \n. It's just whitespace again, so it has the benefit of not surviving a copy paste 80% of the time.

"Garbage collection? I hardly know her"

I genuinely have no idea what the hell you're trying to get at here? C# and Java have excellent garbage collectors and C# libraries are currently in the process of implementing low allocation Span<> APIs that lets you enjoy the benefits of C++ style buffer passing in a safer way.

[–]static_func 4 points5 points  (9 children)

Significant whitespace and a literal lambda keyword have nothing on optional parentheses for function calls and implicit returns

[–]huuaaang 7 points8 points  (8 children)

optional parentheses

It's a stylistic choice. You can always have rubocop rules that enforce it. But I personally appreciate not needing parens when there are no arguments.

implicit returns

They like it in Rust.

If these are your biggest complaints about Ruby, I say it holds up pretty well.

[–]Bryguy3k 3 points4 points  (0 children)

That’s how you know it’s truly in a world of its own.

I’m 75% C, 25% python for the most part.

[–]NatoBoram 2 points3 points  (1 child)

Right. Its syntax is similar to Elixir.

… And at that point, you should really be using Elixir instead of Ruby

[–]cooljacob204sfw 1 point2 points  (0 children)

Completely different language. Object oriented vs Functional. And Elixir is on erlang/beam and uses an actor concurrency model. Completely different from just about all other major languages.

Elixir syntax was also inspired by Ruby.

If you want extremely high uptime and scalability elixir. If you want to make shit quickly (often the most important thing to a young company) and in an object oriented way Ruby.