1,079 karma · joined January 24, 2020
When ‘less’ was created, there was a bug where when you scrolled upwards the passwords would be revealed, so it was decided that the passwords should be replaced with actual asterisks and stored in individual files per-user.
For security, these files were given access rights only for the owning user, and immediately deleted, with an encoded copy of their inode number being stored in /etc/shadow.
Fun fact: forced password changes were initially introduced when disks were getting full and deleted inodes of user password files were due to be overwritten. “For security reasons” was correct but misinterpreted.
It might seem like I’m stating the obvious, but I really do think it could be worth spending time with the preview releases.
I assume the reason this isn’t done is as pointed to in the article - a lack of correlation between what goes into a preview release and what ends up in a real release, but is it really the case that none of the three issues raised could have been avoided if they had been spotted slightly earlier?
The first looks like it was a case of over reliance on what was communicated by Apple. “Trust but have a backup plan” would seem like a useful approach here, if it is reasonable to consider the option of enlisting or creating a compatible replacement for using the Javascript zip library.
The second issue - reliance on a bug - just seems like something that is easy to fall foul of, but in retrospect would it have been possible to have noticed that there was an assumption being made, or that there might be a test missing to catch a future change in behaviour?
The third sounds like an assumption in the application code (that a value would not be null) which may have been a perfectly fine thing to do, if it was going to be obvious what the issue was as soon as it broke, but…
… the description of the pain of having to put out an ‘emergency’ release gives the impression that there is scope for making this process easier. I understand, of course, that automated testing of anything that runs in a browser is still hard, so it may be that it’s this part of the release process that causes friction and the returns from improving this have already diminished as it’s been refined.
It’s such a great product and I hope there can be less friction in keeping up with Safari as it’s fantastic to see cross platform web applications continuing to thrive.
People on modest salaries either don't spot the cheaper, just-as-good toothpaste that's not as prominent, they think that it's not as good as the ones with lists of all the great things they're supposed to do, or they aren't feeling the squeeze enough to seek it out.
If you drop into an independent chemist you might notice that sometimes the only toothpaste they stock is the 'basic' one, because their customers are price-sensitive, so that's all they'll buy.
Going rate for pizza is around 60p/100g, with a larger than average Aldi 'Meat Feast' pizza coming in at £2.19, which is 39p/100g.
Again, if you're on a 'modest salary', you pick the cheaper products or pick the supermarkets which only really sell the cheaper products.
I'm not saying that prices aren't going up, just that closer to the 'survival' line, there is much less room to increase prices, because people aren't at the point of choosing based on preference, so you can't rely on them switching to a slightly cheaper option from your artificially differentiated product line (yes, you, Colgate-Palmolive). They'll just be forced to stop buying your products altogether.
Speaking of Super Mario Odyssey, two of us have played it from beginning to end, so we definitely got a lot of fun game time out of the cost!
I also always use the short form: house number and post code.
Is this a good method? No idea. Decades of sending parcels. None failed to arrive, so no attempts to return to sender.
I am convinced there must be some kind of ‘spatial’ processing going on, even though I’m as certain as I can be that I’m listening to a plain stereo source, Spotify web version on Firefox.
Why does it sound like a particular instrument is up in the air to my right? I’ve found myself getting up and looking for the source of a sound before realising it was in the music.
By the time I compared UUIDs to sorted UUIDs (in the special pattern that was supposed to work for SQL Server) and ints, however, I didn’t find any difference in performance.
Perhaps by the time I tested it had been fixed, or perhaps it was only an issue in certain circumstances, but never an issue with a few million rows for me.