FR version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
60% Positive
Analyzed from 1679 words in the discussion.
Trending Topics
#github#more#microsoft#footer#aws#commit#https#move#still#com
Discussion (63 Comments)Read Original on HackerNews
- the worst infinite scroll I've ever seen making it impossible to access the footer
- the title tag doesn't seem to work properly (just shows the URL in the tab title, on Chrome and Firefox)
- 2007-style keyword stuffing in meta keywords
- the entire page is client-side react with a completely empty body?
The agency that built it even proudly states on their website that they vibecode everything: https://gradientnoise.com/
EDIT: Turns out, the articles are mostly AI-generated as well? https://blog.ryanmerket.com/how-i-built-runtimewire-a-one-pe...
> And this is the gate that lets me sleep: a story only auto-publishes if the editor says PASS, the risk score is comfortably low, a hero image exists, and it has at least one source
The interslop is real. Simulacra and simulation.
Let's be fair, it's possible to reach the footer! You keep pressing the end key for like a minute or two and 665 requests (with embedded base64 encoded images and all) later, you have your footer.
So saying it's possible to reach the footer would be technically correct - the best kind of correct!
Mobile Chrome can't show a tab title either https://i.k8r.eu/3vVCTQ.png
And the infinite scroll causes the page to constantly jump back up, again preventing me from accessing the footer
And of course with JS disabled you get nothing at all (which affects RSS readers, kindle devices, etc)
One of the moments that stood out to me was when Robert Youngjohns (the exec) asked Tom what it would take to have GitHub move to Azure. I was surprised that Tom had a response ready, saying that IOPS were really important and that virtual disks weren’t fast enough.
every fucking time
Heathen lies!
Oh, wait… we have to use it? Oh, that’s terrible…
This led me to reconsider Amazon as a whole, and I still think of it basically as a logistics firm, with the shop and the public cloud merely a monetisation thereof.
There's also this funny outcome from the SpaceX IPO: https://x.com/ICannot_Enough/status/2065449141946253390
He's flying passengers? They stopped new shepherd and that was suborbital to begin with. You can't compare the 2 at all. Getting people to orbit is much much harder than 'a hop'.
On the government contracts, yes they did get some. Some through lawyers though and they still have to show that they can actually deliver. SpaceX has to deliver on HLS as well, but the ISS has one American ride up and that's crew dragon.
So AI means 14x the checkins? That's not 14x features completed, but still... wow.
While that is (hopefully) the upper end of the distribution, several companies have loudly encouraged engineers to light tokens on fire to the AI gods, so it only takes a handful of the devout to push up the average in gas town like ventures.
Spread over a year, roughly estimating a generous 4 kbytes of data per commit, comes out to a throughput of a little under 2 MB/s.
Of course, it isn’t spread out uniformly and there is also a lot of hashing and other things going on.
Maybe pulls and clones drive more I/O ?
That's also just assuming the good-faith usage. There are probably plenty of adversarial and poorly behaved scrapers that are putting additional load on the system.
We had it internally with our teams that open a PR to then push like 10-20 more commits but never actually interested in the client builds etc. turned out they opened the PR as a checkmark/ way to share the current state. We set cooldowns and auto cancel for the ci. And then there is the developer who uses the CI compute to run tests instead of running them locally for various reasons. We had to remind that compute isn’t for free.
My belief is it is likely 1% or more. And likely coming in as an avalanche.
If this story is true, it's good that they finally realised that GitHub's performance and availability mattered more than using Microsoft's products. It would mean someone finally came to their senses rather than forcing a wholesale push to Azure - but I bet they still want to have it both ways even if they concede some AWS now.
(Probably just tea leaves. If you wanted to be extra spicy, you’d note that Jassy just threw Fable under the bus.)
https://github.com/aiortc/aiortc
It was fun and I found the code nice and helpful.
I clicked on the PRs to see if there was anything interesting to look at. I started reading one when I just realised I was just reading someone’s Claude talking to GitHub Copilot. That was when I decided that the Dead Internet Theory had already happened.
Agents are starting to use it while they think.
the Solaris bits (storage and routing tables) took far longer - and again iirc the frontend had been rewritten in C# before all the Sun hardware had been decommissioned.