News for hackers. Stuff that matters.

area_man

Definitely a few factual errors here that ought to be corrected.

On day one of the acquisition, Youtube's egress network was at least 4x the size of Google's, built and run by two guys. This shouldn't be a shock, you need a lot more bits to serve video than search results. For the hottest bits of content, third-party CDNs were serving videos and thumbnails.

There was no collapse imminent, but there were concerns about getting YouTube and Google infrastructure on a common path. BandAid was named as such because the goal was "not to break the internet." It was a small project with maybe a dozen members early on, all solid people.

YouTube had its own contemporaneous project, née VCR - "video cache rack". We did not necessarily believe that BandAid would arrive in a reasonable amount of time. Generally Google has two versions of every system - the deprecated one and the one that doesn't work yet.

VCR was a true YouTube project, 3 or 4 people working with one purpose. It was conceived, written, physically built and deployed in about 3 weeks with its own hardware, network setup and custom software. I believe it was lighttpd with a custom 404 handler that would fetch a video when missing. That first rack maxed out at 80Gbps a few hours into its test.

After several months, Bandaid debuted. It launched at ~800Mbps and grew steadily from then on into what is certainly one of the largest networks in the world.

YouTube mostly moved things to Google based on a what made good engineering sense. Yes, a few of them were based on what would break next - thumbnails leaps to mind. Search, which we thought was a no-brainer and would be "easy" took more than a year to migrate - mostly due to quality issues. Many migrations were purely whimsical or some kind of nebulous "promo projects." Many more stayed separate for more than a decade. When a company gets large enough, the foolish consistency tends to trump a lot of other engineering arguments.

To the ancestral poster, do not despair. You can transcode, store and serve video, as you've likely surmised it's not all that difficult technically. In fact, it's so much easier now than in 2005.

What makes a great product is hard to describe and not always obvious. The economics will depend on your premise and success. "the cloud" gets pricey as you scale. There will be a long path of cost optimization if you get big enough, but that's the price of doing business at scale.

Re:Cold brew coffee in 3 minutes using acoustic cavitation on Wednesday May 08, 2024 @11:19AM (#40299095)
It need not be mediocre. I have a Jura J5 which has, as of this morning, made 18,901 espressos. A few years back, I bought the tool to open it and recalibrated the conical grinder. There are now videos that can walk you through this process.

The mediocrity disappeared. It produces a fantastic brew close to the quality of the shop where I buy the beans.

Before attempting all this, I ran an experiment. I had my shop grind the coffee one notch back from where they grind for their in-house espresso. Then I put that into the by-pass chute and brewed it. This confirmed to me that machine’s grinder was not getting fine enough.

If you grind truly as fine as you would for an espresso machine, you may get a very slightly better brew, but it will come with a 5% chance of clogging the machine and wasting the ground coffee. Best not to fly too close to the sun.

A friend who knows a few things about coffee stopped by not too long after I did this conversion and asked if I had bought new beans, because “this shit is top notch”. It was a revealing experiment about the importance of the grind.

It’s a fascinating machine to take apart. We’ve had it for 15 years and I’m optimistic it will just keep going. At this point my goal it see when the espresso counter will roll over back to zero.

Re:Python startup time: milliseconds matter on Wednesday May 02, 2018 @09:33PM (#16982667)
Truly solving this problem is difficult, but you can hack around it with a zygote process to remove a substantial amount of overhead, in exchange for RAM. While this is generally more of win for server processes, you can see it applied to a CLI proof of concept:

https://github.com/msolo/pyzy