Emerging Rust GUI libraries in a WASM world • Hacker News Board

Re: Emerging Rust GUI libraries in a WASM world

#211

Post by LeanderK » Fri, Apr 28, 2023, 1:30 PM UTC

chrismorgan wrote: post #176

LeanderK wrote: post #95

Earlier quoted context omitted.

this take is a little bit too simplistic. There are use-cases where you are bound to a web-based framework but JS solutions are just not fast enough, e.g. data visualisations via jupyter notebooks. So you're stuck with some horribly slow solutions or non-interactive ones giving you pngs. Since you're plotting data, the text is minimal and the needed dialogs etc. are also minimal (clicking on a point and getting a lab…

I believe you’ve misunderstood my intent. When I speak of the pure canvas approach, I mean throwing away almost all that the browser gives you, and rendering everything in a single canvas, with fake scrolling, fake links, &c. For individual widgets like data visualisation, go ahead, use canvas if you want; I won’t complain—though make sure if you have any links in it that you have actual links on top of the canvas fo…

ah ok, now I get what you mean. Yeah, doing everything in canvas is in general a bad approach for all the reasons you listed.

Re: Emerging Rust GUI libraries in a WASM world

#212

Post by pkolaczk » Fri, Apr 28, 2023, 2:01 PM UTC

crispinb wrote: post #208

pkolaczk wrote: post #206

Earlier quoted context omitted.

Prior experience and preferred style of programming can affect severely the difficulty of learning Rust. For me it was mostly 1 week of struggling a bit with the borrow-checker and even that only in places where I really wanted to avoid copies / allocations at all cost - achieving something I wouldn't be able to do at all in other languages. Later I realized that if you are ok with an occasional clone here and there,…

> I think it should be simply considered a different paradigm. I addressed this above and believe it to be an unconvincing explanation of Rust's difficulty. Many polyglot programmers comfortable with, and experienced in, switching (and learning new) paradigms, still find Rust more difficult than other languages they have learned. In my experience most just give up. I haven't, but neither have I become remotely produc…

How come Rust appears at the top of most loved languages in the SO survey so many years in a row? And doesn't even make into the "most dreaded" list at all (when many simpler languages do make into that list)?

Also, there aren't any other mainstream languages with borrow checker at the moment. The problem with Rust is that it introduces many novel ideas, not just some old ideas wrapped in a different syntax (e.g. like Kotlin or Swift). They need time to get into developers heads. Similarly it took many years to accept some ideas from FP into mainstream languages, and people were even debating if Java needed lambdas.

And BTW: I didn't find Rust harder to learn than, e.g. Python or Scala... Scala was kinda fun, but FP required similar amount of mind-bending as lifetimes in Rust, and Python was just purely frustrating.

Re: Emerging Rust GUI libraries in a WASM world

#213

Post by Tozen » Fri, Apr 28, 2023, 2:53 PM UTC

Liberonostrud wrote: post #40

I am betting on Vlang instead. Rust is too complicated for an average person - like me. It's basically the Haskell of system programming. V is basically Go made right.

People should be allowed to have a difference of opinion and like other programming languages, without a swarm or mob of evangelists going on a downvoting party. If others like Rust or Go, that's their preference, but it's not necessary to bully other programmers.

Lots of people like Vlang, so better to accept that. Not everybody is going to prefer or think the same in regards to programming languages.

Re: Emerging Rust GUI libraries in a WASM world

#214

Post by Tozen » Fri, Apr 28, 2023, 3:05 PM UTC

TobyTheDog123 wrote: post #45

Liberonostrud wrote: post #40

I am betting on Vlang instead. Rust is too complicated for an average person - like me. It's basically the Haskell of system programming. V is basically Go made right.

I remember looking into V last year, it seems most of the discussion surrounding it was that it was vaporware. Is that not the case? It certainly looks nice, but is it ready for use?