> they risk brand death like Microsoft

Is Microsoft (one of the largest companies in the world) really a victim of brand death?

have you ever met a person who likes outlook?

Anyone who’s ever tried Lotus Notes.

No but I know oh so many forced to use it regardless.

It must feel so good to make a blog post that hates on vibecoding and get your mandated recognition for a regurgitated point. Nobody is even arguing that this article said anything novel, it’s just pure hate

You're right, I offer these alternatives:

Consistency Preservation Update (CPU)

Guided Probability Update (GPU)

History-aware Distillation Driving (HDD)

Probability Smoothing Update (PSU)

The required cover letter for a $120k-$130k/y job is 3 - 4 short paragraphs explaining why you're interested in Innolitics and this particular position.

It's like they are asking to waste their time reading AI spam. If they read it at all or just check length.

Hey! This link doesn't work.

This link seems to work https://priorlabs.ai/careers

What about this article raises this question? If anything, this article makes it pretty clear that memory safe languages are a win. It seems like a serious disadvantage to require a nondeterministic program to evaluate your code's safety.

In general I agree and suspect that memory safety is a tool that will continue to pay dividends for some time.

But there are tradeoffs and more ways to write correct and 'safe' code than doing it in a "memory safe" language. If frontier models indeed are a step function in finding vulnerabilities, then they're also a step function in writing safer code. We've been able to write safety critical C code with comprehensive testing for a long time (with SQLite presenting a well known critique of the tradeoffs).

The rub has been that writing full coverage tests, fuzzing, auditing, etc. has been costly. If those costs have changed, then it's an interesting topic to try to undertand how.

> If frontier models indeed are a step function in finding vulnerabilities, then they're also a step function in writing safer code. We've been able to write safety critical C code with comprehensive testing for a long time (with SQLite presenting a well known critique of the tradeoffs).

More like: a few people have been able to write C code where the vulnerabilities are obscure enough that we mostly don't discover them very often.

The result of the phenomenon described in the article is that the gap between 99.9% secure and 100% secure just got a whole lot wider. Using herculean amounts of testing and fuzzing to catch most of the holes in a language that lacks secure-by-construction qualities is going to be even less viable going forward.

This is crazy. It's especially crazy how nonchalantly the employees are replying. The person suggesting that Railway should clearly show the effected logs is right.

Might be worth taking a weekend day and letting claude code reverse engineer the apk (just download the apk off google) and then build an open source app with the functions you need

Is there an equivalent for macOS?

This is really good stuff, I just wish they had an email list I could subscribe to. I get that they have an RSS feed but an RSS reader is more ceremony than I'm willing to devote to one website without an email form. It's a shame really because it's a pretty cool site.

Interesting. So you’re one of the ones who prefers email updates to a reader? What do you estimate that breaks down to %-wise of people?

my guess:

95% prefer email (anyone nontechnical)

5% prefer reader (a select group of technical people)

Thanks! Why do you think some technicals like readers?