3,756 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 :)
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
My understanding is that currently python can collect type data in test runs and use it to inform the jit during following executions
Also python is far less aggressive with lint warnings so it is much easier to make mistakes
IMHO the idea of a complex and inference heavy type system that is mostly useless at runtime and compilation but focused on essentially interactive linting is relatively recent and its popularity is due to typescript success
I think that static typing proponents were thinking of something more along the lines of Haskell/OCaml/Java rather than a type-erased system a language where [1,2] > 0 is true because it is converted to "NaN" > "0"
So app state -> bigint -> bytearray -> compressed bytearray -> bigint -> packed utf16 string.
Probably it would but help much
At best we would have less monopolistic global powers trying to rent us everyone of our freedoms
Often when something is discovered or invented is far less influential[1] than when it jumps on and hype train.
[1] the discovery is very important for historical and epistemological reasons of course, rewriting the past is bad
> For me, the ultimate laptop bag is one that looks nothing like a laptop bag; it should look like nothing special at all.