There already is a SRV service name reservation for both http and www-http, with Tim Berners-Lee as the contact name. Fun fact: using DNS address records ("A" or "AAAA") for endpoint name resolution in HTTP is a convention; it is not required in the standard or in any of the normative references. Web services do not own the address record and should never have been using it in the first place. Nonetheless they continue squatting addresses in a de facto assertion of unwarranted privilege, and every other use of the DNS has to steer carefully around.
When SRV is discussed e.g. on the HTTP/2 list, the objections of resolution speed and number of round-trips are usually raised. But SRV records do not intrinsically require an additional lookup or round trip. Unoptimised zone configurations (especially those that slice at _tcp, which occurs at some Microsoft shops) may fare less well, but that is true of all DNS configuration. Services that care about resolution speed already optimise their DNS as necessary, and they would for SRV as well if it were mandated.
In practice, the reasons for non-adoption are, mundanely, simply a matter of inertia, combined with a lack of motivation: the browser vendors who in practice write the HTTP standard do not care to change and have no external force that will push them off overloading the address record.
I don't believe it is quite so simple. Remark ordering also appears to incorporate
* freshness (new remarks get a moment at the top)
* reputation (remarks from high-karma accounts linger higher, longer)
and I may possibly have also observed:
* a penalty box: hidden downweighting, or reduction in effective karma, imposed by moderators upon troublesome users that weren't egregious enough to ban/shadowban.
Word of warning, if you use an ad/content blocker like uBlock Origin, and block 3rd-party JS, then HIBP may give up on its k-anonymity mechanism and just sends your password to their server in cleartext.
Ensure you specifically permit loading jQuery from cloudflare.com, and check network traffic using a test password first.
Ironically, Erlang’s message passing makes it more like Alan Kay’s original definition of OOP than the bowdlerised view of OO perpetrated by Java and C++.
I once told a competitor that we're using Javascript extensively and our TTM for new features is super low thanks to simply adding NPM modules whenever necessary.
In hindsight I should also have mentioned NoSQL databases and a microservices architecture.
It worked before, they broke it, and as usual the response is an egregious "fuck you" and a queue of apologists castigating the aggrieved that they were Doing It Wrong All Those Years And They Must In Future Conform To Only The Approved Way.
And with that, I mourn the obsolescence of my last remaining "absolute unit" joke and will have to develop something equally satisfying based on dressed lumber to replace it.
To be fair to Google, they haven't had enough time to perform a detailed autopsy, and some GCP incident summaries have shown meat on the bones e.g. https://status.cloud.google.com/incident/compute/16007. And balancing the scales, the AWS status page is notorious for showing green when things are ... not so verdant.
I have seen full <public cloud> internal outage tickets and the volume of detail is unsurprisingly vast, and boiling it down into summaries - both internal and external - without whitewashing, without emotion, to capture an honest and coherent narration of all the relevant events and all the useful forward learnings is an epic task for even a skilled technical writer and/or principal engineer. You don't get to rest just because services are up, some folks at Google will have a sleep deficit this week.
Back in that oft-forgotten age I was privileged to know, work, and chill with the brave volunteers (and, subsequently, paid RIR staff) holding down the buttons. It’s worth mentioning that even back then there dwelt in the west a large ugly troll whose name was AS701 (AS701 was not alone, either, having two hideous siblings, AS702 and AS703, that lived in other climes). Everyone tiptoed around the beast, because when angered it would flap its routes and there would be a great wailing and severe packet loss. The brave volunteers tried many times to tame the awful creature and I’m very sorry to see that it is still fucking everyone’s announcements even today.
I agree, and I and many others raised it repeatedly with the HTTP2 editors/mailing list in particular, who sadly murdered that proposal because they believe in their god-given right to squat the A record for their protocol. I believe the failure to address DNS considerations in the HTTP standard has driven a large part of ongoing IPv4 exhaustion.
No. The law is not a virtual machine and legal documents are not programming.
Believing so is a common misconception amongst engineers, but depending on it as such is likely to lead to disappointment, frustration, anger, needless bickering, extended conflict, and vexatiously long, hard to read, and mostly unenforceable contracts.
I think they might be suggesting that Scott may have specific exemption from Apple's PR policy (summary: "say nothing to anyone") to be allowed an independent public voice - particularly on a technical/engineering topic. Apple is not, so far as we know, currently developing orbital-class rocketry, but there's genuine potential for product topic overlap in Project Titan vs Tesla and perhaps more besides.
I would not be at all surprised if there's a List Of Things Apple PR Hereby Politely Requests That Scott Doesn't Mention.
When I was at AWS I was similarly forbidden from mentioning anything to do with video games to just about anybody, despite not having anything to do with video games myself, and many other topics besides the obvious (e.g. "don't disclose EC2/S3 capacity numbers"[1], "don't reveal how Glacier works"[2]), and in fact there was a whole programme of PR training and tiered permission to speak at conferences or to the press/analysts that boiled down, mostly, to knowing what you could and couldn't say, and how diplomatically you parried questions on the latter.
Either that or Terry Pratchett's law of rewritten rules applies.
[1] no-one would believe me anyway
[2] it's a massively redundant array of vinyl records
"Feynman was a truly great teacher. He prided himself on being able to devise ways to explain even the most profound ideas to beginning students. Once, I said to him, 'Dick, explain to me, so that I can understand it, why spin one-half particles obey Fermi-Dirac statistics.' Sizing up his audience perfectly, Feynman said, 'I'll prepare a freshman lecture on it.' But he came back a few days later to say, 'I couldn't do it. I couldn't reduce it to the freshman level. That means we don't really understand it.'"
-- David L. Goodstein, Feynman's Lost Lecture: The Motion of Planets Around the Sun, ISBN:978-0393039184.
Melbourne, Australia has heatwaves exceeding that, and shivers through thoroughly miserable wet winters, and yet we have a large, thriving, and ever-growing corps of recreational, competitive, and commuting cyclists, and that's despite the increasing hostility and declining levels of competence exhibited by local drivers.
The suggestion that cycling is a fair-weather activity is hogwash.
Communications technology has moved past the ability of human brains to tolerate and mitigate the adverse effects.
Every addicting dopamine surge from a Like or Retweet is the evidence; every viral pile-on, every echo-chamber lunatic fringe.
Making humanity resilient to the negative externalities of our own technological advancement is essential for the survival of our species. Right now, a vast army of the smartest people are employed at the intersection of cognitive and computer sciences, but in the service of political and commercial interests. I'd like to see more of them on the other side of this arms race, working on our individual and societal defenses.
Some folks (myself included) by default prefer to segment their trust by vendor, not by application, since it tends to be aligned anyway. For example, as per GP I'm fine with any Apple app having location access because by buying the phone I made an implicit decision to trust the company. In contrast, Facebook's stuff can fuck off into the black hole of mistrust they dug for themselves.
Finer granularity of trust (+ve or -ve) occurs only in exceptional cases.
As with so much in life (and in tech), the greatest process efficiency occurs when you standardise a common case and manage by exception.
IANAL but I do run a business that's subject to Australian consumer law. The limitations are not based on the date of the contract of sale, but the date on which the consumer became aware (or reasonably could have been aware) the product was defective, and/or an action was taken by some party to render the product defective.
The consumer legislation does specify a six-year time limit from then on, but that clock only just started ticking.
However, a refund is not obligatory. Repair i.e. a patch is an acceptable remedy under ACL.
There’s a perspective that the transaction log of a typical RDBMS is the canonical form and the rows & tables merely the event-sourced projection. After all, if you replay the former, you should always get exactly the same in the latter.
It’s curious that over those projections, we then build event stores for CQRS/ES systems with their own projections mediated by application code.
Let’s also mention the journaled filesystem on which the database logs reside. And the log structure that your SSD is using internally to balance writes.
It’s been a long time since we wrote an application event stream linearly straight to media, and although I appreciate the separate concerns that each of these layers addresses, I’d probably struggle to justify them from first principles to even a slightly more Socratic version of myself.
> notice how dumb journos are when they cover subject matter
This is a key takeaway that, I suspect, everyone who has ever been interviewed, covered, or quoted in the press feels.
Every time you see a story in the general media that grossly misrepresents a subject you know well, remember that feeling. Because for every other topic covered, I guarantee there is a domain expert feeling as you did.
I’m three for three in terms of regretting journo contact. Whether it was the local rag or a national broadsheet; misquotation, glib misrepresentation and sheer fabrication are inevitable results.
Corollary: reserve your greatest mistrust for anyone that openly and actively courts the media. They are well aware of the outcomes and are manipulating the game. This includes your in-house PR team and most elected officials, including the ones you voted for.
Some of worlds most useful and powerful data structures are the projection of an event log. The tables of a RDBMS, the balanced writes of a SSD, and even the classic: double-entry book-keeping.
Even the data stream of a TCP connection is a projection of events, which is why (and how) we can reconstruct them by replaying captured segments.
So just because there are some lousy executions of a general architecture, doesn’t mean we should recoil from the basic idea.
My takeaway is that successful event-sourced structures are crafted for the domain they represent. I’ve developed a couple for my own work, for very specific aspects of an application, and they work well in context.
If your experience has been that a general-purpose ES framework leads to shitty, hard-to-maintain apps, I’d say that’s evidence for the corollary.
I've been soldering, crimping, and plugging things in for forty years, and I struggle to think of a connector for which there is exactly one configuration, pinout, cable specification, capability and equipment compatibility for all its use cases seen in the real world.
In my household, USB Type-C has in practice been a great simplifier. Less so at work, but still not more complicated than the multifarious uses of, say, the modular connector family, or the DIN series.
Our monkey brains are not evolved to deal with the satisfaction barrage of met expectations, or the microdosed dopamine of incremental reputation tallies.
We've weaponised the apparatus of retail and communication against our own limbic systems.
A few weeks ago, in support of a customer's new facilities, I tasked a satellite imaging platform to take a photograph of Dubbo, Australia, using an app on my iPhone. Placing the instruction took less than two minutes, the longest part of which was downloading the app. The processed image was downloaded to my device before close of business that same day.
Against a glowing surface, my hand describes a complex sigil, and orbital mechanisms leap into action on my whim.
Next up: pulling together the components for Karsus's Avatar
It's well known that experts can distinguish the African Swallow from the European Swallow simply by airspeed.