State of the Game

tbh, I don't have any complaints about Brizzle mate... :)
I didn't when I lived there - but it changed much over the years and even visiting my parents up until a few years back the place felt pretty alien to me. I guess it is just the way we change - going into the middle of the city from 'home' on the Suffolk / Norfolk border, then from the Valleys when I moved to Wales after my dad died... I think being used to clean air was the major issue!
 
I only remember from using some Unix/Linux/whaever system while studying IT, that there are two things you should not do intoxicated: recompile kernel and change root password.
The next level of fun like this is then figuring out how much you can strip down your linux kernel whilst still being able to run a java VM on it - or any VM actually - once infected with this idea to minimize the kernel and put a VM on top of it, one might get infected with the creation of own VMs for all kind of specific purposes- and of course one will again fiddle with the linux kernel - this is somewhat addictive so be careful trying.
 
I didn't when I lived there - but it changed much over the years and even visiting my parents up until a few years back the place felt pretty alien to me. I guess it is just the way we change - going into the middle of the city from 'home' on the Suffolk / Norfolk border, then from the Valleys when I moved to Wales after my dad died... I think being used to clean air was the major issue!
Someone, I forget who, said we can never go home again, and my understanding is that it boils down to how both we and places change over time and that we and those places are no longer the same as they are in our memories anyway.
 
it's a shame the razr has such deep design flaws because it looks great and the hinge is great and the screen is great (for a foldable)... But the wifi antennas are garbage, the outside screen is fragile and easily broken, is too heavy and glassy so it slides off literally anything not absolutely level, and the firmware on the phone is made by motorola/lenovo so it's horribly out of date all the time.

almost makes me want a flip3... but the flip 3 still looks like you'd have to use two hands to open it all the time and you'd still need to open it all the time to do nearly anything.
 
it's a shame the razr has such deep design flaws because it looks great and the hinge is great and the screen is great (for a foldable)... But the wifi antennas are garbage, the outside screen is fragile and easily broken, is too heavy and glassy so it slides off literally anything not absolutely level, and the firmware on the phone is made by motorola/lenovo so it's horribly out of date all the time.

almost makes me want a flip3... but the flip 3 still looks like you'd have to use two hands to open it all the time and you'd still need to open it all the time to do nearly anything.
Yeah, star trek communicators never had video.
 
The next level of fun like this is then figuring out how much you can strip down your linux kernel whilst still being able to run a java VM on it - or any VM actually - once infected with this idea to minimize the kernel and put a VM on top of it, one might get infected with the creation of own VMs for all kind of specific purposes- and of course one will again fiddle with the linux kernel - this is somewhat addictive so be careful trying.
I concur, VMs are awesome and extremely useful.
 
I concur, VMs are awesome and extremely useful.
We needed something what breaks most of the commonly used programming paradigms while making parallel programming at the same time that simple, that nearly all common problems like avoiding race conditions, creating and managing threads and thread groups, acquiring and releasing locks and so on are done by the VM and it can be nearly as easily coded as a single task program.

Furthermore we needed compile time binding, runtime binding (once or every time), runtime compilation, runtime repurposing of routines, operators, interfaces, you name it. Furthermore allow for compile time compilation of circular references, where the final or temporary binding is postponed to runtime and the actual code might not yet exist at compile time. This all is somewhat required for programs, which can learn how to learn by themselves and change during runtime, while still offering consistency of code which is currently running on parallel tasks, but can change for all other tasks. The whole thing of course highly fault tolerant whilst at the same time not being tolerant to faulty tasks -those simply die and will be replaced - those problems we deal with allow for that, so why deal with exceptions and handle them, if we can just kill the task and replace it? (this is actually what nature does in it's highly parallel machines - faulty cells will most of the time mark themselves for removal and will be dissolved and replaced by others).

So we created a VM which can do that - a byte-code VM with 64 machine instructions and 192 short-cuts for often used numbers. A lot of those machine codes perform tasks which are common in complex adaptive systems and just take a single instruction - like "perform fitness test on stack for those 3 candidates following on stack and leave the 2 winners and their offspring on stack" - that is a 1-byte instruction - that is why VMs are that awesome, one can do incredible stuff with those quite compact.
 
Last edited:
Back
Top Bottom