It's a client/server architecture with an Open API spec at the boundary. You can tear off either side, put a proxy in the middle, whatever. Few hundred lines of diff weaponizes it.
Terminal scrolling opens a big can of worms for them, I doubt they'll ever implement it. The best you can do is enable scrollbars in opencode so you can quickly jump places.
> A couple months ago, I found that particular bridge was next to an office building inhabited by some of my old colleagues. A start-up I had been a part of in New York. Where I was the first employee. I had owned equity. They had eventually sold for $350 million.
It is depressing easy to have this happen and even worse how many people are convinced it could never be them.
For what it's worth: I know it could be me. I'm currently with tens of thousands of dollars in savings (in Europe, not American) but it could still be me. I'm quite afraid of it actually and I live every day so that it won't be me. I've noticed that reduces chances significantly, not to zero, but significantly.
As I understood the current state is "saving money and getting a little return would be OK", since he is still employed?
For sure, if the jo is lost in an expensive town, this money does not hold long.
What you describe sounds counter-intuitive. And the paper you cite seems to suggest an ISA extension to increase the number architected (!) registers. That is something very different. It makes most sense in VLIW architectures, like the ones described in the paper. Architectures like x86 do hardware register renaming (or similar techniques, there are several) to be able to exploit as much instruction level parallelism as possible. That is why I find you claim hard to believe. VLIW architectures traditionally provide huge register sets and make less use of transparent register renaming etc, that part is either explicit in the ISA or completely left to the compiler. These are very different animals than our good old x86...
reply