4 ms·

Yup. And the fact that you don’t need a build system is one of the things that makes JavaScript so great. Of course, lots of people add build systems to their

Yup. And the fact that you don’t need a build system is one of the things that makes JavaScript so great. Of course, lots of people add build systems to their JS projects, but you don’t NEED one. I spent the last five years writing a web development toolkit that lets me keep doing JS work without any build step. It’s been a lot of work but it’s so dreamy. I hardly have to worry about a black box ever. My sites start more or less instantly. If anything is wrong anywhere in the system I just put a breakpoint and trace execution. There are no “artifacts” to puzzle over. It’s the best. Check out browser-bridge on NPM if anyone is interested.

tuesdayrain 7y ago
So you don't minify any of your JS?
- erikpukinskis 7y ago
  No need to, HTTP responses are compressed already. Also it makes debugging production issues a nightmare. Minification helps a tiny bit with client side memory too I guess, and parse time. But I save so much memory by not putting random pointless crap into the browser environment from web pack, Babel, etc, that’s where I want to make my savings. Not shaving a couple chars off a variable name.
  - mruts 7y ago
    There's no way minified js plus compression isn't smaller than just compression alone. It's not possible.
    - erikpukinskis 7y ago
      For sure, it gets you some of the way there. I make up for the rest by not using Webpack or Babel.
yawaramin 7y ago
Have you checked out https://www.pika.dev/cdn https://www.pika.dev/cdn ?
- erikpukinskis 7y ago
  Interesting! Not useful for me because I target 100% browser compat. I try to code in ES5 exclusively. I don't like leaving poor folks with old computers in the dustbin.
  - yawaramin 7y ago
    That's very ambitious. Good luck.
Too 7y ago
The reason JS works everywhere is that mozilla went through the effort to ensure their JS engine compiles and runs everywhere. JS operates on a much high level of abstraction. Or, ask someone from a undeveloped country why they go fetch water from the local well when you can just pour some from the tap?

tuesdayrain 7y ago

So you don't minify any of your JS?

erikpukinskis 7y ago
No need to, HTTP responses are compressed already. Also it makes debugging production issues a nightmare. Minification helps a tiny bit with client side memory too I guess, and parse time. But I save so much memory by not putting random pointless crap into the browser environment from web pack, Babel, etc, that’s where I want to make my savings. Not shaving a couple chars off a variable name.
- mruts 7y ago
  There's no way minified js plus compression isn't smaller than just compression alone. It's not possible.
  - erikpukinskis 7y ago
    For sure, it gets you some of the way there. I make up for the rest by not using Webpack or Babel.

yawaramin 7y ago

Have you checked out https://www.pika.dev/cdn https://www.pika.dev/cdn ?

erikpukinskis 7y ago
Interesting! Not useful for me because I target 100% browser compat. I try to code in ES5 exclusively. I don't like leaving poor folks with old computers in the dustbin.
- yawaramin 7y ago
  That's very ambitious. Good luck.

Too 7y ago

The reason JS works everywhere is that mozilla went through the effort to ensure their JS engine compiles and runs everywhere. JS operates on a much high level of abstraction. Or, ask someone from a undeveloped country why they go fetch water from the local well when you can just pour some from the tap?