Comments by "George Albany" (@Spartan322) on "Theo - t3․gg" channel.

  1. He was talking about priority and spam queues, which solves that issue trivially.
    16
  2. Just gonna say I hate both Rust and Javascript as languages, they also suffer from the same build problems because Cargo is just npm with a native compilation built in, making both equally insecure (every npm vulnerability will happen with Cargo) and detrimental to the build, its worse with Cargo specifically because it needs to natively compile Rust in order to run whereas Javascript/Typescript are interpreted languages and require a separate process to build as native apps. (which honestly also suck) I also don't really like Typescript, if I need Typescript I'd just go to Dart instead because it is more inspired from C++ and C# in syntax, Typescript still generally needs to be a subset of Javascript much like YAML is a subset of JSON so you have to add additional syntax to run TS with the same JS syntax which limits what you can do, Dart doesn't have this problem, it still carries the npm problems but I'd prefer Dart to Javascript if I needed a Javascript system. However majority of Rust's behaviors are still implementable in the C++ compiler, they just aren't implemented by default. And I honestly prefer everything in C++ to anything Rust because the syntax is less trash and code paradigms are a lot less opinionated, it doesn't tell you what you must do whereas Rust insists only on its own ways with no alternative, not as bad as C# and Java, but God do I hate most opinionated languages, if I need an opinionated language, I'll just use C#, there is no reason to use any other opinionated language either. And the syntax of Rust is way too verbose, and there is no reason for a strict statically typed language to use a postfix type specifier.
    1
  3. Truthfully I just find that everyone completely screwed up the transitioning to a standardized wasm that doesn't suck and now everyone is mad that they can't change anything in this fragile pipeline, the web devs, tool devs, and engine implementors are all frustrated but none of them are really willing to assist each other in fixing the problem, (I would suggest by getting out of the JS as a base mindset) meaning every single issue will remain unsolved. At this point compiling JS would've been the best solution but nobody can really use a compiler for JS yet and doing so would just piss off a lot of web devs and implementors alike.
    1
  4. If you have arbitrary precision, then it would be equal, but the problem is that the current implementation almost certainly isn't an arbitrary precision.
    1