Diggsey

7 ms·

31.
by Diggsey 1y ago
Why would it only be run once? The WHERE condition of the outer query is run multiple times: once for each row, so of course it can return TRUE multiple times. For example: DELETE FROM example WHERE id = (SELECT RANDOM(0, 100) FROM ot
32.
by Diggsey 1y ago
I think your logic is flawed (even if PostgreSQL may behave this way in practice). First, let's make sure we're talking about the same two examples. A: DELETE FROM task_queue WHERE id = ( SELECT id FROM task_queue
33.
by Diggsey 1y ago
Based on my understanding, your comment is the most accurate in this thread. However, I think it's telling that almost every single comment here has a different understanding of how PostgreSQL works, and nobody can link to any document
34.
by Diggsey 1y ago
> Every webapp built with something other than GraphQL ends up with an ad hoc, informally-specified, bug-ridden, slow implementation of half of GraphQL. Not remotely true. There are plenty of web apps that work just fine with a standard
35.
by Diggsey 1y ago
If you just mean using array indexes instead of pointers, that can work in some cases, but can run into concurrency issues when the container needs to be resized. With pointers to nodes, new nodes can be allocated and old nodes freed on a s
36.
by Diggsey 1y ago
They are definitely more error-prone usage patterns, and coming from Rust the amount of hidden unsafety is quite unsettling (in addition to the obvious potential for user errors, depending on the aliasing model of your language/compile
37.
by Diggsey 2y ago
> I worked on the Cell processor and I can tell you it was a nightmare. It demanded an unrealistic amount of micromanagement and gave developers rope to hang themselves with. So the designers of the Cell processor made some mistakes and
38.
by Diggsey 2y ago
I recently had to implement SAML and this headline does not surprise me in the slightest. The SAML spec itself is fairly reasonable, but is built upon XML signatures (and in turn, XML canonicalization) which are truly insane standards, if t
39.
by Diggsey 2y ago
This is the worst take... People consistently misuse the Swiss cheese security metaphor to justify putting multiple ineffective security barriers in place. The holes in the cheese are supposed to represent unknown or very difficult to exp
40.
by Diggsey 2y ago
I have a Rust crate (ijson) which implements string interning and a generally much more efficient in-memory JSON representation. It probably doesn't compete with the author's specialized implementation, but if you just want a plug
41.
by Diggsey 2y ago
> Now imagine that corporate tax rate was 40% instead. It completely changes the decision-making process. Seems more like a question of degree. Dividends are also taxed as income so ~36% is already paid in tax depoending on the income of
42.
by Diggsey 2y ago
I don't think that's accurate. It was adding Rust DMA code that was to be shared between Rust drivers that was the spark. The C code was unchanged AFAIK.
43.
by Diggsey 2y ago
Huge! Async function traits resolve one of the biggest pain points for async rust.
44.
by Diggsey 2y ago
I haven't used Caddy but it's config format can't be worse than nginx's. Some crazy gotchas with the way nginx config works...
45.
by Diggsey 2y ago
I don't agree, I think you're just describing two sides of the same coin. As a software developer I want strong abstractions without bloat. LLMs are so successful in part because they are a really strong abstraction. You feed in
46.
by Diggsey 2y ago
Noone's asking the maintainers to make the project happen. It is the maintainers job to determine whether a project should be pursued at all. If a maintainer says "yes I'd be happy to accept feature X", and then simp
47.
by Diggsey 2y ago
He's not wrong, but he hasn't addressed the problem: Some maintainers are rejecting changes as a way to block a project they disagree with - ie. there is no path forward for the contributor. I wouldn't assume this normally, b
48.
by Diggsey 2y ago
The example is overly simplified. It glosses over many of the subtle-but-important aspects of durable execution. For example: - Steps should be small but fallible operations - eg. sending a request to an external service. You generally want
49.
by Diggsey 2y ago
Using AI is like trying to build a product with only extremely junior devs. You can get something working fairly quickly but sooner rather than later it's going to collapse in on itself and there won't be anyone around capable of
50.
by Diggsey 2y ago
You seem to be very confused. Even in countries like the UK with weaker freedom-of-speech laws, there are specific exceptions to slander law for insults.
51.
by Diggsey 2y ago
The "right to not be insulted" is literally censorship.
52.
by Diggsey 2y ago
Companies already pay for cyber insurance because they don't want to take on this risk themselves. In principle the insurance company then dictates security requirements back to the company in order to keep the premiums manageable. How
53.
by Diggsey 2y ago
In this case you just set the column value to the existing value...
54.
by Diggsey 2y ago
That has not been my experience. SQL is a fully fledged programming language so there's very little that you can't express this way. What are you doing that requires dynamically building a query?
55.
by Diggsey 2y ago
FWIW, you very rarely need to make the query itself dynamic. After all, SQL alone is powerful enough to do conditionals. For example: SELECT * FROM example WHERE ($1 IS NULL OR field1 = $1) AND ($2 IS NULL OR field2 = $2)
56.
by Diggsey 2y ago
SQL, while not great, does have some advantages that are hard to beat: - Everyone knows at least some basic SQL, even non-technical users have often encountered it in some form. - The documentation for eg. PostgreSQL is for SQL, so if you w
57.
by Diggsey 2y ago
I thought this was https://simonsapin.github.io/wtf-8/
58.
by Diggsey 2y ago
> Maybe not yet, but it is heading in that direction; It's definitely getting more complex, but C++ has a huge lead haha. C++ is like a fractal in that you can look at almost any feature closer and closer to reveal more and more c
59.
by Diggsey 2y ago
Historically there have been too many constraints on the Linux syscall interface: - Performance - Stability - Convenience - Security This differs from eg. Windows because on Windows the stable interface to the OS is in user-space, not tied
60.
by Diggsey 2y ago
> 65% of the public believe it is fair for electric car drivers to be taxed, but at a lower rate than petrol and diesel drivers Electric cars still use roads, which still need to be maintained. There's no "extrapolation of logi

More ›