underneath

It still uses SQL underneath, but limits what you can do with it. Let's talk schemas.

Then, I programmed the mill to trace out the contour of the leg while the lathe spun the wood underneath the mill head. ...

I can tell there's content underneath but screw that, I'm not reading it after that.

Other steps send me hurrying back underneath the ground. Yours will call me, like music, out of my burrow.

You can write code that looks like pain old procedural code but underneath there's magic that uses userspace task switching whenever something would block. Sounds great.

There was some interesting math going on underneath. Modern radars sample at 50 MHz, giving a 3m inter-sample distance.

If you are used to firefox, thunderbird and libreoffice, to many users it doesn't matter much if it's windows or linux underneath.

There seems underneath to be no reason to believe that there are results like this. If they were random then there might be numbers that cannot be expressed as the sum of 3 primes, but somehow every number ends up so expressible.

Suffice to say, most hardware does not support DSA, and underneath, it's all texture units, even in Direct3D, so railing against texture units is a complete red herring. #Many ways to do the same thing: Again many factual errors.

It also reminds us that solving what is on the surface a simple problem lets one uncover all sorts of interesting and messy details underneath - including more problems to solve! These are steps that he'd have to take no matter what the code or feature.

I'd be overjoyed if there was a solid crypto system underneath an OpenSSL compatible API that gives us a path towards an open source, reusable crypto platform.

You've got libraries changing underneath you in incompatible ways, so you've got to support both versions of the library, or even ship your own build of the library. You've got any number of different desktop environments, which makes integration with the native environment hard.

Of course somebody is going to chip in here and say that if the above is happening then you are writing your tests at the wrong level of abstraction and that you should be testing at the point where you can create a stable API that remains unchanged while you throw away the speculative implementations underneath. But if you are tacking a new problem you have no idea where those boundaries lie.

He was able to greatly slow, but not stop, the emergence of an OS-independent Web, because he controlled the majority of the OS market underneath it. But then the second shoe dropped. Mobile came along and MS was not able to stop its explosive growth. The growth of mobile made MS just another minority OS underneath the Web, and they lost their ability to disrupt the standardization of the Web platform.

I am mostly for the ostensible cleaning up of YouTube comments, but what got me was that any time you share a YouTube video on Google+ proper or comment in a thread where someone shared a YouTube video, it automatically cross-posts what you said back to the comments underneath the video on YouTube. And that's not just for shares/comments going forward: it's everything you've ever shared publicly, ever.

So, we're going to have rods, and disks, and rods are going to have the number of disks on them, and disks are going to have size, and probably a reference to the disk underneath, and a reference to the disk on top, and maybe also weight and color... and by the end of the day instead of a 10-line snippet [2] we're going to have Enterprise Java Beans.