Question: Is there room for a new Picnik?
Edit: hmm, the Google+ version of Picnik (scaled down) is still Flash-based. So this is most likely part of the "Drive Traffic to Google+ At All Cost!" strategy.
1,758 karma · joined September 5, 2010
Question: Is there room for a new Picnik?
Edit: hmm, the Google+ version of Picnik (scaled down) is still Flash-based. So this is most likely part of the "Drive Traffic to Google+ At All Cost!" strategy.
You need to think harder about quality control. A simple email-based dispute process is a start, but you need more. How about teacher rating? Teacher credentials, etc.
I created a better one (based on pg's essay) a while back: http://www.tagxedo.com/shop/y-combinator
Now compare that to HashSum, a a Silverlight-based implementation of the SHA-1 (I verified that it generates the same result), I clocked it and it is 20X faster than the Javascript implementation, and ~3X slower than native. Try it at http://www.hashsum.com (I wrote it; Silverlight required; sorry about the ad/layout, it was an "exercise" a while back).
So HTML5/Javascript is the future, and the future does not include Flash/Silverlight. Perhaps. But this experiment shows that Javascript is clearly way too slow compared to native or plugin. You could argue that the plugin-based scenario is going out of favor. Politics, competition, distribution, etc, are all valid reasons. But "Javascript is now just as fast" isn't one, because it is not. Those who are gung-ho about how fast Javascript is needs to write their own SHA-1 implementation that beats http://www.hashsum.com ... or at least not be blown away by it.
Like the other commenter said, you did a dis-service to yourself by notifying your ex-boss, especially given your wording (face-palm).
However, I was thinking of making a different kind of tribute, which is to allow you to turn your own C/C++/C#/ObjC code into a word cloud artwork in the shape of the blue "C", and make a T-shirt/mug/bag out of it (via Zazzle). Of course you can already do that if you know how to use Tagxedo, but I presume most people don't. Stay tuned if you are interested.
You have two points that I think are reasonable to raise: (1) is there a mistake (intentional or not) in the assumed margin of error in the measuring equipment? (2) is the DRAM caching behavior taken into consideration? Neither of these two points have anything to do with FPGA per se. Now by including the enchilada word "FPGA platform" into the fray (whereas it was clearly not the intention at the beginning), I feel like you are making things up as you go, which is unfortunate since part of your argument is valid.
Clearly, the author did not know what he is talking about.
I can see that we'll immediately benefit from a few improvements, such as auto variable, lambda support, standard support for unique/shared/weak_ptr. Even old school C++ users who have no interest in fancy new idioms would benefit from these "syntactic sugar" features found in other modern languages. There are a lot more that I'm still exploring, but so far I like what I saw.
Also these new features just work on the compilers. Given how long the standard process has been, a lot of the features were already baked in. Modern g++ and VC++2010 both have very good support. I listened to a BUILD presentation on C++ and the Microsoft folks are very committed to full C++11 compliance in VS11 (next version of Visual Studio), but AFAIK, VS2010 is already quite capable.
So, I agree, if you have a choice, switch NOW.
Transaction information - When you use Google Wallet to conduct a transaction, information regarding the transaction may be stored in the Google Wallet Application. We may collect information about these transactions from the Google Wallet Application. We also collect transaction data from your use of the Google Wallet Service. For example, if you use the Google Wallet Application to make a purchase at a merchant or download a merchant coupon, we may obtain information regarding that transaction from the Wallet Application, from the merchant and/or a partner, as applicable. The information may include the date and time of the purchase, the store location, the amount of the purchase, and the offer associated with the transaction.
Information about your use of Google Wallet - We may collect information about your interaction with the Google Wallet Service and the Google Wallet Application. This may include, for example, data on number of offers saved, payment attempts, and provisioning activity. Using added services may require your opt-in consent for Google Wallet to offer the functionality. For example, you may be offered the opportunity to opt-in to a service whereby Wallet would present offers to you based on your transaction activity through Wallet.
It's a Silverlight application I wrote years ago (as a warmup) and it does MD5, SHA1, SHA256, etc. and it is much faster than any Javascript or Flash implementation I've ever seen, including this one.
Apology for the very poor Google adsense placement and UI. Yeah it is embarrassing. It was my first introduction to web programming, Google Adsense, and UI, and I've moved on from it long ago. Needless to say I have learned a lot since then.
Hashsum can handle much bigger files than 10MB. In fact, for a file that small, you won't even notice that it did anything. Try something bigger, like a DVD-sized ISO (4.7GB) which will take about 1 or 2 minutes. All computation is done on the client side.
Anyone who claims Javascript is "as fast as C/C++" should at least try to beat Hashsum, which is only C# based.
Sadly, Microsoft is putting an end to this amazing technology, but that's another story.
In other words, Microsoft means to say "please use Metro, but if you have legacy code don't be angry with us, 'cuz you have the desktop UI option... but not on all devices"