737
JavaScript (sh.itjust.works)
submitted 2 years ago by to c/programmer_humor@programming.dev
88 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 58 points 2 years ago* (25 children)

Yup. The libraries underneath will still allow nonsense at runtime, though, and it will now be harder to see, so it's a partial solution as done in standard practice.

An all-TypeScript stack, if you could pull it off, would be the way to go.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 25 child comments
    •
  • [–] 22 points 2 years ago (2 children)

    Most libraries have TypeScript types these days, either bundled directly with the library (common with newer libraries), or as part of the DefinitelyTyped project.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 11 points 2 years ago (1 child)

    DefinitelyTyped is the exact kind of thing I'm talking about. You put TypeScript definitions over things, but under the hood it's still JavaScript and can fail in JavaScript ways.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 20 points 2 years ago (19 children)

    So a strictly typed language.. I think those already exist.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 19 child comments
    •
  • [–] 7 points 2 years ago (16 children)

    If there was an easy way to use rust or something on webassemly and use that instead of JS. I'd be so happy, but I can't find how to do it without npm.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 16 child comments
    •
  • [–] 5 points 2 years ago (10 children)

    It's in alpha, but there is a Kotlin to wasm compiler in the works.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 4 points 2 years ago (9 children)

    Does WASM do DOM manipulation nowadays?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 3 points 2 years ago (6 children)

    Doesn't look like it, unfortunately. But it's planned. Kotlin can also compile to JavaScript with DOM manipulation. I've not tried either scenario, myself.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 2 years ago (4 children)

    I can't wait for the day I can use something like Kotlin to write Frontend code. Maybe there'll be something like vue or react build on it

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 2 years ago (3 children)

    You could use Java ages ago and it was, very rightly so, abandoned.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 2 years ago* (last edited 2 years ago) (2 children)

    Rust would probably be the wrong tool here. This is scripting, so pointers like Rust is built around aren't really meaningful. Kotlin or Python or something are more on the ticket.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    Websites have grown beyond mere scripting.
    Rust is about more than just nicer pointers, it has a very expressive type system that enables correctness rarely seen outside FP.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 years ago

    Websites have grown beyond mere scripting.

    Parts of them, yeah. WASM in Rust makes total sense.

    Rust is about more than just nicer pointers, it has a very expressive type system that enables correctness rarely seen outside FP.

    If you say so. I'd suggest Haskell, but it doesn't work very naturally with interactivity, either user or intersystem.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 years ago

    You can use WebAssembly today, but you still need some JS interop for a bunch of browser features (like DOM manipulation). Your core logic can be in WebAssembly though. C# has Blazor, and I wouldn't be surprised if there's some Rust WebAssembly projects. I seem to recall that there's a reimplementation of Flash player that's built in Rust and compiles to WebAssembly.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago (1 child)

    Yeah, ideally TypeScript would be natively supported. Or maybe just Python, which is sort-of strictly typed, and definitely won't do "wat". Alas, it's not the world we live in, and browsers take JavaScript.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 years ago (1 child)

    The libraries underneath will still allow nonsense at runtime

    Only if you use a badly written library. Most libraries have types provided by DefinitelyTyped. Those who don’t are (in my experience) so tiny that you probably aren’t using them; or, if you really wanted, can check yourself.

    In the end, if you encounter a bug, it’ still 99% of the time not a library’s fault, even if it’s written in plain JS.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 years ago* (last edited 2 years ago)

    Like I said to the other person, those are just types over top of JavaScript that can still fail if/when coercion happens under the hood.

    I don't even know how to search it now, but a specific example came up on here of a time when JavaScript libraries will cause problems, and problems you can't even see very well if you're expecting it to act strictly-typed.

  • permalink
  • fedilink
  • source
  • parent