- Deal with legacy code from day one.

- Have mess of a codebase that is most likely 10-20x the amount of LOC compared to human code

- Have your program be really slow and filled with bugs and edge cases.

This is the battlefield for programmers. You either just build the damn thing or fix bugs for the next decade.

What's your point?

Maybe then we just go back to an oldschool text based way of communicating.

No google. No socials. Just text.

Do you know what the letters in LLM mean?

If we dont have any of the above the propaganda or AI slop is just not worth it.

This is why having small focused MODERATED communities is the only viable future.

- Silently closes the tab, and makes a remark to avoid given software at any cost.

That said, the bravest we have are asking that they please not be murdered. And then peacefully kneeling down to be executed, even when they are armed.

Obviously this only emboldens the murderers. The options moving forward look bleak.

The best thing to do is to be out there recording everything. You are right that they are emboldened, so you're putting yourself in danger by filming. When people continue to do that despite the danger, and despite the internal or external pressure to escalate, it shows more people what's really happening.

I've witnessed people change their position on ICE's actions based on the video evidence of the last killing. Videos 1 and 2 weren't convincing to them, but the 3rd angle was. That's important, because they now know that the administration is lying in the face of directly contradicting evidence.

I don't understand how that will be meaningfully different from what is happening already?

FWIW I do think things might be different later but there’s still a lot of room for escalation left

Do yourself a favor and sit this one out while the rest of us fix it.

We have a fascist President, yes. We will see if this means we have a fascist government within the next decade.

The "its only bits" thing makes no sense in the world of types. In the end its machine code, that humans never (in practice) write or read.

Within a single computer that’s easy because a single computer is generally well behaved and you’re not going to lose data and so yeah your type assumptions hold.

When you add distribution you cannot make as many assumptions, and as such you encode that into the type with a bunch of optionals. Once you have gotten everything into optionals, you’re effectively doing the same checks you’d be doing with a dynamic language everywhere anyway.

I feel like at that point, the types stop buying you very much, and your code doesn’t end up looking or acting significantly different than the equivalent dynamic code, and at that point I feel like the types are just noise.

I like HM type systems, I have written many applications in Haskell and Rust and F#, so it’s not like I think type systems are bad in general or anything. I just don’t think HM type systems encode this kind of uncertainty nicely.

You absolutely can make all assumptions relevant to the handling/dispatching logic expressed at type-level.

> and as such you encode that into the type with a bunch of optionals.

Not necessarily, it can be `Alternative f` of non-optional compound types that define the further actions downstream.

> Once you have gotten everything into optionals, you’re effectively doing the same checks you’d be doing with a dynamic language everywhere anyway.

Not true, your business logic can be dispatched based on a single pattern comparison of the result of the `Alternative f`.

With JS i kind of get it as you cant control the env. Bit PHP does not have this limitation, and they still cant fix the mess that is PHP.