Maël Nison

The more I see async iterators, the more I feel like they're a really fancy way to make a frustrating and painful API

I don't think it's just that. Once the cost issue is solved it'll be a new media, perhaps the primary one. How much would you invest to be in control of it?

Meh. It felt like the movie occurred within a dream. Nothing else than the characters mattered. Side characters had no depth, main characters no flaws, world governments no agency, plans no credibility. It was ok tier, action was nice, but I preferred Thunderbolts a lot better.

Lost my own Simba last week... so sorry for your loss... 😢

For writing heavy Yarn core code LLMs are pretty bad. For writing well-scoped libraries used by the core they are ok to get quickly unblocked as long as I replace the code down the road. For writing prototypes without domain expertise needed? They're amazing.

So we can hope stage 4 for next week and can it a day? 😇

GitHub - tc39/proposal-import-bytes: A modest proposal for importing bytes in javascript A modest proposal for importing bytes in javascript - tc39/proposal-import-bytes

I've been hoping for this proposal for so long ❤️ github.com/tc39/proposa...

Actually more up-to-date link: nodejs.org/api/permissi...

There is something: nodejs.org/download/rel....

We need a European Sovereign Tech Fund With a new feasibility study, GitHub’s developer policy team is building a coalition of policymakers and industry to close the maintenance funding gap.

We need a European Sovereign Tech Fund
github.blog/open-source/... "Open source software is critical infrastructure, but it’s underfunded. With a new feasibility study, GitHub’s developer policy team is building a coalition of policymakers and industry to close the maintenance funding gap."

MIT works well at a time mostly everyone is well-behaved and works for good. Current times make me a little more cynical though...

For instance something like "Entreprises operating in countries with concentration camps are excluded from this agreement."

Of course I'd prefer smarter people than me to come up with more impactful rules, but you see the idea.

Two hypothetical notes though:

- I don't think any single project could pull this off successfully. A concerted effort would be interesting though.

- I don't think singling out organizations by name would be a working strategy. Imo it'd be more interesting to define characteristics.

❌(REVERTED): Add text to MIT License banning ICE collaborators by jamiebuilds · Pull Request #1616 · lerna/lerna The Lerna Core team has reverted this PR and revert information and response can be found in #1633 ============================================ In this PR, the following text has been added to the ...

My opinions about an old license drama are subtly evolving

Not sure what your point is. Companies routinely drop the non-compete on exit since otherwise they must compensate the employee for the duration of the non-compete (at least UK and FR).

I imagine it would be different for key employees in a very hot space of course, but I don't see that as a bad thing. If someone is key, they likely are privy to internal information that it wouldn't be fair to leak to competitors.

Citation needed on "most companies enforce" - I never once worked for a company who enforced it. Otherwise they have to compensate (pay a third of the salary for nothing), and it's time+location bound, so they all explicitly release employees on exit.

Yep; for instance if you're using Esbuild you'll NOT be using the React compiler, it'd negate a good chunk of the perf improvements.

No I don't have room to display them but that'll be a problem for future me to solve

My wife gave me a birthday present and the kid inside me is screaming 😱

Le cringe de faire un alt pour bypass un block ...

Peut-être dit différemment, je trouve qu'il y aurait du sens à tirer profit des apprentissages du passé autant que des analyses du présent pour appréhender ces évolutions.

Ah non du tout, c'est une véritable question que je me pose, indépendamment de la question de l'IA elle-même, au final. Je me demande à quel point on aurait un biais à penser que notre situation est unique alors qu'elle serait cyclique.

Mecton il faut vraiment te calmer, je suis un péon sur un réseau social et autant ça m'intéresse de discuter calmement autant me faire agresser par un random qui impose son point en hurlant ça a tendance à me friser.

Oui, tandis que sur internet tout le monde sait faire preuve de retenue et sens critique, je vois ton point, ça n'a effectivement RIeN à VoIR.

Tout à fait d'accord sur la boîte ouverte. La question qui va se poser imo c'est 1/ comment utiliser ces technologies d'une façon éthique 2/ comment accompagner l'apprentissage de cette technologie. On a raté le coche avec les réseaux sociaux, c'est important de garder ces considérations en tête.

Par curiosité, quelles étaient les conclusions des recherches du même type, lorsqu'Internet est apparu? Ca n'est qu'un soupçon mais ça ne m'étonnerait pas que les conclusions aient été similaire (les gens ne cherchent plus, ils perdent en autonomie, etc).

It's neat to know what are all the workspaces in the project. At work we use this information to perform some more validation or generate files around. Other package managers wouldn't install it (up to them to support this feature or not).

I guess `process.versions.pnp` would remain PnP-exclusive, just as a marker that the runtime environment is a "true" PnP environment.

The `pnpapi` could be generated as a regular package in the `node_modules` folder. This way even pnpm or node_modules installs could introspect their dependencies.