197,147 karma · joined March 12, 2008
email: username at that google mail thing
http://about.me/rbanffy
https://linkedin.com/in/ricardobanffy
[ my public key: https://keybase.io/rbanffy; my proof: https://keybase.io/rbanffy/sigs/HtF1uAf_RNpwIkNP1-YGWP_-3doWV6S5Cc1KywXeLYo ]
I get the frustration, that it’d be nice of commercial entities that use our software to do more to support its development and maintenance, but that’s not in the license. A good project will create a healthy ecosystem with sufficient voluntary influx of resources. If it doesn’t, then maybe it’s no longer healthy or viable.
There will be a time things like Python, FreeBSD, Linux, MySQL, and so many others we know and love, will have been surpassed by new successors better adapted to that time. We’ll cherish their memory, remind everyone of their role in taking us to that future, and move on.
If the CEO is indeed insane and incapable of fulfilling his duties, and he still controls 84% of the voting shares, all options are nuclear.
That said, why do we think compilers produce correct code?
This is pretty impressive.
Server side rendering makes sense for mostly static content, but for web applications, a front end framework and a back-end API are a much better match.
If you don’t build the product that’ll kill your cash cow, your competitors will.
There is an issue with this idea - we write software, we read it, we make sure it does what it should do, that it’s implement in a sensible and efficient way, and, most importantly, we make sure the tests do what they should do.
If you no longer write the code, it’s harder to understand it. If you don’t write the tests, you need to trust the LLM did both jobs correctly (multiple adversarial LLMs can help), but, ultimately, it’s code you can no longer claim you understand. And you can’t really be sure it does what you want until you understand it.
This is one of the reasons IBM introduced an AI accelerator and added specific instructions to use it on their Telum II processor - so that limited inference can run in-process in transaction processing with latencies measured in clock cycles.
I think these instructions are for the case where inference is a minor part of the time it takes to process some data on that server - in that case the server will be more effective by having more, faster memory than having to go across a PCIe but to a GPU that will be idling most of the time, or going over the network to a dedicated system.
Compatibility was their greatest weakness and, at the same time, their greatest strength. It allowed the Cambrian explosion of the 70s and 80s personal computers, each with their own superpowers.
Currently I’m looking for a VT-330 or some other terminal with Tektronix graphics. These seem like unobtanium this side of the Atlantic.
So, if someone has a Rainbow, Z-100, AT&T Unix PC, 3278 terminal, or anything like that, I’m rescue stray computers.
https://rbanffy.github.io/fun-with-big-computers/fun-with-vm...
BTW, I have updated the container images for VM/370 Sixpack and VM/370 CE today.
Years later, the machine was still chugging around on top of that floor's networking rack. Someone added a PostIt with "Do not turn this off".
But I have to say OpenVZ didn't do all the tricks one could do with Zones, and Zones combined with Crossbow, were able to test a huge number of networking scenarios to see how things would break.
They were always a hardware provider. If they could have offered credible desktops at PC prices, they could have made a serious dent in the low-end server (one step up from desktops), which is an essential stepping stone for securing midrange and above.