338
What are your programming hot takes?
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Sep 2023
338 points (96.2% liked)
Programming
17314 readers
475 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 !webdev@programming.dev
founded 1 year ago
MODERATORS
Yet Markdown languages are far, far more limited in both scope and functionality than HTML is. How do you bridge this gap without making it just as complex?
They didn't start by writing a spec with half of it deprecated already. They started with something, and over time kept developing it - and deprecating other parts. No matter what you propose, unless it's 100% absolutely perfect (and nothing ever is) you'll end up in the same situation. The only other choice would be to break backwards compatibility, which is obviously not a good thing to do.
People say the same about no-code frameworks. There's a good reason that stuff doesn't work beyond the absolute basics. If it was really possible, HTML+CSS+JS give you all the necessary tools to build it. You won't get there with a more limited system.
That's a really big topic but in general I'd combine theming and markup to one language (not necessarily coupling CSS and HTML in one file but having something that does both with similar syntax and rules), make things simpler so there's one clear way of doing something rather than using a generic container for everything, etc.
Obviously deprecating a few things will happen over time but the reason web dev is how it is now is because technology used to be a lot more limited and websites were a lot simpler. 25 years ago, nobody knew what the "modern web" would look like so it was made up as people went along. We know what specifications we would need now if anybody went back and re-did them, I think you'd end up with something better.
I don't think they're comparable. You won't use a GUI and drag-and-drop for everything obviously, you'd still be able to add sections with code.
The fact that Wordpress powers almost half the internet is proof that a simpler web dev experience like this is in demand and it can work. Most websites don't need something complex, just something that supports rapid development and is intuitive, and doesn't make it easy to fall into bad practices. Like I said, it's a hot take, but I would prefer it so much this way.
You'd have to show an example of such a language, it's difficult for me to imagine a good combination between styles and markup - it's good that they are as separate as they are, intertwining them makes the web less useful.
We know the specifications we need for current development and applications. If we were to "reset" and build new specifications now, how do you know they won't be just as useless in 25 years?
Why do you think such a tool doesn't exist as of now? The platform definitely enables you to build it if it's possible - and a less capable platform will not make it easier to enable such a thing.
There are other options. A version on html/css/js would be good IMO. Then you can remove things you should not use in newer versions or make other breaking changes and better evolve the standard. Yes the browsers need to implement and understand each version. Much like how rust works with its editions.
This increases complexity a lot, since you don't just have to implement compatibility with the editions etc., but also have to properly test a giant amount of cases against all of them. What is the advantage compared to marking things as deprecated?