convolvatron

when I'm working as an architect, my job is to put myself out of a job by teaching everyone to be an architect - for themselves and for each other. that admixture of high and low level concerns breeds really effective teams. with the side bonus that everyone has a chance to grow into larger responsibilities.

the internet corporations for names and numbers was established specifically to coordinate the for profit registrar model. but sure, an organization like that with a charter to simply manage the namespace directly.

angle grinders run really fast, and even those with speed control just lower total power, not increase torque.

it would have made more sense to just mount the motor and the planetary, but I think the planetary is important here.

I certainly wasn't nominating the US government. something more like international NGO. the us can do whatever it wants with the .us root, just like all the other ISO country code roots.

this is going to be an unpopular opinion, but this was the inevitable result of changing a function with trivial cost and broad social utility (name registration) from a public service to a commercial one. at the time we heard a lot of standard arguments about the innovation and competition that only a market based solution could bring. its really not a surprise that this is the kind of innovation that resulted.

No one thinks that there non-zero corruption in the Democratic Party. but we're at point where things like environmental policy, foreign relations, military alliances, tariffs, wars, and a whole bunch of actually important issues are being decided by how much Trump can extract from the arrangement.

Maybe they're just really good at hiding it, but I don't really remember a time under any administration when we could say something like 'as a country we're now supporting Russia and abandoning Ukraine and our traditional allies in Europe because they offer much better bribes'.

we should be going after corruption by anyone, its extremely corrosive. I don't understand why if that's a concern why we're supposed to be ok with turning it up to 11. Not only outright personal deal making, but the active replacement of foreign governments, state and local officials with people who know how to play that game properly.

What have you got to even begin to claim an equivalence here. Pelosi's stock trades? Biden's sleazy son?

if you didn't have a multi-user operating system running on every node that basically demands this, because of its complexity and fragility, and you had the necessary introspection to look at memory usage and open sockets, and disk bandwidth, and everything else you might need to mange those processes, then the utility of your escape hatch - which also is complicated and fragile, becomes negative.

not always. Asci-red had a distributed version of OSF/1. this wasn't a great design because it was built on distributed shared memory, so it had fault tolerance and performance problems. the MTA had a shared memory monolithic BSD, but that was almost a forced choice.

The Cray T3D had a really nice distributed services model (really kind of a distributed exokernel) that would be worth emulating

on some machines there was an interactive ganged run facility like 'mpirun'. I think even this distinction where there are 'login' or 'service' nodes and anonymous runners would be at least a little structure. I guess you could argue that k8s is this, but it kind of falls short and seems to require a lot of continuous propping up.

I worked on a single system image project that didn't ever get shipped. it turns out that a syscall proxy layer isn't that difficult to implement, and that leaves you with an undisturbed user space.

anyways, there are a whole host of design options that don't look like k8s or slurm. and having spent some time recently on non-hyperscaler clusters, that bottom level of bringup (provisioning, networking management, reporting, fault tolerance, distributed filesystems) is really a nightmare. I think we lost a lot of traction there by raising generations exclusively in someone else's operational context.

maybe we _should_ be thinking about building proper distributed operating systems instead of loose collections of services. we really missed an opportunity to rethink the OS interface for 'the cloud'. or rather we kind of wasted alot time and maybe we should get our shit together and do it properly. no matter how much we chant 'cattle not pets' everyone is still installing individual nodes and logging in and puttering around.

this question always comes up. I personally think the status quo is pretty weak here. I have certainly added a gdb stub to a unikernel before, but that apparently given that it was never used it wasn't the right answer.

people always talk about losing the excellent debugging facilities that linux gives you. if a service crashes in a big cloud environment what is that you do now that works so well. do you think its intractable to implement that in a single-process kernel?

you crossed a really big gap moving from 'communicate' to 'creating policy'. I certainly do not trust Google in particular to write any policies, given that their whole business model is to attempt to sit at the boundaries between consumers and companies, or email senders or recipients, or job seekers and hirers. not a fan of Schumer, but Schumer should be soliciting input from Google, who is free to submit a public white paper, and NIST, and DJB, and citizens groups, and everyone else that might have a stake in the outcome.

I lived in that world, sunos, solaris, unicos, hpux, aix, irix, ultrix. I always found it preferable to have Os and even compiler specific includes for a whatever definitions needs to be different. and I certainly wasn't interested in having a rewrite pass on the makefiles. but it worked well enough when I dug up something on archie.

and then they wrapped it another layer of translation, and then another and I think more. and things started breaking because I needed the right version of autotools, and at some point I started just running "cc *.c -I. -o foo" before even starting to try to use configure, and it usually worked and saved me a lot of screwing around.

its certainly settled down some, but only because everything is really linux. but still we're here more than 30 years later checking for socklen_t.

it was a always a bad plan.

and in what sense is it doing that at all? unlike the US, the signatories arent parachuting into other sovereign countries to effect their laws. they are enforcing their laws within their own borders.

for some reason that's offended the US, who then proceeds to extra-judiciously impose their will on citizens of other sovereign nations who aren't even in the US.

so who is coloring outside the lines here?

more importantly those abstractions were designed to try to make it easier to reason about what was going on for the author, build additional internal abstractions and to allow a reader to follow along and gain an understand of the structure. unless we believe that we can completely punt on having agency over the codebase, then llm code is only as valuable as it is readable.

this process of giving out your 'secrets' (ccn, exp, ccv, zip) to tens of people a day with no other real authentication is inexcusably insecure. and instead of trying to get on top of the problem for real (like an hsm), we have this very half-assed fraud detection and chargeback mechanism that costly, ineffective, and seems to just bury the real issues behind a facade of concern. its been decades that this has been going on, I remain confused as to what incentives the banks have to continue to prop up this farce.