Java LSPs are essentially the same approach, headless Eclipse JDT or NetBeans.
While Metals for Scala was an overhaul from the former Eclipse plugin (and Ensime) plus early experiments embedded in the Scala 3 compiler. And Metals v2 is yet another rewrite.
Ask anyone who tried to dispute a purchase that happened within the EEA, whether online with SCA or card present with PIN, card issuers often tell you to deal with the merchant directly. The interchange cap has significantly reduced revenue made on card payments, they have an incentive to avoid unnecessary manual work.
I've never used iDEAL but I assume the confusion comes from the fact checkout widgets (e.g. from Adyen) are transitioning from iDEAL to "iDEAL | Wero". I assume UX is the same, i.e. scan a QR code with your mobile wallet app?
If I understand correctly it's developed by the same people: Payconiq.
Which is pretty much the case with Visa and MC too. There's little card payment fraud in Europe thanks to mandated strong authentication, and very low transaction fees as interchange is capped by the EU; card issuers don't initiate chargebacks so easily.
Easy and approachable sound pretty subjective to say the least; feature and syntax wise, Swift has become an absolute monster of a language. Rust's tooling and ecosystem are ahead and these points matter to me more than the raw syntax in the age of LLMs.
Almost exactly the same (or worse) can be said about Google's E2EE RCS, but somehow Apple decided to publicly back the initiative. Most people would much more benefit from 1) a faster and broader rollout 2) every other feature in recent versions of the spec, rather than getting a false sense of privacy, yet we're getting a barely compliant RCS client stuck in 2019, plus performative E2EE.
SEPA transfer fields need to follow a standard. I think it's fine, we shouldn't put more control and censorship there (try to put Daesh membership fee if you want to get your account locked...)
However a chatbot should absolutely not be able to display arbitrary and clickable links outside a pretty tight whitelist (like, the bank FAQ).
I was a teenager when Switzerland introduced the mandatory ID check, in 2003 or 2004 iirc.
My carrier added 10 CHF credit to my prepaid plan for the trouble.
It's still fairly easy to buy a Lycamobile SIM/number that was enabled with a fake or stolen ID. Consequently some banks and services ban entire number ranges, which is not only ineffective but also affects people who committed the sin of keeping their first phone number even after moving to a proper postpaid plan...
Bilateral agreements were signed in 1999 and freedom of movement enacted in 2002 so you must not have looked very hard. Also claiming that immigration from a country like Portugal was hard before FoM is extremely funny given the number of Portuguese immigrants in Romandie.
Words have a meaning and bringing diplomatic permits to the topic when they follow their own rules and are specifically outside any immigration quota is not particularly helpful.
You're throwing a lot of words that you don't understand nor have much relevance to the topic.
Before bilateral agreements and the freedom of movement, not Schengen which was ratified much later and is completely irrelevant here, you needed a work permit, not a visa (lowercase), which anyway at CERN is the equivalent of a diplomatic permit given to all international and tax-exempt NGOs in Geneva/Switzerland. And of course you lose your CDL permit quickly after your contract expires.
Getting a B permit before FoM would specifically not have been as hard for you as for someone from another continent.
Yes. We can cap non-EU/EFTA immigration to zero but that's relatively small anyway. Getting out of Schengen-Dublin and more importantly the Freedom of Movement of workers would basically unravel all bilateral agreements.
The ML/AI ecosystem is a minefield, and pure Rust rewrites (Candle, Burn, ...) are still immature and incomplete. But I'm pretty sure we're eventually going to see the same uptake that's already happening in the data processing world.
LLMs are leveling the developer experience and productivity in a way that makes Python's strengths almost irrelevant, while it's still suffering from bad tooling (even with uv and friends) and poor performance.
AI/ML: interfacing with C++ libraries directly (or in Rust) is now a real option. For everything else, even 5 years ago I wouldn't have used Python, now there are even fewer reasons to do so. As far as I'm concerned the remaining use cases are notebooks and one-shot scripts.