Yeah, every few years, a group of representatives meet and vote to continue it. So far, it hasn't gotten anyone voted out of office, so they see no reason to stop. Some polls show more Americans support surveillance than oppose it, so this is a losing battle.
Nobody makes a Linux MRI, because there are a bajillion support & certification requirements for software in something like an medical equipment. Which is why you can still find Win98 in brand new devices.
I honestly think you made that up. I don't think you have any clue what you are talking about.
The difference between Javascript and Webassembly, is that the some of the features of the Javascript language make it slow, even if it's JIT'd down to bytecode.
Harry Potter is just one example of many that shows studios can harass fans with copyright law and experience almost no repercussions. Look at the link from 2001......did that stop people from being fans? They even sued one guy, took his idea, and made a movie from it. Was the movie popular? Yes, it was.
Studios don't care about this kind of negative publicity. Fans stay fans.
My theory is, especially in the silicon industry, that Intel strongly encouraged manufacturers to use Windows. Before then, I think everyone was using DOS. I don't know before that.
Linux doesn't have good proprietary drivers and is useless at multimedia.
Linux has good open-source drivers, and is good at multimedia. When it comes to embedded, especially with something like an MRI machine, that's somewhat irrelevant since you'll be writing your own drivers anyway.
Let's be honest, though. If you use Windows on an MRI machine, you made a mistake (and having worked with WindowsCE in that era......I suggest that if you used WindowsCE you made a double mistake).
Webasm is of course not as “free” as asm, but Javascript does even more checks and other side work compared to C, making it slower.
The slowest thing in Javascript isn't about safety (arguably the opposite), it's that each variable access is actually a hash lookup. You can't really optimize that out (although you can make it faster to some degree).
Contrast that with WebAssembly which takes years to add features that clearly need to be there (like access to the DOM), because they know it's better to do it right than half-assed.
WebAssembly is a much safer interface than Javascript. The summary makes it sound like it's some kind of x86 code, but it's not. The fact that it is well thought out, and carefully designed to have a small attack surface means there is a smaller chance of finding exploits there.
So ideally, eventually all Javascript will be compiled to WebAssembly in the browser, and there will be no Javascript running on your machine at all.
Well, if people could fucking master the first three layers of OSI, the additional 4 afterwards wouldn't be a fucking requirement tacked on as an afterthought, and would be totally unnecessary.
ok, I think you have an interesting point here, but it's not really clear what you are saying. Could you please expand it a bit?
Of course you can. It's done by creating operating systems not full of swiss cheese escalation vulnerabilities and giving users meaningful access controls that never devolve into take it or leave it demands of software.
I want to point out that Linux is full of privilege escalation exploits (as is every other OS.....even OpenBSD only brags about remote exploits, not the local ones), so this isn't really an option right now.
His books are heavily influenced by Kafka, which is a problem because Kafka isn't very good. It got so bad, that I re-wrote the end of Metamorphosis for fun. Wasn't hard to make it better.
In one interview, Murakami mentions that once he was asked to write some book reviews for a literary magazine. He didn't want to do it, but finally he agreed (because he owed a favor to the editor). He was able to choose the book, so he ended up writing a book review about a book he completely made up, by an author who didn't exist.
Slashdot Mirror
I've never understood exactly how watson could be reasonably used in the healthcare industry. It seems like a toy to me.
There is no such thing as a "Linux driver". Linux doesn't have a stable kernel interface nor a binary interface of any kind.
Yeah......you shouldn't have posted drunk today.
Yeah, every few years, a group of representatives meet and vote to continue it. So far, it hasn't gotten anyone voted out of office, so they see no reason to stop. Some polls show more Americans support surveillance than oppose it, so this is a losing battle.
There is one item on the agenda:
"How do we get government to stop bothering us about privacy?"
A hammer is good at opening glass bottles, but that doesn't mean it's the right tool for the job
You so eloquently state why no one should ever use Windows.
I don't know that MRI machines are cheap in any aspect.......
Nobody makes a Linux MRI, because there are a bajillion support & certification requirements for software in something like an medical equipment. Which is why you can still find Win98 in brand new devices.
I honestly think you made that up. I don't think you have any clue what you are talking about.
The difference between Javascript and Webassembly, is that the some of the features of the Javascript language make it slow, even if it's JIT'd down to bytecode.
Harry Potter is just one example of many that shows studios can harass fans with copyright law and experience almost no repercussions. Look at the link from 2001......did that stop people from being fans? They even sued one guy, took his idea, and made a movie from it. Was the movie popular? Yes, it was.
Studios don't care about this kind of negative publicity. Fans stay fans.
"Lets download and run executable automatically from the net! What could go wrong?"
This is not any different than Javascript.
I was referring to the MRI vendor. They made a mistake designing the thing.
Webassembly is binary bytecode. It's something different.
What you describe is indeed asm.js, but that's not Webassembly.
My theory is, especially in the silicon industry, that Intel strongly encouraged manufacturers to use Windows. Before then, I think everyone was using DOS. I don't know before that.
Who else has done it?
Linux doesn't have good proprietary drivers and is useless at multimedia.
Linux has good open-source drivers, and is good at multimedia. When it comes to embedded, especially with something like an MRI machine, that's somewhat irrelevant since you'll be writing your own drivers anyway.
Bruce Wayne actually is a snowflake: there's no one like him.
Much of the hardware machinery, such as mechanical drives and fans, should've stopped working by now.
That's unlikely.
Face it, Windows 7 is on it's death bed, and if you do not like it, go Linux or go home. :)
Good plan.
Let's be honest, though. If you use Windows on an MRI machine, you made a mistake (and having worked with WindowsCE in that era......I suggest that if you used WindowsCE you made a double mistake).
Webasm is of course not as “free” as asm, but Javascript does even more checks and other side work compared to C, making it slower.
The slowest thing in Javascript isn't about safety (arguably the opposite), it's that each variable access is actually a hash lookup. You can't really optimize that out (although you can make it faster to some degree).
I'm sure the systemd developers had those thoughts too when they started out. :-)
No, they didn't. You can see the documentation and ideas that were floating when systemd started. The concept is all about features, lots of them, and security is mainly mentioned as something the kernel will do. Minimalism isn't on the menu.
Contrast that with WebAssembly which takes years to add features that clearly need to be there (like access to the DOM), because they know it's better to do it right than half-assed.
WebAssembly is a much safer interface than Javascript. The summary makes it sound like it's some kind of x86 code, but it's not. The fact that it is well thought out, and carefully designed to have a small attack surface means there is a smaller chance of finding exploits there.
So ideally, eventually all Javascript will be compiled to WebAssembly in the browser, and there will be no Javascript running on your machine at all.
Well, if people could fucking master the first three layers of OSI, the additional 4 afterwards wouldn't be a fucking requirement tacked on as an afterthought, and would be totally unnecessary.
ok, I think you have an interesting point here, but it's not really clear what you are saying. Could you please expand it a bit?
Of course you can. It's done by creating operating systems not full of swiss cheese escalation vulnerabilities and giving users meaningful access controls that never devolve into take it or leave it demands of software.
I want to point out that Linux is full of privilege escalation exploits (as is every other OS.....even OpenBSD only brags about remote exploits, not the local ones), so this isn't really an option right now.
His books are heavily influenced by Kafka, which is a problem because Kafka isn't very good. It got so bad, that I re-wrote the end of Metamorphosis for fun. Wasn't hard to make it better.
In one interview, Murakami mentions that once he was asked to write some book reviews for a literary magazine. He didn't want to do it, but finally he agreed (because he owed a favor to the editor). He was able to choose the book, so he ended up writing a book review about a book he completely made up, by an author who didn't exist.