Well, that's true, too.
Well, that's true, too.
My understanding is that the most common use case for both NaCl and ASM.js is to write your code in, of all things, C.
The point of C is that it's fast as hell and gives you almost complete control.
No, assembly language is fast as hell and gives you complete control. The point of C is that it gives you almost as much control but makes it easier to build and maintain large systems without you being some kind of semirobotic idiot savant. In other words, C IS a "dumbed down" language, just like some of the other ones people are complaining about.
The best approach, therefore, is to build a compiler back-end that targets *both* ASM.js *and* (P)NaCl.
Or just compile your code twice, using two different back ends? I don't see much wisdom in building a compiler that tries to do two things at once.
Is the word "platform" officially over? My fucking toaster is a bread-browning platform.
LLVM are only getting funding because Apple wants to undermine GCC.
What on Earth would Apple gain by undermining GCC? I guess it would benefit Apple's buddy Intel, but Intel's compilers are already superior to GCC on its own chips, so I don't imagine it's too bothered.
Yes, this is exactly the issue. GPL isn't "more free" than BSD. Quite the opposite. GPL is far less free as it grants the users less freedoms.
The BSD approach is "Here is something nice I made - have it and do what you like, hope you have fun!"
The GPL approach is "Here is something nice I made - you can use it, but if you you have to let me play with you stuff. I don't care that your thing might be vastly better or more complicated than mine, if you're using my stuff you sure better make sure I can use everything you make."
I think you've mischaracterized the GPL approach. By using the personal pronoun, you make it sounds like the GPL forces people who make derivative works to do things for the original developer. That's not the intent at all. The intent is to make sure that people who make derivative works do things for everyone – meaning everyone collectively, not individually. GPL grants users lots and lots of freedoms; the one freedom it does not grant is the freedom for you to withhold from others the freedoms that you yourself enjoy. BSD does grant you that freedom.
What is with all the HAL©, HAL(Circle-C) nonsense in the submission? Is that supposed to be some kind of joke? Looking at the website, the company doesn't style the product name that way. Is it supposed to be some sort of winking reference to copyright (hurrr, hurrr)? Because that doesn't make any sense...
It is not random. If you have enough knowledge and the ability to comprehend that knowledge, you can predict what will happen. Nothing is random.
Sure, as long as you start a program and let it run all by itself without touching anything. As soon as you introduce human input, the system may still be deterministic, but the output of the program is in effect random because the behavior of the operator cannot be predicted. The kind of "knowledge and the ability to comprehend that knowledge" that you describe is known as omniscience, and most IDEs currently don't support it.
40 here, birthday's in March.
A really common one is simply, "I feel fine. I feel better than I have in years, and I've felt this way for months." That's when people really start looking at side effects with a critical eye ("it makes me foggy") and decide they can go it on their own. And often it's insidious; if someone is manic, for instance, at what point do family members step in and say "you're not doing as well as you think you are"? If you're skipping your treatment, you're probably not getting the feedback you need to properly evaluate where you're at.
This is kind of an old-fashioned argument. Modern VMs are often essentially executing native code by the time the code is actually running. If the bulk of the overhead happens at launch time, or a JIT compiler only has to step in every so often, the level of performance can be such that the difference from "pure" native code is insignificant for most applications. Don't mistake a modern VM for a 1980s style Basic interpreter. The two are very different beasts.
I think ASM.JS is dead out of the water as Google refuses to support it.
No, that's not true. You maybe have things backwards. Mozilla refuses to support NaCl, which is Google's similar-goal-different-approach technology.
There is never time to do it right, but always time to do it over.