3 ms·

So the author can't solve a problem, goes ahead to say that javascript is c because of one situation, then promotes rust by the end. All with a clickbait title

So the author can't solve a problem, goes ahead to say that javascript is c because of one situation, then promotes rust by the end. All with a clickbait title to boot. I'd be more angry but this type of formula for an article is used so often now that it should be expected. I can't wait until people figure out that the individuals that aren't competent enough to handle C's issues, aren't going to be competent enough to handle Rust's either. Hopefully the Rust hype train dies soon. There is simply too much bandwaggoning involved in this language to keep bias out of the equation when considering using it to solve a problem.

shpongled 7y ago
Have you given Rust an honest try yet? I thought it was a hype train too at one point, but I started using it, realized that the hype is well founded and never looked back.
- seemssilly 7y ago
  I haven't but that wasn't my point at all when saying that. It is on a hype train, whether that hype is justified or not is not what I was trying to get at. What I was saying was that this hype and massive surge in use and publicity causes an inevitable bias which clouds judgement when deciding whether or not to use it. That crowd of programmers that seem to hop on every computer fad, the ones that have been adding hashtag reactjs to their twitter posts for the past year, they're probably going to choose rust regardless of whether or not it should actually be used. The bitter contrarian is probably deciding not to use it because he's sick of seeing it mentioned in every other tech blog post in the past year. As soon as this hype dies off, both of these groups can move on and hopefully decide whether rust is actually worth using for whatever they need done. I would use it if it's the right tool for the job. I just want to stop seeing it mentioned 20+ times a day and snuck into blog posts that started off as critiques/comparisons of two other languages.
  - chriskrycho 7y ago
    I don't think you understood the blog post (which is presumably my failure as an author; it was just an off the cuff post and I didn't edit it especially carefully). The point is not to compare JS and C (interesting though that would be) but to note ways in which both of them may be slowly superseded by languages which target the same environments they do but allow much more developer confidence along certain axes—and, in my experience, therefore also a better developer experience and higher productivity along those axes. The whole point was that Rust, Elm, etc. can and do prevent whole classes of problems that are difficult (at best) to eliminate when writing C or JS respectively—Rust and Elm (and F and OCaml and Haskell and Idris and…) were essential to the point I was getting at. One of the challenges for dealing with hype is that things which are legitimately really good tend to get hype, but things which get hype aren't necessarily good. In my experience, Rust is actually really good (so much so that I ran a podcast about it for a couple years). So are lots of other things. It's not perfect, by a long shot. But while there's some of the people hyping it because it's cool phenomenon—that's real!—people also get excited by finding a tool they really enjoy, that solves real problems they experienced previously.

shpongled 7y ago

Have you given Rust an honest try yet? I thought it was a hype train too at one point, but I started using it, realized that the hype is well founded and never looked back.

seemssilly 7y ago
I haven't but that wasn't my point at all when saying that. It is on a hype train, whether that hype is justified or not is not what I was trying to get at. What I was saying was that this hype and massive surge in use and publicity causes an inevitable bias which clouds judgement when deciding whether or not to use it. That crowd of programmers that seem to hop on every computer fad, the ones that have been adding hashtag reactjs to their twitter posts for the past year, they're probably going to choose rust regardless of whether or not it should actually be used. The bitter contrarian is probably deciding not to use it because he's sick of seeing it mentioned in every other tech blog post in the past year. As soon as this hype dies off, both of these groups can move on and hopefully decide whether rust is actually worth using for whatever they need done. I would use it if it's the right tool for the job. I just want to stop seeing it mentioned 20+ times a day and snuck into blog posts that started off as critiques/comparisons of two other languages.
- chriskrycho 7y ago
  I don't think you understood the blog post (which is presumably my failure as an author; it was just an off the cuff post and I didn't edit it especially carefully). The point is not to compare JS and C (interesting though that would be) but to note ways in which both of them may be slowly superseded by languages which target the same environments they do but allow much more developer confidence along certain axes—and, in my experience, therefore also a better developer experience and higher productivity along those axes. The whole point was that Rust, Elm, etc. can and do prevent whole classes of problems that are difficult (at best) to eliminate when writing C or JS respectively—Rust and Elm (and F and OCaml and Haskell and Idris and…) were essential to the point I was getting at. One of the challenges for dealing with hype is that things which are legitimately really good tend to get hype, but things which get hype aren't necessarily good. In my experience, Rust is actually really good (so much so that I ran a podcast about it for a couple years). So are lots of other things. It's not perfect, by a long shot. But while there's some of the people hyping it because it's cool phenomenon—that's real!—people also get excited by finding a tool they really enjoy, that solves real problems they experienced previously.