It's arguable that any group's dialect is actually a fork of English specialized for a specific culture, activity, or context. Occasionally, elements of the fork are pulled into upstream English as groups grow in popularity and jargon or shibboleths become more commonly used across dialects.
QR codes for canonical addressing could solve the publishing problem, with customization of how the QR code appears being a feature for advertising and marketing. Once the canonical address has been accessed once, it could be pet named by the accessing user.
Good answer. But I’m wondering how well this works when a QR code resolves to a meaningless string of digits?
I suppose most people don’t check URL’s anyway, and for some URL’s the domain name is fairly meaningless. Still, it seems like something is lost, at least for techies, when you can’t see and recognize usernames and domain names?
Consider how programming languages work. Who wants meaningless numbers in their import statements or package.json file? Package names seem decentralized enough? Not sure it’s worth throwing out to achieve True Decentralization.
Also, for only two k8s devops engineers in a 24h-available world, you’re gonna be running them ragged with 12h solo shifts or taking the risk of not staffing overnight. Considering most update and backup jobs kick off at midnight, that’s a huge risk.
If I were putting together a minimum-viable staffing for a 24x7 available cluster with SLAs on RPO and RTO, I’d be recommending much more than two engineers. I’d probably be recommending closer to five: one senior engineer and one junior for the 8-4 shift, a engineer for the 4-12 shift, another engineer for the 12-8 shift, and another junior who straddles the evening and night shifts. For major outages, this still requires on-call time from all of the engineers, and additional staffing may be necessary to offset overtime hours. Given your metric of roughly $8k an engineer, we’d be looking at a cool $40K/month in labour just to approach four or five 9s of availability.
They aren't making something for the JS ecosystem: they're defining a new data serialization format built on explicitly defined input parsers (Scroll), and for one reason or another, its current implementation is in JS.
It turns out that creating a data serialization format built on explicitly defined parsers has uses beyond the ontological use cases, and there are several expressions of Scroll that are useful for technical use cases, such as Stamp for templating and ScrollSets[1] for structured data. The ScrollSets page is an excellent demonstration of how Scroll can be used to serialize data for human- and machine-consumption.
From my perspective, this is AI bubble part 3 or 4. DARPA and UKI AI funding for chatbots, perceptrons dried up in the 70s; expert systems and symbolic reasoning dried up in the late ‘80s and ‘90s. Through the ’00s and ‘10s, ML/DL was successful, in part by shedding the guise of AI. Now we’re in an unsupervised learning and large-scale multilayer transformer networks wave, and while I expect the financing bubble for these projects will pop sooner than later, the tech will continue to live on and be integrated into future projects, as have all other previous AI breakthroughs.
While cult followers do not make exceptional leaders, cult leaders are almost by definition exceptional leaders, given they're able to lead the un-indoctrinated into believing an ideology that may not be upheld against critical scrutiny.
There is no guarantee or natural law that an exceptional leader's ideology will be exceptional. Exceptionality is not transitive.
