

Then where do you see the house of cards? What’s the practical difference between == and ===, when your app is type-checked and the inputs are safely parsed?
From Kyiv, in Kyiv.


Then where do you see the house of cards? What’s the practical difference between == and ===, when your app is type-checked and the inputs are safely parsed?


Capitalism or not, fuck animal abusers. There’s no ethical way to keep slave animals, period. The whole “industry” must be destroyed.


Nextcloud Forms have a ranked choice question type. The result shows the admin a Borda count, though for some reason it’s calculated on the front end, not on the server. Easy to set up, to share links, and to vote. Can be anonymous or require an account. Implementing Schulze STV or another multi-winner alternative is in my plans, but idk when I’ll get to that.


Opposite, living in a house of cards is when you blindly trust data that comes from user. Regardless of the language. eqeqeq isn’t in the recommended linting presets because if you end up needing it, you’re probably already in big trouble because of insecure software design.


== has never, ever caused me a single issue. Parsing all server input with type-safe schemas makes sure that where I expect a string, I get a string; where I expect a number, I get a number. Bad data must result in an error before it reaches logic.


From the article it sounds like Kurds actively helping each other online are doing all the work. Not sure where the “AI” comes in.


Libtcod? Cool project. Btw do those generated tests tend to be helpful or confusing?
There were attempts to rewrite imageboard software with modern dynamic frameworks and caching infrastructure, but it scaled worse than oldschool index and thread html regeneration on post event, and was cancelled. The effort was called something like Infinity, by 8chan.