3 ms·
That's the issue, Deno wasn't my first impression of typescript for the backend. Every decision I was took, there was a voice in the back of my head whispering,
by written-beyond 1y ago
That's the issue, Deno wasn't my first impression of typescript for the backend. Every decision I was took, there was a voice in the back of my head whispering, "it's probably easier on node". Not the actual code, but getting information about how to actually achieve those things.
The problem with making something as important as a package file optional it makes it very confusing for new users to get started because a variety of tutorials and getting started guides end up having a lot variation between them.
- bpev 1y agoI mean... I find deno.json-less scripts to be incredibly convenient for creating single-file scripts, and I've found deno configuration to be pretty clear. You're not wrong for disliking Deno; it has opinions, and those can turn people off. But I happen to find those opinions and decisions to be quite convenient and useful for me.