1. 26
  1.  

  2. 44

    “Rust is the new bitcoin” is probably not a selling point for rust. :P

    1. 0

      Definitely not. Bitcoin is essentially snake oil.

      1. -2

        How is bitcoin at all comparable to snake oil? Does Satoshi lie once in his paper?

        1. 37

          As in life in general, trading insults benefits from defining terms.

          Bitcoin as in the decentralized peer-to-peer value transfer system is not snake-oil. It works and is in daily use.

          Bitcoin as a solution to the world’s economic problems is snake-oil.

          1. 3

            Bitcoin as in the decentralized peer-to-peer value transfer system is not snake-oil. It works and is in daily use.

            I prefer my global value transfer system to have more than 17 transactions per second and don’t randomly change my value by 15% every day.

            1. 2

              I never said it was a particularly good system ;)

    2. 17

      “Rust is the new JavaScript”

      What? This is wrong, highly unqualified, and an annoying idea to say. Rust is a systems language with very different concurrency and memory constraints.

      I’m glad you like Rust but this is a nonsense post.

      1. 13

        I expected the article to reference the whitepaper about the maintainers of npm rewriting a CPU-intensive service in Rust in order to improve performance: https://www.rust-lang.org/static/pdfs/Rust-npm-Whitepaper.pdf

        Some quotes:

        The rewrite of the service in Rust did take longer than both the JavaScript version and the Go version: about a week to get up to speed in the language and implement the program.

        and

        The process of deploying the new Rust service was straight-forward, and soon they were able to forget about the Rust service because it caused so few operational issues. At npm, the usual experience of deploying a JavaScript service to production was that the service would need extensive monitoring for errors and excessive resource usage necessitating debugging and restarts.

        Presumably the npm maintainers are among the most experienced JavaScript developers on earth. Yet in one week they were able to learn enough Rust to write a service which turned out to be more performant and more reliable than their typical JavaScript services.

        I don’t know Rust or Node, but if I were a Node developer, I think that would get my attention.

        1. 3

          they were able to forget about the Rust service because it caused so few operational issues

          There’s a certain orthodoxy in tech’s interest in computation. Computation is cool, but only up to a certain point.

          You can’t sell this sort of reliability via HN posts. There’ll be the odd blog post here or there, but it’s drowned out by the thousands of posts on why ReactiVueAngular from $MEGA_CORP is the bandwagon you need to be on. Nor is it ever as exciting as those posts. It certainly isn’t new.

          This is probably the reason that architecture, algorithms, and general software design are viewed as ‘elusive’ skills despite the knowledge being widely available and easy to learn: they require actual time investment.

        2. 20

          I like Rust, there are good use cases for it, but “Rust is the new JavaScript”, etc? Rust’s restrictions, which make it so different and useful also slow down development velocity and application design. Hyping it up to be something it isn’t doesn’t help anyone (except maybe the authors click count). Different requirements, different tools, different solutions. Want a good explanation of the topic (and a pro-Rust talk)? See Bryan Cantrill’s “Platform Values” https://youtu.be/2wZ1pCpJUIM?t=126

          1. 1

            Fair point! Allthough the headlines for these certain paragraphs are a bit catchy, they have a true point: Bitcoin is a decentralised, sort of self-governed structure. Rust is doing the same. JavaScript runs everywhere, Rust does it too.

          2. 7

            Go however is solely maintained within Google, and we all know what happens to most Google projects after a few years.

            This is not true. Its mostly maintained by Google, but it’s an open source project with many contributers. Furthermore its much more widely used than Rust.

            That may change in 5 years, in fact I think it probably will, even though I really like Go.

            So the thing I don’t get about this, Javascript and Rust are very different programming languages. I get why a C or C++ developer would want to get into Rust, or someone who is really interested in performance, maybe even a Java or C# developer, but its such a leap to go from Javascript to Rust… Why in the world did you choose Javascript in the first place?

            There was an idea here about frontend developers being able to get into backend development, as opposed to Java which was so foreboding. Have we all collectively forgotten why Node came about in the first place? Because Rust isn’t an easy programming language to pickup.

            Don’t get me wrong. It’s really powerful, and one of the days I want to sit down and really figure it out.

            But it’s not easy.

            1. 5

              Maybe I’m a pessimist, but I can’t see Rust catching on as ubiquitous web-dev language on account of it being hard to learn and use compared to “managed” languages.

              But who knows. Maybe time will prove me wrong.

              1. 3

                This is promoting a technology for technology’s sake. Sorry but this mentality keeps hurting our community.

                Javascript is the best language when you want to start your frontend development for a product about which you have no idea if it is going to succeed or not, or it is going to be a short lived project. And this is 99.99…% of projects.

                NodeJS is pretty strong if you build a single page web app. And if not, it has similar pros and cons like Python, Ruby, PHP, and etc.

                Whole benefits mentioned in the article are available with Typescript but even that is a big overhead as an investment.

                I believe once a software engineer really focuses to their product instead of techno day dreaming, they don’t even come close writing such articles.

                1. 2

                  A significant reason I find it hard to adopt other tech stacks over nodejs for the web is the large existing ecosystem, especially the tooling, compilers and others. Would Rust be a good contender today, without one having to implement those lower level blocks?

                  1. 4

                    It’s an ongoing process and of course, a decade of Node is not caught up in a few years. http://www.arewewebyet.org/

                    1. 1

                      That’s an amazing link, and exactly the question I was pondering, thank you!

                  2. 2

                    As others mentioned, it’s definitely not the new JavaScript, they are very different languages and I don’t believe it is fair to compare them… Granted, Rust has a fantastic documentation, the compiler (along with the languages design choices) but it’s not at all easy to hop in it and start developing in it. At least, as for now, they have different goals and serve different product needs. Rust is good for systems programming, JavaScript is (as of now) a good choice to get started, with a fast learning curve and a huge community, support by major browsers and having all popular UI framework and libraries relying on it. WASM is a different beast, but in the context of Rust-to-WASM as opposed to using JavaScript, it’s not worth it at the moment. There are other alternatives and competitors for using other languages and targeting WASM, like C# and .NET (specifically Blazor) but Rust isn’t a replacement for NodeJS developers. Feels like a too general read… Almost everything is written by an overlooked point of view. There’s a lot beneath the surface regarding these two technologies, their adoptions and use. (not to bash on OP - just that I think perhaps there are a lot of reexaminations that should be made regarding these ideas)

                    1. 2

                      Rust isnt and never will be a replacement for JavaScript - so as others have said title is highly misleading

                      having said that anything that helps push people away from Node is good - that project is a cancer on the programming community that needs to die. Hands down the biggest case of Square Peg, Round Hole in the history of computer programming.

                      1. 1

                        The author of the article is ignorant about the fact that Go is included in the GNU Compiler Collection (GCC), precisely to avoid “the one true compiler issue”. Go is a language with several open source compilers available.