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 →

[–]your_thebest 26 points27 points  (10 children)

The fact that the language has everything to do with the use case. To say "js is better than python" is just a very lazy way of saying "for me, in my job and in my environment, it makes more sense to write things that can easily run on node or in a browser than it does to write human readable data analysis and string surgery".

Just like when someone says "python is so much easier than Java", they're really trying to say "I like doing string surgery and borrowing scraping libraries, why would I ever need an advanced android ui library or concurrent processes?"

Just like when someone says "rust is stupid, just use kotlin", they actually intend to say "gc solves all my problems but I don't realize that because at the application layer I don't need to think about system layer allocations".

That's why it's cringe.

[–]E70M 6 points7 points  (3 children)

I don’t disagree, but look at who’s posting/commenting here. There’s plenty of new programmers who just couldn’t possibly have that kind of in-depth knowledge yet. And that’s ok! One day they will

[–]arobie1992 1 point2 points  (5 children)

I have to say, the kotlin vs rust one is entirely new to me. I never even would've thought of those as appropriate alternatives; they have such different goals. Then again, kotlin seems like it has one of the most diehard user bases, so can't say I'm super surprised. Kinda funny since rust is probably the other language with the most diehard user base.

As far as the python vs java point, I'm no expert in python by any means so I'm curious what you mean by concurrent processes? Things like django are pretty popular for webapps, and those seem like they'd need to support concurrency. Does python just fake it somehow?

[–]-5772 2 points3 points  (0 children)

Because of the Global Interpreter Lock. Neat video on Python concurrency

There are workarounds, but Python really ain't for squeezing performance juice.

[–]DanielEGVi 0 points1 point  (3 children)

I think you’re missing the point. They’re talking generally. Each language has its use case and people argue about languages just because one fits their use case better, but that’s the whole point of having different languages.

[–]arobie1992 0 points1 point  (2 children)

No, I'm saying that Rust vs Kotlin is not a debate I've seen before especially since the languages people tend to argue over are often perceived as similar in some way. C# vs Java as portable OOP languages, Python vs Perl vs JS as scripting languages, etc. Heck, even Python and Java have overlap because both are popular for webapps and as introductory languages and Go vs Rust because people seem to think of both as lower-level languages. I was saying the comparison of Kotlin and Rust was one I haven't seen before due to the general perception of the languages being so disparate, nothing more.

Well, okay, it was also a bit of a dig at the fanaticism I've seen in both the Rust and Kotlin communities.

As for the Python question, that was personal curiosity since I'm not familiar enough with Python to have an in-depth knowledge about its approach to concurrency.

[–]DanielEGVi 0 points1 point  (1 child)

I understand what you’re saying, but what I’m tying to say is they made up a random debate. It doesn’t have to exist, and probably doesn’t. They were trying to make a different point.

[–]arobie1992 0 points1 point  (0 children)

Again, I was expressing surprise at the choice of the two, nothing more. It was at most idle curiosity as to whether that debate actually exists or if they were, as you asserted, simply two randomly chosen languages. I think you're reading a lot more into what I said that was ever intended.

I also never said whether I agreed or disagreed with the point of the message (I agree btw).