I talk all nonsense - when i am techie guy...
when my sensei is now a cxo guy who specializes in gCloud architecture..
what is a good architecture
- if you design a cluster? eg Kubernetes
would the baldie.exe run kube-controller-manager on a 386?
with worker nodes running dobbie.exe on a hex core ryzen?
infra guys - should make good choices...
this is not so googley - even by cto standards...
cant even riddle me this g_baldie_1?
heat?
cooling fans?
thermal cooling?
or liquid cooling?
doesnt matter - 386 is obsolete
but virtualization surely works. 🤣
automated import. If something looks out of place, check the orig linkedin post
After Thoughts
Thoth:#1
It is just the art taught by sensei - a nerdier/boring version of "satsui no hado" aka domination by raw power of any kinds
this art - can have only 1 master - just like SF..
Akuma had to clash with Gotetsu - his sensei, to carry a tradition which comes with the 'art'/field
sure it looks boring here...but imagine a geek version of 'mightest - test of might kinds'
similar to this ...though i feel gotetsu is happy - seeing his 'pupil' overtake him - a true sensei!!
Thoth:#2
i need to "java it down" - 0raklie levels
386 - ya mind
baldie.exe - ya algos
interrupts - signals generated by paw.exe
...
if anyone was ever even 1/2 an engineer - ever, would understand the signals - are causing a wave of sorts - in all pappu.exe and now rebel.exe
the runtime - aint a sandbox of goraklie g enius anymore...
Brand baby - the stripes which 1 likies - the title, along with 'a huge stack' - 386 cant compete that in secs - but years...
years - next life - maybe baldie.exe can cope up - wishful delusions with veronicas - cheers baojee 😍
Thoth:#3
WINE - "Whining Is Not an Emulation" - doesnt give u superpowers
doesnt give klass
it is an emulator - works well with older baldie.exe environments - like win95, 98 - and other klassy products of baldie gen
these nodes dont run docker or other container environs...
just too much 'wish' and 'whine'