sylvinus

Well, enthusiasm was clearly speaking here but you can consider it epic in that one player will be thrown against potentially "all" the computers of the world. Kind of a "Man vs. Grid" thing.

But yes, in terms of pure strength, nothing epic for now :)

Indeed. APHID doesn't scale well and it will be hard to distribute YBWC efficiently but we think we have a shot at it with very short compute windows for each worker. We may also look at other algorithms but currently a variation of YBWC seems the most promising.

In terms of strength, we'll add the UCI protocol to be able to run games against other engines. We'll see how it performs but we don't expect to beat Stockfish easily, even with a very large number of nodes. That will be part of the experiment and we'll be happy to publish the results.

Now, another path to get real performance would be to find a way of using webGL on the workers. Folding@home has proven it's sometimes 10x more efficient than using CPUs. If we can manage to do that then we might have a shot at being both the largest and strongest AI...

By the way, just posted the source from NKO: https://github.com/joshfire/chessathome

congrats, I wonder how you'll make money though.

90 is an astounding number of useful node modules :)

Most badass JS you will see today? Distributed chess AI with webworkers and nodejs!

http://chessathome.org/

Please vote for us, top right corner :) thx

AWS: "We'll continue to cut our prices forever"

GAE: "Almost all applications will be billed more under the new pricing"

Pick one...

"The WebRTC initiative is a project supported by Google, Mozilla and Opera." http://www.webrtc.org/

I'm always blown away by the consistent performance gains they reach with each new version. Congrats!

Thanks for taking care of it, also good to know they got a suspect.

What can you say on the 24/7 "urgent" line, which sounds like an important feature even for cases less dramatic than this one?

Use a standard jsonp paramter format so that we can use it with jQuery.ajax : jsonip.com/jsonp/?callback=xxx

That would be nice however I'll be offline 99% of the time!

According to http://en.wikipedia.org/wiki/List_of_acquisitions_by_Google this is the 100th acquisition by Google!

you also have to thank tbassetto for that! :)

well, thanks! You sir are a gentleman and a scholar, I hope you can make it to the next ones!

Thanks again for coming and shedding some light on this weird Clojure thing ;-)

All the presentations were and will remain in english. There was a fair share of people that didn't speak french, which is good!

To follow the next meetups there : http://parishackers.org/

Is this linked to Enlightenment? The "e" sure looks familiar.

would be nice not to have the map boxed on the US... there are also dots outside.

That is if you plan to run almost the same code on all platforms

Two counter examples here:

- For devices without a JS interpreter, app is executed server-side

- Progressive enhancement / Graceful degration : some platforms can have more features than others

Titanium from Appcelerator does allow controlling native components from javascript, however the base UI definition is not HTML AFAIK.

we do parts of what you describe:

an app is indeed specified in a quite abstract way (http://framework.joshfire.com/doc/0.9/gettingstarted/overvie...), however we don't go as far as implementing automatic transforms from multiple panels to a composite one for instance.

these choices are left to the developer but we make their implementation easy.

Paris, France

Joshfire ( http://joshfire.com/company ) is looking for :

- experienced JavaScript developers

- designers (from web to smart objects)

We do the open source multi-device framework that was #1 on HN earlier today : http://framework.joshfire.com

We are kind of cool but come see for yourself...

jobs at joshfire.com

yes it's writing an app in JS in a way that's portable and that can use device-specific implementations of both UI Components (video for instance) and input methods (touch/mouse/keyboards/http/...)

very simple, because as a company we'd like for manufacturers (think Samsung or LG) to come to us for licensing if they want to release a device using the framework.

That business plan allows us to avoid dicking around with developers like others do (we're on github, we don't try to obfuscate anything in order to sell "support") while still being able to make real money.

opinions on this position for an open source editor are welcome! we're still young :)

Wrong direction? Depends on where you're headed to :)

The #1 goal for this framework is being cross-device. Having the same language run wherever we need (client side, server side with nodejs) is a big step in that direction.

Now, this is clearly not the same direction as "find the purest, most perfect language" but that's for others to look for :) We just try to solve this one multi-device issue.

can you be more specific?

currently the adapters mostly implement the input methods of each device (touch, tv remove, mouse, ...) and most of the styling is left the the developer with CSS/Templates.

Developers can use phonegap to provide these abstractions where they make sense (mobile).

Another focus of the framework is TVs and connected objects, where we do provide abstraction for media elements like video : each TV SDK (Samsung, Philips, LG, ...) has its proprietary widget

Thanks!

Here's the github link while we activate the cache on the server: https://github.com/joshfire/joshfire-framework

This was released 2 days ago so yes it's still very rough around the edges!

It's currently GPL but there's also a free MIT-like commercial license that applies if you're not an OEM. So no problems for most projects.

Any other feedback is welcomed :)

Hi,

yes it's a Developer Preview, we didn't expect the HN #1 slot so fast ;-)

Back button support is implemented (works on the website which is itself written with the framework) but we didn't polish all the examples enough just yet... will do!

Edit: The "Videolist" example has an Android connector that we test on Galaxy Tab. We do need to get more of these devices asap... (thanks fragmentation!)