thibaut_barrere

Pressure on the road, and profits, are not similar to those induced by pedestrians and cyclists.

Yes but there is a clear relationship between them in most countries!

This is not how authors rights work

Yes but in the case of GH, it also happens in cases where the data is old: not just a temporary drift.

The opt-in is bollocks. I am a LG owner and quite technical and used to legalese too. This will get them fined in Europe.

I like when large projects do that. This gives leeway for sister projects (eg wrappers) to anticipate, room for apps that use it intensively to test things out (release candidate etc), something which has really helped me in the past.

In that specific case I use a Polars wrapper in Elixir (called Explorer) all week long, and I am very happy they are giving us early hints.

I do not read this in the article, I was more understanding that half the kids of the world could be concerned to a level or another, can you quote?

I made a preliminary attempt as well and had the same experience. I hope to renew with a better success.

Just in France, cost of this year heat waves has been estimated between 10 and 15 billion euros (figure shared by a ministre today).

Even before, Turbo Pascal was fairly appreciated in some circles (e.g. demomaking), quite productive and nice to use!

Related: https://saracroche.org/

Some people tend to forget that you got to start somewhere, and a lot of huge undertakings started this way. Such as Linux ;-

It turns out public money is more expensive these days. Debt is a more mainstreamly exposed problem.

Same path & agreed. The amount of things you do not have to care about with BEAM/Elixir compared to Rails is really interesting.

Yes, massive respect for that type of perseverance on long term, important changes.

It is one of these instances where « let the market decide » is not necessarily the best option on the long run.

Afaik the system is being consolidated

https://epicompany.eu/media-insights/ideal-to-phase-into-wer...

« iDEAL will begin rebranding to iDEAL | Wero in 2026 »

Artificial scarcity + the urge to impose fashion cycles, sadly

It feels like we have reached the Turbo Pascal era, but only compiled to the browser.

And sometimes, like in Sharepoint, the process could not be completed.

That backdoor is so up front about it. We might as well call it a frontdoor.

Unless regulations explicitely incorporate how to handle incumbents & newcomers. One instance of that is MMTIS (multi modal passenger information), which explicitly states innovation and new players as a goal. There are other similar examples.

At the anecdata level, you are right. At the global level, let’s say it is a bit different.

There’s a strong narrative that it’s unreasonable to stay in the EU (“too regulated”, etc.) if you want to hack on real stuff. Yet plenty of us do — Bellard being exhibit A.

LLM use is very solid here. I have been shipping some fairly cool stuff for different clients, just like if I was managing a team of 3 or 4 people.

The stable nature of the language, and the static/immutable nature of constructs, presumably really helps moving safely here.

Thanks!

BYD has cars supporting this afaik. And working in the electrical charging point data sector at the moment, we see that fast charge is a breaking point to make people decide the switch is worth it.

You can have well-integrated applicative workflows (eg: progress report on a permalink in your front end app), app-restart-proof resumable workflows, and it avoids adding an extra piece of infrastructure.

We use Postgres for that on https://transport.data.gouv.fr (Elixir app which does a fair bit of processing), and it helps.

Not familiar yet with pg_durable though, but I have used or implemented similar solutions and can relate.

I started migrating to FastMail years ago, but never got to switch in full yet, because in my case with a public email address, the level of unhandled spam is too high.

Did you meet that issue?

US clouds offer are featureful not first because it is useful, but because it is the best way to ensure vendor lock-in. A lot of implementors are now realizing that you can achieve the same level of service, or better, with less cloud features.