oaiey

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.

You can be suite in some European countries if you have a web page without an impressum and latest your domain registration will have your credit card to track you. Obviously, not all cases can be traced back.

Yeah. I agree. As a C# fan I discovered one day the change process and release notes. Like C# it does still have strong momentum in the language design space. It was a joy observing the last 10 releases.

It is their number one selling point vs. the competition. The space has already a dozen vendors with a healthy product mix.

I think there was no specific thinking in that space at all. They went for attestation of the app for security reasons of the API and their testing only runs on normal android and iOS devices. Consequently, they realized later this and write a response pointing to their tested platforms.

So understanding why they drop it is IMHO easy. Understanding why they use only attestation based API despite and forcing their third party ecosystem out is stupid. Companies do not understand open communities.

So roughly the same salary :). After subtracting health care, pension, etc plus currency exchange.

If it is shown to millions, everyone who is interested in you, they are factually not fact checking and you can do nothing against it.

It can destroy you. You are analyzing this on the assumption that people are rational and have capacity to do the check. They have neither.

You forgot to mention that it is the real name and it is shown to everyone who has interest in you and they are not fact checking.

But we agree that this was also wrong, right?

But you are not doing a 2 hour rabbit hole search when you stand in front of a T-shirt and check whether it is fair traded or all-american produced.

It is good for a professional with specialization in history.

UK tech salaries are also not high. And 64k pounds for a history and/or business major is quite right. Do not forget also: history is a overrun study with many people afterwards driving taxis

They really miss out on opportunities here.

WSL 1 was not a VM in a traditional sense. WSL 1 was a Windows subsystem which translated Linux syscalls into NT syscalls (e.g. file open). NT has capabilities there from its origins in the 90s supporting in theory user spaces for posix/os2/...

The whole forum here is bashing Windows for being thermal / performance disaster compared to apple products. I do not see how a laptop running Linux will evade the same fate (at least the bashing :).

Understandable. But would it be much easier to release it without promise to support. That everyone would just accept.

He, however, forgot to upgrade the look over time.

I blissfully ignore the cyberpunk era.

That! Okay, in 2026 this could be a LSP feature with some editor fanciness but this is a real benefit. My nitpick is that we do not have a depreciation on the non async ones