Enough with this cargo cult bullshit approach to technical problems.

The only problem this solves is their need to sell their product.

This so-called "schema-driven development" approach was already tried in the past and failed miserably. Call it SOAP or OData, the world already gave that a try, saw all the mess and operational and productivity problems it creates, and in spite of the gold mine it represented for tooling vendors and consulting firms, it was a collosal mess.

It's very weird how their selling pitch is based on veiled insults on hoe "the industry is still twenty years behind", but they failed to do their homework to learn the absolute mess that their so-called "schema-driven development" approach left behind.

It's as if they are totally oblivious to why the whole world shifted to "free-form" APIs, which worked far better than the SOAP mess, and their are hell bent on betting on a rehash of the bad old days.

What do you mean "take care of the level of detail"?

I can download Debian right now, install it on hardware in about 10min, and get everything to work rock solid without any hitch.

I can't say the same about either Windows 10 or macOS.

In fact, I had mojave crash and reboot more times in the last month than Ubuntu 18.04 since it was released, and mojave is preinstalled in its own target hardware, which is supposed to be high-end, while Ubuntu is installed on a cheap laptop that cost between a third and a fourth of my apple laptop.

What exactly do you mean by level of detail?

But linux is free both as in free beer and in free speech, windows required you to pay the Microsoft tax to use, and lastly macOS required you to pay a premium on hardware.

That price is just the benchmark for that specific combination of CPUs and RAM.

There are plenty of used servers in the market that are being sold for less than 200€.

I've been using VIM for over a decade and currently my customized config consists of a half a dozen tweaks, such as YAML-specific settings stashed in ./.vim/after.

They really aren't. First of all, scientifically speaking each PhD is unique as it focuses on specific venues of research. Thus within the same research group you often have an extremely diverse crowd doing independent research on multiple projects at the same time.

Then there's the fact that the assertion about "being trained (...) to become a professor" makes no sense. PhD students are trained to conduct independent research on a specific subject, and rarely also on how to apply to research grants. Being a professor, which is more of a supervisor/administrator role, is not factored into the equation, and the teaching component is a very small and tangential aspect of being a professor.

The truth of the matter is that graduate schools are effectively diploma mills to entice prospective workers to work long hours for low wages in exchange for a qualification and shot at a research career. Their work is focused on learning how to do research while focusing on a specialized topic, which arguably has no parallel with what a professor does.

Again, that makes zero sense and is another blatant red herring. If the discussion is about taxing WFH to support vulnerable jobs, it makes absolutely no sense to waste time playing the whole whack-a-mole whataboutism game.

If you don't want to discuss the topic under discussion, please refrain from commenting at all. You'll only end up adding noise to an otherwise interesting discussion.

I mean, there's already a progressive income tax. Why should society create incentives to commute to work?

> But when I showed off my build on /r/homelab, reddit’s homelab subcommunity, they mocked me as a filthy casual because I used consumer parts. The cool kids used enterprise gear.

It should be noted that you can purchase used enterprise servers for peanuts.

I'm looking right now at an ad for a used Dell PowerEdge R730xd SFF 24x which packs two Intel Xeon E5-2680 v3 and 64GB of RAM which is on the market for about $1200, and it was literally the first search result.

A Dell PowerEdge R720 8x 2U LFF with the same CPU/RAM/HDD combo is on the market for less than $1000.

A Dell Precision T7610 workstation, with dual Xeon ES-2670 and 64GB of RAM, can be purchased by around $600.

Sounds to me you're describing the whole point of marriage as a contract, as it specifies the default set of conditions and requirements that are applied to both parties, and also the rights and obligations of both parties in case of a contract resolution and even breach of contract.

> This is why prenuptial agreements can sometimes be a touchy subject, since it breaks that assumption of complete trust.

Again, it sounds like you're describing the whole point of marriage as a contract, as its the original (and baseline) prenuptial agreement.

I don't believe it has anything to do with change.

I believe it has everything to do with isolating a vulnerable subset of society to exploit them. Divide and conquer. They want a bigger chunk of your hard earned money, thus they fabricate a tall tale of entitlement to vilify and turn the peole against you, and proceed to rob you of your paycheck because they want your hard earned money.

This is a disingenuous red herring.

It's one thing to claim that some amount of taxes to finance public spending can be benefitial to society.

It's an entirely different thing to claim that taxing remote work brings any benefit to society.

I would too, which is why I vote with my wallet and buy local, even at a premium, whenever I can.

However, income tax is the exact opposite of helping out the community, as it's designed to fatten up the central government's revenue which is then used up to feed the state's current expenditure.

How does that ad hominem refute or support the claim that remote workers should be taxed to subsidize vulnerable jobs?

Not really. Event sourcing is typically implemented with CQRS, mainly due to how ES relies on streams of command messages and as CAP-related requirements already require mutable and immutable commands to be processed differently. However, CQRS has zero requirements other than segregating interfaces.

Hell, in languages like C++ you already get CQRS out-of the-box by following const-correctness.

Not really. REST just models everything as resources that are targetted by requests. REST states nothing about how rewuests should be segregated by commands and queries.

I fail to see how CQRS is a factor in increased complexity. After all, CQRS boils down to separating the interfaces for queries/reads/immutable operations and commands/writes/mutable operations. Unless you're bolting on unrelated concepts, like event sourcing, then CQRS is not a significant source of increased complexity in non-trivial applications.

Can you shine some light on which aspects led to higher complexity in your use of CQRS?

I'm not a US citizen nor I ever set foot in the US, and even from afar the quasi-fanarical displays of support for the US armed forces is a hallmark of supporters of the Republican party.