bit_flipper

7 ms·

1.
by bit_flipper 2y ago
A lot of what you're saying depends greatly on the exact game you're talking about and what winning and losing means, for instance if the game has discrete places instead of a bimodal winner/loser. For a few of the games I wo
2.
by bit_flipper 2y ago
Thanks for the link, I hadn't read this one yet. Very interesting. I feel like as an industry we're still in the stone ages on how we do skill matching systems. A lot of the current and even future system they describe is really n
3.
by bit_flipper 2y ago
I've written game matchmaking before for games and found it far more challenging to do the portions related to matchmaking groups by skill. If you're hyper latency sensitive then perhaps this blog post is really useful? But for th
4.
by bit_flipper 2y ago
Definitely an interesting question. Some things that may explain why -- Mongo was always AGPL and relicensed to SSPL. This had the following consequences: * Very few companies and zero large cloud companies ever attempted to run the MongoDB
5.
by bit_flipper 2y ago
I've run Postgres at large scale (dozens of machines) at multiple companies. I've also run MongoDB at large scale at multiple companies. I like both generally. I don't really care about data modelling differences - you can bu
6.
by bit_flipper 2y ago
You can also build whatever you want with SSPL, as long as absolutely everything you use to run a service that supports it is also licensed as SSPL. It's not that different from the AGPL in spirit.
7.
by bit_flipper 2y ago
By which metrics are you evaluating those companies' license changes? Both are significantly more profitable than before they changed licenses, MongoDB especially. I'm not sure there's a causal relationship, but it doesn&#x27
8.
by bit_flipper 3y ago
I'm not sure what experience you have, but I've run both their Enterprise licensed database on prem as well as migrated to Atlas and there have never been any licensing issues preventing vertical scaling of databases. One of our c
9.
by bit_flipper 3y ago
This article seems to have inspired others to look at MongoDB again, so I'll give my thoughts after using it recently. MongoDB Atlas is a surprisingly good managed database product. I'm not a huge fan of someone else running my da
10.
by bit_flipper 3y ago
SSPL has no provision even close to the reach of the "anti-competition" clause Hashicorp is using. While SSPL is not considered open source, it isn't that far off from the AGPL. The difference between SSPL and AGPL is that
11.
by bit_flipper 3y ago
Source for which claim? Kyle was paid for work testing 3.4.0-rc3[1] and 3.6.4[2] which analyzed single document concurrency in a sharded configuration. Those tests run in their CI [3]. MongoDB had some somewhat misleading copy on their webs
12.
by bit_flipper 3y ago
Not your main point, but MongoDB didn't commission Kyle to do that report as they had in the past, he did it on his own time. That's why his report doesn't mention repeat testing. They do actually run his tests in their CI an
13.
by bit_flipper 3y ago
Where is the root of trust for package signatures? Who is verifying signatures: the package index or end-users? How do you distribute public keys? PGP is mostly maligned because of its support for old cryptography standards, some needless c
14.
by bit_flipper 3y ago
If you use Musl 1.2.4+ (or Alpine 3.18+), there are no longer the same DNS fallback issues: https://www.openwall.com/lists/musl/2023/05/02/1 To summarize the issue: DNS is done optimistically over U
15.
by bit_flipper 3y ago
You can read about why projections still very much matter for large scale (which is what I think you meant; small scale would be something that shows you whole countries and not used for road navigation) maps in the article I linked. Google
16.
by bit_flipper 3y ago
This article doesn't touch on the actual reasons why Mercator is still in widespread use: * It was the first widespread projection because of its practical use for nautical navigation (where it is still the best projection available),
17.
by bit_flipper 3y ago
The author should investigate their networking setup. I can run their Go fetchall example in no more than 70ms. Their benchmarks are surely dominated by noise.
18.
by bit_flipper 3y ago
Sorry, I should have been more precise. encoding/gob is not optimized for situations where you create an encoder or decoder, read/write a single value, then discard that encoder/decoder. As the author noted, payloads for a si
19.
by bit_flipper 3y ago
Your note about encoding/gob being inefficient is somewhat accurate for how you're using it, but I want to talk a bit about how you could improve your use. encoding/gob is intended for streams, not stateless marshals/unm
20.
by bit_flipper 4y ago
Go has probably the most extensive stdlib of major languages outside of Python (happy to be corrected on that). You can get a sense for what is available by looking here: https://pkg.go.dev/std . There is also the "pseu
21.
by bit_flipper 4y ago
It's fine to dislike Go's philosophy on error handling, but in order to save you and your co-workers a lot of headache down the road, I'd recommend you just use another language. This is not something you want to do in Go and
22.
by bit_flipper 4y ago
I had a look through some of your comments here and elsewhere and just wanted to give you some friendly feedback: This style of commenting is quite toxic. I think you'll feel happier if you let go of the tribalism and engage with other