node-v0.x-archive VS samples

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.

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.

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.

setTimeout implementation: https://github.com/nodejs/node-v0.x-archive/blob/master/lib/timers.js

...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.

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...

Element Embedding demo source code

Source: https://github.com/flutter/samples/tree/main/experimental/element_embedding_demo :)

For a complete overview of M3 in Flutter, check out the official Material 3 Demo.

I've tinkered around with the https://github.com/flutter/samples/tree/main/add_to_app/android_view repository. I deleted the content of the dart files and replaced it with just a scaffold and button that connects to my method channel. I wrote a simple plugin which extends FlutterPlugin and Activity Aware the handle the method channel. My main problem seems to be, that the GeneratedPluginRegistrant.java file does not contain any references to my Flutter plugin. pub get within the Flutter Module doesn't add my plugin.

Simple state management, aka pragmatic state management, is based on Provider+ChangeNotifier. It's well documented, and there's a code sample.

That "toolkit" is basically a pubspec.yaml with preconfigured dependencies not including a game engine and some sample code how to use Firebase, Admob, and some other google services.

So it's been 3 days, since I started understanding the new Navigator 2.0 thing, and belive they were worst 3 days I have ever had with flutter, anyways I took nearly all of the code from this official repo.

I can respond to (c.) - We just released a navigation sample app, which demonstrates some common navigation scenarios. We are also actively researching routing and navigation APIs and will share more on that soon.