Perhaps the OP wrote incorrect figures due to this bug in the web site?
I haven't gotten very far with the design yet - it's pretty challenging to have an easy-to-learn phonetic spelling system that doesn't completely mangle either the spelling or the pronounciation of most of the source English words.
Anyway, because of the "network effects" problem, I think it's crucial to design a language that offers value to people even if no one else speaks the language. That's why I've been thinking about features like reliable automated translation (note that the language must be specifically designed to translate easily to a small number of specific other languages, in order to make accurate translation practical in a small open-source effort). Similarly, using English vocabulary is attractive if it means the language can be marketed as a stepping stone to learn English.
You know that there are many interlanguage designs already, right? Before designing a whole language from scratch, you should take some time to make sure that the kind of language you want hasn't already been designed, and in any case you should study what has been done before. (I've been meaning to do more of this myself!)
It's kind of weird that the link to 'Loren Chorley' is broken but anyway, I might like to join a group that is designing a language, in order to help keep the design software-friendly, to write programs to be used during the design process (e.g. a dictionary manager to help manage vocabulary and detect conflicts), and if all goes well, to write programs to help people learn the language (interactive lessons, syntax highlighter, grammar checker, etc.) You can find my email on the bottom of the front page of loyc.net.
Nuclear power has benefited from the near bottomless source of government funds that is called "dual use technology". [. .
.] They all pursued civilian nuclear power as a pretext for starting a nuclear weapons program. [. . .] that's why everyone assumes Iran is lying.
Yes, that's why everyone assumes Iran is lying, but I know Iran is lying for a different reason: because some of the best nuclear technologies ever conceived, such as the LFTR, do not require (significant quantities of) highly enriched uranium. If Iran wants a nuclear energy program, it would make perfect sense to choose one of the "non-proliferation" technologies. Why risk conflict with the U.S. by having a large enrichment program? Only one reason I can think of: they want the Bomb.
A main reason to use asm.js is that you need high performance, but running in a non-asm.js engine kills your performance. Granted, performance isn't the only reason to use it.
But with most web browsers auto-updating themselves, there's no need to restrict ourselves to only JS in the long run. Whatever is standardized, all browsers will support. As for human readability, that's definitely an advantage (for those that want it), but [binary] bytecode VMs can be decompiled to code that closely resembles the original source code, as tools like Reflector and ILSpy have proven for the CLR.
The disadvantages compared to a proper VM are several:
So as it is now, I feel that asm.js is kind of lame. However, it would make sense if there were a road map for turning asm.js into a powerful VM. This roadmap might look like this:
So what's the point of this being a "Web" language? Why not just keep downloading apps like we always have?
The advantage of "web" languages over OS-native languages is that "web" code runs on any operating system. That's a pretty big advantage from a developer's perspective! Plus, the web traditionally has built-in security features to minimize what script code can "get away with", a tradition that one hopes could continue with "offline" web apps.
But Google's NaCl has demonstrated that, in principle, any programming language could run inside a browser. So why not offer the advantages of "web languages" without actually mandating any specific language?
Some people believe that the web has become a kind of operating system, but I think this reflects more the way people want to use it rather than the technological reality. Right now a browser is sort of a gimpy operating system that supports only one language and one thread per page. Real OSs support any programming language. Why not the web browser?
But if you buy, say, a 35 Mbps broadband plan, your ISP will be required to deliver all content to you at at least that speed.
No, if you buy a 35 Mbps plan means that under no circumstances will you receive content faster than 35 Mbps. It's the maximum, not the minimum, and who doesn't know this? Boo "Brian Fung", technology writer for The Washington Post.
It's not physically possible to guarantee 35 Mbps transfer rates, since the theoretical maximum speed is always the speed at which the server can send out the data, which could be 35 Mbps or 1 Kbps. 35 Mbps would merely be the last-mile speed, with all kinds of unadvertised potential bottlenecks elsewhere in the network.
Net neutrality isn't about guaranteeing a minumum speed, it's about having ISPs do their job--providing approximately the service advertised by building enough capacity at both sides of their network, both at the homes and at the connections to other ISPs, backbones, and popular data sources. Without net neutrality, ISPs in a monopoly or duopoly situation have an incentive to neglect that other side of the network, to NOT build more capacity but just give existing capacity to those that pay.
"Trust me. I know what I'm doing." -- Sledge Hammer