Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An interactive guide to learning Rust

github.com

Post reply on HN
Print view View original

51–55 of 55 posts

Re: An interactive guide to learning Rust

#51

Post by chusk3 »

nobleach wrote: post #10
OtterCoder wrote: post #4

Earlier quoted context omitted.

As a web developer, you can write servers that take orders of magnitude less space, memory, and CPU than a similar JS server, without having to deal with the madness that is first-time C development.

Give me something that can run ReactDOM.renderToString() faster, and I'm all ears. Until that day (and I'm kinda hoping it comes) I'm a bit stuck.

You should look at the all-F# SAFE Stack, then. It uses F# and .net core for the whole application and supports elm-style UI programming on the client side with react and server side rendering: https://github.com/fable-compiler/fable-react/blob/master/do...

Re: An interactive guide to learning Rust

#52

Post by stochastic_monk »

kqr wrote: post #22
FridgeSeal wrote: post #9

Earlier quoted context omitted.

There was a demo the other day of Rust outperforming JS for stuff JS usually does. Presumably this will continue to improve, so it won't even be a case of equivalent, it'll be a case of "thoroughly beats the pants off".

"Very close to native" means "much more efficient than JS", because JS is nowhere near native. (Have we really gone so far that people hear "native" and think of the browser? Like the web browser is the machine we target, and not the metal box the end user purchased?)

Is it pretty easy to write C++ extensions to V8? I've seen a couple of projects of that sort. I wonder if they're relatively difficult, and if that's perhaps why the push for WebAssembly has been so strong.

Re: An interactive guide to learning Rust

#53

Post by steveklabnik »

2_listerine_pls wrote: post #2

What's the relevance of learning Rust for someone into web development?

We have an entire working group dedicated to looking at the end-to-end web story this year, both backend and front end. Things are still a bit rough, but coming along nicely. The next release of Rust includes a major language feature that’s helpful when writing asynchronous code (impl Trait), for example.

Re: An interactive guide to learning Rust

#54

Post by nobleach »

chusk3 wrote: post #51
nobleach wrote: post #10

Earlier quoted context omitted.

Give me something that can run ReactDOM.renderToString() faster, and I'm all ears. Until that day (and I'm kinda hoping it comes) I'm a bit stuck.

You should look at the all-F# SAFE Stack, then. It uses F# and .net core for the whole application and supports elm-style UI programming on the client side with react and server side rendering: https://github.com/fable-compiler/fable-react/blob/master/do...

If it's F#, sign me up! That's the current language/stack I'm enthralled with. JavaScript is still the day job though. Thanks!

Re: An interactive guide to learning Rust

#55

Post by v_lisivka »

nobleach wrote: post #47
v_lisivka wrote: post #20

Earlier quoted context omitted.

https://github.com/DenisKolodin/yew

This does look interesting. I don't see a difference between this and any other server-side templating language though. I actually need an isomorphic representation on the client and server. (this is what makes renderToString() valuable) I guess I could be extremely careful in writing the server output, and writing the client output to match, but at that point, I'd be writing it twice... and I could use any language.…

It's for client side, not for server side. It's compiled into Wasm and delivered to client. You can use same code for server-side pre-rendering (for faster loading or for search engine indexing), but it is not main goal of Yew.
Post reply on HN