ColdFusion did a lot of things right for its time, but it can only be appreciated if one understands the engineering challenges of the time period (e.g. perl cgi-bin). Using HTML templating and good support from a small and agile company had a lot to recommend it, and many people built a living out of it, both inside and outside Allaire.
OP here, yes, good write up, although I wish someone would code up a simulation that showed it and allowed us to hear what this telephone sounded like to FDR and Churchill.
I don't, but by that point it was a solve problem - speed-of-light is certainly fast enough, especially with optional pre-bias correction term based on distance. 300,000 km/s, say 6000 km, approx 20ms.. It's also oddly similar to the 50 Hz sample rate.
Great examples, exactly what I'm saying. And every one of these (browsers, OSes, phones, etc) has strong incentives to only offer its own password manager.
It's notable that several of the claims on that page conflict with the other info in both the OP article and the follow-on.
As for choice as the user, it's a choice "for now"... and only for users who understand all of these details (which seems unlikely).
Personally, my observation is that if one tries to properly configure 2FA with any major website lately (no, I don't mean AWS console), the level of "your choice" and properly implemented security has actually gotten worse...
Well, they can (and likely will be) used in both modes. Either these things are just a different way of generating a password for a password manager (itself a big target of attacks), or they are a way "to move beyond password with TPM-level security". If it's the former, the security benefits are limited. If it's the latter, the "it's a trap" logic applies at least in part.
Look, at best, Passkeys shift your logins from your head to OS-supplied keychain management. Whether they do attestation today or not, they big, industry-wide effort to move away from "what you know" (i.e. username/password) + "what you have" (2FA) towards "platform-authenticates-you-to-website automatically" has both security benefits and lock-in risks.
Maybe it was too strong to say the were a "trap", but it is also too strong to say there is no worries here.
It should be said that there were others - like https://interviewing.io/https://karat.com/ et al - that figured out the importance of moving beyond "grind LeetCode" years hackerrank did, but it's good to see them acknoweldge this, too.
"The C74-6502 is a homemade implementation of the venerable MOS 6502 microprocessor. The 6502 was revolutionary in its time, and widely adopted in early home computers and gaming consoles. This design is a microprogrammed, discrete-component 6502, an architecture that was prevalent in 1970s-era mainframe computers which pre-dated modern microprocessor technology.
The C74-6502 is plug-in compatible with a wide variety of 6502 systems, including classic computers from Commodore and Apple, as well as modern systems based around the 65C02 microprocessor still in production today. This CPU runs at speeds of up to 20MHz (vs. 1 MHz for the original MOS 6502)."
The customers are quite isolated, but it doesn't mean that some services or errors do not propagate. In public cloud terms, think back on some AWS or Azure or even Gmail outages - you probably wouldn't even hear about them if it didn't affect millions of users at once, across security and availability boundaries.
Despite all of the snark here, in my experience Salesforce SRE team is quite competent. The engineering challenges of running a large PaaS - not just with own apps, but with millions of customer-written apps running on it - are quite interesting, and sadly things happen. The status page makes sense to actual customers, it's the particular "pods" where a given service runs.
One of the important questions to always ask about solar is the energy inputs required to make a solar panel, and the time required to "earn it back" with solar electricity. This is different than "cheap price" because the energy consumed in manufacturing usually happens on a different continent, in a different currency, different regulatory regime and is thus easily obscured.
"This rare episode of CBS’s Tomorrow series, produced to commemorate MIT’s 100th anniversary (1861–1961), explores the early days of artificial intelligence, robotics, and the potential of “thinking machines.” Hosted by actor David Wayne, this documentary-style special features interviews with pioneering computer scientists, including MIT President Jerome B. Wiesner and AI visionary Oliver G. Selfridge of MIT Lincoln Laboratory."
Thanks for answering, not surprising. I think the transition from all-hardware to Windows-driven digital hard on Tektronix and many other storied engineering teams.
"Arm was officially founded as a company in November 1990 as Advanced RISC Machines Ltd, which was a joint venture between Acorn Computers, Apple Computer (now Apple Inc.), and VLSI Technology (now NXP Semiconductors N.V). "
When I say "unavoidable" I mean exactly things like your "a high allocation rate of long-lived objects (as one example), where the work that has to be done requires a significant number of CPU and memory cycles spent on memory management (manual or automatic).
When I say tradeoffs", I mean exactly things like "inherent increased footprint", or my earlier "wasting RAM" point.
At this point, I'm not sure that we're disagreeing about these details, but rather what we make of them... I view them as just years of continued tuning of tradeoffs (heap size vs CPU cycles vs memory cycles), while you them as major breakthrough that makes garbage collection much more desirable. Is that fair?
Someone runnning Kubernetes on an old unpatched on-prem Windows box, conducting a "failover test" by pulling one of its power supplies, spilling coffee on the other one, catching their house on fire, and waiting to call the fire department due to being embarrassed.
One shouldn't make jokes about a situation where people died. Just to sum up Chernobyl
1. no containment building
2. flawed reactor design
3. operators turned off safety systems and improperly operated the reactor
4. delayed / improper emergency response