brewmarche
Joined 8 years ago
Karma
516
Submissions
323
Member since
Aug 5
Joined 8 years ago
The parts of Linux that get integrated into BSDs should not be GPL-licensed, e.g. <https://github.com/torvalds/linux/blob/c339f4010dea8b0d754f8...> and its siblings use MIT.
Not sure why macOS doesn’t ship such a build of curl.
This was linked in the blog
from <https://en.wikipedia.org/w/index.php?title=Desire_path&oldid...>
Location: Germany (UTC +1/+2), EU citizen
Remote: preferred
Willing to relocate: no
Technologies: C# and previously C++ and Java, I like functional programming and data-oriented where appropriate. I know SQL, Azure, Docker, high performance computing (Monte Carlo simulations), see also CV
CV: https://pub.999568.xyz/wwtbh/rcv-202610-vfay7k0zano.pdf
Email: see CV
I work in mathematical finance so I have domain knowledge in that area (derivatives, pricing, probability theory), but other domains are also welcome.Happy to provide you with an unredacted CV personally.
Some older RFCs even recommended using it for passwords, which needlessly reduces entropy (yes we need to normalise passwords because of combining characters, but we don’t need to collapse symbols that a user can choose from, like ſ and s).
In my opinion, the compatibility form makes mostly sense for searching text, and even then it’s sometimes annoying (I want to search exactly for ss and not ß, browser). If you know of other good use cases let me know.
It also OK to disallow registering two identifiers with the same compatibility normalisation form (edit: this does not prevent all homoglyph attacks BTW, that is another can of worms), but I don’t see the need to normalise the identifier when it’s used.