Am 29.04.2008 um 17:52 schrieb Santiago Gala:
Productivity is a key concern, specifically for front-end programming,
the area where rails or django excel, or where PHP is still leading
most
of web development.
Did somebody just say PHP? Wuhahaha... Ups, Shindig has PHP, too. ;-)
I'm studying and thinking about the long term evolution of computing.
With 4 core computers becoming entry level, this is an increasing
concern. Take a look into scientific bibliography to know that this
is a
hot topic.
Ok, but it is nothing you really notice in practice. And to scale up
webapplications should be done by using clouds, ie. N > 1 (N =
processing node), and not purely by making N = 1 faster. You can't put
Facebook, YouTube and co. on a single machine or DB cluster. The
general architecture must scale.
See for example http://bitworking.org/news/218/N-1
huh? shindig is almost pure backoffice. It delivers javascript and
gadget definitions, and provides services for them (proxying, rest
calls, etc.) An Apache module would probably be able to do all of this
more or less with the same efficiency. Even a thin javascript layer on
top of CouchDB could probably do most of an OpenSocial container
easily.
Disagreed. Shindig's java/social module is a framework (for the java/
gadgets module it is debatable...):
- Your custom social container code has to be in the same programming
language.
- You don't just call a few methods in a pure library style.
- Instead, you have to implement your custom DataService,
PeopleService and ActivityService - inheriting classes/interfaces from
an API and overwriting is very framework-style.
Gadgets are developed completely independent of shindig, it just
serves
them, gives (open social) services and proxy their requests, etc.
I don't mean javascript gadgets, I mean the server-side.
Well, I have been already bitten a number of times by native2ascii
(Latin-1 in author names in javadocs, basically) to feel java as
successful in this area either.
This is a rare case.
As I said, make is routinely used to
build The World, I bet even windows
No, Microsoft has its own build systems based on Visual Studio.
and I bet higher about the javaVMs
included.
That might be true. But maven is a much more higher-level build tool
than make. Make is on the same conceptual level as ant. That's why you
can tweak things more easily with ant or make, but you more often
diverge from useful conventions.
BTW, shouldn't there be separate projects for the different
languages?
What else besides some static files and Javascript is shared among
the
projects?
I don't think anything else, except probably, in the future, DB
schemas
for services if there are demo service implementations, etc.
I see. In maven-terms you'd have a pure resource-containing package
(jar file) for those.
Alex
--
Alexander Klimetschek
[EMAIL PROTECTED]
>> Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/ <<
