Hacker Newsnew | past | comments | ask | show | jobs | submit | patwolf's commentslogin

Pentium marketing was next level. You could buy plushies of Intel workers in bunny suits. The first IMAX movie I went to was called "The Journey Inside", and it was basically a big ad for the Pentium.

I always wondered if some of that was to offset the negative publicity from the FDIV bug in the early Pentiums.


I have a bunny suit plushie on my shelf to this day. The other Pentium marketing blitz I remember was in the 1998 Lost in Space which had a TV ad for a Pentium XXI or something. Also notable was the Silicon Graphics branding in that movie. Which I have always found amusing since SGI didn't have any consumer products and even for businesses the prices were "Call Us" which has always meant eye watering expensive.

These rules apply equally well to system architecture. I've been trying to talk our team out of premature optimization (redis cluster) and fancy algorithms (bloom filters) to compensate for poor data structures (database schema) before we know if performance is going to be a problem.

Even knowing with 100% certainty that performance will be subpar, requirements change often enough that it's often not worth the cost of adding architectural complexity too early.


> Even knowing with 100% certainty that performance will be subpar

I think there is value in attempting to do something the "wrong way" on purpose to some extent. I have walked into many situations where I was beyond convinced that the performance of something would suck only to be corrected harshly by the realities of modern computer systems.

Framing things as "yes, I know the performance is definitely not ideal in this iteration" puts that monkey in a proper cage until the next time around. If you don't frame it this way up front, you might be constantly baited into chasing the performance monkey around. Its taunts can be really difficult to ignore.


I owe much of my career to an SSD. I had a work laptop that I upgraded myself with an 80GB Intel SSD, which was pretty exotic at the time. It was so fast at grepping through code that I could answer colleagues’ questions about the code in nearly real time. It was like having a superpower.


I use it on MacOS, but it doesn't support tabs.


The first time I got a photo scanner, I was blown away that I could see myself on a screen. I eventually got a digital camera, and the novelty started to wear off. Now I can make myself the lead in a blockbuster movie, but that feels boring.


I found that writing rules was tricky when I didn't know exactly what content would be in a spam/promo notification. I ended up having claude code up a filter that asks an AI to review the notification first, which seems to be working well.

Thanks for making it open source. I've been wanting something like that for a while, but I'd been putting it off since I didn't want to learn the underpinnings of the notification service.


I got one of these for my kid a few years ago. He liked to browse Spotify on my phone, and I thought it would be a good screenless alternative. But honestly it just sat in a drawer, and I didn't have the patience to maintain and sync playlists to it.

It's easy to be nostalgic for the iPod era, but having to sync music is something I'm fine keeping in the past.


> In the deal struck on Friday, Canada will allow only 49,000 Chinese electric vehicles into the Canadian market at the 6.1% tariff rate.

I was wondering how Canada would prevent this from damaging their auto industry, and capping the total numbers of cars is how they're doing it.


I've been looking at DBOS for queuing and other scheduling tasks in a nodejs app. However, it only works with Postgres, and that means I can't use it in web or mobile with sqlite. I like that SolidQueue works with multiple databases. Too bad it needs rails.


I wish it had generated the articles themselves. I'd like to know if it imagining IBM growing enough that it could acquire OpenAI, or OpenAI sinking enough that it could be acquired by IBM.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: