This is an *excellent* summary of the tension between being welcoming to new contributors and staving off maintainer burnout. Because if there was a bug / deliberate nefarious thing hidden in that "innocent" 300-line refactoring patch, the maintainer's the one who's gonna be on the hook for it, not the contributor who may be long gone. :\

Whereas, if you take work *off* a maintainer's plate by doing a "thankless" task like improving docs or writing test cases, it's good things all around.

Yep. That is exactly the point of Codes of Conduct, so that **everyone** can just have fun and not worry about being harassed, berated, singled out for some immutable trait, and so on.

If having fun for you necessitates having the freedom to do this to other people, maybe carefully sit down and consider your life choices. ;)

Sometimes you're too immersed in things and forget what assumptions you're making! :)

I actually think the comment by Pseudonymous Powers at https://developers.slashdot.or... does a *fantastic* job of laying out some of those pitfalls, but to be more explicit, I've now added a new section towards the bottom of the article that itemizes them more explicitly: https://webchick.hashnode.dev/...

Hope that helps, and thanks again the candid feedback!

I've been a Netflix subscriber for over a decade. We get DVDs by mail (which includes advertisements on the mailer) and frequently use Netflix streaming. I've heard Netflix has gaming but know nothing about their offerings. They seem to be doing a horrible job promoting the service.

AOL sold ICQ in 2010.

>Do you believe rehabilitation is impossible or do you want revenge?

I don't believe that someone who commits mass murder can be rehabilitated, no. It isn't about revenge; it's about public safety.

Someone once pointed out that hoping a rapist gets raped in prison isn't a victory for his victim(s), because it somehow gives him what he had coming to him, but it's actually a victory for rape and violence. I wish I could remember who said that, because they are right. The score doesn't go Rapist: 1 World: 1. It goes Rape: 2.

What this man did is unspeakable, and he absolutely deserves to spend the rest of his life in prison. If he needs to be kept away from other prisoners as a safety issue, there are ways to do that without keeping him in solitary confinement, which has been shown conclusively to be profoundly cruel and harmful.

Putting him in solitary confinement, as a punitive measure, is not a victory for the good people in the world. It's a victory for inhumane treatment of human beings. This ruling is, in my opinion, very good and very strong for human rights, *precisely* because it was brought by such a despicable and horrible person. It affirms that all of us have basic human rights, even the absolute worst of us on this planet.

This is precisely why I lost all interest in Oculus the instant I heard that it had been acquired by Facebook.

http://ohiolinux.org/

Does robust firewall software exist that can fully lock down a phone to only allow voice stuff over the radio and restrict data in/out to certain protocols and apps? Or by using a phone do you have to accept the fact that Google/Apple/Microsoft or your service provider have full access to your device at will?

I would have no problem with what you are saying if it weren't for the fact that the 'service' they are providing is access to a limited public resources they do not own but instead license it's use from the public. When you are granted a monopoly to resell a public resource, it generally comes with the stipulation that you operate in the public's best interest.

I misread the beginning bit and thought the article was suggesting that the FCC was also asking US telecoms to provide actual cost info. Then reality set in and I remembered that in the US the telecoms "Rule the Air" not the FCC.

Access to the public airwaves and utility lines that provide broadband should be a "right" not a luxury.

Because MySQL uses threads. It doesn't fork() to serve more requests, like PostgreSQL does ;-)

But there is a huge difference.

For MySQL, the database primarily serves the application. The boss is the app developer who gets to tell the db (through the app) whether to treat zero dates as valid or not, or whether 2009-02-30 is a valid date. The app dev is king. This works well enough when there is only one application writing to any given relation (many readers is not a problem there because the writing app is king). But it doesn't work well as a data centralization and management solution. If you have 20 apps writing to the db and they may all be using different sql_mode settings, that is going to be a mess if they share relations.

For PostgreSQL, data is king. The applications consume managed data. The DBA is the one who gets to make the hard calls and every app developer gets to live with the decisions made. MySQL is thus a bottom app tier while PostgreSQL is a data management and centralization solution. They are *very different* and if you have 20 apps sharing the same relations, PostgreSQL will be far saner because multiple readers do not have to tolerate eachothers' sql_mode settings.