541 karma · joined December 21, 2009
[ my public key: https://keybase.io/arturventura; my proof: https://keybase.io/arturventura/sigs/WmemHKEaIAvrvrPnKeFCKIoCUDLrhEiYcDAY11mFhDw ]
To make a collision work, you would need to inject the payload into the program, and find a specific blob to put into the zip file, that once compressed and hashed would cause a collision. This isn't computationally efficient.
I would like to see someone tackle this though.
Apple is gonna make IBM build a cloud base infrastructure with Apple User interface and QA. We are talking very high end costumers, not the typical small or medium corp. No one will be fired for buying Apple and IBM. Google, maybe.
Enterprise Cloud was one Horse race for Microsoft market. Now there are two.
The problem is that Google launched something that does pretty much all that, and is integrated in their Google play games.
It didn't started as a LMS, actually started as a Academic Management System. We needed a system to control all the academic administrative operations. Later we developed the LMS system connected with the AMS.
Right now we are on the process of replacing our old LMS with a new one. We have very cool ideas that we are developing right now (timeline based view for the students, tools for interactive presentations, transparent support for MOOCs, etc.)
FenixEdu was designed for a single school for the past 10 years and now we are trying to refactor it to be installed anywhere. We want to create that can tackle the needs for the next decade of teaching. If people are interested in this kind of thing please talk with us, we are most welcome to receive any kind of suggestion or feedback.
First of, market. Not there isn't a market for computing power, but a market for this kind of thing. This is a good parlour trick, to show of browser power, but as a computational framework it doesn't work. There are far better and cost sensitive solutions, even using the cheapest AWS service. I know, because I did the math.
Second there is the ethical problem. You are are off shooting the cost of cloud computing to the website client that will pay for the extra electric power generated by your tasks. How do you justify that? More so, how can you justify a ecological minded person paying for mapreduce geological data from oil company?
Third, and the one that kills you, security. You cannot assure the confidentiality of the data being processed. You can not use homomorphic encryption because you do not know the operations you need to do on your data, and since you are working over it, at least in memory it must exist in plain text. Therefor you cannot assure your clients data confidentiality. Worse, this screws up the market fit. The only people that have big data needing to be processed that isn't confidential is research institutions. The thing is, research institutions buy computer power by the stack. I know, I work at one. There is always some grant that allows them to buy a bunch of computers to do parallel processing.
I've heard about you guys for over an year. And it took you more than a year to complete the full product to launch it. What have you been up to? I've seen clones of your product on techcrunch 500. I made a clone of your product using bitcoins, in a weekend. (I did the calculations and wasn't cost effective and I decided not to launch it) Where I work, Técnico Lisboa, we are actually thinking about deploying my clone in my work, over computers we own and provide that computing power to the faculty. Actually I've seen this in 2009, when it was shown of by Ruben Fonseca on Codebits (http://blog.0x82.com/2010/11/22/map-crowd-reduce). If anyone can do this, how can you assure the competitiveness of your product.
I don't like the change, but if they are competing with google by making drastic changes to their interface, then they have a problem.
1) No. This was just a hacking solution that I got. ECMA already has a solution but browsers haven't implemented yet. When JS engines start implementing ECMA class system, JSC will became obsolete.
2) I looked to ES4 and 5 spec, but they were too extense. I wanted something more simple, that could be similar in syntax to Java-like language with some flavours of SmallTalk. My main problem was with code from the same class being scattered on several files. This led me to creating the same classes and packages concepts that exist on other languages. More so, if you never code in JS before, this syntax seems more friendly than some weird new object system.