ralegh

Depending on who is paying and how much, someone might light a small fire to avoid the fine.

Open source for bot protection specifically would be difficult. If I as a bot developer can see the tests you run I can just modify my bot to pass them (either trivially or by brute force).

Its channels from Spain, so presumably appeals to Spanish speaking countries.

Wonder if it would be better to auto translate to broken rust, ie forcing the user to fix memory issues. I imagine that would lead to pretty big refactors in some cases though.

I stand corrected…

Just noting that 4000 vCPUs usually means 2000 cores, 4000 threads

DoS is a performance problem, if your server was infinitely fast with infinite storage they wouldnt be an issue.

This is fine assuming the popular request types don’t change, but arguably if both new versions of matching are sufficiently fast then I would prefer Ken’s long term as the other could become slow again if the distribution of request types changes.

Could you give some examples of where you're using it?

Web browsers could have 1/10th of the features, basically enough for markdown, forms, forums, displaying media, and minimal styling.

I used generics once, was kinda useful, but definitely avoidable. The only feature I could see myself using is something Linq-esque for slices and maps. Otherwise I’m content.

I personally found the polars API much clunkier, especially for rapid prototyping. I use it only for cemented processes where I could do with speed up/memory reduction.

Is there anything specific you prefer moving from the pandas API to polars?

Markets are what you described. Participants that regularly beat the market are rewarded with more money (and confidence) which lets them bet larger size and have more impact on the market.

Uninformed bets should wash out as noise, and informed bettors should reverse uninformed moves so long as they are profitable.

I guess I’m in that camp. I can come up with a good abstraction after working on a problem for a while and refactor it into my code. Or I can come up with a really simple abstraction (eg a Go interface with 2-3 methods), and that usually works well. But I try to avoid starting a project by defining a bunch of abstractions, since I just end up writing loads of boiler plate. Yes, I’m probably doing some things wrong.