41–50 of 83 posts
I helped set up the first meeting between a Microsoft executive and Thomas Preston-Werner. 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
Earlier quoted context omitted.
Is that even a lot? 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 ?
I suspect there is a cacophony of work that happens when a commit hits the server. That request needs to get replicated, git repositories need to be repacked, pull requests need to calculate diffs, CI jobs need to execute, on and on. 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.
What kind of vibecoded website is this? - 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…
[flagged]
What kind of vibecoded website is this? - 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…
[flagged]
There are so many bad and false assumptions baked into your short comment, it's hard to begin. For instance: in what world does someone have provide justification for their critique of an AI-written website, because they didn't happen to respond to some previous post?
What kind of vibecoded website is this? - 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…
[flagged]
That said, I likely wouldn't have read that thread even today. I prefer engaging more deeply with fewer stories.
Another new AI benchmark result is of little interest to me, in contrast to a story about Microsoft stalling or even partially reversing the GitHub Azure migration.
Earlier quoted context omitted.
[flagged]
> https://news.ycombinator.com/item?id=48440448 this had >300 upvotes with a link from runtimewire.com and you didn't even criticize it then. why now? There are so many bad and false assumptions baked into your short comment, it's hard to begin. For instance: in what world does someone have provide justification for their critique of an AI-written website, because they didn't happen to respond to some previous post?
What kind of vibecoded website is this? - 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…