camgunz

52 ms·

901.
by camgunz 3y ago
Implicating isn't a great way to document an API. You could easily do something you didn't intend to do, which could be no big deal or extremely costly.
902.
by camgunz 3y ago
> finding a server with rational administration is not cheap Sure it is: choose the server everyone else chose. We know exactly how all this stuff works out because we already hashed it out with email. Everyone will just use the equivale
903.
by camgunz 3y ago
You could say the exact same thing if federation could be forced. You can make whatever facile analogy you want; my point has always been there's bad scenarios no matter what.
904.
by camgunz 3y ago
Again it doesn't really matter because it's just the way it works, but it's also a feature for server admins. Imagine being harassed by someone, or imagine that person harassing your users, blah blah blah. Is there some hypot
905.
by camgunz 3y ago
You can imagine all kinds of scenarios, but it comes down to "are users of server X forced to handle content from server Y". It can be both good and bad, but either way the Fediverse chose "no".
906.
by camgunz 3y ago
I think it's probably a pretty bad idea to publish someone's stuff (content on threads) somewhere they don't want it published (a shitposting server). Feels like a TOS or copyright violation, if not just rude.
907.
by camgunz 3y ago
Thanks!
908.
by camgunz 3y ago
Is there a good list of dark game patterns to avoid? I'm not really up on the latest research.
909.
by camgunz 3y ago
Oh I'm not at all pretending there's an equivalence between a personal coach that delivers you anywhere you want to go and a coarse, generic mass transit system that's relatively indifferent to your destination. I'm sayi
910.
by camgunz 3y ago
What I do is make them test everything their code might do. "Oh you built a generic builder builder builder huh? I need at least 80% coverage for anything the builders might build." The code shrinkage you can achieve is remarkable
911.
by camgunz 3y ago
> potentially a game changer for our city My bet is you'll be amazed by how little changes. Sure you won't spend any time at gas stations/car dealerships and you'll be able to watch YouTube on your commute, but that&#
912.
by camgunz 3y ago
This probably applies to all tech workers.
913.
by camgunz 3y ago
Nah they're super different. Rust failing at compile time means you fix the bug before you ship it, which is helpful. MongoDB failing in production means either you fix the bug via testing before shipping, or you discover the bug after
914.
by camgunz 3y ago
Yeah there are many use cases where you aren't really using transactions, or where hard accuracy isn't a requirement (you're taking a percentage out of millions of rows) but you need fast write performance. It's very nic
915.
by camgunz 3y ago
> In 2022 Jepsen commissioned the University of Porto’s INESC TEC to develop LazyFS: a FUSE filesystem for simulating the loss of un-fsynced writes I love this; what a great example of pushing the state of the art forward. Kudos!
916.
by camgunz 3y ago
I think there's a lot of value. IMO we should add one of two (or some combo) things: - Hashcash - Clients can send an allow list to servers; anything from an address not on the allow list goes to the spam folder Email is a foundational
917.
by camgunz 3y ago
You'd probably be surprised by how many systems are just Postgres/mysql + Redis.
918.
by camgunz 3y ago
Yeah systems like this essentially just centralize power. For a failure case, see spam IP address blacklists. I think generally it's not a good model.
919.
by camgunz 3y ago
> No. Just don't use outside state? Obviously you can just make the state of your PRNG part of your overall state as well. You can't write a program to analyze any given PRNG (or whatever) to know what it will return when witho
920.
by camgunz 3y ago
I think SWEs think of databases only as a kind of generic persistence layer and aren't super interested in a lot of the details (more than one has said to me databases are just an implementation detail) or additional capabilities, whic
921.
by camgunz 3y ago
You can define functions in all major databases
922.
by camgunz 3y ago
Sure yeah but like, you gotta deal with clashes. The problem itself isn't hard, but trying to get the ergonomics right is pretty tough, especially when you're talking about multiple dependencies that didn't coordinate at all
923.
by camgunz 3y ago
n.b. I think some of your misunderstandings and invokings of the halting problem are nerd sniping people here. One in particular that got me was: > For any program running on actual physical computer hardware it is obviously possible to
924.
by camgunz 3y ago
(your formatting got a little lost but I get the gist) I've done a little langdev and I've found that UFCS interferes with stuff like field access (person.name) or things like interfaces. Let's say you have a person struct li
925.
by camgunz 3y ago
Sure, of course. My point is just that engineering orgs are generally super conservative and thus consistently fall prey to sunk cost fallacies everywhere. In a very irritatingly bureaucratic sense, you have to have a process for improving
926.
by camgunz 3y ago
The most interesting part IMO was at the end when op was noting his new company doesn't have teams/engineers create and maintain their own jobs. I've worked lots of different places now and something that's always frustr
927.
by camgunz 3y ago
Fair, I mostly mean the media here though. Like we're gonna spend decades lauding Ray Dalio and only when he retires are we suddenly gonna pop the hood and check what's going on in his hedge fund? It's just the meekest clickb
928.
by camgunz 3y ago
I'm broadly not that supportive of these kind of character assessments or psychological evaluations from afar. They're at best salacious clickbait. I despise Trump and I was even uncomfortable with all the same things around him.
929.
by camgunz 3y ago
> The thing is, customers don't necessarily want a distributed messaging system, they might be perfectly fine with a decentralized one if it supports E2EE. Maybe! You could argue that basically all the successful messaging systems e
930.
by camgunz 3y ago
> That's what "effectively" means. Sometimes hard things are hard, and it turns out a distributed E2E messaging system is one of those things. Same goes for writing a fit-for-purpose C compiler. Doesn't make GCC or th

More ›