![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/f3189f30-f8c8-4c4f-b957-e3a7bfd1c784.png)
Solid idea. One consequence of this would be the possible delay in removing material that really should be removed as fast as possible, though.
Solid idea. One consequence of this would be the possible delay in removing material that really should be removed as fast as possible, though.
Mint is my go to suggestion for new people switching over.
That is terrifyingly true. Wired cameras all the way.
I also got very relevant results for that query.
You’re agreeing with something I didn’t state. I’m not defending the idea of introducing bugs through bad code and then blaming others. I think the way Linus responded to that was the issue.
I don’t think I am missing the forest. There’s not an issue with the idea of correcting a developer, but there is an issue in the way the correction was carried out. Just because something behaves “better” after punishment doesn’t mean the punishment was good. Ends justifying means and all.
“An oldie but a goodie”… What?! This shouldn’t be celebrated. What an absolutely unacceptable way to behave. Shame on anyone encouraging this.
If your interview involves telling me a username is “something you are” rather than “something you know”, I’m running away from that job as fast as I can.
#2 is a dangerous assumption!
Right, but that content will still exist server side.