mjw1007

6 ms·

1.
by mjw1007 1mo ago
Parliament can also impeach ministers. It hasn't bothered trying for about 180 years because a vote of no confidence is simpler, but it hasn't given up the power (and it's hard to argue that it's somehow fallen into abey
2.
by mjw1007 2mo ago
The physical replication docs say "the hardware architecture must be the same", though they don't define "architecture".
3.
by mjw1007 2mo ago
I think the postgresql maintainers don't claim to support moving a database from x86 to arm without a dump-and-reload. The docs tend to say "same hardware architecture". Though if they don't intend to support this case I
4.
by mjw1007 4mo ago
GitHub also centralises abuse detection. I'm not thinking about sophisticated attacks here so much as dealing with plain old spam. That's fairly easy to deal with on a tiny scale, and possible on a huge scale, but it's a grea
5.
by mjw1007 7mo ago
It's common that if you extract a function or a module with a well defined interface, that function or module can't tell whether a "bad" input indicates an expected or an unexpected error. For example division by zero of
6.
by mjw1007 7mo ago
Not any more, according to this article you're commenting on, no.
7.
by mjw1007 9mo ago
> If a package hosted by Fedora or Debian or PyPI or crates.io, etc claims to correspond to an upstream git commit or release, then the hosting system should build the package, from the commit or release in question plus whatever packa
8.
by mjw1007 10mo ago
They weren't in any way attempting to rely on security by obscurity. They didn't assume nobody would guess the URL. They did take active steps to ensure the data was only available at the correct time. But they didn't check t
9.
by mjw1007 10mo ago
Is this a real judge, or is an "Immigration Judge" one of those not-actually-a-judge decisionmakers employed by the executive?
10.
by mjw1007 10mo ago
I think what you've written is pretty much what the "almost all programs have paths that crash" was intended to convey. I think "perhaps the density of crashes will be tolerable" means something like "we can re
11.
by mjw1007 11mo ago
It makes tab completion work.
12.
by mjw1007 1y ago
One of the things that this group of "stewards" could do to get their costs down is get together and implement a high quality free software caching proxy that understands all their back-ends. But that would compete with the commer
13.
by mjw1007 1y ago
It's clear from that bug tracker that you shouldn't let libxlst see untrusted stylesheets or xpath expressions. I haven't yet seen a problem with running your own transformations against untrusted XML. Maybe a new maintainer
14.
by mjw1007 1y ago
There's still work being done on the Reference, which is being maintained in the same way as it has been since the Rust documentation team was disbanded in 2020. But it's a very long way from being either complete or correct enoug
15.
by mjw1007 1y ago
The plan described in "Our Vision for the Rust Specification", and the linked RFC3355, were abandoned early in 2024. The team that was formed to carry out RFC3355 still exists, though it's had an almost complete turnover of m
16.
by mjw1007 1y ago
Also vidir, which is in the moreutils package in popular distros.
17.
by mjw1007 1y ago
It's supposed to be 10^5 W heating per square metre, and the aeroplane's cross-section is much smaller than a square metre.
18.
by mjw1007 1y ago
My mistake. The support for writing CGI programs in Python is in wsgiref.handlers.CGIHandler .
19.
by mjw1007 1y ago
The Python maintainers are removing the module _named_ cgi, but they're not removing the support for implementing CGI scripts, which is CGIHTTPRequestHandler in the http.server module. All that was in the cgi module was a few functions
20.
by mjw1007 1y ago
It would be better if there was a layer of maintainers between the free software authors and the end users that could act as a buffer in cases like this, in particular to take care of security vulnerabilities that genuinely need dealing wit
21.
by mjw1007 1y ago
I agree it can be domain-specific, but I think it's more common than not that empty containers, and the number zero, are corner cases rather than typical values. So I think it would be a decent quality-of-life improvement to make gener
22.
by mjw1007 1y ago
I've found in practice that shrinking to get the "smallest amount of detail" is often unhelpful. Suppose I have a function which takes four string parameters, and I have a bug which means it crashes if the third is empty. I&#
23.
by mjw1007 1y ago
I suggest it would be helpful if the README's intro expanded a little more on the project's scope. "for postgres" is a bit vague, and "focusing on developer experience and reliable SQL tooling." doesn't te
24.
by mjw1007 1y ago
A year or so ago I read through one smallish section (basically function calls) and filed issues for the problems I found that were easy to write up crisply. They fixed the easy bugs: https://github.com/ferrocene/specif
25.
by mjw1007 1y ago
The Ferrocene Language Specification has two serious problems: there are very large gaps in it, and what's present is very buggy. If you pick a small part and look at it in isolation it typically looks quite plausible, but if you try t
26.
Adopting the FLS(blog.rust-lang.org)
2 points by mjw1007 1y ago|0 comments
27.
Ferrous Systems Donates Ferrocene Language Specification to Rust Project(rustfoundation.org)
61 points by mjw1007 1y ago|5 comments
28.
by mjw1007 1y ago
Beyond the basic implementation of quoting and escaping, those are things you also have to worry about if you use someone else's csv parser. And if you implement your own, you get to choose the answers you want.
29.
by mjw1007 2y ago
The former.
30.
by mjw1007 2y ago
The bad documentation I come across often shows every sign of having taken the advice from this article (and others like it) to heart. The trouble is that the advice doesn't include ways to make sure your documentation actually covers

More ›