Viewing a single comment thread. View all comments
twovests wrote
i mean, i can understand html/css frameworks
if i ever make a site, i'm probably gonna slap on one of those cool styles with nice buttons and responsive designs
but i'll still need to fill in where buttons go... and i understand people are somehow using javascript for this? my understanding it was like <button id="cool_logout_button"> and then you hook that up with some Spicy Javascript later down the line?
do you know where the many <div> come from? do they serve a purpose, or are they just extra cruft from the layers of abstraction?
view-source is once again a fresh mystery
devtesla wrote (edited )
Using a web app framework to build a website means yea, you can use JavaScript to set where buttons are. I do believe it's mostly for like, calling a server to decide what text to out where
The div stuff is probably cruft, the sort of thing that could be removed but people don't because it might cause an issue that they wouldn't be able to catch because of all the different places html has to render
twovests wrote
ah that makes sense
it feels cursed to say, but i guess html and css are to modern webdevs as bytecode are to other devs? i assume the compiler or JIT magic is trying to cut as much fat as possible, but i've rarely ever touched a compiled output
devtesla wrote
both of these problems are caused by web devs using more and more abstract frameworks that add junk to the markup. I think html/css frameworks are usually justified, they can handle weird edge cases and are really easy to build something quick with. most developers don't have time and aren't rewarded for making something that doesn't have <div><div><div> on it
these big javascript frameworks started because people needed to build webapps that work like desktop and mobile apps, but are being used in places that aren't really appropriate in order to add useless visual flair, heavy advertising, and track user behavior