x1gma

Unless there are those who need certain words for their jobs, I can kinda understand why Microsoft wouldn't want emails from work addresses to go out with political agendas... for either side.

Sure. Then block both sides, and not only the one not bringing you money.

Work emails should just be about work. Too many people use their work emails like a personal email... with their banking, shopping, etc. That's what personal email addresses are for.

No one uses their company email for their personal banking, simply for the reason because if you'd leave, you'd lose your access, and since most companies run behind firewalls, vpns, 2fa tokens and similar additional credentials, it's simply harder to use.

This policy should go for many non-work related topics too. IT can unblock the words for certain users who need to use them for their job.

Of course, let's waste resources to maintain idiotic blocklists that are out of date the moment they are rolled out, and additional resources to make the blocklist actually work. Palestine, p4lestine, pale s tine, p a l e s t i n e, paleztine. Need more?

You're not at work for someone with this kind of unhinged mentality watching you working for 8 hours a day straight with no breaks and no distractions. You're there to get your work done. In my current team, we've had the best ideas talking about our problems at the coffee machine. I personally focus best when I have music on. We're doing sports together once a week on a company fitness incentive, which boosted our team dynamic massively. None of this would be possible in such a controlled environment.

Take the following with a grain of salt, it depends on your specific setup, environment and preference, but might help you:

Regarding system backups, and depending whether you need to run fedora, check out nixos, which takes a declarative file and builds your system based on that. Declarative immutable system, no moving parts, no breakage. If your system breaks, revert to a prior version and keep using what you've had before before retrying. Your backup is a git repo or whatever is keeping your handful of config files. Has been an absolute game changer for me, and the community and ecosystem around it is far beyond the point of quirky esoteric immutable distro.

VSCode has a powerful feature that I've yet to see in another editor/IDE - remote development, and it works really, really well. Spin up a VM however you like (I'd recommend checking out Vagrant), and depending on how much you need to do in windows either use the windows box as a remote run target (just running your built artifact in windows), or as a remote development box (running everything in windows and using your Linux VSCode as a "Frontend" for everything else happening in windows). Both methods can be made to work seamlessly in vsc.

Excel - again depending on your usage, you can try wine, you can use a VM, dual boot, M365 in browser, or a remote VM.

It's not about being dumb and expecting stuff for free but a general anger towards subscription based models. Fair models exist and are possible, but are a collateral of the general hate.

Then, free alternatives exist, and believe it or not, some people do not have a tiny monthly fee they could spare or do not want to pay for something that a free alternative exists.

Threema tried exactly that, and failed comically.

Just as AI will replace developers, and then we have Devin. Also don't forget the artists that will be replaced, that'll happen just when it learns that humans have 5 fingers per hand.

It's all marketing for AI, by the afaik currently biggest supplier of AI hardware.

The whole hype will implode when AI itself implodes, not as the AGI singularity, but when the resource costs spiral out of control, and its keeps getting its own generated glop spoonfed

No, but the more people block them, the less up votes and visibility they will receive for their posts.

Why are we giving this person their stage again? How probable is it that the instance admins of the like 15 instances they have accounts on will all collectively ban him? It's just your average nazi spammer on the internet. You've read that "bio" this person has. Even if they get banned, they'll come back just on principle. Just block him like any sane person would do, leave him shadow banned like that with his nazi friends, and call it a day.

So, you mean using a proprietary vendor to operate something binds you to that vendor? Congratulations, you've just discovered vendor lock-in.

"Obfuscating the environment" is also an absolutely unhinged claim, what even is that supposed to mean?

And again, Automattic is NOT in the right. What Automattic did was break license terms, attempt to extort, steal code, and light their whole brand, company, ecosystem and community on fire. Matt spit in the faces of his open source community (and open source in general), and every single person dependent on WordPress losing their job because of the shift he's causing will be blood on his hands personally. Even if WP Engine was questionably morally or ethically, they did play by the laws and the license terms. Matt went on a mental breakdown and additionally to his unethical behavior broke several laws on that journey, which is exactly why he is losing the lawsuit. Matt and Automattic are NOT in the right.

To be fair, Matt is providing meltdowns regularly and totally free of charge. 😂

I'd laugh my ass off if WP Engine would lead a hard fork called WP Core. If any WP Engine folks read this, feel free to use the name, I won't sue, I promise.

It really depends what you're doing. If it's really "only" blogging I've seen a lot of blogs using Ghost. Hugo is more of a "simpler" static site generator.

That whole blog post is so full of salt, that it really hurts to read.

Still going on about the "imbalance of the contributions", well that's open source for you - you don't get to control who contributes how much, all you can do is ask nicely, and provide a good experience for contributors. Acting like a lunatic does not do that.

legal attacks started by WP Engine

Of course they did after the witch-hunt and the absolutely illegal, unethical and plain ridiculous behavior of Automattic. The counter they did, the whole ACF takeover and the slandering are a lawsuit handed on a plate.

The way "community" is quoted in that article for those who dared to disagree.

This legal action diverts significant time and energy that could otherwise be directed toward supporting WordPress’s growth and health.

Yeah, as a developer I also hate when lawsuits are stopping me from working. He had no problem letting go of nearly 10% of his staff with their "alignment offer" to get rid of people who again dared to disagree, but the legal action is diverting resources now.

But the whole "Focused on the Future" paragraph is going full mask off:

Before, they said that resources will be reallocated to "for-profit projects within Automattic", and

We will redirect our energy toward projects that can fortify WordPress for the long term

It's only a matter of time another hostile takeover will take place, and Matt will attempt to go full for-profit on WordPress itself.

We’re excited to return to active contributions to WordPress core, Gutenberg, Playground, Openverse, and WordPress.org when the legal attacks have stopped.

Full on extortion. Stop the lawsuit or we won't contribute.

Honestly, if I'd be dependent on WordPress for my work, I'd not sleep well and start going into something else right fucking now. How are people that stupid, childish and entitled getting into such positions.

Matt never ceases to amaze with his smoothbrain decisions.

The amount of effort this moron puts into his weird personal vendetta against WP engine, even after the court told him that he has nothing, which was actually his last chance to end this kinda gracefully, could've been used for so much better things.

And he's not only successfully kicking himself in the balls, he's willing to throw so many years of community and project time and effort under the bus for it.

Go on Matt, keep telling how much you're only doing this for WordPress.