292 private links
Eine How-to guide
The virtual DOM replacement for React. Gain big performance wins for UI and data heavy React apps. Dead simple to use – try it out today with just a block()
Pour faire partie du club des 1% les plus riche en France, il faut avoir 7 180€ par mois.
Pour le club des 5%, c'est 4 113 euros par mois.
Ups. La coupe du monde du Quatar n'était pas neutre en carbone?
A sort algorithm found by an AI is integrated to the LLVM standard C++
A blog post vulgarising the thing https://www.deepmind.com/blog/alphadev-discovers-faster-sorting-algorithms.
We can read here that less instructions are needed at assembly level.
It can be useful to generate an HTML view of entries :)
Create a command line interface from a REST API.
It seems powerful!
Joat uses a YAML file to define subcommands of two types: requests and scripts. Requests subcommands ease the interaction with a REST API and scripts combine multiple commands into a more convenient one.
Use one package manager built on top of corepack to support npm, yarn and pnpm.
#idea #project support more package managers such as cargo, deno, ... :)
Oh wait, there is already something https://github.com/egoist/dum
Execute powerful common commands
A collection of awesome projects. It is great to find good quality projects in it.
It looks good.
32 bits integers: at most 4 billion.
Times it is not enough:
- database primary keys: 4 billions record is not that much
- IPv4 addresses: we want more than 4 billions computer on the internet
- registers: limited to 4GB of RAM
- unix timestamps: end at Jan 19, 2038
33 specific ways to improve your Rust code
2b||!2b
Definitely a cool project!
All of these sound good to me. The thoughts are in contradiction with some terms of the current IT developments and programming.
About the current state of the software:
- it is getting slower as demonstrated by the latency. A computer from 2015 is 2-5 times slower than an Apple 2e from 1986 just at reading a keystroke and displaying it on screen. https://danluu.com/input-lag/
- putting all-in-one software increase complexity, and maintenance costs. They become untrustworthy.
- they are more a liability than an asset
I take some quotes out of it.
Humanity didn't get good at building houses by building the same house a million times. We built lots of different houses and learned from each other's failures.
As a programmer, I've tried multiple times in the past decade to create services just for myself and a few friends. Each of them has fallen away after a year or two. And a big reason for that was the burden of keeping up with updates for all the tools they depend on.
My initial plan had been to create clones of apps for myself and take out lots of features. [...] I didn't expect to find myself wondering what a web browser for memory palaces might look like.
Solutions
- making forks instead of all-in-one software. It keeps them lighter.
- we can have a huge amount of softwares. It is ok. Prefer software with thousands rather than millions of users, that seldom requires updates, that spawns lots of forks, that is easy to modify, that you can modify.