6 ms·

In 5 years? I think you misspelled weeks here. Last six months with my last employer I spent immersed in the full Next, React, Prisma ecosystem. I swear that 8

In 5 years? I think you misspelled weeks here. Last six months with my last employer I spent immersed in the full Next, React, Prisma ecosystem. I swear that 80% of developers' time was wasted on fighting compatibility issues. Actual work happened in the small crevices of time left between endless stream of build breakages or chasing random bugs caused by changes in transitive dependencies. My God, never again.

ravenstine 4y ago
Next is the worst name for a JavaScript framework. It might as well be called "yet another JS framework." It's things like this that make me ponder self deletion. So much pointless work we create for ourselves.
- fijiaarone 4y ago
  It’s layers on top of layers on top of layers, etc. I’m looking for a framework that compiles to web assembly to generate next.js to spit out react components that generate JavaScript that prints html.
  - Nextgrid 4y ago
    In the era of Yarn, Bower, etc I was joking that we need package managers for package managers.
    - flatcakes 4y ago
      I just learned about Volta today...
      - SenHeng 4y ago
        Let me introduce you to asdf. No, that is not a typo. https://github.com/asdf-vm/asdf https://github.com/asdf-vm/asdf
josephg 4y ago
I feel like es modules have killed javascript. They have enough momentum that everything supports them (or needs to support them). But they’re not good enough, or compatible enough to actually integrate well. Recent example: bundler X insists on import statements including file extensions. But the typescript compiler refuses to let you import foo.js and won’t rewrite an import of foo.ts to foo.js when you build. There’s giant GitHub issues about this but nobody wants to fix it on their end. In short, everything is awful. Writing javascript in the browser used to be just the same as nodejs, with the exception that you needed a bundler like browserify - which mostly just concatenated everything together. Now I dread setting up new projects. Will typescript work with svelte? Will this webassembly module work with rollupjs? Will it pull in my type definitions correctly? Will the url path system magically work or break? Urgh. I feel like I’m no longer competent enough to get arbitrary tools working properly together. We need bespoke build systems now because it seems like they’re the only thing that works any more. And that means I can’t throw together a simple server side rendering system like I used to be able to do. Bryan Cantrill once joked that javascript was the failed state of programming languages. That doesn’t feel like much of a joke any more.
- RedShift1 4y ago
  I once set out a simple goal, instead of shipping a production Node package with all the js files and node_modules, just have it all in one js file that can be executed by Node. After trying several compilers and messing with their settings, I ultimately failed exactly because of the different ways to import/export modules. My own code was all esm with .mjs files, but many npm libraries aren't so basically you're stuck.
  - fragile_frogs 4y ago
    https://github.com/vercel/ncc https://github.com/vercel/ncc
    - RedShift1 4y ago
      Tried that one too, failed me as well and I recall correctly due to a different reason. However I see there have been new releases, maybe it's time to try again.

ravenstine 4y ago

Next is the worst name for a JavaScript framework. It might as well be called "yet another JS framework." It's things like this that make me ponder self deletion. So much pointless work we create for ourselves.

fijiaarone 4y ago
It’s layers on top of layers on top of layers, etc. I’m looking for a framework that compiles to web assembly to generate next.js to spit out react components that generate JavaScript that prints html.
- Nextgrid 4y ago
  In the era of Yarn, Bower, etc I was joking that we need package managers for package managers.
  - flatcakes 4y ago
    I just learned about Volta today...
    - SenHeng 4y ago
      Let me introduce you to asdf. No, that is not a typo. https://github.com/asdf-vm/asdf https://github.com/asdf-vm/asdf

josephg 4y ago

I feel like es modules have killed javascript. They have enough momentum that everything supports them (or needs to support them). But they’re not good enough, or compatible enough to actually integrate well. Recent example: bundler X insists on import statements including file extensions. But the typescript compiler refuses to let you import foo.js and won’t rewrite an import of foo.ts to foo.js when you build. There’s giant GitHub issues about this but nobody wants to fix it on their end. In short, everything is awful. Writing javascript in the browser used to be just the same as nodejs, with the exception that you needed a bundler like browserify - which mostly just concatenated everything together. Now I dread setting up new projects. Will typescript work with svelte? Will this webassembly module work with rollupjs? Will it pull in my type definitions correctly? Will the url path system magically work or break? Urgh. I feel like I’m no longer competent enough to get arbitrary tools working properly together. We need bespoke build systems now because it seems like they’re the only thing that works any more. And that means I can’t throw together a simple server side rendering system like I used to be able to do. Bryan Cantrill once joked that javascript was the failed state of programming languages. That doesn’t feel like much of a joke any more.

RedShift1 4y ago
I once set out a simple goal, instead of shipping a production Node package with all the js files and node_modules, just have it all in one js file that can be executed by Node. After trying several compilers and messing with their settings, I ultimately failed exactly because of the different ways to import/export modules. My own code was all esm with .mjs files, but many npm libraries aren't so basically you're stuck.
- fragile_frogs 4y ago
  https://github.com/vercel/ncc https://github.com/vercel/ncc
  - RedShift1 4y ago
    Tried that one too, failed me as well and I recall correctly due to a different reason. However I see there have been new releases, maybe it's time to try again.