51–60 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.
Earlier quoted context omitted.
I think they should get a reasonable return. Deno has a lot of hype and Node has a lot of cultural weight, as does Ryan himself. Not sure about unicorns though! It does not seem like a unicorn product, but I'm not a VC
You don’t get $21M from investors for nothing. They will force the square peg through the unicorn-shaped hole - or kill the company trying
Do you think that investors see every company that isn't a unicorn as "nothing"? I think you're living in a fairytale
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…
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` built-in by default, and generally follows browser standards around interfaces like Request, Response, etc. Instead of needing a complicated build process to make Node code work on the browser, now we have a complicated build process to make Deno/Browser code work on Node. ¯\_(ツ)_/¯
Comments are a bit negative. I for one think they are onto something here. Surprised it's only 21M. I would have expected in these market conditions to beef up more for the next 2-3 years.
Indeed, especially when you compare with a company such as Supabase (which is working on way less interesting technology imho) who just raised $80M: https://news.ycombinator.com/item?id=31328783
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…
are there real-world, commercial products actually running on """serverless""" architecture? no matter how much I think about that whole concept, I see no application for it that couldn't be done better, faster and easier with regular tools
> Cold start (time to first response, ms) O(100) O(1000) O(10000) I think ~100 ~1000 ~10000 would be clearer than using the big O notation, since this has nothing to do with fuinctions.
If it’s big O notation, it makes no sense because O(10000)=O(1000)=O(100)=O(1).
> 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?
I am an optimist in that I (have started to) believe that this slowly allows us to converge on better solutions for everything.
PHP was easy to set up, easy to host, easy to understand and easy to build stuff with, but it resulted in an unmaintainable mess over the long run.
Then Node was all of that, but JS was a better language than PHP. Then Node grew warts in the form of the clutter that is npm, then it grew complex build systems and unstable libraries.
Now there's Deno. It uses TypeScript by default, which is a surprisingly useful and productive language, it rethinks some things, it's much more secure by default, and now we're back at the PHP-level easiness to host using Deno Deploy.
We've ended up with an overall better solution and it only took us 20 years :)
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.
Surprised this is the case because I use their Rust v8 bindings on an ARM laptop almost every day. Have you tried building it from source?