this post was submitted on 23 Jun 2024
735 points (96.5% liked)

Programmer Humor

19512 readers
314 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 119 points 4 months ago* (last edited 4 months ago) (29 children)

Use TypeScript, and nonsensical things like adding arrays to objects will be compile-time errors.

[–] [email protected] 58 points 4 months ago* (last edited 4 months 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.

[–] [email protected] 20 points 4 months ago (19 children)

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

[–] [email protected] 7 points 4 months ago (4 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.

[–] [email protected] 6 points 4 months ago

We use this framework at work: https://leptos.dev

[–] [email protected] 5 points 4 months ago (1 children)

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

[–] [email protected] 4 points 4 months ago (2 children)

Does WASM do DOM manipulation nowadays?

[–] [email protected] 3 points 4 months ago (2 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.

[–] [email protected] 2 points 4 months ago

Kotlin -> JavaScript would work. I assume there must be a Python version of that as well.

[–] [email protected] 2 points 4 months ago (1 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

[–] [email protected] 1 points 4 months ago (1 children)

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

[–] [email protected] 1 points 4 months ago (1 children)

You meanbJavaFX? Yeah the web version of it never was great

[–] [email protected] 1 points 4 months ago (1 children)

Even worse, I’m old enough to have used GWT at some point.

[–] [email protected] 2 points 4 months ago
[–] [email protected] 0 points 4 months ago (1 children)

Just use javascript and don’t try to add {} to [].

[–] [email protected] 2 points 4 months ago

Well, you never try to.

[–] [email protected] 2 points 4 months 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.

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (1 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.

[–] [email protected] 2 points 4 months ago (1 children)

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.

[–] [email protected] 2 points 4 months 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.

load more comments (14 replies)
load more comments (19 replies)
load more comments (22 replies)