2,021 karma · joined July 18, 2011
This was the original:
https://en.m.wikipedia.org/wiki/Stargate_Project_(U.S._Army_...
TFA is about the apparent continuation of that same work from the 70s.
https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal...
Part of the awkwardness in the post is also mixing what looks like express with promises. I think using an async function as the handler with express 5 would probably feel a lot nicer.
I agree about CORS being frustrating. I think we should have allowed totally anonymous fetch requests across domains for saved to home screen PWAs (or with a permission prompt.) Missing that feature means you end up needing native apps for a lot of things that otherwise are totally reasonable web apps. CORS does make sense though because the alternative is drive by attacks against your local network from random web pages. And since the S in IOT stands for security that seemed like a bad idea at the time.
https://en.wikipedia.org/wiki/OpenBinder
It's more like a micro services framework that abstracts threads and processes.
Fuchsia takes the approach to the conclusion and powers the entire OS through a similar system:
I think folks forget how long ago we made Flutter.
https://github.com/facebook/hermes
https://x.com/tmikov/status/1869945330638442651
Btw that Angular history is backwards. The first versions of angular were written in JS back in ~2009. jQuery was the most popular way to build web apps, and Angular provided a (very fancy) declarative data binding framework over it. Everything ran in your browser by inspecting DOM attributes.
Later in ~2014 they built a new framework on similar principles in TypeScript, but with an AOT compiler and called it "Angular 2". Then they retconed the original framework "AngularJS" and made the 2+ framework be just "Angular". In that era some Ads folks forked the Angular 2 framework and rewrote it in Dart and the two frameworks evolved separately since.
So there's really 3 separate "angular" frameworks...
That depends on what the zero proof spirit is aiming for. I've found some of them are not very good alone because they're trying to replicate a particular flavor in the cocktail, but others (ex. Monday's Gin) are great with just ice. We keep a bottle of it around for a fun evening beverage.
The "savory non-tea zero proof beverage" for the evening is a difficult thing to come by. That's the space these fake spirits are trying to fill.
https://bigbangtheory.fandom.com/wiki/Wolowitz_Zero-Gravity_...
Space toilets are one of those things that are both critical and ignored in most depictions of space. Even in all the years of Star Trek they have "sonic showers" , but never depict a toilet.
It's amazing that NASA publishes this data in real time.
https://en.m.wikipedia.org/wiki/Smart_tag_(Microsoft)
https://stackoverflow.com/questions/2167301/what-is-the-purp...
https://alistapart.com/article/smarttags/
Response was extremely negative and the feature was removed. The only thing remaining is the opt-out meta tags all over the web.
(a) Element#matches
(b) Element#querySelector(All)
(c) By the engine for updating style and layout
The GP seems to be talking about (b), but even then browsers are checking each element one by one not advancing through the selector state machine in parallel for every element. (There's one exception in the old Cobalt which did advance the state machines IIRC).(a) and (c) are conceptually very similar except that when doing (c) you're checking many elements at the same time so browsers will do extra upfront costs like filling bloom filters for ancestors or index maps for nth-child.
In TFA they're doing .matches() which I would expect to be slower than a hash map lookup, but for a simple selector like they're doing (just tag name) it shouldn't do much more then:
(1) Parse the selector, hopefully cache that in an LRU
(2) Execute the selector state machine against the element
(2.1) Compare tagName in the selector
Apparently Nokogiri implements CSS in a very inefficient way though by collecting ancestors and then converting the CSS into xpath and matching that:https://github.com/sparklemotion/nokogiri/blob/e8d30a71d70b2...
https://github.com/sparklemotion/nokogiri/blob/e8d30a71d70b2...
I'd expect that to be an order of magnitude slower than what a browser does.
At first I thought maybe we should add a "hack" to cycle all the pods over 24 hours old, but then I wondered if making holiday freezes behave like normal weeks was really a hack at all or just reasonable predictability.
In the end folks managed to fix the leak and we didn't resolve the philosophical question though.
While this might be true in other industries, in big tech companies like TFA is talking about SWE promotions come with rather large increases in pay.
https://www.levels.fyi/?compare=Amazon,Facebook,Google&track...
The author was trying to go from L4 to L5. Promotions are also backwards facing, which means at the point you get promoted you're already doing the larger workload.
https://www.irs.gov/government-entities/tax-implications-of-...
https://eyeondesign.aiga.org/we-spoke-with-the-last-person-s...
It's now all done with properties on ElementInternals:
https://developer.mozilla.org/en-US/docs/Web/API/ElementInte...
They also decided not to ship AccessibleNode's which is unfortunate because it removed the clearest path for canvas+wasm based UIs.
https://cfdocs.org/coldfusion-versions
CF is interesting because it started as basically server side includes with some extra features to connect to a database. It was meant to be very approachable and not general purpose. Like a distant ancestor to Jupyter and Observable.
That approachability made for some big messes, but it also spawned a huge community of software developers who might not have gotten into it otherwise.
These days it feels a bit like boost is to modern C++. A monument to amazing engineering of the past, but something to keep in the archive.
It's one of the oldest, most stable, and never rewritten parts of the Gmail codebase.