| ▲ | rovingeye 4 days ago |
| It was the first thing I tried and of course it didn't work. It might finally be time to switch to Deno or Bun =( |
|
| ▲ | chamomeal 4 days ago | parent | next [-] |
| I switched to deno for new projects ~1 year ago and it’s only been joy. There’s a shockingly small amount of friction to switch over, and there are so so many benefits |
| |
| ▲ | steve_adams_86 4 days ago | parent | next [-] | | I have only one issue I've encountered with Deno that mattered (so to speak) and it's probably my fault. I actually created an issue for it (https://github.com/denoland/deno/issues/30433). My project config is weird (slightly more sophisticated that my repro), so, it's probably on me. Otherwise I absolutely love Deno. It makes TypeScript simple and joyful. It's the simplicity this language/tooling ecosystems badly needs in my opinion. Sometimes I feel like it makes TypeScript feel a bit more like working with Go; you can just throw a main.ts in there and build an excellent CLI from it in minutes. | | | |
| ▲ | throwanem 4 days ago | parent | prev [-] | | I'm glad you've said this. I have a project at nearly a perfect point to try out that cutover. Not that it isn't nice to understand the circa 2018-2022 TS stack, but it sure would be nice not to have to. (Our ancestors had the same discussions about cfront(1). Everything old is new again.) |
|
|
| ▲ | preommr 4 days ago | parent | prev | next [-] |
| > It might finally be time to switch to Deno or Bun =( Bun has been great. Deno... perhaps the less said, the better. |
|
| ▲ | agrippanux 4 days ago | parent | prev [-] |
| Bun has been awesome for me and my team fwiw |
