91–100 of 112 posts
Earlier quoted context omitted.
Something along the lines of > docker run -it --rm -v "$PWD":/app -w /app node:18 node main.js It's a tad longer but it's more flexible too ;)
Of course, now you have to boot and run an entire VM on your MacBook, just to run that one Node.js program.
Earlier quoted context omitted.
Yep. I saw Deno as intended to be a platform for new projects that want to start fresh without all the legacy cruft from Node. Somewhere along the way they decided it was a priority to be able to transition legacy Node projects to Deno, and I'm afraid that what's going to happen is it will freeze the ecosystem's development of independent solutions in favor of just using Node libraries for everything.
I don't think this will happen. People _love_ cutting edge innovation. Cutting edge innovation happens on cutting edge platforms, not in the legacy.
Only the people who like having to rewrite everything with every breaking change that happens on cutting edge platforms. It's not all that fun for most people. I'll wait until "new shiny" isn't as new and shiny, when it finally becomes stable and dependable. Until then the current stable platform is what I'll continue building on because it still does everything I need it to do.
Earlier quoted context omitted.
What do you mean by "same fate as kotlin"? I would say Kotlin is doing great. Anything I missed?
You missed the parent comment this is in reply to
Earlier quoted context omitted.
Of course, now you have to boot and run an entire VM on your MacBook, just to run that one Node.js program.
Ah yes, I always forgot some people don't use Linux as their OS to develop. That always seems weird to me because then they have to launch VMs each time they want to simulate their target OS :D But I do see your point :)
Earlier quoted context omitted.
Ah yes, I always forgot some people don't use Linux as their OS to develop. That always seems weird to me because then they have to launch VMs each time they want to simulate their target OS :D But I do see your point :)
As if docker doesn't run a VM on Linux when you invoke that one liner.
Earlier quoted context omitted.
Ah yes, I always forgot some people don't use Linux as their OS to develop. That always seems weird to me because then they have to launch VMs each time they want to simulate their target OS :D But I do see your point :)
Being a developer!== Linux.
Earlier quoted context omitted.
Sad such a reasonable question is downvoted, lol. I agree with the sentiment. It's expected any development would want to have the highest reach, which means Node. If Deno supports node features, and node does not support deno clearly the logical conclusion is that features will be node-first, with deno expected to support it anyway. Thus leading to the question of why even bother with Deno? Deno does have some benef…
> Thus leading to the question of why even bother with Deno? 1. Native support for TypeScript. 2. Better built-in APIs. 3. Security model. 4. Easy package management. Node.js is closing the gap. E.g. top-level await, fetch() API, Permissions. I believe Node.js will follow Deno and implement more and more features. Sort of a npm/yarn situation. It's cool to see what Deno does, but I don't think you will be left out by…
Earlier quoted context omitted.
You missed the parent comment this is in reply to
Yeah i guess i kind of did., I should have asked the parent comment. I'm not a java/kotlin developer but for me it looks like kotlin is thriving. Is that not how it looks for insider's?
Kotlin is doing fine, but its growth has slowed a lot and the team is pivoting rapidly to multiplatform to try forge a niche that isn't just "better Java". That pivot isn't smooth because most Kotlin code—even the standard library—depends heavily on the JVM and Java libraries.
I didn't mean "fate" to imply that Kotlin as a language is dying, just that their position as "better Java" is no longer tenable and they've had to shift strategy dramatically to try to stay relevant. That's what I'm afraid will happen to Deno as Node catches up.
Earlier quoted context omitted.
Interesting theory ;)
Easily proven by happy consumers on Apple, Microsoft, Sony and Nintendo devices. Or the millions of daily passengers in transport mechanisms powered by high integrity operating systems.