bricss

You mixing broadcast band physical phenomenon with censorship.

If only there was an algorithm for password strength estimation > . <

How about Xitter? :)

No wukkas, JPEG XL support in Chrome ships by the EOM \o/

Rogue AI removed containers from deployment?

Barely ~3 t/s on a laptop GPU > . <

Qwen3.8-35B-A3B would be really appreciated (-/\-)

FYI -> https://www.npmjs.com/package/rekwest

Are Bun and Deno in the room with us right now?

There also DRUUID: https://gist.github.com/bricss/53e5babedf44bf3ab71334c15102e...

Somebody has to revive Nullsoft WASTE p2p from 2003 tho

But can we train AI on this beautifully hand-crafted material, and ask it later to rewrite Rust with Zig? :]

Mitochondria emits UV light

All correct

Welp, never use sequential IDs

In huge number of cases you will have timestamps in the payload anyway, since most db records will have unredacted createdOn, updatedOn fields for display in the UI.

If knowing IDs has a negative impact on security, then application system design is probably a trash.

React is a pure abomination, and probably the worst thing that could happen to the web. Imagine Backbone with JSX, but w/o MVC, MVP or/and MVVM in mind. The amount of code that one needs to write even to handle simple registration form is the mind-blowing. Thanks to the lack of two-way binding support, when everything needs to be handled by hand, leading to the bloated codebase of copy-pasta of zillion of hooks. So, instead of focusing on biz logic, devs mostly end up writing scaffolding and functional logic.

Wrong, maintainer started conversations with complete rejection, and continued to coming up with new ideas why not to accept the PR. And maintainer started to drag politics into conversation, such as elitism.

Replace N in Nue with V for Vue, and it will be perfection.