332 karma · joined January 2, 2019
https://github.com/Stirling-Tools/Stirling-PDF/blob/7f577a60...
> NATS is an open-source messaging system. At its core, NATS provides publish-subscribe messaging, but has expanded to enable other features. It has a request/reply mechanism which you can use for service-to-service communication (in lieu of HTTP APIs). And it now includes a persistence layer which means it can on workloads you'd normally turn to Kafka for. The project is supported by the CNCF.
https://github.com/prettier/prettier/issues/15476
Prettier moves ts-ignore comments which can cause TypeScript errors:
https://github.com/prettier/prettier/issues/15876
Interpreting nested CSS functions' "-" as minus and inserting a space:
1. Pressure to maintain numbers
2. Fear and silence
3. Young ‘uns and a bigger-than-life CEO
4. Weak board of directors
5. Conflicts of interest overlooked or unaddressed
6. Innovation like no other company
7. Goodness in some areas atones for evil in others
From a game theory perspective, perhaps this makes sense, as any bargaining power that a successful app might have to come to a special agreement with Apple/Google is diminished if their app isn't in compliance.
My system's SSD's are both 3 years old, and most of my friends' are over 5 years old. So I would say it is a problem.
There must be a browser plugin that offers the date a website was first indexed.
I am surprised that Marc didn't retract a fourth paper, based on: https://stanforddaily.com/2023/07/19/sources-refused-to-part...
> Unfortunately, we just couldn’t get it to work
Every time I read one of these migration stories, I find myself waiting with baited breath for the part the team couldn't achieve. After finding it, the remainder of the story becomes difficult to read.
It isn't necessarily the team's fault, the developer experience clearly has room for improvement. Props to Val Town for being so honest, it is difficult to do.
It is similar to pseudo-blameless engineering cultures, where engineers won't admit to bugs, or update the status indicator, least they face the shame of writing a post mortem, or having it brought up in their performance review.
The result will automatically be await-ed.
Please don't do this, it is more confusing to omit the await keyword.