I'm currently writing my diploma thesis on Serverside Javascript at
Dortmund Technical University, mentored by Prof. Clemens Cap from
Rostock University.
You guys are my biggest hope and my biggest fear. You could save me
from some unpleasant gruntwork (a workable SSJS implementation) or
preempt my attempts at creating something slightly meaningful (a
lightweight framework that utilizes JavaScripts special features).
I don't have much to report right now, I'm still at the planning stages.
What's on my mind for a technical foundation, roughly, is V8, tied to
a TCP/IP
stack or mongoose, enhanced with MongoDB bindings.
I have a blog at http://jan.varwig.org/ and I'm on twitter going by
@agento
regards
Jan
I'm Robin, usually as darobin when on IRC. I have a rather long
background as a Perl hacker with a bunch of things on CPAN, and have
been doing some PHP lately (love the symfony framework but the
language still annoys me). I've also done quite a lot of work in W3C
standards, notably working on SVG, CSS, XML, and chairing the Web APIs
group for a while. Naturally, I'm a big fan of Web technology in
general, with a soft spot for Javascript. I have some experience
writing specs and designing APIs that I'd love to put to use here :)
--
Robin Berjon
Robineko (http://robineko.com/)
I think so, too. Thanks for starting this thread.
I'm Kevin. I've been in software-related sorts of work for 20 years,
in a variety of roles. I've done a fair bit of work in Java,
JavaScript, Perl and a bit of PHP. Oh, and I've used Python on and off
since 1995 and very heavily for the past 4 years. I'm best known as
the founder of the TurboGears web framework.
Last year, I learned a whole bunch of new stuff about client side
JavaScript while working amongst the Dojo guys at SitePen. At the
beginning of this year, I joined the new web developer tools group
within Mozilla Labs. Thus far, I've been largely working on a project
that will be announced soon. I've been doing that server side work in
Python and hope to port it to JavaScript before too long.
I'm quite happy that my role at Mozilla gives me some leeway to help
with this initiative which I think will ultimately help JavaScript
flourish even more.
Kevin
I'm Ross Boucher, one of the other founders of 280 North (with Tom).
I've also got a lot of code in Objective-J and Cappuccino, and our
product 280 Slides.
I also wrote "Roundabout", which is a "Sinatra" inspired http routing
library that sits on top of Jack. The basic idea is to match HTTP
verbs and URL paths containing simple wildcards to arbitrary blocks of
code. And since it sits on top of Jack, you can actually route entire
Jack applications this way.
We're working on a few other server side JS projects, so hopefully
there will be more to share in the future.
Hello all,
I’m Steven and I’m from the Gold Coast, Queensland, Australia.
I have been developing mostly PHP since 1998 and for the past couple of years I have been developing primarily with Zend Framework.
I have developed everything from desktop applications in Delphi and Java, to CD-ROM applications in Director/Lingo and Flash/Actionscript, to websites in Perl, Flash/ActionScript, Red5/Java, PHP and ofcourse JavaScript.
I stumbled across a Jaxer introductory video during development of a major AJAX application and really didn’t do anything with it for several months as I was in a period of heavy startup development using PHP/JavaScript/Flash/ActionScript.
Once I came up for air I started playing around with Jaxer. While the benefits are obvious (especially server-side DOM for me) the implementation can be a bit trickier.
My frustration with Jaxer’s somewhat limited 1.0 framework (the essentials are all there but the dots have not all been joined yet) have led me to begin development of Jaxo (www.jaxo.org) a Jaxer MVC framework of sorts based on my experience with Zend Framework. Depending on where ActiveJS goes I may leave MVC to ActiveJS and focus more on utility code.
Unfortunately I live in a country where programmers are treated like monkeys and there is no respect for programming as something to be mastered. My employer has me on endless deathmarch projects and has implemented several policies against the very programming practices we need apply to deliver quality code in a short period of time. There is certainly no room in the job for trying something like Jaxer so I need to push forward with new technology in my spare time which is limited.
I look forward to absorbing knowledge from those of you creating the future of programming and hopefully I can chime in every now and then with something valuable.
Cheers,
Steven
I am also a Dojo committer and on the OpenAjax Alliance steering
committee and EcmaScript/TC-39 committee.
Thanks,
Kris
Though I've not been battle-hardened in JavaScript, I have been
playing with it pretty much since it's been available, over 10 years
ago. My Smalltalk colleagues gave me funny looks when I told them
that JS was a pretty nice, little OO language, prototype based like
Self. Of course, back in those days, it was used primarily to scroll
messages along the status bar, and implement popup menus. I wish we
could have been having these discussions back then. :-)
I'm most interested to see how some of the things that fall out of
this effort might be used in all forms of JavaScript enablement,
including better integration with web browsers. But interested in
server-side JS as well.
Patrick Mueller - http://muellerware.org/
This is wrong in so many ways...
Each time an HTML page is rendered serverside, a cute kitten
dies. On top of that, the MVC pattern is totally fucked up and
the 3-tier architecture is dealt a killing blow.
You want to do that sort of stuff serverside with JS you can
use E4X. HTML belongs on the client and data content should be
pulled from the server by the client, not pushed by the server
to the client embeded in HTML (server pushing to the client data
in JSON is OK though)
-- MV
Yes, but really I would rather have the equivalent to WSGI for python in SSJS.
There have been lots of one off SSJS servers, many around for years,
but they all have incompatible interfaces, meaning applications are
stuck to them, and part of the reason no one true framework has
emerged, because they are always tied to one server side VM and server
application implementation.