Comment Re:Great news! (Score 2) 267
Comment Re:its a white dragon. (Score 1) 414
Comment Re:I wouldn't work there. (Score 1) 392
Comment Re:It's Hillary time! (Score 2, Insightful) 271
Comment Re:The entire premise is pure BS (Score 1) 294
Sexism is alive and well, and definitely impacts who is considered 'most competent' in the hiring process. I think
Submission + - Wikipedia Founder Jimmy Wales Ridicules Government Plans To Ban Encryption 1
The Wikipedia founder said any attempt would be "a moronic, very stupid thing to do" and predicted all major web traffic would be encrypted soon.
Wikipedia itself has moved towards SSL encryption so all of its users' browsing habits cannot be spied on by intelligence agencies or governments.
Indeed, he said the efforts by the likes of the NSA and GCHQ to spy on individuals have actually made it harder to implement mass-surveillance programs because of the public backlash against Edward Snowden's revelations and increased awareness of privacy.
Wales also reiterated that his site would never co-operate with the Chinese government on the censorship of Wikipedia.
"We’ve taken a strong stand that access to knowledge is a principle human right," he said.
Comment Re: illegal autonomous cars? (Score 1) 398
Comment Re:Elaborate click bait advertisement? (Score 4, Funny) 58
How do you test software?
uh...
Comment Re:For starters... (Score 2) 842
Comment Re:For starters... (Score 1) 842
Comment Re:HP/MPE had a hierarchical database, too (Score 1) 166
For Kaiser, they set up logical geographic nodes and built their own sync system to update the network of nodes on demand.
Comment Re:MUMPS is nothing special (Score 1) 166
In safety-critical systems where invalid data could kill someone, using a typeless, schema-less system with nonstandard language conventions as a starting point seems irresponsible. Why not start with a normalized relational database and a language designed to encapsulate and protect data from inadvertent data-entry or programming errors?
Because performance. Yes, Epic had to put extra work in to essentially build their own version of the SQL server black box, but now they are very difficult to compete with.
Epic doesn't use the Cache SQL API. Instead, they built an API on top of objectscript that stores fields safely. They have a staggering amount of code written in objectscript, and while it's true that "nothing will stop you" from writing directly to the underlying data oddly enough that doesn't seem to be an issue because developers can learn how to follow best practices.
Comment Re:HP/MPE had a hierarchical database, too (Score 1) 166
There is nothing a hierarchical database can do that relational databases don't do better.
That's rather absolute. It seems performance is an area that hierarchical can be better, at least in certain use cases:
http://www.intersystems.com/assets/datamart_wp-ee478edf530b40311ef506615c0da74d.pdf
Conclusion
In tests simulating a data analysis application typical for a telecommunications software
firm, Caché was 41% faster than Oracle when creating a data mart of mobile
phone information. When the resulting data mart was queried using SQL, Caché’s
response times ranged from 1.8 to 513 times faster. Clearly, Caché’s unique multidimensional
data engine make it a good choice for applications that require rapid
analysis of large amounts of data.
Comment Re:MUMPS was designed for a different world (Score 1) 166
As a computer scientist, I was appalled by certain features of the language, particularly the ability to change a running program by executing a variable. That's a security nightmare, since you could effectively read a string (stored as a global or input from the console) and then execute it as MUMPS code.
Do you spend a lot of time being appalled? Many languages have this capability, including SQL and the C variants.