Pity that HN's ability to detect sarcasm is as robust as that of a sentiment analysis model using keyword-matching.
3,331 karma · joined June 9, 2020
https://justfuckingusereact.com
Perfect satire. Thank you.
Which led me to this very interesting article from 1965: https://www.thecrimson.com/article/1965/6/17/the-university-...
In it, the author described the attacks on specific personnels and public villainification of Harvard. More tellingly though, the author wrote the article for students in the 60s, who, growing up a mere decade after, most likely considered the events "an aberration which could not have lasted", and that, "the whole [McCarthy] period has an air of unreality".
Those who did not know history are bound to repeat it. Unfortunately, no amount of textbooks and historical resources seems to be sufficient to impart lessons to subsequent generations, and we are bound to repeat it after a few cycles.
It is interesting to see the resurgence of such imperial practices in modern-day America. I think it worked out quite well for the Tang dynasty, but arguably that was because all East Asian feudal states were authoritarian monarchy back then. A logical next step would be for POTUS to declare himself as the supreme leader of the world, emend educational materials to propound the idea that the US is superior to other tributary states, quell all internal cries of undemocratic practices, and ban books that promote historical knowledge to avoid unnecessary dissent.
https://socket.dev/blog/pypi-package-disguised-as-instagram-...
https://socket.dev/blog/monkey-patched-pypi-packages-steal-s...
https://socket.dev/blog/malicious-pypi-package-targets-disco...
https://socket.dev/blog/typosquatting-on-pypi-malicious-pack...
[1]: https://craftinginterpreters.com/representing-code.html#the-...
> There is a new entrant: WeLib. They appear to have mirrored most of our collection, and use a fork of our codebase. We have copied some of their user interface improvements, and are grateful for that push. Sadly, we are not seeing them share any new collections, nor share their codebase improvements. Since they haven’t shown commitment to contributing back to the ecosystem, we advise extreme caution. We recommend not using them.
With how bloated browsers are right now, good riddance IMO
On state, in my current project, it is not statefulness that causes trouble, but when you need to synchronize two stateful systems. Every time there's bidirectional information flow, it's gonna be a headache. The solution is of course to maintain a single source of truth, but with UI application this is sometimes quite tricky.