lightningspirit

10 ms·

1.
by lightningspirit 3mo ago
Good to know you're still building your own tools like back in the "old days" :)
2.
by lightningspirit 3mo ago
And then everybody left, yeah, I remember this exactly.
3.
Benchmarks and Obscurantism: A "red" line that should not be crossed(clickhouse.com)
3 points by lightningspirit 3mo ago|0 comments
4.
by lightningspirit 3mo ago
I think we're comparing two very different categories. COBOL is an application language, whereas TCP and HTTP are foundational infrastructure. Replacing a language is challenging, but replacing the infrastructure that underpins most of
5.
by lightningspirit 3mo ago
> {"a":1,"b":2} and {"b":2,"a":1} are the same query and two different cache entries These two payloads are actually different. You're talking about semantics, which is determined by the paylo
6.
by lightningspirit 3mo ago
This is controlled by the (Last-Modified, If-Modified-Since) and (ETag, If-None-Match) header pairs. HTTP is stateless; it does not require any persistence. The only thing that defines kind of an optional persistence is the caching layer, f
7.
by lightningspirit 3mo ago
How does the origin server indicate that?
8.
by lightningspirit 3mo ago
I don't think this requires so much discussion; it is a very obvious and simple addition, IMO.
9.
by lightningspirit 3mo ago
How does this break rest?
10.
by lightningspirit 3mo ago
It won't break GraphQL, as it uses POST. It can very much improve it if adopted: - use QUERY method when querying resources - use POST method for mutations
11.
by lightningspirit 3mo ago
Because HTTP is stateless by definition, you now need to support persistence (state) on the server side whenever you want to run a slightly different query, which contradicts the preamble. I understand the confusion around GraphQL's ca
12.
by lightningspirit 3mo ago
The internet is complex, and you have tons of protocols that are not well supported. TCP/HTTP are well supported by proxies and have well-defined, stable specs, which also help with caching, throttling, etc. Just because it's old
13.
by lightningspirit 3mo ago
I think most of the value LLMs provide comes from connecting the dots between unsolved questions and patterns or structures that have already been demonstrated, which accelerates research. Now, reasoning in the sense of making truly origina
14.
by lightningspirit 7mo ago
Yeah, I was surprised by that as well.
15.
by lightningspirit 7mo ago
If there's only a centralized system that uses digital IDs to hand off providers only a "yay" or "nay"...
16.
by lightningspirit 7mo ago
That makes sense. Wi-Fi uses radio waves, part of the light spectrum. Like our eyes or cameras can watch and record, Wi-Fi can also be used for this purpose.
17.
by lightningspirit 8mo ago
If you do `new Date('2025-11-31T00:00:00Z')` you get `2025-12-01T00:00:00.000Z`, which is weird and potential cause for bugs when parsing date string from input. Right because of these inconsistency I created a small package backe
18.
by lightningspirit 8mo ago
I like this solution, it looks very simple and should’ve been consider as part of best practices if it works technically. However, I also think that this whole trade off is broken from the beginning, it should be part of browser’s set of ru
19.
by lightningspirit 10mo ago
It is mentioned in the article that round-robin DNS is an alternative to this setup, however, in reality, it is not the same thing, and that's the reason load-balancers exist, and it is not feasible to provide something very similar du
20.
by lightningspirit 10mo ago
In that case, can you reduce pricing for customers, too?
21.
by lightningspirit 1y ago
I've been using Docker Swarm for almost 6 years now deploying entire stacks for customers on top of it — it's stable and incredibly cheap to maintain.
22.
by lightningspirit 1y ago
The balance example should have been explained in more detail — it’s clearly a transactional system where the balance is derived from the sum of transaction log data. CRDTs have nothing to do with it and it is a bad example.
23.
by lightningspirit 2y ago
Matt also knows that the messy WordPress API (both actions and filters) is difficult to integrate into a well-architected software project as a plug-and-play mechanism.
24.
by lightningspirit 2y ago
Actually, when someone forks a project creates a new repo. This is not the case, the plugin was indeed a take over instead.
25.
by lightningspirit 2y ago
Although jq query style is not absolutely pleasant I see many examples where this tool can be used such as data transformation, import/export and linux pipelines that need access to databases.
26.
by lightningspirit 2y ago
Docker (and to an extend, Docker Swarm) is a good alternative where simplicity, lightweightness and stability are key points. Using it for almost 4 years in many projects with thousands of views each day, both on single or two VMs. No failu