1,318 karma · joined November 6, 2016
Formerly at Palantir, Apple, and co-founder at Symbolica AI. Currently at GitHub.
If that flow was broken there’s only a handful of things it could be; specifically azure blob store or azure MySQL, but both of those should have layers of redundancy. Public anonymous download bypasses most everything else; no auth services, rails monolith, or metered billing. It does emit some events to the message bus for metrics, but that’d effect much more than packages if there was an issue with it.
As far as I’m aware this is the first time anonymous public package download broke since I left a few years back.
Having dumped several large blockchains into Scylla with indexing in Elastic, I can't imagine a situation where there's enough value-add to justify building a custom database to store it.
Google will give you an expansion of the acronym and a generic business definition, sure. But I think it’s nice to be able to contextually tailor the response to the presumed audience of HN and the assumed expertise of the asker.
I get that us engineers are obsessed with efficiency in information sharing, but I do like participating in actually being a human from time to time.
It means a “special purpose acquistion company”. It’s effectively a company set up for the express purpose of facilitating an acquistion or merger of companies, so that assets or IP ownership can be moved in an optimally tax or otherwise cost efficient way.
Many have argued they provide no value except for helping wealthy people retain their wealth, hence why you see a lot of folks here lacking sympathy in their collapse.
A JWT has all the information for verifying its own lifetime contained within it, which is cool in that you don’t need to hit the DB to verify it… until you want to invalidate it before the embedded expiration is hit.
Then you need to hit the database or some cache layer to verify that it isn’t invalidated, and now one of the biggest reasons to use it is gone.
They do mention that for CRUD operations you’ll need to hit the DB anyways, which is in the same vein as this issue tho.
Sounds like a conflating of correlation and causation.
The one we got is 15,000 BTU, which is frankly too much. You can find 10,000 or 12,000 BTU options for cheaper, and will probably get some more fine grained control out of it.
The butane lasts for quite a while in it for wok use as well, since you’re generally only cooking for a few minutes at a time.
Luckily there’s a fantastic non-nonstick option for that too; a carbon steel wok. Amazing tool that is frankly under-utilized in the western world.
J. Kenji López-Alt released a book this year that goes over how to use it in great engineering-focused detail for anyone wanting to give it a shot.
May be better to just italicize or bold that rather than change the color. Or better yet, actually make it a link to a short “how does it work” page
If your code ever deletes data or uses an index this certainly wouldn’t be a drop in replacement as that copy text makes it seem.
However I think it’s hard to ignore in light of recent issues that there has been a large amount of attrition in the last year or so, specifically to PlanetScale by some of the most senior/database focused engineers.
Edit: just noticed that you’re the CEO of PlanetScale. I don’t mean this as a slight against you or GitHub or the folks that moved. I genuinely do just think that the number of people who shifted over left GitHub with a fairly large experience and knowledge gap. I don’t think anyone is to blame, it’s just an outcome of organic evolution and changing of a technical organization.
> New services like Packages and Codespaces rely on the `mysql1` primary db.
A lot of this is due to that DB handling core data to GitHub (notably organization and repository data), which the integrated nature of the new feature offerings forces them to interact with (syncing permissions from repos for packages, publishing from actions, etc.). The link between repos and codespaces is even more unavoidable.
We were careful with Packages to keep as few service dependencies as possible in the critical path, especially for things like the anonymous read path, so serving project packages to users for open source projects or package managers such as homebrew are as insulated as they can be (and I suspect were unaffected by this incident).
But at the end of the day, there is some data that is central to most everything at the company, unfortunately.
Sure, you could scan blockchains and extract NFT data yourself, and sure you could run your own node for every blockchain that interests you (paying god only know how much for storage and bandwidth). Just like how in web1 you could run your own email server to handle email and have your own blog server to publish info and your own git server to host your code and your own domain name to put it all under…
But it turns out that exceptionally few users actually care about putting in the time/effort/money to do that. Hence the rise in web2 and platforms. The people who run their own infra now are all doing it more as a hobby than anything else.
Like it or not, recentralization is the future of web3 for the average consumer. You can be a crypto decentralization purist, but I hope you realize that you’ll be the minority in that, if crypto/web3 actually is to gain widespread adoption.
For the average consumer, convenience is the real feature, and true decentralization is inconvenient.
It was kind of designed to be a distributed systems building block that you can develop interfaces on top of without worrying much about implementing the durability, consistency, or distribution of data.
“ZeroVer is satire, please do not use it”
Public source for that info, so I don’t get accused of NDA violations - https://youtu.be/HLE8chgw6LI
Timestamp 14:15 touches on CloudKit’s extensive FDB usage.
Who wrote this? Who funds them? How can I know that they aren’t introducing bias to their assessment in their own self interests?
If following the guidance set out at https://semver.org, a patch release wouldn't add any new functionality, it would just address bugs in a backwards compatible way. A minor version would introduce new functionality in a way that doesn't violate backwards compatibility.
Quickly scanning the release notes for some of the MySQL 8 versions, they seem to be generally sticking to this; most of the versions fixed some bugs or unintuitive behavior, but it doesn't look like much new functionality has been introduced since 8.0.4, the last release candidate for the major version bump.
I think this will end up with a large class action lawsuit for sure, tho I really think it’s a toss up as to who would win it. This conversation was bound to happen eventually and we’re in uncharted territory here.
I think it’s going to hinge on whether machine learning is considered equivalent in abstraction to human learning, which will be quite an interesting legal, technological, and philosophical precedent to set if it goes that way.
So by your logic ABC, CBS, Fox, and NBC have all been plagiarizing and violating copyright for doing so? I’m not sure if there’s been a legal challenge/precedent set in that case yet, but that seems like a more apples to apples comparison than the Google Books metaphor being used.
Disclosure: I work at GitHub but am not involved in CoPilot
I think the thing to remember about Cook is that he’s a process and money guy, previously being the COO. I don’t think anyone at Apple would call him a “visionary” like they said about Jobs; that’s just not his style.
However the repercussions of this were pretty clearly felt, at least by me and my organization. We were tasked with a monumental infrastructure undertaking while continuing to support production use cases, and we were running as a skeleton crew for a lot of it, because getting headcount to hire more was such a heavily scrutinized process.
So I ended up on a team of 3 people maintaining 3 separate server components. It was honestly sort of brutal.
And I know Jobs was also famous for working people hard, but he had the charisma to make it have purpose. We were under Tim, and then under Eddy, who are… not the most charismatic fish in the sea. It really just felt like we were being pushed needlessly hard when hiring one or two more people would have made a massive difference and improved the overall development cadence and quality.
Wouldn’t work in this case with the overlays and styling tho.
So probably good enough for reading/coding/browsing static sites, but scrolling will feel laggy and videos/animations will be a hard watch.
Still a pretty significant improvement over the eInk displays you get in Kindles which can take 500ms+ to refresh.
Given how polarizing politics tends to be, especially in a two party system such as America, I’d wager that most people put all 5’s for candidates of their party and all 1’s for candidates of the other party.