This must be exhausting for the Automattic staff who just want to get on with their jobs.

Anyone who wanted to get on with their jobs would have taken one of the buyouts. Everyone who still works there has to be committed to Matt.

Changing jobs can be rough or maybe even impossible in this job market. I'm sure there are many there that are not aligned with Matt, but just need the steady paycheck. Same was true after Elon took over twitter.

>Changing jobs can be rough or maybe even impossible in this job market.

Wasn't there a 6 month severance on offer?

In this market, 6 months isn't enough.

> Also, if you're just there for a paycheck, you're probably not that upset at distractions.

Not true, I've worked jobs where I was there for the paycheck, I'd still prefer that it be a stable working and environment and still wanted to do good work.

I'm happier when work doesn't expect me to be "part of the vision" or "part of the family", treat me with respect, I'll treat you with respect and do good work - that's all it needs to be.

I mean, I'm currently working a job where I'm here for the paycheck. I fantasize about a buyout.

My feelings are not "boy I wish I could get back at that grindstone". It's "this is the ride I signed up for"

Applying the word "impossible" to leaving a white collar job seems like a stretch. Also the buyout was almost 2 years ago now, anyone still there must be either in dire financial straits or quite commited.

That's until you find yourself in this job market and you realize now how stupid the digital creation job market and overall jobs are. Once you get laid (off) you are now you're in a pile of 100(edit 1000s) other applicants equally qualified vying for the same job and then hundreds of thousands who can all type to Ai to do a job that once required knowledge & skill.

> Once you get laid you are now you're in a pile of 100 other applicants equally qualified

I'm assuming there should be an "off" after "laid"...

I don't know, I've had some years where without "off" would also make sense.

Only 100? Those are good odds in the current market...

What reality are you living in?

The software job market, especially for those of us outside the major tech hubs has been severely biased in favor of employers for the last 3 years, with constant layoffs and rising inflation.

If I was working for Automattic I can definitely see electing to stay there until the job market improves.

or they just love wordpress, the product, so much, and believe in it fully. lol

Or they need the pay. It's all well and good to go "they could just leave" but then what? Spend 6 months looking for a new job only for everyone to go "sorry, the hundreds of thousands of layoffs from every other highly skilled tech workforce beat you to it"?

This is RWNJ garbage dressed up in false "think tank" legitimacy.

Who are you to tell people what to be proud of, and and what to want to share?

I like whimsical applications like this. Thank you so much.

For those who want to try this out quickly, `uvx --from flower-garden-cli garden` works perfectly.

Because in a few months, people won't remember the details, but they will remember "the time the Wordpress guy abused his influence to damage the Wordpress ecosystem".

Or, alternatively they could remember "the time the Wordpress guy smacked freeloader leeching off the Wordpress ecosystem"

Apart from that - major turbulences in the WP and in general CMS world could be a positive thing. Maybe it's time for a new player in the space. Wordpress absolute dominance for basically decades kind of sucks air out of the space for competitors, there are some like Ghost and others but they are barely crawling compared to WP market share. Apart from that even fork within WP itself wouldn't necessary be a bad thing - some decisions and direction of the WP itself are questionable looking from developer standpoint like bringing to life insanely complicated React-based toolkit as WP editor building block, archaic conventions in the PHP codebase, lack of standardized patterns and guidelines for plugins creation and many more.

Personally I would love to have PHP-based CMS, built either based on Symphony or Laravel with extensive plugins and theming, capabilities and resonable market share.

A PHP based CMS based on Symfony with extensive plugins and theming, capabilities and some market share? https://w3techs.com/technologies/comparison/cm-drupal,cm-wor...

Yeah, I recently looked into their "Starshot"[0] initiative to make their CMS more appealing and it's interesting to some degree, but we'll see when it comes out - presumably ~ Jan 15, according to the video

[0] https://www.youtube.com/watch?v=Wce6FkNN2Io

My Compuserve username is permanently burned into my brain: 100131,756. And my password was the wonderfully evocative "spite:ambush".

Username, yes, 75006,702. But not the password. It was a decent password though. I didn't pick it.

You can configure almost everything using an app.json file.

https://dokku.com/docs/deployment/deployment-tasks/

I believe they are talking about the Dokku commands that are needed to set up a new Dokku app.

For example for a static site that would be the following:

    dokku apps:create dewey.at
    dokku domains:set dewey.at dewey.at www.dewey.at
    dokku letsencrypt:enable dewey.at

That's also one of my wishes to get improved, currently I just have a long text file where I store them so that if I move servers I can just re-run them if needed.

Could you put them in a .sh file and then just run `sh setup_dewey.sh`? Maybe put `&&` between them so that if one fails, it won't keep running through the script?

> Maybe put `&&` between them so that if one fails, it won't keep running through the script?

Or just add `set -o errexit` at the top of the script. Or use make.

Yep, in theory I think that should work nicely. So the recovery procedure after a server died would be to restore the dokku data directory from backup and then re-run all the commands. I haven't tested that but I think that should do the job.

Right now I keep the list of commands more as a reference to look up things like how I mounted a volume or my naming scheme for data directories.

Exactely, I was really surprised that dokku isn't all based on storing these commands in a config/script which gets executed every time you change something.

This is not open source.

These assertions are just not true. I'm working right now on a document with coworkers, concurrently, via a Sharepoint server. Change tracking is enabled and can even be enabled by default by the Sharepoint admin.

I share a lot of your sentiment about open formats in previous comments, but this is classic FUD and demonstrably wrong.

Then our Sharepoint server must have disabled sth. I regularly get a message on save that the document has changed meanwhile, with the option to overwrite those changes or discard my own...

No change tracking is visible to me, other than a timestamp and name of last edited.

FUD is isn't. Please don't use buzzword gratuitously, I know _a lot_ more about the deployment here than you. Also, you didn't counter the statement that it doesn't do concurrent editing (like Google Docs, OnlyOffice), which in 2024 is a major gap imho.

Your original comment was speaking in general terms, about all Sharepoint services. Not your specific deployment. Details matter or your argument falls down.

As for concurrency, read my comment again, I use the specific word.

If you see that I talk about a certain config of Sharepoint, it's much faster to point that out than being argumentative.

What did you do to have concurrent editing (or what did you not do), and how does it integrate the various diffs?