oaiey

Also HR has bad employees / agent once in a while.

This is the fine after it got influenced by the political branch. It is a sign towards the companies that the law still bites and has to be adhered but reduced in this case to a level where it can be accepted by Google without major escalation in trade politics.

Yes. Entering the US is now a risk factor for anyone from abroad with even moderate political opinions.

Particularly node.js single threaded operational model basically eradicating concurrency from the brains of a generation of developers.

When I learned about async/await when it came out with .NET, they put tremendous amount into explaining that async/await is not concurrency. But that was in time when you did a training when a new version of your programming stack came out and you did not consume knowledge in 30s snippets.

I agree with you. For one, if you are small, build a good monolith and call it a day. So much more efficient than anything else.

Stream based systems where you maintain your own curser are a strong architectural decision similiar to a messaging systems. They also have their downsides.

Lastly on the last sentence: as soon as you need reliable processing of external input or output, inbox/outbox are needed. You are distributed because of your payment processor, because of your user email sending, etc. You do not want to block your core job processor just because the email server is overloaded right now.

If you write a good monolith, you would do exactly that. You message between the subsystems and you are good with just adjust the "ownership" within a transaction.

If you are distributed you have the problem of shared databases. It would break your Microservice ownership etc if you all operate on one database. It is an anti pattern. For very good reasons.

In the past there have been distributed transactions between databases or other systems but they fell out of love due to their proprietary and limited nature (e.g. Microsofts MSDTC)

I agree all about company creed and also in many cases the standard is the lowest common denominator of their implementations. I am also a fan of putting national sovereignity over profit, but that does not change that in most cases only companies have the interest, the need and the insights to standardize stuff.

The bridge between inbox/outbox and queue is not perfect. But it derisks the process a lot. It is much saver to insert a (ideally idempotent) message into the database and then (without transaction) confirm it to the queue than running the whole business process. The likelihood the process will fail is much higher than the inbox / outbox. These patterns also keep your brokers queue empty and allows you to gracefully shutdown your systems.

The amount of confusive naming of CarPlay vs CarPlay Ultra and Android Auto vs Android Automotive brings into this conversation is amazing.

So that your ass get fingerprinted you would need to use the Usermedia control and then hold the camera behind your back ... Okay, I let myself out.

That is not how standards work. Some for sure, but the majority are established by groups of companies / a guild establishing rules. The law pressures them often into it (e.g. the EU did not say USB-C port, they said: one standard, you industry figure it out).

There are surely exceptions (maybe the IEEE; which are professionals union).

Sounds like you advocate for the Amish just 300-400 years later. I think you are right.

It has been trained already to kill humans. It is already an option in many applications.

The key part of European projects is not their quality or greatness. They do not think big.