I’m solidly in favor of the Benevolent Dictator For Life (BDFL) model of open source stewardship.

Now let me show you how that exact model can go sideways and disrupt massive swaths of the development community, without a whiff of irony.

The answer has been “No” a few times and boy does that suck.

“No one has ever attempted something so convoluted/silly/impossible before. Guess we get to see if we’re actually programmers or not.”

I made sure answering, “Has someone figured this out already?” is a formal step in defining project scope at my company.

In my experience, and in the experience of my coworkers/contemporaries, our formal education taught us how to program which is distinct from which language we program in. For instance, my Java dev friend learned to program in C++ because that’s what was being instructed. I was forced to learn ActionScript 2 and then was forced to migrate to ActionScript 3, because that’s what was being taught. The experience of programming something and iterating on it was far more valuable than knowing a language like C++ or ActionScript.

Languages come and go, some faster than others, and you’ll eventually get to a point where your personal preferences stop mattering as much as which language is best for the task at hand.

PHP is dead. Long live PHP.

Okay, so, FOSS.

If WordPress doesn’t want WP Engine doing what it’s doing, they need to change their license. It’s not “Free Open Source Software Until Something We Don’t Like Happens.”

I maintain that we should all aspire to be a firetruck when we grow up.

TL;DR - This waterfall of word vomit makes no mention of contemporary PHP-based CMS and can be ignored entirely.

It’s paid like WinRAR is paid.

You should check out the app directory at Selfh.st. There are a bunch of selfhosted solutions for what you’re looking for, be they all in one or micro services.

That’s genuinely hilarious. It’s so hyperbolic and dripping with contempt I can hear the user finish it out loud with, “you stupid motherfucker.”

Excellent, but it needs another QA pass on mobile dark mode. Black hyperlinks and headings on dark gray backgrounds are unreadable. (Firefox on Android)

Hey, I was in a similar situation at that inflection point but veered into PHP application development and couldn’t quite get away from the front end. Let me tell you: CSS Flexbox and Grid are amazing. AlpineJS is “just the good parts” of jQuery. You can go back now. Check out 11ty.

We will continue to use Bugzilla, moz-phab, Phabricator, and Lando.

Although we’ll be hosting the repository on GitHub, our contribution workflow will remain unchanged and we will not be accepting Pull Requests at this time.

The cool thing about distributed version control is that it’s distributed. It sounds like GitHub will just be a public remote, rather than the place where active development happens.

“Running from within a motherboard BIOS” is waaaaay different than running from BIOS (aka Direct Boot). Before Windows, many games were playable by booting directly into them.

Did you use Shoelace, or is the name a coincidence?

tl;dr - It’s okay to refactor code now and then.

I bought my first keg with the cash made from un-fucking Dreamweaver output.

Source?

I would describe this as an uncool GitHub project. Federation isn’t the answer to every problem.

I’m another git-flow fan. Have not encountered a situation that would motivate me to change workflow. We use submodules all over the place, too.