No. In fact we're actually realizing the way we used to ship code was egregiously slow, inaccessible, and no interoperable. Welcome to front end _Engineering_. https://twitter.com/ben_howdle/status/930012526628110337 …
-
-
Exactly. This is exactly what I mean. No one holds every other compiler/lib toolchains to build size, perf, or speed as heavily as Web either. Think if C++ developers couldn't ship more then 200kb of binary.
-
Yes, let's insist that people write real-time, 60fps, instant-loading-on-2g, distributed software without a compiler or significant runtime. Then, when people try to make those things, tell them they're overthinking it.


-
Yeah they should go back to when server side was easy and you could just write assembly, 1s, 0s, and SigV, and just reload.......pic.twitter.com/PYCQS8ZZrZ
-
Omg that thread is painful
-
Back in the good old days the C++ developers pushed bits uphill both ways. You kids with your 20k of libraries and fancy pants compilers have it so easy. Yawn.
End of conversation
New conversation -
-
-
Agreed. My opinion is it is considered too complicated because there’s not “one true way”. Imagine Android without a proper SDK, testing support, etc. If it all relied on 3rd parties, it’d feel the same as the web
-
But the fact that nobody goes around making people feel guilty for using libraries in Android makes a difference.
-
No disagreement there. It's just so weird to me that there is no "here's how you build an app, here's how you test code, etc" from the big players.
-
What you're asking for is convention over configuration. Which is what we have with things like Django, rails, etc.
-
By a major company, yes.
-
Why does it need to be by a major company? We have stuff like Angular, Polymer, React. I'm happy stuff like Ember exists despite not being by a bigco.
-
Not to mention vital tooling and infrastructure like babel webpack lodash, blah blah, and fire catching like vue.
-
Not sure Babel's the best example for you here - the (heroic) maintainers are chronically under-funded and overworked. Its one of the best examples of why I think the OSS model is so profoundly broken and un-maintainable.
- 2 more replies
New conversation -
-
-
I think the tweet kind of should be more about how the “community” has overly obfuscated front-end programming and raised the wall as a barrier to entry w/ complication, obfuscation, and lack of explainations.
-
Pretty please, if you have examples, and they are issues with our project (
#webpack), please don't hesitate to reach out. We want 0 of this across all our projects. -
You can start with better describing what exactly
#webpack is. Someone who does basic front-end javascript like interactions/animations, etc doesn't know what a "module loader" does or is. Does it run on the server to compile or in the browser? -
That is quite literally one of the biggest gripes I have with all of the various front-end tools. No one says the obvious, which is not really obvious in a world of new serverless/stateless programming.
-
Okay so honest question, how far back should we go? Because: If I say Module Bundler: => Let's you write modules that work in the browser You should write modules => Because people love organizing, preventing scope creep, etc. History of Modules => ???
-
Wow... I can't tell if you are asking for real or being sarcastic, because I don't think what I presented was *that* ridiculous.
-
No I'm being 100% serious!!! webpack exists to let you write modules that work in the browser, on top of that it has a set of other layers that you can add to it, but primarily a module bundler There is still a number of folks who've never used / written modules.
-
Something that one the inside that scares me, is that when we show webpack, and then teach people first: Modules, type of modules, and why you use webpack and it works the best with modules, then we lose people from diving too deep. So I really want to find the right middle.
- 9 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.