435 karma · joined February 14, 2013
Wow you have no idea how happy that makes me as a OneNote user since 2006 or so. It's my favorite part of Office.
The thing about compatibility is that it doesn't matter how great your new and shiny is if it can't talk to old things at all. Imagine the best new text editor in the world, but it's completely incompatible with every file format that's ever been written previously, even .txt! No one would use it, because the cost of switching is too high.
In some cases, it's definitely worthwhile to have some development pain to keep that around. Stuff like keeping vimscript (and therefore the entire ecosystem around vim) functioning means that neovim could be a drop-in for some people, and HAS to be preserved at least partially. Stuff like keeping ancient Amiga support or integration with Sun workshop? Definitely not worth it anymore.
Good deal to the Simple team, I hope this works out for everyone involved well.
They should be in flat storage somewhere, with some directory or file name scheme that makes sense based on your version numbers / builds / what have you. Backed up, (ideally) with hashes that verify that they're the same file they once were.
The main vulnerability he talks about is if a major provider were to be hacked and have their file replaced (or go rogue, entirely). In either case, is any login system that doesn't use two factor authentication and allows for password resets via email really going to do any better?
Edit: I realize he points out that 2 factor auth really is the only solution here, just, it seems like the criticism applies much more widely than just against Persona.
I play the same game, and I love it (no one ever believes me about it, either).
I wouldn't imagine it would be too hard to get an IDE auto-formatter to follow all of this (it's more or less what I use with mine, anyways).
Except not. This was misreported and spread like wildfire.
Lennart hate is fine, but let systemd stand on its technical merits (or lack thereof, if you really feel that way).
I'd actually not even entirely hate that incarnation of a returning start menu, which is hard to believe at this point. Good job.
And the problem then becomes "okay, now, which of the other 16,000 untested files in this codebase are relying on that broken behavior." It's not a fun place to be in (welcome to my day job) but you have to remember--You're writing characterization tests, you're trying to capture what it currently does. Not what it should--every difference between those two is, unfortunately, potentially an important one.
It's not worth fixing one minor thing if it breaks 14 other things down stream (that you then won't catch, since they also don't have tests).
Facebook, you've had enough privacy problems in the past, is it really that hard to outline what's going on here or even just not require the number? I've heard that GVoice numbers don't work, as well, which just makes it even worse.