soulbadguy

> Meanwhile, consider a 3x3 object. That's 192x192 = 36,864 pixels. Assume it has a 60 fps, 2-second animation loop. That's 4,423,680 pixels. With 8 bytes per channel and 4 channels (RGBA), that's about 17.7 MB, which allows you to store 56 objects per GB.

I am assuming that they are laveraging multiple compression technics like using texture specific compression on the gpu, or sub sampling the resolution directly. 8 bytes per channel seems rather large here as well.

Since we have a couple of tailscale employee here :

It would be nice to have an easy way to define a multi node proxy. Right now i have several devices in my network which i can't install tailnet directly on. For each, i have to create a seperate container for each (since i tailscale node can't share network namespaces).

That was my thinking as well. I got the unify fiber gateway specifically for unify teleport and vpn integration.

I find tailscale to be simpler, more reliable and cover my needs better. I am pretty sure that have i known about tailscale before, i wouldn't have got the unify gateway.

I still love my unify though, dashboard galore

> A device can advertise subnets, and can route them through tailscale

This is still L3 layer though. One the main use case of L2 is proper DHCP propagation and avoid subnet collisions. I do not think that this matters in practices though. Only a limited amount of user facing service require proper L2 emulation (apple TVs ?)

> Glazing as a service is a hell of a drug.

You my friend made my day.

> like add jj workspace support

care to share a pr :)

> You're getting confused between lifetimes (the static analysis that prevents use after free and similar errors) and lifecycles (more commonly discussed under the heading of ownership) which determines when objects (and thus memory) are allocated and deallocated. Ownership is

That's a semantic distinction which does not matter in the point OP is making. And contrasting rust static approach to general GC.

Is the information actionable ?

I felt the same for a while after switching to jj. I think using the word "commit" in jj is creating a lot of confusing. The snapshotting is closer to auto-save in your favorite editor. In does not change your ability to version and save your work. It's just a savety net for quick undo

Additional complexity ? jj just increase the frequency of snapshots. it does not fundamentality the complexity of the system

> This is meant to be mitigating? What is this thought process? Who in their right mind is like "okay, a group of people broke into your home at night but your state shouldn't have been so hard on them for what ensued because akshually it was part of a whole nationwide trend at the time."

You analogy doesn't not hold, and in manyways point at the root of the issue. The point was to show that harsher punishment did not seems to result in meaningful effect on crime stats. It's fine to want harsher sentencing for some kind of emotional fuffilement, let's just not pretend that is helping in any otherways.

> focusing on punishment rather than rehabilitation.

punishment is a prerequisit to rehabilitation

> Whereas someone who has committed 30 petty thefts and then gets arrested, locked in a cage, and guarded by armed agents of the state, is extremely unlikely to commit another theft as long as he remains locked in the cage.

How does that help, if after incarceration that person become a much hardened criminal both because of the lack meaning pathway to integration, and you know spending years locked up with the worst of society.

> but we don't really have a good understanding of what specific people can and cannot be rehabilitated, or how to go about actually effectively doing the rehabilitation.

Then let's work on that.