3,748 karma · joined January 23, 2019
http://unsongbook.com/
My guess is it will be the weirdest book you will have ever read.
If it is not, please, I am curious about what is your weirdest book :)
That is because they are not vector spaces of function but a quotient of one
In this world the user is left vulnerable because attackers can use published vulnerabilities that the maintainers are to overwhelmed to fix
I guess we disagree on the reasonable interpretations of this sentence
Things can have similarities without being the same. Also not being unique is not a moral failure.
I think I am failing to understand your stance.
The main difference I see is that of focus here the focus is to migrate a database without downtime or excessive global locks, keeping multiple versions of the schema is a detail.
Of course there are failure modes in any approach but "oh no! Herding cats is hard. Who could have imagined!" is funny to me
But something that can bite you with these solutions if that browsers allow you to duplicate tabs, so you also need some inter-tab mechanisms (like the broadcast API or local storage with polling) to resolve duplicate ids
Even if pizza hut wanted people to order pizza the most efficiently with no time wasted it would still want it to happen on their own platforms.
Because if people went to all-pizzas.com for their pizza need then each restaurant and chain would depend on them not to screw them up
LLMs can cite sources as well as any human, that is with a non-trivial error rate.
LLMs are shit for a lot of things but the problems are with the quality of the output whether they work by magic, soul-bending, matrix multiplication, or whatever is irrelevant.
Whether LLM are good or not, liars or not hardly depends on them being implemented on random black boxes algorithms becouse you could say the same of our brains.
for example in css which does not have inline comments vscode fails to reliably comment a block of text.
for strings it is even worse as usually they use the same tokens for opening and closing which make everything more ambiguos
To my knowledge only Zig's multiline strings work this way
const hello_world_in_c =
\\#include <stdio.h>
\\
\\int main(int argc, char **argv) {
\\ printf("hello world\n");
\\ return 0;
\\}
;I am making a parallel to how email works. With my own domain I can configure my DNS to use various different email providers and move however I like.
This is both decentralized and federated.
I can also use someone else's domain like gmail.com but then I lose portability for ease of use.
This is federated but not centralized.
Or I can host my own email server on my own domain and deal with spam fileters, bots, etc. directly
This is decentralized but less federated.
Mastodon is federated between instances but each instance is entirely centralized. Even account portability requires admin consent IIRC.
Bluesky is trying to create a space where users can own their own data like you can own your email AND aiming for widespread adoption.
I am not particularly focused on Mastodon, it is just the only part of the fediverse with a modicum of adoption.
Bluesky is trying to build something as decentralized as email where still few providers dominate the market and most use few common ip/domain blacklists.
Yet it is one of the most decentralized protocols on the internet.
I a not saying Bluesky is a masterpiece but I think it is naive to hold it to a higher standard than email as a protocol.
If it fails due to little adoption then it is a fail, if it succeed there is a possibility of it becoming a good decentralized protocol
Something like
- maintainers of package com.foo.pkg want to transfer it to com.bar.pgk
- com.bar creates their own pgk clone and marks it as a successor to com.foo.pkg (with a specific version)
- com.foo.pkg pushes an update with that specific version marked as superseded by com.bar.pgk
- package managers warn users at update time that a change in namespace happened and ask for consent
This could be extended to multiple forks to let the user choose
I feel it would work fine
This together with the fact that the main benefit of range types is on the consumption side (ie knowing that a PositiveInt is not 0) and it is doable to use try-catch or an equivalent operation at creation time