krab

The issue is that you don't have to give the credit card details in this case. That charge wouldn't probably have gone through anyway.

During a significant part of history, text was definitely considered a source of truth, at least to the extent a lot of people see video now. A fancy recommendation letter from a noble would get you far. It makes sense because if you forge it, that means you had to invest significant amount of effort and therefore you had to plan the deception. It's a different kind of behavior than just lying on a whim.

But even then, as nowadays, people didn't trust the medium absolutely. The possibility of forgery was real, as it has been with the video, even before generative AI.

Yes, there is definitely some overlap. Kubernetes will help you with the restart and to deliver network packets to the right process. It's also programmable. On the other hand, you have to manually craft the process APIs to communicate and they look very different from the in-process APIs for most languages. You have to think about exposing metrics to some external system that collects them. That and logs are about it for introspection. The rest you have to build yourself.

On the plus side, out of the box it can do things like "run this process N times", "don't run these on the same node", "run this on every node exactly once".

I'd like to get some experience on a real distributed project in Erlang. Mostly in order to be able to assess how big a productivity booster it really is. :-) But it's a chicken and egg problem. Not a hugely popular language <-> fewer developers <-> higher risk for the company.

Thanks! I kept reading about the magic HA properties of Erlang/OTP. Being familiar with systems built on e.g. Kubernetes, I thought I was missing something because I couldn't find a solution to the aforementioned problems in OTP itself.

What you say makes sense. I can see the benefit in message passing as a first class citizen so it allows extraction of some processes to a different node. But you still have to manage the process placements.

How do the supervisor trees avoid a single point of failure? Let's say I build "etcd in Erlang". How would I tell the cluster that there should be N processes running, each on a different node? And is there anything in OTP that would help me elect a leader or do I still have to implement that myself?

I have no experience with OTP but have read some books and did toy projects.

They mean .ai should exist but it shouldn't be managed by a foreign country. ;-)

Isn't API out of scope for copyright? In the case of CUDA, it seems they can copy most of it and then iterate in their own, keeping a compatible subset.

If there's enough space, a toggle emulation with two labels works well.

Loudspeaker [()---] Crossed-out loudspeaker

What about LinkedIn? That substitutes resumes for a lot of people. It has photos and it's not a euro thing.

Not familiar with the OP but this may have been the pitch for migration: "K8S will allow us better automation".

I was hiring that way in the previous company I worked for. Before we decided that, we had a few good candidates from UA and several African countries because initially we thought we'd limit only by the time zones.

In the end, we decided for EU/UK because of law compatibility, ease of enforcement (in case we would have to deal with some serious problems) and ease of gathering together from time to time.

Maybe it would be more practical MITMing near the CPU. Some plastic "extender" routing the relevant pins through an external device but still allowing for cooling?

But could the communication be authenticated? Like in CPU having a public cert, self signed. TPM then can authenticate the CPU that generates the key and later sends it only over an authenticated TLS session to the same CPU.

If you can reliably find the key in memory, even if it's partially damaged, it may practically possible to recover it. You can try keys sorted by edit distance from the recovered material. Maybe there are better methods taking into account the actual cryptography.

I see. But the business owner will compare the whole amount vs. an alternative system's fees.

This doesn't seem right. At least from the small business point of view. The banks here in CZ charge around 1 % + $10/month for the device and card acceptance.

The market may be looking at the Europe where instant wire transfers are free and people use them (paying rent, phone, anything recurring, paying for larger items like a car). Often people use them to split a lunch bill.

Mastercard/Visa is a huge thing here in retail but PayPal is really niche. No app leveraging the instant wire transfers is getting much traction. The network effects are huge and the card fees apparently aren't that high.

The latin cursive scripts differ country by country. And reading old letters, even if it's in my language, is very hard. The letters looked differently. A proficient writer would write them consistently but to read it, you're looking for "distinguishing traits", not for the letter shape as depicted to learners.

I think most of the latin alphabet languages have cursive forms. Cyrillic as well. Definitely English is no exception.

It's a kind of a tax - computed from your income. Similar to health insurance (in Europe). There are caveats like "you must be actively looking for a job" and "you weren't fired for an offense".

As I understand it the validation happens online to avoid tracking. Nowadays banks and telcos share a lot of information on their clients. So instead of giving out the unchanging personal ID number (containing the date of birth), you're supposed to give out the number of your ID card that changes every five or ten years. Or, in the online world, the bank gets a unique token.

I don't think it will fulfill that purpose in practice. The name plus date of birth is a very good tracking identifier and people will be still giving DOB to these companies.

While removing the driving license carriage requirement is a strict removal of a hassle, I understand where people don't trust the electronic ID card.

Unlike the driving license, you still need to carry it, either in plastic or as an app in your phone. And it's becoming a bit complicated. It's not a self-contained QR code with an electronic signature. It's a whole system that allows you to share only part of the info to someone (e.g. only age in the pub). It also remembers who asked for that info.

Experience from CZ and very fresh. The electronic ID app for instance is still only a few days old.

What's the difference from the previous state? You had to carry a driving license but the government had all the info anyway.

If you didn't have the license on you, they'd find you in the DB anyway. Possibly you get a €10 fine. The electronic driving license is just a simplification to me. You don't have to carry anything.

No, they claim their company would be worth 1/2 more had Apple not infringed their patent. Or probably they're asking for something extra to compensate for the fact they have to sue. Anyway not directly related to current market cap.

Without Austria it would be about half Catholic, half Protestant with a significant Jewish minority.

There are niche databases like that.

Check out https://evitadb.io/ for a very different use case. It has a rich query language supporting various e-commerce aggregations (as in faceting). They claim it benchmarks 100x faster than Postgres for this specific use case.

Although it looks very cool, if I'm not building an e-shop, I'm not using it. There will be some unfavorable tradeoffs for my case.

The probabilities aren't independent. The person jumping through the first hoop is probably more able than average. Therefore, any additional hoop - if it doesn't require a completely orthogonal skill - is less selective.

It's everywhere. Next day delivery vs in a week. Streaming vs DVD rental. CI jobs. Notification about relevant news for stock traders. Switching files in editor. Jump to definition in IDE. Typing and videogames you mention have a very tight latency budget.

If you don't fit in the budget for the specific task, your product features don't matter much.

Yeah, that's right. I just feel that latency is sometimes missing from the discussions re. developer efficiency vs paying more for compute.

In my experience, you need to care about latency. That affects user experience. It's quite hard to pay for better latency.