• 0 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: July 18th, 2023

help-circle



  • I think that’s a small part of it, the lack of nuance from new coders, but the origins weren’t so cut and dry, IMO. It was really how poorly things were supported by browsers. Tables became used for styling because they were the only way to achieve some layouts that would have any hope of calculating correctly in the browser. JavaScript became used for active elements because html/css originally couldn’t do anything dynamic or responsive. Many things became divs simply because they were the only building block that didn’t come saddled with tons of preconditions and assumptions. etc, etc, etc.

    HTML5 and ECMA2015 are when it started to turn around. Browsers finally got their shit together and supported a proper, useful baseline set of features that could cover most use cases, and the resulting standardizations made a HUGE difference. If it stayed going the way it was pre-HTML5, I wouldn’t be surprised if we’d be wrestling with some popular framework trying to wedge a new standard in next to HTML in the browsers… Heck, that probably would’ve happened anyways if HTML weren’t just glorified XML (meaning it’s already nearly infinitely extensible)!


  • Because many of the frameworks, including Angular and React, were getting started while HTML and JS specs and the support of those specs were a giant hodgepodge MESS.

    Why are so many things divs instead of standard components? Because for WAY too long, those components weren’t standard. Some browsers didn’t even fully support basic components or styling options that had been standard for years.

    Why is everything a div? Because in many browsers, divs got the most feature support.

    The frameworks seem nonsensical and dumb because they’re covering up a LOT of even worse things.

    Not to say a ton of nasty things cannot remain, or new gross things crop up, but at least this one has a history that’s more interesting than, “they designed it poirly”. Nope, a lot of the problems have no design at all, or might’ve been worse with a more “standard” implementation!













  • Depends on the workload, really. 120 users using small services? probably. 120 users sharing large files or bandwidth heavy stuff? Doubt it. Also a lot of enterprise hardware is about reliability. Multiple PSUs, NICs, more robust hardware for constant load/network traffic, etc.

    Sure, a gaming rig can handle it until it can’t. Another question is what happens when the box crashes? Is the business down until a new PC is built and restored from backups?

    A small business can probably afford two PCs, but scaling up and up eventually becomes a lot of trouble and space.