upvote

points

by maccard14 hours ago |
comments
upvoteby nicoburns1 hours ago|
next
[-]
It's mostly because a lot of the web tooling is written in JavaScript. The build times for the "next generation" tools written in Rust/Go are dramatically faster.
reply
upvoteby Hamuko13 hours ago|
prev|
next
[-]
As a non-frontend developer mainly observing and touching something here and there, a lot of the things that frontend developers do seem vastly over-engineered.
reply
upvoteby ramon15613 hours ago|
parent|
next
[-]
I'm not insanely deep into frontend, I mostly just pick up React and call it a day, but it seems like this is also over-engineered?

I've seen vanilla JS before, and I just know I wouldn't want to do the housekeeping that comes with it. People claim it's less work because it' simpler, but I fully expect myself to rewrite the thing at least twice, only to give up because I have no actual mental model anymore of how it works.

reply
upvoteby selfmodruntime12 hours ago|
parent|
[-]
I have never in my career encountered a Vanilla JS project of at least medium size that I would have called simple. They all feature brittle selfmade frameworks whose developers have since left the company years ago.
reply
upvoteby maccard12 hours ago|
parent|
[-]
I write C++ and C# all day - I think it’s fair to say the same about a project in any programming language!
reply
upvoteby thibran13 hours ago|
parent|
prev|
next
[-]
Isn't the main problem that the building blocks the modern web is based on are not a good fit for what we do with it?

CSS is a total mess. HTML is a mess. JS is okay, but is not a high quality language.

We would save so much time and money if we would have a modern base to build on. Sadly this will probably never happen, because company interests will try to corrupt the process and therefore destroy it.

reply
upvoteby selfmodruntime12 hours ago|
parent|
[-]
How are CSS and HTML a mess? Combined, they're an incredibly powerful layout engine that works almost the same across all environments and devices while also featuring easy accessibility.
reply
upvoteby thibran11 hours ago|
parent|
next
[-]
When taking a bird eyes view on CSS it will be hard to oversee that CSS is a mixture of different concepts that evolved over time with a lot of inconsistentsies. It is possible to make it work, but it's not pretty.

Same for HTML. If the web would be reimagined today, there is a very low chance that we would create HTML as is.

reply
upvoteby rk0612 hours ago|
parent|
prev|
[-]
the biggest problem with html/css is that they are tightly coupled. you can't meaningfully modify a layout with css alone.

second biggest problem is "no stricter mode". so even wrong or useless html/css code goes unflagged and is treated as it is normal.

CSS is way too powerful.

reply
upvoteby manuelmoreale6 hours ago|
parent|
next
[-]
> you can't meaningfully modify a layout with css alone.

https://csszengarden.com/pages/alldesigns/

That statement wasn't true ages ago, and it's even less true now.

reply
upvoteby rho13811 hours ago|
parent|
prev|
[-]
> you can’t meaningfully modify a layout with css alone Wut?
reply
upvoteby maccard12 hours ago|
parent|
prev|
next
[-]
This is my understanding too - tools like react are like microservices - they’re a technical solution to an organisational problem. HTML/css/JavaScript is an imperfect abstraction, so we got bootstrap. Then we got client side frameworks which introduced a build step, and then we got asset bundles, optimisers, linters, validators, tree shakers, package managers, validators for your package managers. All of these monkey patched around the actual problem with more abstractions, and the end result is what we have now.
reply
upvoteby mmarian6 hours ago|
parent|
prev|
next
[-]
Not that backend is any better - microservices everywhere, must scale to Facebook traffic even if we only have 10 customers, etc. Saying this as a backend dev
reply
upvoteby pjmlp11 hours ago|
parent|
prev|
next
[-]
Like using SPAs for classical Web development, and then they rediscover PHP.
reply
upvoteby itopaloglu8313 hours ago|
parent|
prev|
next
[-]
It’s mind blowing when you check the generated code, because it goes over 50 elements deep for a simple looking website.

Makes me think that there’s no way this is computationally efficient either.

reply
upvoteby crooked-v12 hours ago|
parent|
[-]
That particular issue is nothing to do with Next or React and everything to do with how HTML/CSS is a really shitty layout engine.
reply
upvoteby maccard12 hours ago|
parent|
[-]
Hard disagree. This is JavaScript frameworks building a hierarchy for themselves and ignoring any sort of complexity on the generated DOM. There’s 0 reason for these 8-10 nested divs other than that’s what the framework spits out.
reply
upvoteby nixpulvis13 hours ago|
parent|
prev|
next
[-]
Same reason why 90% of websites have serious UX issues and constant bugs. This and ad frameworks.
reply
upvoteby rafaelmn6 hours ago|
parent|
prev|
[-]
And underenginered at the same time !
reply
upvoteby 2 hours ago|
prev|
next
[-]
deleted
reply
upvoteby selfmodruntime12 hours ago|
prev|
[-]
C is infinitely less complex to parse and validate than Typescript. C is compiled in a single pass, the `tsc` type checking algorithm has to check structural typing, conditional types and deep generics while also emulating JS' dynamic behaviour.
reply
upvoteby iptq12 hours ago|
parent|
next
[-]
I don't think any C compiler has been single pass for the last 20 years. Typescript's analyses are also not that complicated, it's just that the typescript type checker is written in js. Iirc the actual ts -> js part is pretty fast with some of the more recent compilers.
reply
upvoteby HeavyStorm11 hours ago|
parent|
prev|
next
[-]
That's not the point...
reply
upvoteby maccard12 hours ago|
parent|
prev|
[-]
I disagree - this is an excuse. Even the post we’re commenting in now shows that it’s a series of poor abstractions and bad tooling that takes way too long to do the basics, combined with a language and ecosystem that encourages this behaviour . They saw a 5x speed up by changing tools while still using a JavaScript framework so it’s clearly possible for it to not be complete nonsense.
reply