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. Learn more →
Node-v0.x-archive Alternatives
Similar projects and alternatives to node-v0.x-archive
-
-
-
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.
-
-
cli
Snyk CLI scans and monitors your projects for security vulnerabilities. (by snyk)
-
-
-
-
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.
-
-
wpt
Test suites for Web platform specs — including WHATWG, W3C, and others
-
webview_deno
🌐 Deno bindings for webview, a tiny library for creating web-based desktop GUIs
-
cross-project-council
OpenJS Foundation Cross Project Council
-
raptor
Discontinued Asynchronous serverless engine powered by Deno (by littledivy)
-
deno-udd
Update Deno Dependencies - update dependency urls to their latest published versions
-
nodejs-advisory-board
Discontinued Meeting Minutes and Working Group Discussions
-
native-messaging
Native Messaging Host Protocol for Browser Extensions
-
-
node-convergence-archive
Discontinued Archive for node/io.js convergence work pre-3.0.0
-
RaceLogic
Designs, infrastructure, and experiments around Race Logic
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
node-v0.x-archive reviews and mentions
-
Wizards of Opensource, Ep 1: Ryan Dahl
On 16 February 2009, a GitHub commit was made. By a person who would later turn out to be the creator of two of the most successful, impactful, and standard tech platforms the world has ever seen. Who is he? Let's explore.
-
Stop Wasting Connections, Use HTTP Keep-Alive
Based on several issues in the Node repository (nodejs/node-v0.x-archive#7729, nodejs/node-v0.x-archive#5488, nodejs/node#5436) this error can occur when a DNS server fail to respond, perhaps due to it rate-limiting requests. Reducing DNS lookups can reduce or eliminate these errors.
-
Why does RSS constantly grow when reading data from a child process and calling process.stdout.write()?
I don't know how node is processing the stream and buffering or not buffering. I just invested the past few hours into researching Node.js buffering and not buffering read(). There are more than one issue regarding the subject-matter, e.g., https://github.com/nodejs/node/issues/2972, https://github.com/nodejs/node-v0.x-archive/issues/4000, https://github.com/nodejs/node/issues/6379. From what I gather Node.js blames the process itself. However, I run the same algorithm using Python, C++, C, QuickJS JavaScript engine where the RSS does not exponentially increase during usage.
-
I am proud to announce, a new Sorting algorithm!
setTimeout implementation: https://github.com/nodejs/node-v0.x-archive/blob/master/lib/timers.js
-
Why console.log(this) prints an empty object when used in the global context? Shouldn't it point to the global object?
...or something similar to that. I mean, it's pretty close to that. You can see for yourself if you want. These lines there are exactly what they do: They set thisValueto point to module.exports and then they execute your file/module with that as the value of this. (Only they have some additional helper stuff like ReflectApply because there are some additional complexities now with modules. In the older versions of the code you could see the apply call directly there.
-
Deno 1.9 – native http2, performance boost, blob and import completion support
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...
-
A note from our sponsor - InfluxDB
www.influxdata.com | 17 Apr 2024
Stats
Popular Comparisons
- node-v0.x-archive VS samples
- node-v0.x-archive VS raptor
- node-v0.x-archive VS webview_deno
- node-v0.x-archive VS deno-udd
- node-v0.x-archive VS nodejs-advisory-board
- node-v0.x-archive VS node
- node-v0.x-archive VS agentkeepalive
- node-v0.x-archive VS wpt
- node-v0.x-archive VS Apache Kafka
- node-v0.x-archive VS pkg