211–220 of 235 posts
Deno Deploy dropped from 35 GCP regions to just 12: https://news.ycombinator.com/item?id=39127598
If anyone from Supabase is reading here, your main marketing page still says Edge Functions run on 29 regions. Since they run off of Deno Deploy, it seems like this needs updating.
Earlier quoted context omitted.
You download it to you game rig, not some cloud solution with limited resources to be paid for. Plus you may want to have more than one instance of service running.
Pretty much all cloud services offers way more than that for free and besides, maybe don't use javascript if 100mb is such big of a deal?
And we were not talking about js, we were talking about Deno specifically. And about binary growing year to year notably.
>Pretty much all cloud services offers way more than that for free
More than what? The question is always about difference in %. The number of services\instances can grow faster than you can rewrite your conde in go\c++\rust of whatever (not to mention you will have to hire people for the task). And all of a sudden this x3-x4 difference matters.
Earlier quoted context omitted.
> a11y I apologize for this being so besides the point of your post, but I hate this trend so much.
Yes it’s awful, “A eleven Y” or is it “A one one Y” Is stupid, inaccessible and the people who use it and came up with it should feel bad.
Seems like good acronym semantics no?
Earlier quoted context omitted.
Yes it’s awful, “A eleven Y” or is it “A one one Y” Is stupid, inaccessible and the people who use it and came up with it should feel bad.
a11y is similar to Andreessen Horowitz => a16z in that there’s exactly 16 letters in between the first letter and the last. Seems like good acronym semantics no?
Earlier quoted context omitted.
What does that mean, though? Does Deno create an HTTP server in Rust directly?
A ton of NodeJS modules are not part of V8 at all, like "fs" or "path" because those don't really make sense in a browser context. Basically everything that is not a W3C standard is probably not implemented in V8. Like, for example, I recently found out that there are 3 separate ReadbleStream objects in NodeJS, one from "stream" (older one used in Request), one from "stream/web" (W3C standard, used by global.fetch())…
Those API could be thought as from the "environment" in which JavaScript run. For example we often call web-only APIs "DOM API": `fetch`, `xmlHttpRequest` and so on.
Node.js also has its own environment. For example both `setTimeout` and `setInterval`, though present in both web and node.js, are implemented differently by browsers and node.js (it's just that node.js decided to go with roughly the same API - see below for code examples for both).
Taking requests as examples there are both declared in blink, the rendering engine and not v8 again because they aren't JS:
- fetch (https://source.chromium.org/chromium/chromium/src/+/main:thi...)
- XMLHttpRequest (https://source.chromium.org/chromium/chromium/src/+/main:thi...)
For the fun of looking even more at some code of reputable projects: for setTimeout / setInterval, I would guess they are declared here in blink: https://source.chromium.org/chromium/chromium/src/+/main:thi...
And maybe here for Node.js: https://github.com/nodejs/node/blob/8a41d9b636be86350cd32847...
To note that "filesystem" API also exist in web world: https://fs.spec.whatwg.org
Again, this API is completely different than in Node.JS
Earlier quoted context omitted.
I actually found this worrying, since it means they are not committed to make NextJS work nicely, quite the opposite they now have incentive to not make it happen
Bartek from the Deno team here - we are actively working on improving experience running NextJS projects in Deno.
what is a great comparison between Bun, Deno, and Node.js? Why should I choose Bun over Deno or vice versa?
Deno has built-in support for TypeScript. Deno has members in Ecma TC39, so they take part in the development and standardization of JS. Deno brings a new mentality to development focused on simplifying things, whereas Bun aims to be an improved Node. Deno aligns with web APIs: you can use the same APIs in the browser and in Deno. Many packages work in both platforms. Deno is even in the compatibility tables in MDN.…
Most of Deno's code is actually V8 in C++
Earlier quoted context omitted.
Aren't a lot of abbreviations unintuitive until you learn what they mean? Didn't we just have a thread the other day about the meaning of "MDN" - which also many people didn't know. I see on this site "IMO" "FWIW" "IANAL" "TLDR" all the time. You generally can't tell what these mean either without looking them up or just knowing already because of them being so engrained in culture.
No it’s not the same, a11y creates a dissonance in the mind because part if it wants to see it as “ally”, the other part wants to see it as “A eleven Y” and the other part cringes and thinks its stupid.
Earlier quoted context omitted.
> FLTK and other libraries cannot be used from JavaScript. What's the obstacle to using it via FFI (which Deno seems to support)?
Someone has to first write bindings to the library using said FFI. This is not something most JavaScript dev can do. This has to be written by someone who knows C++ and JavaScript, and be good at both to understand all the details. (How the two interacts, how the lifetime of C++ objects play with the garbage collector, how do the inventloop mixes, ...) Writing such binding is a huge work as they the whole API need to…