Imagine a C compiler that produced sarcastically formatted assembly
A framework that makes things worse on purpose
11–20 of 60 posts
Re: A framework that makes things worse on purpose
#12I don't need a new framework for that. The app I'm currently working on clocks in at 75MB of JS before minification. That's enough for the browser to take seconds to parse the whole thing.
Oh my. Oh my. Please tell me there's some dead code elimination step in your pipeline too.
Here's the kicker: none of this is dead code. Vendor libraries alone take 28MB.
Apparently one of the second order effects of rolling your own components is having enormous bundles because there's no incentive to minimize them.
3rd party libraries on the other hand usually go out of their way to be as small as possible.
I'm doing my best not to be sarcastic about this.
EDIT: we treeshake the bejesus out of it, but it's possible that there's some code duplication going on, because the build pipeline is, ahem, custom made.
Re: A framework that makes things worse on purpose
#13The sarcasm is real: the web has gotten out of control by a series of overly bloated framework designs that have resulted in a domino effect that has made the web slower, less user friendly, and buggier.
Re: A framework that makes things worse on purpose
#14I don't need a new framework for that. The app I'm currently working on clocks in at 75MB of JS before minification. That's enough for the browser to take seconds to parse the whole thing.
That's the joke.
Re: A framework that makes things worse on purpose
#15Sometimes I wonder what the point of those web frameworks are. I find them harder to use than plain HTML/CSS/JS.
Part of the downvotes to your comment may be coming from the fact that this framework is (I'm assuming?) a joke.
Otherwise, I completely agree with you. The last few projects I've worked on I used vanilla HTML/CSS/JS and I found it so much better than using any of the popular front-end frameworks. I didn't have megabytes of dependencies before a single line of production code was written. I didn't have to spend time trying to understand any Webpack incantations.
Re: A framework that makes things worse on purpose
#16I don't need a new framework for that. The app I'm currently working on clocks in at 75MB of JS before minification. That's enough for the browser to take seconds to parse the whole thing.
Step back and realize that entire operating systems with browsers that can run JS can fit into 1.44 MB.
Re: A framework that makes things worse on purpose
#17Imagine a C compiler that produced sarcastically formatted assembly
Even more true for an assembler. I guess, there's urgent need for a transpiling 6502 tool chain.
Re: A framework that makes things worse on purpose
#18I don't need a new framework for that. The app I'm currently working on clocks in at 75MB of JS before minification. That's enough for the browser to take seconds to parse the whole thing.
> I don't need a new framework for that.
Ahhh, you have some of the same front end dev team I have, huh?
Re: A framework that makes things worse on purpose
#19Earlier quoted context omitted.
Oh my. Oh my. Please tell me there's some dead code elimination step in your pipeline too.
Here's the kicker: none of this is dead code. Vendor libraries alone take 28MB. Apparently one of the second order effects of rolling your own components is having enormous bundles because there's no incentive to minimize them. 3rd party libraries on the other hand usually go out of their way to be as small as possible. I'm doing my best not to be sarcastic about this. EDIT: we treeshake the bejesus out of it, but it…
What tech do you use? Also which kind of app is it? Does it have some special feature that causes the code bloat, or is it just lots of screens?
Re: A framework that makes things worse on purpose
#20The sarcasm is real: the web has gotten out of control by a series of overly bloated framework designs that have resulted in a domino effect that has made the web slower, less user friendly, and buggier.
bUT WE cAn PeRSonAlIzE Your AdS!!!