senko

MongoDB could lose your data on a single instance after acknowledged write. And corrupt the entire database in case of server crash.

Yes, this is worse, but in both case the root cause was human carelessness, not AI.

To everyone pointing out that artificial intelligence is to blame here, you may want to read his takedown of MongoDB back in 2013: https://aphyr.com/posts/284-jepsen-mongodb

I guess MongoDB was also vibe-coded back in 2013: https://aphyr.com/posts/284-jepsen-mongodb

So the cost was zero.

It'd cost ~$250 via API (ie. paying current API pricing per token).

Source: copy pasted the tokens into a chatbot and told it to figure it out.

The author has been a free software author, contributor and active community member to many projects including GNOME, Freedesktop, GStreamer/Pipewire, and (if I recall correctly) LibreOffice for decades.

kids these days have no respect...

TFA addresses that:

> I decided to buy a negative photo scanner and found that the Plustek 8200i was supported under Linux so I bought that. Only to discover that the chipset in the scanner had changed to one that wasn’t supported under Linux anymore

HTTP was created in '91 and HTML in '93. SMTP in '81. That's 9-19 years before the dotcom boom, depending on how you want to count.

In '93 people were still complaining that computers weren't bringing in productivity improvements (Solow paradox):

> You can see the computer age everywhere but in the productivity statistics.

The big change is that we now (due to the internet and interconnectedness of everyone) learn about the technology much faster than before.

But diffusion through business and population still takes time. Especially if there's a hardware crunch that acts as a brake.

I lived through the dotcom boom era (went online in '93 or so). If you can't compare that change to the magical science fiction we're living through (I can press a button, speak to my computer and tell it to build me a 3d game, then play through it 15 minutes later), I beg to differ.

(edit to add: not to mention the existential crisis many artists, developers and mathematicians are going through right now...dotcom was nowhere near that in terms of psychological impact)

Future is already here, it's just not evenly distributed (also said in '93, and I believe it's applicable again).

Models do seem to have a preferred style, see for example what Opus likes to do: https://s3.us-east-1.amazonaws.com/vault.senko.net/blog/quic...

The pelican from the post can be changed by prompting, as other commenters show. But I found it pretty hard to guide Opus away from the above.

Other models' results look different, but also show style convergence.

You can also see in "creative" game output (Astra loves 3d), or text output.

It's not all bad - this shows we should treat AI as a tool and assume any creativity (or lack of it) as coming from the human.

This nicely redefines slop as work you slapped together without much care, irrespective of what the tool was.

Ranks deep sky objects for tonight at your location.

A single-binary Go CLI (feat. WASM port for in-browser use) that tells you what to image tonight from a given location.

Source: https://github.com/dkorunic/astro-recommender/

Depends, is my friend getting paid a lot of money to give me this advice, by a 3rd party that will massively benefit if I take it?

I might just trust a random redditor more...

> Astral [...] The actual product was secondary at best.

No one who has tried ruff, uv and ty would agree with that.

Nor go back to any of the previous alternatives Astral's products replaced. (With the possible exception of ty since that's still pretty new)

I love the typo.

The post is a zero-information personal rant (good for him/her!), impossible to comment on without violating at least half of the HN guidelines[0].

[0] literally; even this comment violates a few

A crawler that respects robots.txt is useless in practice since many sites only allow Googlebot and maaaybe Bing - by name.

Since it's a PDF, here's an excerpt from the summary:

> This report introduces Kolibri, an English–German Mixture-of-Experts transformer with 78.1B total parameters and 3.46B active parameters per token, released as open weights under the Apache 2.0 licence.

> We built Kolibri for sovereign and specialised deployment, with a particular focus on German and on regulated domains such as public administration, industry, and aerospace. To support these settings, we control the full model-development process, including data, architecture, training infrastructure, post-training, and evaluation.

Dupe of https://news.ycombinator.com/item?id=49942706

As a Linux user, sad to hear, but totally understandable. As a paying Kagi user, I don't want them to spread their resources too thin.

Thanks for the honest attempt! Hope someone takes the torch and carries it forward.

Warning: Hyperion ends on a cliffhanger, you'll want to get The Fall of Hyperion (the sequel).

The entire cantos is great, tho I prefer the first two to the Endymion/Rise of Endymion.

> if my product/company was focused on some sort of classification problem

It's more likely the product is focused on something else, but a classification model could come in handy...

You need to have enough high quality data to train with, knowledge how to do it, and developer time.

In practice, that's enough of a barrier to not even try the approach on a number of cases where it might potentially be useful.

I wouldn't be surprised if Jev turned out to be a "gateway drug" that validates approach on a use case, the team gathers experience and labeled data, and switches to an in house locally tuned model to minimize costs.

> The OP seems to have anticipated this and mentions you can fine tune it for your use case. Did you try that?

You can already so that with classification models such as ModernBERT, at 0.4B.

Jev's value is its zero shot performance without having to fine-tune.

I have a few qualms with this response:

1. For a techie, you can already de-Google yourself trivially by asking the AI to build you a bespoke web crawler and run it on Lambda or Cloudflare workers to index the entire internet and store it in DuckDB.

2. The answer doesn't actually help the user get back useful results from Google.

3. "Let me know" doesn't scale, and it's not obvious how talking to random internet strangers about their Google problems will increase your startup SEO?

I hope disabling /r if telemetry is disabled is also unintentional...

Opus 5.5 is neck-and-neck with Fable 5.1 and Astra 6 in my vibe-coding tests - maybe even better than Fable 5.1

Minecraft clone: https://senko.net/vibecode-bench/2026/voxel-opus-5.5.html (Opus 5.5) vs https://senko.net/vibecode-bench/2026/voxel-fable-5.1.html (Fable 5.1) vs https://senko.net/vibecode-bench/2026/voxel-gpt-6-astra.html (Astra 6)

Warcraft clone: https://senko.net/vibecode-bench/2026/rts-opus-5.5.html (Opus 5.5) vs https://senko.net/vibecode-bench/2026/rts-fable-5.1.html (Fable 5.1) vs https://senko.net/vibecode-bench/2026/rts-gpt-6-astra.html (Astra 6)

The above Opus games took ~45min to generate with the cost between $11 and $14 (per ccusage - I'm on a Max sub). Used from Claude Code with xhigh effort.

Full tests with prompts: https://senko.net/vibecode-bench/

How about just not connecting it to nukes, then?

> Just five years ago, the only way to build a working project of moderate complexity was to learn the basic to intermediate concepts required to make an MVP.

> Now, if you can steer an LLM reasonably well, you can quickly build an MVP that goes well beyond your own understanding of the implementation.

Somewhat agree. Five years ago you could build an MVP without understanding how to open TCP sockets or how to parse HTTP headers. You didn't need to understand relational databases, let alone B-trees or cache locality. You didn't need to know how to install Linux.

Now you don't need to understand the details of connecting to Stripe or Auth0 or setting up a Kubernetes cluster.

> You have to intentionally build your understanding as you build your projects.

Some things you need to understand-others, not so much. Depends on what you're doing, the scale, risks, etc, but that's always been the case.

Maybe not to the same extent. In a company I worked with recently they used it a lot but didn't store data in it, meaning there was very little lock-in: mostly inertia/convenience.

If BS slightly raise the price and ruthlessly cut costs (think - leave just a skeleton crew to keep it running), the calculation may make sense even if there's slow churn in the users and no special lock in.

(disclaimer: pure outsider speculation on my part)

Shit that sucks. They'll probably all be let go if BS do their usual thing.

Dupe: https://news.ycombinator.com/item?id=49643848

(this one is older but the other one got to the front page and will accrue more discussion)