4 ms·
Deno is moving into a similar space as Kotlin started at by adding all this interop—they're trying to be the "better Node". Meanwhile Kotlin is frantically tryi
by lolinder 3y ago
Deno is moving into a similar space as Kotlin started at by adding all this interop—they're trying to be the "better Node". Meanwhile Kotlin is frantically trying to differentiate itself because Java is closing the gap, but it's hard for them to do because they've spent so long piggybacking on the Java ecosystem.
Deno is very vulnerable to the same fate. Yes, it's easier to get adoption if you can plug into an ecosystem that is already popular, but then it's not your ecosystem and the behemoth that actually owns the ecosystem will feel the threat and adapt.
If you don't prioritize interop, your initial adoption will be much much slower, but if you make it out of the early stages you have an ecosystem of your own that has its own distinct advantages. The incumbent can't just pull in a few good features and thereby take your mind share.
- jrsj 3y agoDeno Deploy is the killer feature for me, and it’s ultimately the main product of Deno, Inc. too. Node support just makes it easier to get existing software running there. I don’t think it will suffer the same fate as Kotlin because a lot of the value add is in Deploy, Deno KV, etc.
- sisve 3y agoWhat do you mean by "same fate as kotlin"? I would say Kotlin is doing great. Anything I missed?
- triyambakam 3y agoYou missed the parent comment this is in reply to
- sisve 3y agoYeah 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?
- lolinder 3y agoParent here, and I'm writing as someone who loves Kotlin and much prefers it to Java. 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.
- strangescript 3y agoHave you use vercel before?
- eropple 3y agoHave you used Cloudflare Workers? How does Deno Deploy stack up, if so?
- golergka 3y agoThis may be bad for Deno if Node will close the gap and okay if it doesn't, but both cases are good for users.
- mark_and_sweep 3y agoPersonally, I haven't heard of any Kotlin devs going back to Java nor of any Deno devs going back to Node.
- spixy 3y agoI have inherited Deno web app in my job and I cannot wait to migrate it to Node
- strangescript 3y agoGenuinely curious the motivation here
- eropple 3y agoI'm not the OP, but I've built a little bit of software [0][1] in Deno. I don't know if I'd do it again. Thoughts, in no particular order: - Big plus: the built-in stdlib is strong (coming from Node; it's not as strong as Python or even Ruby, but I'll take what I can get). The stdlib is also pretty "good Unix citizen" focused--it's very easy to build an ergonomic command-line application. - Theoretical plus: the capabilities-based security model is smart and cool. - In-reality minus: you end up passing most `--allow` flags anyway for anything that isn't trivial. It could scope down to specific modules if you are a tryhard, but I am not sufficiently a tryhard, and this really should just be within the capability of Deno to figure out and recommend for you. - Moderate plus: `deno compile` being built in is nice, and it is easier than the Node `pkg` library from Vercel. - Small minus: The set of targets for `deno compile` is limited, though, and (for reasons that are both reasonable and unfortunate) it spits out truckasaurus-sized executables, which is a bummer. - Enormous, world-stopping minus: dependency management. It's bad, and it's not easy to get around. "Just put all your deps in a TypeScript file and export it" is not the amazing solution that its adherents want you to think it is. The developer experience of upgrades is annoying and unpleasant and `deno-upgrade` helps but makes your project feel out-of-control. (Import maps don't really help, it's just another road into the same unpleasantness and since they don't work if you're writing a library I don't think you should ever use them at all; just stay consistent between applications or libraries.) - Whiny minus: VScode support is pretty bad. It exists, but it's not great, and there's a weird lag to dependency management that I never figured out. - Real minus: the Deno VScode stuff freaks out when you use a Node project, even if you set `deno.enabled: false` in your .vscode/settings.json file. There are definite, real benefits to some of what Deno does. But I just don't see why I'd continue to use it over Just Continuing To Use Node. [0] - https://github.com/eropple/tmuxed https://github.com/eropple/tmuxed [1] - https://github.com/render-oss/render-cli https://github.com/render-oss/render-cli
- debaserab2 3y agoThe way I see it, if Deno only ever existed to push node to do better that in itself is a universal win for everyone.