Twitter | Search | |
@rem
Every single time I read `import…` in client side JavaScript, I get a little more pissed off that there's a hidden extra of adding the build tools to the process. And no, current import implementation support does not solve the `import x from 'someLib'` (and yes, importMaps…)
Reply Retweet Like More
@rem May 9
Replying to @rem
I mean…I kinda hope I'm not the last bastion of developers still writing "just JavaScript" for the browser. Maybe I didn't get an invite to the echo chamber.
Reply Retweet Like
Florian Gilcher ∠(・.-)―〉 →◎ May 9
Replying to @rem
I'm super frustrated of this regularly that every time I want to "just code", the environment is "just JavaScript" (a language which I can write quite well) + tons of build environments (which, as someone who doesn't write JS day to day) is hard for me.
Reply Retweet Like
xnoɹǝʃ uɐıɹq 🐻 May 9
Replying to @rem
Nah, just very few of us have the energy to argue obvious outcomes. Webpack/Babel ecosystem definitely popular but then again so is Nickleback.
Reply Retweet Like
John Nelson May 9
Replying to @rem
You are not alone. Definitely prefer to work with plain old JavaScript. Maybe it has to do with using JavaScript during a time where browsers supported almost nothing and transpiling code wasn’t even on people’s radars (pre coffee). We had no choice but lowest common denominator.
Reply Retweet Like
Ivan Čurić May 9
Replying to @rem
Not sure I follow. That's the standard ES6 import syntax which is supported everywhere.
Reply Retweet Like
Jeremy Keith May 9
Replying to @rem
Reply Retweet Like
pɾuɐıɹq May 9
Replying to @brianleroux @rem
😬
Reply Retweet Like
Haroen May 9
Replying to @_baxuz @rem
only relative ones will work out of the box in browsers though, not "bare" imports, like package names (yet)
Reply Retweet Like
xnoɹǝʃ uɐıɹq 🐻 May 9
Replying to @brianjd @rem
there's no accounting for taste ¯\_(ツ)_/¯ I'm sure everything will compile just fine in a few years..
Reply Retweet Like
Ivan Čurić May 9
Replying to @haroenv @rem
Gah didn't see the 2nd part of the tweet
Reply Retweet Like
@rem May 9
Replying to @haroenv @_baxuz
They're coming - which is useful. You can try it in Canary with an importMap file. Obviously mileage varies.
Reply Retweet Like
Jarrod Overson May 9
Replying to @rem
Every time I write import I get a little more pissed that IDE assistance and autocompletion wasn't considered in the syntax. An IDE can't help complete imports if it doesn't know where we are importing from until the end. All it would have taken was from "foo" import { bar }
Reply Retweet Like
Jake Dohm May 9
Replying to @rem
I mean, even if you're writing "just JavaScript" without any frameworks, imports are super useful, and way better (IMO) than the old way of manually making sure all of your scripts loaded in the right order 🤷‍♂️ I don't disagree that our tooling can get better, tho.
Reply Retweet Like
pɾuɐıɹq May 9
Replying to @brianleroux @rem
In a few years, trying to compile.... 🎶 How the hell'd we wind up like this Why weren't we able To see the signs that we missed Try and turn the tables I wish you'd unclench your fists 🎶
Reply Retweet Like
Anders Don Gissel May 9
Replying to @rem
Setting up the build pipeline can be tedious if you don't start from a boilerplate or make your own (as I did), but once it's set up properly, I couldn't live without it. Dynamically importing/codesplitting payloads makes conditional use of heavy dependencies so much easier.
Reply Retweet Like
David Humphrey May 9
Replying to @rem
This is one of the things that's bugged me about TensorFlow.js, with everything being `import` style.
Reply Retweet Like
Alexey Raspopov May 9
Replying to @rem
Do you use http server in development and some minifiers for production?
Reply Retweet Like
rektide de la fey May 9
Replying to @humphd @rem
While I am 100% as rubbed the wrong way as by the state we're in (suffering these modules-that-aren't-modular implementations), `import` syntax is still what I expect to see & prefer in any current codebase. I can't think of a single reason why anything else is ok anymore.
Reply Retweet Like
Ivar Nilsen May 9
Replying to @brianleroux @rem
I'm pretty sure there's a webpack plugin for turning nickelback into music
Reply Retweet Like