Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
Deno's interactive permission prompt is still easily bypassed by nicely asking terminal to confirm it:
https://github.com/denoland/deno/issues/9750#issuecomment-79...
Direct link to asciinema:
Just like you did in the browsers back in the day when you imported code from URLs with , the "deno way" is supposed to follow browsers in these regards as well.<p>And you can always use `npm`, `node_modules` and `import maps`[0][1][2] to kind of mimic "nodejs way".<p>[0]: <a href="https://wicg.github.io/import-maps/" rel="nofollow">https://wicg.github.io/import-maps/</a><p>[1]: <a href="https://blog.logrocket.com/es-modules-in-browsers-with-import-maps/" rel="nofollow">https://blog.logrocket.com/es-modules-in-browsers-with-impor...</a><p>[2]: <a href="https://deno.land/manual/linking_to_external_code/import_maps" rel="nofollow">https://deno.land/manual/linking_to_external_code/import_map...</a>
There's the web APIs which are tested against https://github.com/web-platform-tests/wpt (albeit without full coverage), and there is ffi/plugins - for deno specific things like readFile.
I don't know the history of Node... but why would there need to be a diversion?
> How would e.g. a company like CloudFlare run Deno instead of v8 for it's serverless infrastructure?
Raptor is an example project which does that: https://github.com/littledivy/raptor
deno_runtime crate provides high level abstractions which you can use to execute code for deno. It has full support for deno namesake ops, I think.
As for getting started, you can go through the manual: https://deno.land/manual
The most updated webview bindings I know of for deno: https://github.com/webview/webview_deno
It's likely you will find some hiccups in latest deno release because it uses rust plug-ins and they are getting overhauled at the moment. Maybe a few more months before getting stabilized.
I was referring to node <0.1.30[1] which did have promises for a while. largely from jQuery deferred, which were ungood in a couple ways I don't remember. but also remarkably similar.
I still largely think kris kowal building the "Q" promise library is what made promises interesting, what surfaced the idea that we might want to first-class our completeablea/futures. I know kris had some specific inspirations but I forget what.
pains me somewhat to this day that promises ultimately became somewhat un-value like, that handlers don't get to see what it was resolving. all the chain/spawn discussion, the functional promise folk: they got rolled by those insisting we had to target only the lowest rings of the developership, and that allowing more potent systems was unacceptable. wish I could find those es-discusa threads, for the powerful sorrow of the afteath, what we are stuck with, in it's so lites form, haunts me. especially as we double back a decade latter & invent controllers & signals toanage our promises. which we would have had for free.
way off topic now. forgive me my late night ramblings.
[1] https://github.com/nodejs/node-v0.x-archive/blob/v0.1.30/Cha...
I have only seen Dart code in Flutter code bases, and my comment here might be the result of incomplete knowledge. However, from what I can see, Dart seems to resemble the Java way of doing things a lot. Specifically, the over-use of is-a inheritance.
Just scrolling through the list of examples in the Flutter samples directory illustrates this point.
https://github.com/flutter/samples
Use of inheritance seems to be the canonical way of doing things in Flutter and it seems to permeate the code base, both in the use of core Flutter APIs as well as associated library ecosystem. I find them rather hard to read and reason about. It's easy to be a bit confused on encountering a function in an object that inherited the function from a superclass 3 levels up in the hierarchy.
To be clear, I completely recognize that it's unfair of me to attribute to Dart (the language) issues/patterns I see with a library/framework ecosystem (Flutter). But this is mitigated by the fact that Flutter is by far what the lion's share of Dart code is written for.
If you want to do this with node, pkg exists.
https://github.com/vercel/pkg