Splines

I would not be surprised if DMV employees were measured and rewarded on their throughput, so punting people who have anything wrong is incentivized.

Is Blizzcon streamed in China? I agree - nothing will happen. They'll likely heavily filter what they broadcast in China if they do stream there, and that's about all they can possibly do.

I think that's one of the reasons NPR bought Pocket Casts - to get this data. Where are users skipping? When are they dropping out of a podcast? Etc.

Personally I skip forward past ads all the time.

I have half a mind to write a podcast player that skips ads for me. It doesn't feel like an insurmountable problem.

Check out the video game "Soma". It's a horror-themed game but you can play in "Safe" mode if that's not your thing. I'd say more but that would spoil things for you.

That 1TB you always pay for, while Backblaze is pay-per-use.

> I hope I can repurpose them for other iot signals.

I bought one for that - it's authenticated on my wifi but doesn't know what to order on Amazon. Pushing the button will make it visible on the network but do nothing else. So I wrote some scripts to run when it associates on the network, works pretty well.

I'd say that disk comes a close second, if not first. Overtaxed slow disks with low memory makes for a terrible desktop experience.

Once your memory usage climbs and your OS starts paging/swapping things to disk, seemingly trivial operations that page in new code will take forever.

> Google Mail is quite fast for me as well... And I'm not even using some crazy fast computer, just old PC with Core i5.

If you want to see fast mail, go load the basic html version of Gmail. I have it bookmarked because it loads as fast as you think it should.

Regular google mail loads so painfully slow in comparison, they needed a splash screen.

Probably some combination of things that break principle of least surprise along with not needing to think about that thing very frequently. A good IDE and good coding standards can smooth things over.

I'm ok with regex too, but if you asked me to do something with look-behind I'd have to experiment a little to figure out how it works again.

Re: performant code, the developer writes the code once, it is read many times, and it is run many many many times. Several orders of magnitude more.

Yes, making code that is easy to read and less bug-prone is good. But at the end of the day the customers are going to be running your code millions of times a day, and if you need to make the code slightly harder to read to improve performance, then by all means do so.

If your code is only going to be run once and must be reliable, then you can make a different trade-off.

It should just be turned off for large channels. Pop an error message and direct users who need it to a support article, if they follow up real support people then see how many people complain.