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 :)
If a bunch of good people acting in good faith produce a result an evil mastermind would want does it matter if they are good? On many levels obviously yes, on some practical levels the system and the incentives still need to change.
ht tp://[\x00::gg]\t/foo\nbar/%/%QZ/%F?q=<\"|{}>##also this one is valid too for the regex
%_%://%_%.%_%/%_%?%_%#%_%A parser that assumes the input to be already valid is usually not enough for most applications
according to that regex this is a valid url
__..__..%%%zz..
The difference between the 2 requirements is the level of technical knowledge needed and the necessary investment in tools
except that without a "prime minister" now there is no separation between the "king" and the fulcrum of political power.
The "lock on write" problem is that in MySQL i could run a OLAP pipeline for a few hours and have a fully functioning database with degraded perfomance, on SQLite the same pipeline would lock the database for the full hour. (there are surely ways to solve this (eg using the main db as read-only and a secondary db for writes or splitting the writes in incremental transaction), but it is not a "myth".
For better or worse they are much more well understood in C as they are front and center of the language semantics
> How is not having to mark your unsafe code as unsafe a good thing?
The problem with unsafe code in Rust is that IIRC nobody actually figured out yet the "rules" of unsafe i.e. which invariants you can stretch and which can cause UB. My (not super up to date) understanding is that this is an active area of research and progress is being made and also that in practice there are many well understood usages.
In short unsafe rust is somewhat worse than C++ as the boundaries of UB are less well understood/defined
By necessity a lot of people write very similarly to how llm do