So you can guarantee being able to break out of the VM
Now where did I say that? What's with the lies over something so trivial?
I wrote what I wrote and not what the strawman in your head is up to.
This is a very old and well understood problem ( http://www.csl.sri.com/users/r... ) and I suggest you learn about the implications instead of frothing at the mouth in denial.
When the VM has been designed without security in mind and with hooks deep into the host at the kernel driver level without separation then an exploit of the VM software can escalate to the host. You don't have to trust me on this - learn about the topic and you'll be able to see that much yourself.
It's not -just- going by the book
Indeed - success was from a lot more than "the workers consistently follow the specified procedure".
The cultural differences that you are crediting are neither so simple or even something that originally came from Asia.
The differences today really come down to a changed idea of who can be a manager and how to do it - the irony of the "born to rule" attitude infesting US management would be funny if it wasn't so tragic. Henry Ford and Thomas Edison were not born to rule.
You live in a silly small country that hopefully soon will drift into insignificance
I live in a very large country that is already insignificant but has not dropped the ball on education as badly as the United States of America has. A few decades ago I believe it educated it's engineers well, so that even if I was the least of them I can at least deal with simple stuff as this.
I suggest watching some videos of buildings in real disasters to cure yourself of this very sick little conspiracy theory.
The tiny bit of difference in earth rotation speed from top of a sky scraper to its base is _hughe_
WTF - do the mathematics yourself instead of taking the word of whatever nut fooled you- it's ignorable. You may be a coder and not an engineer but you can work this out and shake the bullshit out of your head.
Actually if it is hardened it can certainly help
The point is these things have been designed without security in mind, they have been designed for a completely different purpose, so they can't be described as "hardened", not even the catchup game years after design with your example.
So yes, a virtual machine providers security benefits
Not really, and effectively zero if it exploits a bug in the VM. The point is these things have been designed without security in mind, they have been designed for a completely different purpose, so they can't ve described as "hardened" - not even the pathetic security catchup game being played with Hyper-V.
Am I the only one who read "Asian" as a politically correct version of "Indian" in this story?
The funny thing is that an American wrote "the book"
That's kind of my point.
It's not an "Asian cultural thing" but instead a good idea.
Not a great comparison, the 10 gig switch is mostly SFP ports which are only useful for short run twinax or with fiber optic SFP modules for anything beyond twinax lengths. 10g copper SFP modules don't exist. Useful in a rack with servers with SFP NICs or if you want to fuck around with fiber, but in my mind that rates them as less useful than base-T which has much simpler and cheaper cabling demands.
I see a lot of twinax/optical deployments as converged core server + iSCSI storage but mostly in new cluster deployments where the expectation is everything is new and there's a few fiber handoffs or for core network deployments in larger networks.
But the most useful is always the base-T version because it drops in easily and handles pre-existing equipment with only 1g copper connections.
To be slightly fair with switch vendors, there is something complex about 10g-baset PHYs which makes them more expensive, but not THIS expensive for this long.
I still think IEEE messed up by not rolling variable (2.5/5/10) link speed into the 10g-base-t standard up front. It would have driven switches with broader footprints and driven more adoption by giving full speed where the cabling was good and 2-5x speed where cabling was just OK. More adoption, more unit volume and lower prices.
Well would you look at that indeed! I argued for a loss of 348-282=66 sec in Merlin, and said that Raptor would be somewhat less of a difference but not much, as "chamber pressure has a positive but fairly weak correlation with ISP". You said 384 - "360-370" = 14-24 sec difference.
And the reality is... drumroll... the envelope please...
384-334 = 50 sec
I hope this has been a learning experience for you.
The longer the title, the less important the job.