Comment Re:Problem with proprietary 'free' offerings (Score 1) 174
Yep I want to stop for the night at 7 pm where are the hotels you can stay at and here are some places to eat...
Yep I want to stop for the night at 7 pm where are the hotels you can stay at and here are some places to eat...
One word.
Debugger.
Compilers are actually easy to come by today. Debugging is where you run into issues.
Mobile, Routers, NAS, and now servers. ARM is getting very big very quickly.
In computers Attacks come from the bottom up. PC where a joke and could not hold a candle to a real computer like a PDP-11! Forget about mainframes like the 370!
It was not HURD at the time but GNU Unix that was going to be the next big thing.
It wasn't but hey no one is perfect.
X86 has gone away. Everyone is using X86-64 and Arm. I would be more Unix like systems are ARM than X86 or X86-64.. So is AMD64 X86-64 orX86/64? I can never remember.
Except he was right in 1992.
He just underestimated the growth in speed and power of a PC. On a 386 with 4 megs of memory and a single slow hard drive he was right.
It'll make great post-apocalyptic architecture.
This reminded me of the domes in Ergo Proxy.
Will this one be called "Mosque?"
Simple native development can be a lot easier than cross development.
If you have the money for some really good embedded tools, cross development is not bad at all. But if not native development is a lot simpler.
I would still do most of my work on an X86 Linux box and then move the project over to the embedded for testing but that is just me.
That's pretty bad, although it's not that unusual for them to have terribly high standby draws like that. On the majority of them, there is a tangible difference in energy use though (as in you can touch them and feel the heat difference).
To repeat myself: there is no single "ordinary SQL." SQL standardization has gone through many iterations: SQL-86, SQL-89, SQL-92, SQL:1999, SQL:2003, SQL:2006, SQL:2008, SQL:2011. The SQL standard is presently maintained by ISO/IEC JTC 1. Your original statement was "SQL certainly is not turing complete," and that is a false statement. Under the ISO standards, it is absolutely possible to create a Turing machine with SQL. Examples have been provided, including (but not limited to) one written "entirely in SQL:2008-conformant SQL." The degree to which any given database engine may adhere to ISO standards may vary, but by adhering to said standards, there exist code examples which demonstrate Turing completeness. You're only insulting yourself by continuing to refuse to accept reality, but if you're still in doubt, per the previously supplied references you're welcome to purchase SQL standards documents from ISO, IEC or ANSI.
With computers it's better yet to use a phone or tablet instead of opening a laptop.
A big one is to turn your cable box off when you're not using it. Ever notice how bloody hot most of them get? It's because they're horrendous power guzzlers. People who aren't nerdy enough to program universal remotes properly just turn off the TV itself when walking away, leaving the cable box to run like a little electric space heater.
I'd drive a cheap-to-run car with torque like a supercharged V8 and my electricity would come from sources that put out their radioactive waste in neat chunks instead of slowly spreading it out the top of a smokestack!? This awful socialist future is going to ruin us all!!!
...unless you're good looking enough to make a career out of it.
They might take that as a challenge. North Carolina made global warming illegal after all.
I agree, it seems pretty close to that. Any lawyers want to comment? This could be entertaining
Numeric stability is probably not all that important when you're guessing.