jQuery is an unneeded dependency.
There are only 2 things done with jquery: - a domready handler - ajax request
Could be done with 2 smaller functions and not with an full-blown framework.
31–40 of 57 posts
jQuery is an unneeded dependency.
There are only 2 things done with jquery: - a domready handler - ajax request
Could be done with 2 smaller functions and not with an full-blown framework.
1. Some people are on limited bandwidth plans, this adds to the plan since i am downloading and uploading data, and if the data that has to be processed -coming from the server- is big then this is going to kill my bandwidth.
2. This could slow down a lot of mobile devices that are JS capable, or old/moderate hardware.
3. Memory leaks?
4. If a startup is based around this idea, and me as a published i'll use their JS code to run tasks, then i'm basically giving them a key to my site :).
Other than that, the idea it self is awesome, if it could be implemented through :
1. Asking user permission. 2. work on idle browser tabs only. 3. used for non-profit organizations to solve real problems, maybe to fight cancer or to analyze data coming from space.
Why nobody's built a startup around this already: (a) There's no money to be had. A company that offered to solve your distributed problems using distributed JavaScript could only charge as much as the spot price of buying EC2 instances. Otherwise, you'd just buy the EC2 instances and solve it there. A problem not amenable to solving with temporary machines wouldn't be amenable to solving with times slices of JavaScr…
I just think that charity would be a great angle to it. How about you donate your CPU cycles for charity ? Companies that need to use large scale parallel processing use the service, your browser does the client side processing and the money that the gets paid by companies goes to charity minus running costs.
Now that would be beautiful. CPU cycles for charity!
Why nobody's built a startup around this already: (a) There's no money to be had. A company that offered to solve your distributed problems using distributed JavaScript could only charge as much as the spot price of buying EC2 instances. Otherwise, you'd just buy the EC2 instances and solve it there. A problem not amenable to solving with temporary machines wouldn't be amenable to solving with times slices of JavaScr…
Or the (dead) http://pluraprocessing.com from 2009?
I find the idea really interesting. And the portuguese startup called crowdprocess seems to be down with this stuff. I just think that charity would be a great angle to it. How about you donate your CPU cycles for charity ? Companies that need to use large scale parallel processing use the service, your browser does the client side processing and the money that the gets paid by companies goes to charity minus running…