And the Web SQL initiative failed, for just this reason; SQL itself does not define enough to write portable SQL, so they just had to say "well, SQL as implemented by SQLite as of this particular version", and that was pretty much a non-starter. Web SQL had even got a little more buy in from multiple vendors (Safari, Chrome, and Opera), but due to the problems with it Mozilla and Microsoft refused to implement it.
The same is likely to happen to PNaCL. It will probably survive for a while in Chrome, as it may be useful for writing ChomeOS specific apps, but it will never be adopted by any of the other browser vendors. ASM.js runs just fine in other browsers, the only difference is that they don't implement the stricter subset and same optimizations as Firefox does, so it's a lot more likely to catch on, as people can write cross-platform ASM.js right now.
Correction: you can write cross-platform PNaCl code; there's a project called pepper.js that compiles the PNaCl application using emscripten. To quote the GitHub README: "Native Pepper applications can now be run in Chrome, Firefox, Internet Explorer, Safari, and more."
This leaves them in roughly the same place; write code that will be heavily optimized for one of the browsers, then include a compatibility layer that will make it runnable in all of the others. Without making an argument as to which underlying approach is better, I see no clear upper-hand from the perspective of compatibility.
What somebody needs to do now is define another language that compiles to both PNaCl and asm.js-suitable languages, and offer a deployment mechanism that correctly uses one or the other when in a browser-optimizable situation. Nothing beats too many standards like adding another standard to unify them. ;)
Yeah, and you can also run Linux in a browser and run Chrome within that and then everything will be portable everywhere. Except, well, for performance.
One of the big differences between ASM.js an PNaCl is that ASM.js just exposes ordinary standardized Web APIs, while PNaCl gives you the Pepper API, which is basically an entirely Chrome specific API. That means that rather than just using Emscripten and compiling with two output targets (PNaCl and ASM.js) which call the same APIs, you need to do a wrapper layer on one or the other (emulating PNaCl with standard Web APIs, or vice versa, or having some other intermediate layer that abstracts over both). The whole point of ASM.js is to leverage existing standardized infrastructure, while PNaCl just exposes what's convenient to expose in Chrome, while likely being considerably more expensive for other browser vendors to implement.
This is a lot like Filter Effects in IE. Rather than specifying a reasonably portable syntax, they defined something that was build specifically on some random subset of DirectX filters, and pretty much impossible to implement anywhere else without implementing a large amount of DirectX. While other browsers eventually released most of the same things in a portable manner, there was a while where you had to either implement both or use some kind of wrapper of one over the other.
While I think that it's a good thing that Google has spent time experimenting with and building NaCl and PNaCl (in general, you need ad-hoc single engine experimental implementations that people can play around with in part to figure out what will actually work for authors and is actually implementable, like canvas was, or various CSS3 effects over the years), it's a standardization dead end, and it would be nice if they would spend their effort on trying to extract something that could be standardized from it and ASM.js, rather than enabling it for web pages so it'll become another single-vendor technology that leaves others as second-class citizens.
This kind of vendor lock in is out of line with promises of openness and supporting standards that Google has made in the past, and especially concerning since they're selling hardware that only runs Chrome. Between locking people in to a single browser on that platform, and a single browser if they target PNaCl (with maybe second-class support for other browsers via Emscripten and pepper.js), this is starting to remind me of what a certain other company did when they had the sleek, fast new browser that was trouncing the big buggy slow incumbent.
Is it really cross-platform PNaCl code if making it cross-platform requires converting the PNaCl LLVM IR into an actually-portable language (Javascript) using asm.js technology and a reimplementation of Pepper? That sounds more like someone went to the trouble of writing an emulator/translator for a foreign platform, treating PNaCl the same way they'd treat old game consoles or ARM for android simulators.
>there's a project called pepper.js that compiles the PNaCl application using emscripten.
That made me laugh. You write code that is supposed to compile to native code, only to have it compiled to javascript instead. It's a crazy world we live in.
You're right, it actually may be more fun and interesting to provide you with all of the tools, and instructions on how to use those plus various common household substances to produce the chemicals that you need. Perhaps along with a few samples that are either impossible, difficult, or dangerous to produce yourself, but are useful for various reactions (since I haven't touched chemistry since junior year in high school, I don't necessarily know which those would be).
Yes. Texas requires you to have a permit to buy laboratory glassware, under the assumption that if you don't have a permit, you are going to use it to manufacture meth:
Why does he need to have a "business model"? This isn't a startup. This appears to be essentially a hobby business; something that can be sustainable for a single person and maybe a few employees but not something that can scale considerably. By using CNC routing to cut out the boxes, it can scale beyond what he could cut by hand, and thus he can offer a Kickstarter, but this doesn't really appear to be something that he's intending to scale up beyond the Kickstarter, just a way for him to be able to sell some of his sets to people who wouldn't be able to go there in person and buy them directly from him.
The liability concern is greater. He can personally talk to those who walk into his store about safety; less so those who order this over the internet. No one is going to be building a bomb however; all of these samples are in quantities of 30 ml or less. That's less than the 3 liquid ounces you're allowed to bring on a plane, and that limit was set because you can't actually build anything all that destructive with only a few ounces of material.
I'm not sure how you are determining that there are no solid or liquid disposal instructions; did he post the contents of everything that will be included?
Who cares about patents here? He's shipping a chemistry set that is identical to one from 1936, plus a couple more that he thinks are useful. How are you going to patent that? It's just a collection of chemicals, and an instruction manual. The patents on producing all of these materials have long since expired. There's nothing patentable here.
And sure, other manufacturers could do this for a fraction of what he's doing. As you point out, there is some liability concern; liability concerns are greater for a larger manufacturer than for him, doing this as part of his hobby business, merely because they are a bigger target. Asian manufacturers would probably have a hell of a time getting this past customs. And again, who cares? If someone else produces an awesome chemistry set, great! The whole point is to teach about chemistry, and get kids engaged by allowing them to experiment and explore rather than swaddling them and protecting them. The point is not to get rich. Despite what you may think reading about lots of startups on Hacker News, some people just desire to do a good job, not to build a scalable business that makes them filthy rich.
So, the two main concerns I see are liability, and his ability to scale if the Kickstarter is wildly more popular than he anticipated. Even if CNC machining the case cuts down on a lot of the labor, assembly and finishing will take time. However, I don't see this as being particularly more risky than the average Kickstarter; in this case, he's already been making these for a while for sale in person, so it's far past the prototype stage that many products do a Kickstarter at.
I don't understand the liability issue. He isn't selling it as a toy, it is a science kit. Anyone can walk into any store and buy stuff that is dangerous if ingested or misused... cleaning supplies, cooking knives, etc.
Parents should be responsible for teaching their children how to work with dangerous things that we encounter every day in a safe way. The chemistry set should be used to teach science. I don't see the issue, but I guess I'm not surprised in our litigation happy society.
I think it's because they are being completist, including all of the chemicals from the original A. C. Gilbert chemistry set from the 1930s (plus a few extras that they think are particularly useful). If you take out carbon tetrachloride, where do you stop? Lots of these are considered unsafe, and are well labelled as being poisonous.
Some people want these effects. Without them, the choice is to write it all by hand using canvas, or use animated gifs or Flash or something.
Sure, there are varying levels of support of the most bleeding edge features, but browsers are catching up with each other all the time. For real world sites, you use what's widely available, which corresponds to the gee-whiz demos from 5 years ago (give or take, and depending on how many truly obsolete users you need to support). So yeah, this isn't really all that useful outside of a gee-whiz demo now, but in a few years all of the major browsers will support it and people can use it. This kind of effect is most likely to be used in a game that has a large asset library to load, but the underlying functionality can be useful in a variety of designs.
This was specifically targeted at mathematicians, and pure mathematicians are a lot more likely to be hired by the NSA than any of those other organizations that you mention.
Engineers, programmers, and so on all already have to grapple with this issue with big defense contractors. It's more rare that mathematicians have to deal with it.
I'm not really sure how. Most web pages don't have dynamic lighting. I suspect that the amount of information to encode the flat image plus the normal map is going to be more than the amount of information to encode the pre-rendered effect.
Now, if you were planning on doing some kind of dyanmic lighting in a web page, then sure, this would help. But I can't think of much use for dynamic lighting outside of games or other physical simulations, which is likely overkill for most webapps.
You do realize that many of the people who object to IP laws don't object because they want to build consumer services without having to pay for content, but because they want to produce hardware and software without having to cripple them, right?
This is not "just another market with a a wide variety of interested parties." This is people telling me what I am legally allowed to do in my own home. This is passing laws saying that you can't produce an innovative new device because someone, somewhere may use it to subvert someone else's IP interests.
And the issue with the treaty process is that a treaty can be used to bypass the democratic process within a country. A proposal that would be shot down due to public outcry can instead be done in a secret treaty, only revealed once it's fait accompli, with everyone involved being able to disclaim that "I didn't want that, but that's what we had to do to get the treaty passed" and thus dodge the political ramifications.
I've been hearing this since the late 80s and the sky still hasn't fallen. If you don't like it by all means call your senator, donate to opponents of the trade deal, fight against it/ I'm not trying to get you to support the TPP (not least because I don't know what's in it either, so far); my reason for jumping into this thread is to point out that the EFF is making flat-out false arguments, which strikes me as an absolutely stupid way to gin up opposition about it.
If they had written an article saying 'TPP negotiations should be public' I wouldn't object in the least - that's a perfectly reasonable view, even though I am not very exercised about it. Indeed, I linked to a letter from a group articulating exactly that position up thread. But saying 'NYT endorsed secret trade treaty' is simply a falsehood.
> If you don't like it by all means call your senator, donate to opponents of the trade deal, fight against it
Well, I would LIKE to do that. I would LIKE to contact my president and the administration officials who are negotiating the treaty and provide them with my feedback and comments on the proposed wording. I would even like to spend some of my hard-earned money paying world-renowned experts (such as those who work with the EFF) to review it and provide even more insightful feedback.
Unfortunately, the text of the treaty is secret so I cannot do these things. I complain that I am being prevented from participating in democracy and you write that if I don't like it I should participate in democracy. Perhaps you don't understand the complaint that is being raised.
You'll be able to read it when it's presented to the Senate for ratification. There seems to be some notion that the Senate is going to vote on it in secret, but I don't find any evidence of this being the case.
When it is presented to the Senate for ratification is too late to have any influence on the text -- at that point the agreement can only be accepted or rejected.
The same is likely to happen to PNaCL. It will probably survive for a while in Chrome, as it may be useful for writing ChomeOS specific apps, but it will never be adopted by any of the other browser vendors. ASM.js runs just fine in other browsers, the only difference is that they don't implement the stricter subset and same optimizations as Firefox does, so it's a lot more likely to catch on, as people can write cross-platform ASM.js right now.