71–80 of 397 posts
The color changing on this page gives me a migraine: https://deno.com/deploy I like Deno in principle, but I'd love to see how Slack, Github and Netlify are using it.
> Early in cloud computing, virtual machines were the compute abstraction […] This is funny to me because serverless sounds to me like the return of PHP (etc) shared hosting. What's old is new again?
It’s amusing to see a whole generation of senior developers (“senior” as in 5+ years of experience) that haven’t experienced web development without React[0] and who proceed to reinvent PHP/ASP.NET/RoR. [0] Used here as shorthand for “modern js driven development”
Nobody is reinventing PHP or RoR development. What is happening is the community taking all our favorite parts of these stacks and combining and implementing them in ways that facilitate a dev experience that we could only have dreamed of back in the PHP/RoR days.
- Senior dev that started off in the PHP and then RoR days
What does O(100) mean in the comparison table?
Interesting how this will play out. It's an ambitious goal to consolidate client side and server side javascript ecosystems which is quite fragmented today. On the other hand, this may only increase fragmentation further by introducing another target to develop for (wait for transpilers that can automagically convert between deno and node code). I will always look at javascript as this problem kid that cannot get its…
There is already a system for building a NPM node package from a Deno package, called dnt (deno to node). It's maintained by some Deno team members. Here's a blog post they wrote about porting "Oak" (a deno HTTP server framework) to Node: https://deno.com/blog/dnt-oak The nice thing about Deno conceptually, is that it's much more similar to the browser platform than node is. It uses ES6 only, has things like `fetch`…
This question is going to make me sound like a jerk, but why do you want to write your back-end in JS? Deno looks like a great improvement over node.js, but I don't feel compelled to use it. It seems like people jumped to node based on some performance promises that didn't really pay off (IMO). And since then, we have newer options like Rust, Go, and Elixir as performant back-end options, and even older choices like…
I'm coming around on Elixir.
I never want to write Go that interacts with a database again.
Rust seems complicated. I don't think I'm smart or committed enough to get anywhere with rust.
Somebody doesn't understand O notation.
I played with an early version of Deno a few years back and it was already way more comfortable to use than node. It's a real counterexample to second-system syndrome. The only reason I didn't continue was a lack of ARM support.
+ People get paid, hopefully a few even get big $. - Investors want unicorn returns. Good luck!
I love Deno and want it to succeed, but it doesn't feel like a unicorn, and I'm worried about it being expected to become one
This question is going to make me sound like a jerk, but why do you want to write your back-end in JS? Deno looks like a great improvement over node.js, but I don't feel compelled to use it. It seems like people jumped to node based on some performance promises that didn't really pay off (IMO). And since then, we have newer options like Rust, Go, and Elixir as performant back-end options, and even older choices like…
FWIW, I think Typescript would make an even stronger case. And I think(?) that's one thing Deno is trying to do.
Earlier quoted context omitted.
Not to take away from the rest of your message, I thought you wanted to get up to speed on that `fetch` is now available in nodejs core since version 17 or something like that (think it got included early this year).
I think this requires the `--experimental-fetch` command-line argument (per https://nodejs.org/tr/blog/release/v17.5.0/ ), so I don't think it qualifies as "by default".
(node:340760) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)