Asking end users of your product to report issues via DM'ing your personal Twitter account, an account which is full of retweets of homophobic garbage, is really REALLY bad.
Quietly editing your comment after being called out to hide it is even worse.
>You start with a background in English or professional writing and learn the technology, or you can start with a computer science degree or something similar and learn how to write.
Could you please recommend some good resources for learning to write, in the context of technical writing or more generally?
Seconded. I've never heard this in the UK from people of any age.
I wonder if it has anything to do with the way "an" sounds when spoken with an American accent. A mishearing and then repetition of "an accident" seems much more plausible to me than confusion with "on purpose".
One of the things I found really interesting here is how much could be done with just basic userland tools, and how old some of those tools are.
Docker was released in 2013, but support for kernel namespacing has been around since ~2007. That's quite a long time for such a great feature to go mainstream.
Interesting, it was my understanding that Docker was going in the other direction. Moving off AuFS towards Btrfs due to issues getting AuFS patches into the mainline kernel.
I'll have to look info CoreOS's reasons for going with Ext4.
Yep, even better imo is that when you run a query it outputs the generated SQL. Often I'll have a psql console open next to vim while creating Sequel queries and just copy this output over to verify the generated SQL does what I expect.
The history is correct. However the enforcement comes between the author of the code and the distributor.
The author(A) allows the distributor(D) to distribute their(A) code so long as they(D) provide the source plus any modifications to the recipient.
The recipient has no right to demand the code due to there being no agreement to provide it between the distributor and the recipient.
So the author, on behalf of the recipient, must be the one to enforce the conditions of the agreement they made with the distributor.
In cases involving projects like Linux or BusyBox this can be anyone who has committed code, as these projects do not require copyright assignment.
In cases involving projects like GNU and Ubuntu all committed code is owned by the parent organization, the FSF and Canonical respectively. So they are the only ones who can enforce the GPL.
That said, the end user can report violations to groups like The Software Freedom Law Center and GPL-Violations.org. These groups have contacts to various copyright holders and will assist with enforcing them on a pro bono basis.
Yes, since it with it on the functionality remains off until the final (and only partially full) packet. Rather than being delayed by 200ms, tcp_nodelay sends it out instantly.
They look like they start at around $1000+, which means you are looking at about 1 year before it pays itself off. Based on my estimated heating bill anyway.
Additionally the biggest problem I find when turning off the heating in winter is hands and feet. You can wear gloves but then you can't type.
The title of "Systems Engineer" generally refers to someone who designs and implements systems, as opposed to a "Systems Administrator" who administrates these systems.
Are they a "true" engineer? That's probably not for me to say, but the roles of "Systems Engineer" and "Systems Administrator" are very different things in my experience.
Indeed, not to mention the GPL explicitly forbids this[1].
The point of the GPL is to fight for the rights of the user, no matter if that user is a single hacker wanting to tinker with the code or a giant multinational wanting to use it for $$$.
1. Delve Labs has commercial scanners which bundle but do not link with WPScan.
2. WPScan, previously licensed under the GPL, introduce a commercialization clause in addition to the GPL.
Side Note. WPScan may not have the right to do this because they do not use copyright attribution. Without this they need permission from everyone who has ever contributed code to their project.
3. WPScan demand money from Delve Labs.
4. Delve Labs make a fork from a point before WPScan introduced the commercialization clause. They keep this version licensed under the GPL.
Not to sound cliche, but try Gentoo. It takes a bit of getting used to be it's concept of USE Flags are designed exactly because of "everything is getting intertwined so much that it is hard to actually pick and choose applications".
Quietly editing your comment after being called out to hide it is even worse.