Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dwheeler
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
63 ms
·
571.
▲
by
dwheeler
6y ago
That's the main working solution I found: code works in both versions. The problem is that it's way trickier than it should be. Has they made that relatively easy, the Python 2->3 transition would have had a much smoother "
572.
▲
by
dwheeler
6y ago
> If you started only making new stuff in python 3 in 2010 2 years after python 3 came out how much python 2 would you have to convert? In many organizations there was never a time where they could start writing new code in Python 3. The
573.
▲
by
dwheeler
6y ago
It's true that you need to budget for maintenance. It is a serious societal problem that maintenance is underfunded. But that means that any language revision needs to work hard at making the transition easy and incremental. 2to3 was a
574.
▲
by
dwheeler
6y ago
> 2to3 has worked for an overwhelming number of use cases. And in fact, most code requires very few changes to begin with. That is not at all my experience, nor is that experience of most other people I've ever talked to.
575.
▲
by
dwheeler
6y ago
Not at all. It's only too generous if there is a low-cost way to incrementally transition to 3, as is normally the case with language updates. Python 2->3 was a poorly managed update that did not follow normal upgrade rules, so the
576.
▲
by
dwheeler
6y ago
Usually yes. But almost all language transitions are easier than the Python 2->3 transition.
577.
▲
by
dwheeler
6y ago
I think that's very likely, but I've never seen a post mortum from Apple where they track down what happened. I wish they would be more open about what happened. Mistakes happen. It's better for the industry if we can all lea
578.
▲
by
dwheeler
6y ago
That makes sense. In addition, the telecomms were generally not interested in the very early Internet (TCP/IP) because they couldn't figure out how to do per-packet metering, and they assumed that was necessary. All 3 examples sho
579.
▲
by
dwheeler
6y ago
Very sad. I had the privilege of taking a class from him at George Mason University, and he was (unsurprisingly) very knowledgeable. He worked hard to enable software reuse. No one was interested in his idea of trying to monitor component u
580.
▲
by
dwheeler
6y ago
Faces mostly work. Limbs and feet are way more hit-and-miss, lots of disturbing messes. It's still intriguing, especially since I expect further improvements to the tech over time.
581.
▲
by
dwheeler
6y ago
> ... your excellent essay (with many useful hyperlinks) about it. Thank you so much!
582.
▲
by
dwheeler
6y ago
No problem! Thanks for pointing people to the article, I write articles with the hope that someone will read them :-). That article is part of a series of articles called "Learning from Disaster": https://dwheeler.com&#
583.
▲
by
dwheeler
6y ago
Thanks! And while I'm here, THANK YOU for all the thankless work you do. MANY people, including me, appreciate it!
584.
▲
by
dwheeler
6y ago
Hi, I'm the author of the referenced article. Thanks for pointing to it! However, can you change HN thread to the article title, which is: "The Apple goto fail vulnerability: lessons learned"? I never used the term "ba
585.
▲
Preventing Supply Chain Attacks Like SolarWinds
(linuxfoundation.org)
2 points
by
dwheeler
6y ago
|
0 comments
586.
▲
by
dwheeler
6y ago
> Why has it never been appropriate? Because UTC has never worked that way. UTC is an international standard for a "time of day" standard where every second is exactly one second long and is boundedly synchronized to the ro
587.
▲
by
dwheeler
6y ago
THANK YOU for posting this link. This is really helpful in explaining what the law actually says.
588.
▲
by
dwheeler
6y ago
It's weird to talk about "switching" to atomic time. If you want seconds to always go 58,59,0, and you want time to always increment 1 second at a time, then UTC has never been appropriate. People who need to measure time t
589.
▲
by
dwheeler
6y ago
SD cards are useless for long term storage, they last maybe 5 years: http://www.datarecoveryspecialists.co.uk/blog/what-is-the-li... They depend on holding electrons within cells, and over time the electrons leak out.
590.
▲
by
dwheeler
6y ago
Artichoke is interesting, but it's still really young and doesn't have a lot of compatibility with MRuby yet: https://eregon.me/blog/2020/06/27/ruby-spec-compatibility-re... I don't know o
591.
▲
by
dwheeler
6y ago
Open design is basically a generalization of Kerckhoffs's principle. Kerckhoffs's principle is usually stated as "A cryptosystem should be secure even if everything about the system, except the key, is public knowledge."
592.
▲
by
dwheeler
6y ago
It is generally accepted in the security community that hiding source code does not provide security. The principles for developing secure software were identified in the 1970s by Saltzer and Schroeder, and they're still true today.
593.
▲
by
dwheeler
6y ago
Engineering uses knowledge , only some of which is scientific. A good engineer will use the best data where available, and where pragmatic will try to gather more (e.g., by making small prototypes to test a concept). But even today, a lot
594.
▲
by
dwheeler
6y ago
I completely disagree, and I have a degree in electronics engineering. Engineering is simply using knowledge & resources to develop systems or processes that solve human problems. When you're developing software to solve human prob
595.
▲
by
dwheeler
6y ago
If the compromise was inserted during the build process, then one countermeasure could have been reproducible builds. Reproducible builds require the source code, but they can verify whether or not the build matches the claimed source code.
596.
▲
by
dwheeler
6y ago
I have played it, and Chess960 is fun. I do not think that Chess960 helps humans against computers. 960 possibilities is just too small an amount of randomness. Besides, computers now have substantial advantages against humans in anything
597.
▲
by
dwheeler
6y ago
I wish you the very best at your new position!! Maybe the Metamath community can steal a little more of your time :-), especially since there's more Rust-related work in it. I think the "Report on the 2020 FOSS Contributor Survey&
598.
▲
by
dwheeler
6y ago
I'm the article of the referenced article on chess openings. I'm also one of the authors of the Wikipedia article on Chess960 (Fischer Random Chess); you can see the information I wrote about it here: https://dwheeler.
599.
▲
by
dwheeler
6y ago
I'm the author of the referenced article. I agree, even low-rated players should learn at least a few moves of a few openings. I think trying to learn 12 moves is too much for a beginning player, but knowing a few moves is helpful beca
600.
▲
Open Source Contributor Report (Linux Foundation/Harvard) – Improving Security
(linuxfoundation.org)
1 points
by
dwheeler
6y ago
|
0 comments
More ›