Most benefits of Rust are true, except in some cases it does not allow you to compile an absolutely valid and safe program like here https://github.com/rust-lang/rust/issues/47680 - unfortunately you don't have freedom of code design decisions! I see some possible problems with refactoring, extending logic and functionality, and lots of issues with async code design and readability. For me, Rust looks like a temporar…
You have successfully linked to the only meaningfully loud bug in the borrow checker; declaring that as proof that Rust is a temporary step does not seem like the most cool-headed of evaluations, especially as it will be fixed by a new borrow checker in active development. These assertions are always made, and always alongside information suggesting the speaker has not actually spent very much time using Rust.
Why Rust?
251–260 of 294 posts
Re: Why Rust?
#252Earlier quoted context omitted.
Rust will never make it to the frontend at scale. There is a reason why JS was invented. People doing frontend dev don't want to bother with slow compile time or 3 strings implementation. And the fast argument is missleading at best, every modern language are "fast" enough, if Amazon and Google runs Java that mean it's fast enough for 99% of workload.
Typescript and React project build times are easily in the same ballpark as Rust or C++ for similar code base sizes though, yet they are used in the frontend 'at scale' ;)
Re: Why Rust?
#253Earlier quoted context omitted.
C++ was C with a better interface for GUI widgets and generic templates. There was a lot of hype about OOP too, but I am not sure it was ever adopted because of it.
C++ was C with a better interface for GUI widgets and generic templates. That came a lot later in its life, like mid to late 90's.
But was C++ widely adopted at that time? I remember C++ compilers being a huge pain by the middle 90s. I can't imagine everybody using them earlier. (But then, it wouldn't be the first time everybody just decides to do something I can't imagine.)
Re: Why Rust?
#254Re: Why Rust?
#255> By using Rust for both our frontend and backend, we have a unified stack of Rust everywhere, simplifying our hiring. > I can write web apps in another language than JavaScript > I can write web apps that are fast Yeah, this is what's worrying me. If you look at rerun.io website, you will notice that it's built with Next.js, i.e. is using a React framework to build pages that have no interactivity whatsoever. Next.j…
Hi, author here! We are building the frontend of our _application_ in Rust and rendering it to a canvas using egui.rs. For the web site we are using more "traditional" tech, as you've noticed. I am not a big fan of the complexity of modern web sites (including our own), which is exactly why I created egui. However, it is targeted at web apps, not web sites.
It is difficult to believe this will be the future of the web.
I don’t think websites should take this approach. Seems like a bad idea
Re: Why Rust?
#256Earlier quoted context omitted.
What are crypto companies doing that I should care about? Give me something I could go check out and use that is: (1) Not speculation, gambling, or some variation thereof. (2) Useful for something other than crypto itself. (3) Actually works and can be used today. (4) Continues to make sense even in a crypto bear market. (In other words: I will still buy milk even if the US dollar is falling because the point is the…
https://news.ycombinator.com/item?id=32406095 I prepared that post since the question you posed comes up every week here, if not more frequently.
This was all technically possible in 2009. What I was getting at was… what’s new? Billions and billions have been poured into all kinds of app development and R&D in this space and all we have is still what we had when Bitcoin launched.
What are all these people in crypto building? Where is it? Where can I use it?
Imagine if 25 years after the dot com era after hundreds of billions had been spent we still just had e-mail, static html4, and text chat protocols over dialup modem.
Re: Why Rust?
#257Earlier quoted context omitted.
Reference counting is much slower than 'garbage collection'.
Technically yes, but if you only use it when you need it, it's often not a performance concideration. And for systems programming, the often overlooked truth is that people care far less about perfect performance than they do about control - ref counting doesn't give up control to a mysterious oracle running in the background which may or may not wreck your performance in hard to predict ways, it just pays a known co…
It's possible in C#. Some language and runtime features like lambdas insist on using the GC, but with some care they can be avoided. The usability becomes worse without these features, but IMO that's not a dramatic downgrade.
Many pieces of the standard library in modern .NET don't require managed heap. Instead, they operate on stuff like Span which can be backed by anything: unmanaged heap, native stack, or even the memory mapped to user space by a Linux device driver (I did it with DRM, V4L2 and ALSA devices).
Re: Why Rust?
#258Earlier quoted context omitted.
Scala, Kotlin, Haxe, Swift, and several others. The search term you want is "Algebraic Data Types" Erlang has the superpowered version of this - binary pattern matching, that lets you pattern match on a bitstream directly.
Erlang doesn't have enums.
Re: Why Rust?
#259Re: Why Rust?
#260I've started working in Rust too and I too find it a tremendous breath of fresh air. It's the first time I've been excited about a new programming language in many years. C++ promised to be a language that was both high performance and very expressive but I always found it very difficult to work at a high level of abstraction in C++. The sharp details always stab through. Rust code, on the other hand, often doesn't l…
> Too bad most of the Rust jobs right now seem to be in crypto. What is the problem with that?