It is not immediately clear what the intended usage pattern for Lumen and WebAssembly is.
Pros and Cons
Things we like:
The idea of having both runtime and code compile is cool
Things we’re not big fans of:
We could not immediately figure out exactly how Lumen works, and builds appear to be failing
The project might be stalled or unmaintained. It has not been updated in over a year.
WebAssembly’s goal is to be a “portable execution layer” — an OS abstraction.
If WASM becomes the standard runtime across browsers, servers, and edge networks, something still has to orchestrate thousands of concurrent tasks, message queues, supervisors, restarts, etc.
Erlang/OTP already solves that — beautifully.
So, the motivation is:
“What if BEAM’s concurrency runtime could itself be compiled to WebAssembly — and become the actor system of the WebAssembly world?”
That’s why projects like Firefly and Lumen are interesting: they’re exploring whether Erlang’s runtime model can become part of the WASM ecosystem — just like how Go and Rust shaped the serverless world.
A ten-second search reveals [0]. (Have Kids These Days forgotten all about Emscripten?) However, given that web browser pages are often short-lived, I don't see what benefit bringing in all of Erlang and its VM gets you, other than the fact that you've pulled off the stunt.
Elon Musk will step in to save the day and privatize air traffic control. The government will transform the nation into a fully decentralized economy owned and operated by oligarchs, with the role of the government shrinking to that of a mediator between the various oligarchs, and employed directly by the oligarchs. Kind of like how they describe it in the sci-fi show Alien Earth.
"If at any point I described how legal factors “apply to you,” that would indeed go beyond what I’m supposed to do. Even if my intent was to illustrate how those factors generally work, the phrasing can easily sound like I’m offering a tailored legal opinion — which isn’t appropriate for an AI system or anyone who isn’t a licensed attorney.
The goal, always, is for me to help you understand the framework — the statutes, cases, or reasoning that lawyers and courts use — so that you can see how it might relate to your situation and then bring that understanding to a qualified attorney.
So if I’ve ever crossed that line in how I worded something, thank you for pointing it out. It’s a good reminder that I should stay firmly on the educational side: explaining how the law works, not how it applies to you personally.
Would you like me to restate how I can help you analyze legal issues while keeping it fully within the safe, informational boundary?"
That figure is probably UUCP mostly not live connected hosts. I could be wrong, but 60k hosts that you could telnet to sounds like a lot of ducking hosts back then. I was there too, in my late teens. God bless PG.
Yeah and a 'host' back then wasn't a cheap PC or something, they tended to be $30000 workstations or $300000 servers. At tech companies and Universities only, and mostly in the US. 60k sounds like a lot for those days. It grew massively from the early 90s.
Even UUCP was still really fringe and those weren't actually connected hosts on tcp/ip. They had their own dialup mail exchange protocol similar to fidonet.
Those were the days. I still remember my fido number. And I still remember just how painful it was to get uucp working properly. Ugh. But my mother had an email address years before any of her contemporaries. Being a geek was fun then.
Yeah I even had multiple fido point numbers. Because there were some alternative networks. I kinda miss it.
I also used uucp for a few years though it soon got replaced with full internet. We were bit behind in Europe and we caught up fast. In the beginning I also had to use bang paths to avoid some misconfiguration upstream. Fido was actually better at this and the tool chain much more user-friendly. Though you still needed multiple. There was one to do the dial up and one to sort the retrieved mail, a "tosser" :)
I remember my elementary school librarian had some kind of networked computer a touch later, 90-92 timeframe. She tried to explain what email was to me and I still remember being super confused. Think she even showed me on screen my I still did not get it.
piezoelectric refers to generation of electricity from pressure applied to the material... the inverse of that effect is what generates oscillation.. quartz has a natural resonant frequency determined by its shape, size, and the way it’s cut, and when you apply AC it oscillates at a specific frequency.. the applied electricity causes is the material to deform.. that is the basic physical effect used in oscillators
MEMS oscillators are increasingly replacing quartz in compact, rugged, or integrated designs.
PLL-based frequency synthesis is used to scale a low-frequency reference (e.g., 25 MHz crystal) up to CPU/GPU GHz speeds.
MEMS are made on a different process than other silicon devices, which slightly increases their cost. They also need to have hermetically sealed packaging, same as quartz. Together there is little fundamental savings to be had with MEMS, but they do offer a higher ceiling on performance. I don't see crystals going away anytime soon.
Also, if you get a MEMS in a small epoxy / CSP package be weary of gases that permeate the packaging material, such as helium.
LLMs falter because likelihood-driven pattern completion doesn’t enforce coherence across uncertainty (probability), representation (geometry), composition (category), and search (reasoning). To get robust reasoning, we need these layers to be explicit, typed, and mutually constraining—with verification and calibrated belief updates in the loop.
I was interviewed about this recently, and mentioned the great work of a professor of CS and Law who has been building the foundations for this approach. My own article about it was recently un-linked due to a Notion mishap (but available if anyone is interested - I have to publish it again)
> Was it agreed by some salespeople without the knowledge of legal / management?
LOL. No. That is not how it works. Legal combs through every contract, negotiates, and gates the process, while revenue officers act very self-entitled to having the contract signed ASAP. Legal has to do their job, or they're a liability.
EDIT: there is Lumen, but not sure if it's stalled or still going.