41–50 of 127 posts
A couple things I noticed when comparing to webpack: 1. This doesn’t bundle 2. This doesn’t support source maps
Come on, it clearly says it's not a bundler. > Also...Zwitterion is NOT a bundler. It eschews bundling for a simpler experience.
Earlier quoted context omitted.
This. It's funny tough, people are starting to pump giant runtimes over the air just to get C# running on the frontend, while people already complaining about JS bundle size smh.
Indeed, I tried Blazor and a simple Hello World page loaded about 7 megabytes of DLLs in the browser just to show some text.
Can anyone point me to a workflow where the cognitive load is similar to how it was in the good old days? i.e. some thing that does everything for me apart from the bit where I write application and presentation code? That mostly just works and doesn't require me to understand the whole stack. Because when I switch to other languages/environments I can most remain blissfully unaware of the plumbing that keeps the thi…
Which do you use?
Earlier quoted context omitted.
No they are not. Standard DOM API is not i their roadmap. There is no point of doing it when WASM has to be loaded by JS anyway. Currently DOM libraries using WASM are implemented by importing JS wrapper functions.
The interface types proposal will allow to call DOM APIs from WebAssembly directly [ https://github.com/WebAssembly/interface-types/blob/master/p... ] The point of doing it is of course performance.
Earlier quoted context omitted.
Vanilla JS? For most purposes I find that all these frameworks are simply unnecessary . As a bonus, all the debugging tools in Chrome work much better when there's no obfuscation or packing, and "recompiling" is just Ctrl-R. Code size and load speed is also massively better than it would otherwise be. Pages load instantly. It's nirvana, I tell you.
In my experience that results in the team building an inferior, untested, undocumented, and buggy version of React|Vue|jQuery|lodash. Now you need to train new peeps to handle that mess. And you haven’t even started solving actual problems. Provided you really need so much bulk at your disposal. But that’s a different story.
JQuery / lodash: we’re slowly getting better about modern browser availability and needing these less, but it’s a long road.
Earlier quoted context omitted.
Indeed, I tried Blazor and a simple Hello World page loaded about 7 megabytes of DLLs in the browser just to show some text.
Blazor (WASM) has not been released yet - they're working on optimizing payload size.
Earlier quoted context omitted.
Awesome with new ideas and approaches to things. Just because someone have taken time to solve things differently does not automagically imply that this is something that forces someone to throw old stuff out. Strange comment IMO.
I think he is pretty spot on. JS community is infamous for the constant replacement of tools with the next shiny thing, which are all built on a house of cards (one-line npm packages). I would rather see some more serious tools being put out and matured instead of this constant running around. My own personal theory is that because the barrier of entry is so low, people get a little too excited about being a contribu…
Earlier quoted context omitted.
But then you're forced to use React...and as soon as you need to do anything outside of what it provides it all falls apart which happens pretty quickly in my experience with it.
I’ve been doing React for years and haven’t experienced this. What kinds of apps are you building?
- runtime plugins
React is great if you stay in the design constraints, which is to be expected. This covers the vast majority of web apps.
edit: [removed svg snippets] I think I was confused with WebComponents not supporting svg elements that don't include the root tag
Earlier quoted context omitted.
But then you're forced to use React...and as soon as you need to do anything outside of what it provides it all falls apart which happens pretty quickly in my experience with it.
I’ve been doing React for years and haven’t experienced this. What kinds of apps are you building?
Angular and to a lesser extent Vue give you more direction.
This is of course not inevitable in a React project, but it does take good technical leadership not to be hindered by analysis paralysis before you even set off.
0 - An exaggerated summary of what I gather on various forum and discussions.
Webpack does more than just module importing though. Tree shaking, minification, uglifying, compiling SASS and a lot more.