Unless those lines are autogenerated I’d be rather concerned
Unless those lines are autogenerated I’d be rather concerned
Y’all are taking my hyperbole a bit literal. I’m sure rust is fine. The article had brought up that iteration and flexibility are the weak points. This resonates with my personal experience. That was my entire point from the beginning. I don’t like rust, I will never like rust. I’m glad y’all like rust. There is no “argument” here. It’s just opinion
The only thing I have issue with is people pretending I’m somehow a crazy person for not liking their favorite toy
I’m glad you enjoy it. If you find the blog to not fit within your world experience no one is saying you need to take it otherwise. However the author’s take did resonate with me
The “problem” (as you put it) is that people get emotionally invested in their language of choice. Instead of just accepting that there will always be as many languages (and styles of language) as there are types of people
Rust is great! I’m glad people like it. But for me it will always be painful and that slows me down. A slow developer is a hungry developer
People can like different things y’all
Seriously what’s up with lemmy and taking the most disingenuous interpretation of someone’s words
The article literally covered how rust is terrible for iteration and refactoring. Which are corner stones to building software in a small business. Which is where I’ve worked for the last six years. Which is also my personal favorite way to write code.
Y’all don’t have to start a damn argument every time someone disagrees with you
As someone who is a big fan of shipping fast and shipping often :tm: this article is both really great and also cemented why I’ll never like rust. It’s a neat tool, just not for me
Honestly man it just sounds like you have struggled with dynamic languages and by extension prefer static (compiled) ones. Which is totally fine you don’t have to like everything. But I do think you’re missing the real issue with “everything looks good.” It’s a lack of experience with the tool. It doesn’t matter if you’re using something as strict as Rust or dynamic as Lisp. “Everything looks good,” is always bad. You should know “this is how this works,” which is just not something a newbie can handle when they still don’t know the difference between pass-by-reference and pass-by-value (or that those words even exist!)
What issue is that you think is unique to python?
Hey at least they didn’t have to trace a bug in their core framework. Only to find it is both in the issue tracker and 10 years old, and there is no offical fix. So you have to make a hacky patch yourself
As someone who has taught people a variety of languages. No. This happens regardless of what language you choose. It’s just a universal programmer experience to get frustrated at your work
Oh yeah the leftpad incident. Was fun watching that from a distance
Given how software is a giant Jenga tower made of smaller Jenga towers it’s amazing any of it works at all
Fives years of fucking around and breaking shit. Worth it though
Don’t forget the comments!
// will probably replace…
Yes I would
Are you trying to imply that python is both fast and strongly typed? As for the syntax that’s largely a matter of opinion. Most ruby-enjoyers I know specifically call out the syntax as something they like
Also I’m not qualified to comment on Lua so I won’t. Most of my language exploration has been with languages many people famously hate (perl and lisp)
All of that is to say I generally don’t think talking about what language is “best” is really a productive conversation. I was mostly curious if you had an intimate understanding of the tradeoffs or otherwise a strong opinion about how it was constructed
Curious what use case you have for needing a do-while. Honestly I barely use while at all, a good ol for-loop normally does the trick
Ruby is a really nice language especially when taken in the context of it’s time. Curious why you feel it isn’t worth being someone’s favorite?
not all problems are worth busting out the heavy machinery (until they are)
Ime anyone who is experienced enough knows how to avoid these Types of issues anyway (through tooling and good convention etc)