hbbio

Not comparing. Sometimes, there are 2 bad apples.

Strange that they apparently raised $169M (really?) and the website looks like this. Don't get me wrong: Plain HTML would do if "perfect", or you would expect something heavily designed. But script-kiddie vibe coded seems off.

The idea is good though and could work.

A much better source is https://go.dev/doc/go1.26

Now they acquired Photomator with Pixelmator, but it's still an independent subscription... not even included in this bundle. Maybe they just forgot.

Makes a lot of sense for SQLite to be written in C. It's a heavily optimized and debugged database implementation: Just look at btree.c with all its gotos :)

The only language that would make sense for a partial/progressive migration is zig, in huge part due to its compatibility with C. It's not mentioned in the article though.

The problem we tried to solve with Opa was more general than RSC, probably too general.

    // Opa decides
    function client_or_server (x, y) { ... }
    // Client-side
    client function client_function(x, y) {= }
    // Server-side
    server function server_function(x, y) {... }

Without the optional side inference (which could also use both), it seems we had similar side constraints, and serializers/sanitizers. Probably with the same flaws as the recent vulnerabilities... Like all the OWASP AppSec circa 2013-2015 range of exploits in browser countermeasures when the browsers where starting to roll out defense in depth with string matching :)

We pioneered a lot of things with Opa, 15 years ago now. Opa featured automatic code "splitting" between client and server, introduced the JSX syntax although it wasn't called that way (Jordan at Facebook used Opa before creating React, but the discussions around the syntax happened at W3C notably with another Facebook employee, Tobie).

Since the Opa compiler was implemented in OCaml (we were looking more like Svelte than React as a pure lib), we performed a lot of statical analysis to prevent the wide range of attacks on frontend code (XSS, CSRF, etc.) and backend code. The Opa compiler became a huge beast in part because of that.

In retrospect, better separation of concerns and foregoing completely the idea of automatic code splitting (what React Server Components is) or even having a single app semantics is probably better for the near future. Our vision (way too early), was that we could design a simple language for the semantics and a perfect advanced compiler that would magically output both the client and the server from that specification. Maybe it's still doable with deterministic methods. Maybe LLMs will get to automatic code generation of all parts in one shot before.

Ethereum is so good at being distributed than it's decentralized.

DynamoDB and Spanner are both great, but they're meant to be run by a single admin. It's a considerably simpler problem to solve.

> Blockchains are still a scam

Did you actually look at the blockchain nodes implementation as of 2025 and what's in the roadmap? Ethereum nodes/L2s with optimistic or zk-proofs are probably the most advanced distributed databases that actually work.

(not talking about "coins" and stuff obviously, another debate)

Power10-based processors are manufactured by Samsung using a 7 nm process

Previous discussion: https://news.ycombinator.com/item?id=11477565

Who would have predicted KDE could become the foundation of both AI and gaming

Codeberg is a fork of Gitea, itself a fork of Gogs.

Both forks originated for "philosophical" reasons, not technical ones and Joe Chen (@unknwon on GH) deserves a lot of the merit for building a clean forge in Go mostly by himself.

Thanks for adding!

Extending beyond the pelican is very interesting, especially until your page gets enough recognition to be "optimized" by the AI companies.

It seems both Gemini 3 and latest ChatGPTs get a deep understanding of the representation of SVGs that seems a difficult task. I would be incapable of writing a SVG without visualizing the result and a graphical feedback loop.

PS: Would be fun to add "animated" in the short prompt since some models think of animation by themselves. Tried manually with 5 Pro (using the subscription), and in a sense it's worse than the static image. To start, there's a error: https://bafybeie7gazq46mbztab2etpln7sqe5is6et2ojheuorjpvrr2u...

You should add ChatGPT.

I tried the first one and 5 Pro gives this: https://imgur.com/a/EhYroCE

Thx for the explanation!

Side thought as we're working on 100% onchain systems (for digital assets security, different goals):

Public chains (e.g. EVMs) can be a tamper‑evident gate that only promotes a new config artifact if (a) a delay or multi‑sig review has elapsed, and (b) a succinct proof shows the artifact satisfies safety invariants like ≤200 features, deduped, schema X, etc.

That could have blocked propagation of the oversized file long before it reached the edge :)

Yes, if anything it's bullish on CloudFlare because many investors don't realize how pervasive it is.

> livestreams had transient memory leaks for months already

maybe it's vibe coded nowadays

Has been the true core vision of the web if not mobile. If I remember correctly, that is how the original Basecamp was implemented, or Craigslist (still is?)... or this very website

Still on Sublime, and helix in terminal.

Tried zed, it's interesting but several things are missing including the ability to skip extensions auto-update... which imho is critical for security.

TEEs don't work, period.

FHE does (ok, it's much slower for now).

Nothing wrong with using AI to write code.

It's probably good to disclose this upfront and since you're a student that can be a starting point to keep improving the project until it's well architected and you understand every detail of it and why it's designed this way.

The article (and maybe the code) is/are written by LLMs.

There's more than the README that is generated.

Coinbase was hacked for $400M when literally someone from outsourced support services was taking screenshots on their phone!

The culprit had more than 10k photos of all security details for thousands of wealthy customers.

I have been using mc for almost 30 years, and the original Norton Commander as a kid before that!

Pleasantly surprised to see this topping HN today, and even more than the project and its website are still maintained in 2025.

Didn't expect to see the FSL for that kind of project :)

The part I'm interested in is the tray_icon crate but I'll look at the package directly https://docs.rs/tray-icon/latest/tray_icon/.

I would say in 2025, it has become exponentially more complex, not simpler:

1. The ecosystem has fragmented further. Every app uses even more tools and frameworks, each with its own quirks and version incompatibilities

2. With E2EE and blockchain-based apps becoming mainstream, the frontend now handles complex cryptographic operations, key management, and secure data handling entirely client-side. Mistakes here are security vulnerabilities

3. Advanced interactions, personalization, and real-time updates require sophisticated client-side computation. We're beyond "thin clients"

4. The Big 4 invest $millions in each interface and users expect the same level of UX/UI from anyone. Let's talk about simplicity on the surface :)

The elephant in the room is who controls/decides on the outcome.

See https://decrypt.co/311634/polymarket-allegations-oracle-mani...

Yes, I know them too, I live there!

The hardware is great, CANN is not CUDA yet.