It’s actually kind of nice to see this as a JS developer.

Not like, “Oh wow this is neat!”

But like, “Finally the golden child, Python, also has some fucked up shit”

For those out of the loop:

1. There’s WordPress (the non-profit and open-source software), and Automattic (which runs for-profit companies like a paid WordPress, Tumblr, Gravitar, etc).

2. Automattic (Matt’s company) pays their devs to support the open-source software.

3. Lots of companies sell WordPress hosting.

4. Matt is calling out WP Engine for not just using WordPress without a lot of contribution back to the open-source software, but also selling a chopped up experience.

The metaphor would be: imagine if a company selling tablets contained VLC, bragged about all the movies you can watch, gives back very little to VLC, and you can’t use the playlist feature.

Also, not trying to shit on WP Engine. This is the post everyone should get to see.

https://www.briancoords.com/the-wcus-closing-i-wish-wed-had/

Still waiting on approval for more resources. It’s not a priority in the company.

I swear we have like 4 runners on a raspberry pi.

Envious. It averages 15-30 mins

A lot of these old-fashion types are oblivious to social justice and get upset at even the thought that Institutional racism even exists, because they can point to their one black friend in tech who owns a mansion.

I used to get into arguments why master and slave was a problematic word to engineers. That’s how ignorant they are.

Those folks are dying out, especially as more diversity exists. Which is humourous because these folks will also rage about that too.

During the George Floyd Protests, Robert gives us a beautiful take that police stopping black people isn’t racist, it’s just math.

as a chronic documentation reader, the best advice i can give is to document everything Anything that the user can and will potentially interact with, should be extensively documented, including syntax and behavior.

I don’t know about that. I’ve read some terrible documentation that had everything under the sun. Right now in the library I’m using, the documentation has every available class, every single method, what it’s purpose.

But how to actually use the damn thing? I have to look up blog posts and videos. I actually found someone’s website that had notes about various features that are better than the docs.

There’s a delicate balance of signal vs noise.

I used to mock people who make YouTube videos that literally just walk through the documentation. Like bro, get some reading comprehension!

But then when I fumbled with some self hosting tutorials, those YouTube videos were the only thing that made sense, because they’re explaining why and how.

Sorry y’all.

One obstacle may be the assets. Im not a lawyer.

But you pay for a license to use a piece of music in a commercial software. To make the game open source would imply the music is also something others can use, which wasn’t yours to give away.

Music is easy to rip out.

But think about the headaches. Is this 3D model that you purchased and slightly edited licensed in that way? Is this UI for the options page? What about this sound effect? It gets even worse with code dependencies. You paid to use this library…

It’s now this massive headache to itemize every single thing and determine the origin, as well as if it’s something you can release as part of your open source. And if you do it incorrectly, you can get sued.

Why can’t I delete System32? It’s taking up space.

Right?

This reeks of inexperience.

We lock things down because a malicious program can easily be “owned” by the user through stupid choices. And now you got viruses.

This is a way to stupid proof things. And the workaround isnt difficult, but it’s to stop people like Andrew. And so far, success.