This matches what I’ve seen in practice, individual tasks may become faster, but the overall development process doesn’t automatically improve. Heavily dependant of the real hands behind.
HN user
rfmoz
Another SQLite user here. My site gets constantly hammered by crawlers, and SQLite just keeps going on hit miss. Anyway, the real magic is on the ram and the ssd perf.
What would be the best device to put any of these ones over the desk? And old phone? Maybe an esp32?
The main differences between OpenBSD, FreeBSD, NetBSD and DragonFly BSD
https://unixdigest.com/articles/the-main-differences-between...
I used to run it on a laptop too, but the battery life was shorter and the laptop ran noticeably hotter than under Linux, so I eventually switched back.
That said, OpenBSD feels unusually coherent (ej. check wifi connection from terminal). The whole system has a level of consistency that's hard to find elsewhere, also between other BSDs.
For pet servers, it usually fits perfect.
Totally agree, Vis really hits an spot between modern feel without losing what made vi great. The structural regex is a game-changer.
I miss on the list Counterpoint GUI for Amstrad PCs with MS-DOS
Any provider for critical domain vault?
Search on bios-mods for a modified whitelist BIOS firmware -> https://www.bios-mods.com/forum/Forum-WiFi-WWAN-Whitelist-Re...
There are modified BIOS firmware that allow any WiFi card. Good luck
Vis editor [0] also has multicursor and powerful sam's structural regular expression
Yes, "everything is a file" but the mouse on Rio is written in stone.
Aside of that, plan9 wins on the theoretical side, it was a research OS, but in the practical one... it's opinionated.
Linux Firewalls by Steve Suehring covers nftables. It’s a good book to know the basics.
Give a try to Meshcore, their design has proven to be reliable in realworld use.
Chinese AI is doing large amounts of request in the past weeks.
They had pretty neat infra, maybe it still runs in the same clever way. https://meta.stackexchange.com/questions/10369/which-tools-a...
Quora, sadly, is a good example of enshittification.
I reply myself because I've found that idea already porposed:
"Origin policy was a proposal for a web platform mechanism that allows origins to set their origin-wide configuration in a central location, instead of using per-response HTTP headers." - https://github.com/WICG/origin-policy
But their status is "[On hold for now]" since, at least, three years ago.
The reference of robots.txt offer a good way to define specific behavior for the whole domain, as example. Something like that for security could be enough for large amount of websites.
Also, a new header like “sec-policy: foo-url” may be a clean way to move away that definitions from the app+web+proxy+cdn mesh to a fixed clear point.
Adding more security headers every year feels like strapping seatbelts onto a collapsing roller coaster. It would be better to stop this "sec headers stack" in favour of simpler, secure by default browser primitives with explicit opt-out. Getting an example from https://securityheaders.com the list nowadays is as follows:
- Strict-Transport-Security - Content-Security-Policy - X-Frame-Options - X-Content-Type-Options - Referrer-Policy - Permissions-Policy - Cross-Origin-Embedder-Policy - Cross-Origin-Opener-Policy - Cross-Origin-Resource-Policy
CDNs manage user TLS certificates and that is one of the advantages of using them.
A node server could negociate https close to the user, do caching stuff and create an other https connection to your local server (or reuse an existing one).
Https everywhere with your CDN in middle.
They do in some way because the LaLiga blocking problems in Spain don’t affect the paid accounts=large websites.
An other suggestion is to do it along night shift in every country, right now they only take into account EEUU night.
MeshCore app is way better than the Meshtastic one.
Let me extend the question to what’s wrong with NFTables on Linux? It’s a different way to manage Netfilter, out of IPTables
The development move in ZFS from FreeBSD to OpenZFS (AKA Linux) was a mayor point on that.
Playing with protocol number change usually results in “Protocol Unreachable” or “Malformed Packet” from your OS.
RUDP from Plan9 was a nice step between TCP and UDP - https://en.wikipedia.org/wiki/Reliable_User_Datagram_Protoco...
An interesting thread about the upgrade exists on the same list that the link points to, just a few messages earlier. Hopefully, with the donations, the project can improve the existing friction points - https://mail-index.netbsd.org/netbsd-users/2025/10/01/msg033...
from what point of view are you looking for?
Connecting to wifi on OpenBSD terminal is wonder simple, one reflection to the meticulous work behind the system.