something I wrote in JavaScript built on top of the exact same API as has been reproduced in rust by a library now

rewrote it in rust but 1/5th the features cuz lazy

has three times the bugs as the original version... like... before my bug fixing

is it rust. is rust the problem

JS-heads are a funny bunch.

Every time that someone says something bad about JS, they are quick to point out that the tool is never the problem and the dev is to blame.

But when they write something in a language that they are less familiar with than JS and it’s buggy, then suddenly the language is to blame.

Well, never underestimate the work that you did before. Rewrites are always underestimated.

@Lensflare An equivalent of 'It must be the hardware issue.' I've heard so many times before.

/* It almost never was. */

@Lensflare js is easy to use so I don't understand what problems there is to be had to begin with

@Lensflare a lot of things seem to be buggy in rust

I broke tui for no reason

reqwest just hangs all the time and I worked really hard to solve that one for months

in JavaScript things weren't buggy though. there was just data you shoved in the wrong location because you forgot something but that was pretty mild

idk what to do with these other things

@jestdotty another funny thing that JS-heads do is assume that when someone complains about JS, it must be because they don’t understand it or/and it‘s too hard for them.

"Problems" in JS are never about complexity or the lack of understanding.

I have pointed this out so many times now and I don’t want to compile a list of what is wrong with JS again.

@Lensflare I don't see how JavaScript could be too hard

at any rate. rust rust rust