andersmurphy

7 ms·

1.
by andersmurphy 7d ago
I mean the fact that comments like this get downvoted is wild.
2.
by andersmurphy 7d ago
You'd think theft would still be illegal regardless of what a privacy policy says.
3.
by andersmurphy 11d ago
I think people get hung up on high availability (HA), and ironically don't test their backups. Single node with streaming backups to S3 (simple in a single writer system) can give you a system that will at most lose a few seconds of da
4.
by andersmurphy 13d ago
Sadly they do not. They stop after the first frame (at least last time I tested it). They also don't always support window sizes above 8MB which means levels above 19 can fail to decompress (if they use the more than 8MB of window).
5.
by andersmurphy 13d ago
I'm surprised the faster decompression speed of zstd wasn't mentioned. Feels like a big win for cache (assuming decompress on read). A shame browsers don't support concatenating zstd frames (which zstd does support). Then you
6.
by andersmurphy 13d ago
There's negative levels for faster decoding and compression. level -1 uses half the CPU of level 1 and with a custom window size can be really good for streaming compression. I think the negative levels go down to -7 if I remember corr
7.
by andersmurphy 25d ago
Project into sqlite on your app server is the main trick I use. Denormalize if you have to. Hell, for a lot of projects you don't even need to get that fancy. Run a single server with an embedde database, running Go or Java and you&#x2
8.
by andersmurphy 26d ago
I think a lot of the time when people say the network is slow. They really mean their backend is slow. With a fast backend ~1-5ms response times (not even that fast). Streaming compression over something like SSE to keep your response sub 1
9.
by andersmurphy 27d ago
The paradox of AI. The better it is the less benefit there is to being an early adopter.
10.
by andersmurphy 27d ago
Is it? Sqlite seems pretty fast. [1] [1] - https://andersmurphy.com/2025/12/02/100000-tps-over-a-billio...
11.
by andersmurphy 1mo ago
This is why my theory is LLMs are self defeating in large orgs. Or worse terminal for the organisation. For everyone adding value with LLMs there will be way more destroying value. If you roll a critical failure a mediocre LLM enhanced VP c
12.
by andersmurphy 1mo ago
I mean that's a fair take. But, for me it's not so much that it doesn't match my view. I'm honestly mixed on the whole thing (I am probably most concerned about the finances). It's more that the articles they write
13.
by andersmurphy 1mo ago
Judging by the amount of insider interviews it's more than just ads. Longtime subscriber. Pretty disappointed in how biased their coverage is. The most critical piece they have put out on AI is oh no it's so powerful it's hac
14.
by andersmurphy 1mo ago
Anthropic is a sponsor of The Economist. So maybe that influences their retoric somewhat.
15.
by andersmurphy 1mo ago
Also worth pointing out Anthropic is a sponsor of The Economist. Probably muddies the water some more.
16.
by andersmurphy 1mo ago
Agreed! Cloudflare absolutely destroys user experience and honestly doesn't seem that effective in practice. What's worked for me is I block any client that don't support brotli compression and http2. Seems to work well enoug
17.
by andersmurphy 2mo ago
So compression ratios with streaming compression (brotli/zstd) come down to the regularity of the data, the size of the change, and the size of your window. Basically, if your html fat morph frames are 65kb uncompressed and you make a
18.
by andersmurphy 2mo ago
It's nice to see HTMX4 is adopting the core strengths of Datastar. That sort of cross pollination of ideas is a huge boon to the wider hypermedia community in general.
19.
by andersmurphy 2mo ago
A focus on morph by default means you don't have an explosion of endpoints and can write programs like the 300 redirect days. [1] Once you want realtime/collaborative app SSE + morph lets you do that easily. Add streaming compress
20.
by andersmurphy 2mo ago
My experience was similar. I'd wound down a startup and as a solo developer could no longer afford to do react + a backend. So I tried HTMX, then turbo (which introduced me to morph and push based re-fetch). Finally moved to datastar b
21.
by andersmurphy 2mo ago
RDS*
22.
by andersmurphy 2mo ago
Sqlite with litestream has a smaller default window of data loss than RDF. 1s vs 5 minutes.
23.
by andersmurphy 2mo ago
I would only recommend sqlite if you know what you are doing (and/or prepared to learn it inside out). It's more of a build your own database primitive (often you'll have multiple sqlite databases for different things). Which
24.
by andersmurphy 2mo ago
Personally, I think the better way to tackle sqlite_busy is to have a single writer managed at the application level. That effectively eliminates sqlite_busy in the context of a single process. > To ensure write operations don't suf
25.
by andersmurphy 2mo ago
> The bottom line Is how Claude ends 90% of articles. So yes LLM slop.
26.
by andersmurphy 2mo ago
Maybe maybe not. In large organisations for each person creating value with LLMs there are probably more destroying value. Bob used to only waste one person time with LLMs he can waste the entire organisations time. Anyone can use an LLM ma
27.
by andersmurphy 2mo ago
Philip Walder (one of the creators of Haskell) was our lecturer for my CS introductory course. I'd never done any programming before then. Yes, imperative languages were initially counter intuitive to me. OO was even worse. SQL was fin
28.
by andersmurphy 2mo ago
Yeah compile times have always mattered. It's why games often have a scripting layer in lua despite the engines being C/C++.
29.
by andersmurphy 2mo ago
Lisp/smalltalk programmers have been going on about this tradeoff for a long time. It mattered before LLMs too. Lisp/Clojure repl allowing you to compile tiny parts of your program inside your running program is incredible for you
30.
by andersmurphy 2mo ago
That's partly the problem ORMs. Lowest common denominator that prevents you from leveraging a lot of the power of your actual database.

More ›