0xFEE1DEAD

Exactly.

I blame apple for making me run an old macOS version because I don't want to look at this ugly mess they've created. I've been running macOS since 2008, and unless they manage to turn things around, my next laptop won't be an apple.

Have you tried WezTerm yet? It also uses lua for writing its configs which makes it highly customizable.

I've switched to it from iTerm2 a couple of years ago and gradually added more and more to my config and it's super powerful.

I think they're using SpamAssassin so don't expect world leading spam filtering.

But, they allow you to write your own sieve scripts so you can really customize the experience a lot.

Don't think of them as another proton mail, they're much more a DIY mail provider.

I recommend purelymail.com (not affiliated in any way, just a happy customer).

I've been a customer for 4-5 years, ever since I saw a hn post about them, and I have zero complaints.

It's dirt cheap ($10 per year for unlimited amount of users).

They allow wildcard addresses and I've set up my own "trash mail" so I can register an account at e.g. LinkedIn with [email protected].

I've set up 4 different domains and 3 accounts and all of this for $10 a year.

Sorry if this reads like an ad, but I think it's super cool to offer such a great service for a fair price.

For anyone curious: "c" just means that it's a character device.

There is also "b" for block device (e.g. a disk, a partition, or even something like a loopback device) and "p" for FIFOs (similar to mkfifo).

The two numbers are just identifiers to specify the device, so in case of `5 1` it means the systems tty console, while `1 8` would mean "blocking random byte device" (mknod dev/random c 1 8)

I agree with this take, but I'm wondering what vibe coders are doing differently?

Are they mainly using certain frameworks that already have a rigid structure, thus allowing LLMs to not worry about code structure/software architecture?

Are they worry-free and just run with it?

Not asking rhetorically, I seriously want to know.

I honestly don't get vibe coding.

I've tried it multiple times, but even after spending 4 hours on a fresh project I don't feel like I know what the hell is going on anymore.

At that point I'm just guessing what the next prompt is to make it work. I have no critical knowledge about the codebase that makes me feel like I could fix an edge case without reading the source code line by line (which at that point would probably take longer than 4 hours).

I don't understand how anyone can work like that and have confidence in their code.

They actually sued a lego youtuber (or threatened to sue - unsure) for using a lego brick in his logo. this lead to him creating a new word for lego bricks "Klemmbausteine" which means "clamping building bricks".

Thank you for sharing, what an interesting read.

> Now, the researchers are working on further research to extend their technique to detect breathing [...]

Impressive from a technical standpoint, but super scary from a privacy standpoint. Surely this must allow them to detect and differentiate between plosives, which is probably enough to infer what's being talked about.

On one hand, it's super impressive how far we've come in such a short amount of time. On the other hand, this feels like a blatant PR move.

GPT-5 is just awful. It's such a downgrade from 4o, it's like it had a lobotomy.

- It gets confused easily. I had multiple arguments where it completely missed the point.

- Code generation is useless. If code contains multiple dots ("…"), it thinks the code is abbreviated. Go uses three dots for variadic arguments, and it always thinks, "Guess it was abbreviated - maybe I can reason about the code above it."

- Give it a markdown document of sufficient length (the one I worked on was about 700 lines), and it just breaks. It'll rewrite some part and then just stop mid-sentence.

- It can't do longer regexes anymore. It fills them with nonsense tokens ($begin:$match:$end or something along those lines). If you ask it about it, it says that this is garbage in its rendering pipeline and it cannot do anything about it.

I'm not an OpenAI hater, I wanted to like it and had high hopes after watching the announcement, but this isn't a step forward. This is just a worse model that saves them computing resources.

> on internal, legacy codebases, enterprisey stuff

Or anything that breaks the norm really.

I recently wrote something where I updated a variable using atomic primitives. Because it was inside a hot path I read the value without using atomics as it was okay for the value to be stale. I handed it the code because I had a question about something unrelated and it wouldn't stop changing this piece of code to use atomic reads. Even when I prompted it not to change the code or explained why this was fine it wouldn't stop.

Yes, for me it is and it was even before this experience. But, you know, there's a growing crowd that believes AI is almost at AGI level and that they'll vibe code their way to a Fortune 100 company.

Maybe I spend too much time rage baiting myself reading X threads and that's why I feel the need to emphasize that AI isn't what they make it out to be.