this post was submitted on 19 Aug 2024
330 points (98.8% liked)

Programming

17034 readers
347 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



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

Can we not do away with CSS/JS, learn from those mistakes and try something else? Pls, I beg you πŸ₯ΊπŸ™

E: Sorry, forgot the /j Lighten up, Lemmy, not everything is a serious comment that needs your scrutiny or meticulous rebuttals.

[–] [email protected] 8 points 1 month ago (2 children)

What would you replace it with? There are lessons to be learnt from the web, but to "fix" it is much harder

[–] MagicShel 17 points 1 month ago (3 children)

Flash and applets. Let's just have a do over of the 90's and early 00's.

/s

[–] [email protected] 7 points 1 month ago

Nah, just back to Gopher and 5k baud. As an aside: Gemini is pretty awesome

[–] [email protected] 4 points 1 month ago

Frankly AS did a lot of things well

[–] [email protected] 3 points 1 month ago

Please! I miss my Action Script 3, not this cheap wannabe TypeScript 😭

[–] [email protected] 0 points 1 month ago
[–] yogsototh 6 points 1 month ago (1 children)

The first pass of elm ecosystem solved it. Before elm, it was also solved by other frameworks. But people wanted to be able to reuse their components and not rebuild new ones. React provided the ability to reuse css, and dirty js code in the middle of your application. You already had an way bigger ecosystem because you didn’t have to learn and built a complete new system again.

Personally if I had the choice I believe a new start should start at the browser level. Stop supporting HTML/CSS/JS. Create a new app-centric DSL and not a document centric one like html/css/js.

Ideally something inspired from cocoa layout. And I am dreaming but not accept generic code on the client side and only support a small controlled API. It would solve so many security issues. Sure, the creativity in such an ecosystem will be severely reduced. But we will have a so much improved UX.

[–] [email protected] 5 points 1 month ago

I get the reasoning but anything like that would just be abused to enshittify things further with unblockable ads and enforced DRM on everything. At least with the open standards there is the ability to adblock and manipulate certain annoyances at a browser level

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

Maybe we should start by doing away with x86?

[–] [email protected] 2 points 1 month ago

Intel's way ahead of you.