mjw1007

52 ms·

541.
by mjw1007 7y ago
If you're trying to analyse a program statically and find some property of its runtime behaviour, the halting problem only gets in the way when you need to be accurate about both whether the runtime behaviour does or doesn't have
542.
by mjw1007 7y ago
As I understand it, this is a proposal for formalising Rust's existing rules around memory safety and the borrow checker.
543.
by mjw1007 7y ago
It seems to me that there are three pieces we'd like to have, to show that we can trust Rust's borrow checker as much as we'd like to: - a runtime model of a hypothetical dialect of Rust without a borrow checker, defining whi
544.
by mjw1007 7y ago
« Exclusion of the lower bound forces for a subsequence starting at the smallest natural number the lower bound as mentioned into the realm of the unnatural numbers » There's a parallel argument for being inclusive in the upper bound:
545.
by mjw1007 7y ago
If the message was silently censored, there's no reason to believe that the list manager is claiming that it was antisemitic. Here's another possible explanation: maybe the message was posted by an individual who is generally bann
546.
by mjw1007 7y ago
To be honest, I think you're being too generous. The problem isn't that they're providing documentation which is good but only appropriate for a narrow audience. The documentation is just bad: it misses out things that need t
547.
by mjw1007 7y ago
It looks to me like that quote is talking about one particular sequence that they've left out of their list (it's explaining why they did that), not about the 13 sequences that they have listed.
548.
by mjw1007 7y ago
Not as far as I can see, no. That article contains the following claim: « Computers, however, are only as good as their programmer and tend to offer engineers a false sense of security. » which matches the "dark side of expertise"
549.
by mjw1007 7y ago
I think "wrong inputs" here is an odd way of saying that the model was bad (presumably to distinguish that problem from outright bugs in the design software or computer hardware failure). https://eng-resources.uncc.edu&
550.
by mjw1007 7y ago
There's also an unexplained leap from "the calculations are correct" to "we should proceed as planned even though it's sagging when it shouldn't". Even if the engineers were infinitely arrogant and assumed
551.
by mjw1007 7y ago
What "deepening crisis" is this? Is it just the usual internet drama with a few people being unpleasant to each other and then storming off in a huff, or something more serious?
552.
by mjw1007 7y ago
Also https://github.com/brutusin/wava
553.
by mjw1007 7y ago
« better specs for jobs dependencies, timeouts, resource policies and retries without hacky wrappers and boilerplate » This is what I miss. There's a strange gap in traditional Unix there, compared to other time-sharing systems. I hav
554.
by mjw1007 7y ago
I think if Go hadn't been already known, it would have been discovered in the twentieth century. Dozens, if not hundreds, of other abstract games were, and I don't think there are many as simple. It's not so obvious that anyo
555.
by mjw1007 7y ago
https://support.mozilla.org/en-US/kb/firefox-preview-upgrade... appears to say that, yes, that is what they plan on releasing.
556.
by mjw1007 7y ago
I don't think he was at all surprised at how bad the films were, but that doesn't mean he shouldn't complain about them. I think it's easy for many people who are used to a diet of truly terrible adaptations to mistake o
557.
by mjw1007 7y ago
According to this article, the lawsuit was settled in September 2019, though it doesn't give a reference and I haven't seen it reported elsewhere. https://www.computerworld.com/article/3487825/mozilla-in-
558.
by mjw1007 7y ago
I wonder if they got less (if anything) from the settlement from the Yahoo (Oath) lawsuit than they'd been planning on.
559.
Conservancy Joins Mozilla's Amicus Brief in Google vs. Oracle(sfconservancy.org)
4 points by mjw1007 7y ago|0 comments
560.
by mjw1007 7y ago
I hoped it would discuss how SSDs cope with sudden power loss, but it doesn't seem to. I remember this page but I don't know of a modern update: http://lkcl.net/reports/ssd_analysis.html These days, if I want
561.
by mjw1007 7y ago
"Does not object" is better than nothing, but I think it would be better if the PSF actively helped to coordinate this work (again, without bothering the core team). As far as I'm concerned, this is exactly the sort of thing
562.
by mjw1007 7y ago
I think it makes a great deal of sense for the Python core team to say "we're finished with Python 2 and want nothing more to do with it". But I'm very disappointed that the Python Software Foundation isn't explictl
563.
by mjw1007 7y ago
It was Gareth Rees. https://garethrees.org/2001/12/04/python-coverage/
564.
by mjw1007 7y ago
It's still not ideal. With git's DAG-based "patch model", I think what you'd really want to do is, after making the new branch and cherry-picking the fix, make that new commit a second parent of the original commit
565.
by mjw1007 7y ago
But you don't want your VCS to dictate your project management. Maybe you want to apply the patch to the main development branch, let people try it there for a while, and then decide which maintained release branches should get the pat
566.
by mjw1007 7y ago
I agree that commit messages aren't a good place for detailed documentation. Another reason is that if you had a mistaken understanding when you made the commit and wrote up that understanding in the commit message, you're creatin
567.
by mjw1007 7y ago
Maybe this is the same effect as when Hollywood tries to convert a novel to the screen. Often they'll spend half of their time budget on a decent adaptation of the first couple of chapters, then have to rush through the rest.
568.
by mjw1007 7y ago
If I had tooling which I trusted to be able to transition from any schema state I might want to use to any other such state, I would happily use it. I've never found any, though it's a few years since I last looked. (I use Postgre
569.
by mjw1007 7y ago
Something like this simpleminded approach: Use VCS tags to identify schema versions, and a naming convention including those tags to track the migration files. Have a script that validates a migration in the obvious sort of way (check out t
570.
by mjw1007 7y ago
I use SQL-level COMMENTs and comments in the schema source for different things. The former can be made visible to people using the database; the latter are for people maintaining the schema. In any case, I don't think I'd get on

More ›