This document discusses breaking down language barriers by using technologies that allow traditionally client-side languages like PHP and JavaScript to be used server-side. It introduces Quercus, which allows PHP applications to run on Java servers, and server-side JavaScript (SSJS) technologies like Rhino and SpiderMonkey that bring JavaScript to the server. The goal is to leverage existing skills in popular languages and make them applicable to more environments like enterprise Java applications. Code samples are offered to demonstrate these technologies.

1. Ă

3. …

4. Language Barriers

9. PHP vs. Java Java vs. PHP Rails vs. PHP Python vs. Rails Etc..

10. Enter Web-Development

11. Language Barriers

12. Client-Side (Everyone) HTML,XHTML,CSS,JavaScript,Flash, Flex …

13. Server-Side (Normal People) PHP(Cake/Zend/other), Perl, Python(Zope/Turbogears/etc.), Ruby(Rails/Merb)

14. Server-Side (“Enterprise”) Java (JSP,JSF,Seam), ASP.NET(C#,…)

15. Clear limits to most people

16. …

17. Let’s bend (break) them.

18. Who here programmed in PHP?

19. Who here hates PHP ? By free-will or other reasons.

20. Introducing Quercus http://quercus.caucho.com/

23. Why use it?

24. 1. It’s FAST Same as PHP+APC, but with more potential for improvement

25. 2. It’s “Enterprisey” Deploy on your company’s existing J2EE servers/infrastructure.

26. 3. Java Integration Plays well with your company’s existing java code/modules. Easy to write extensions in java (hell of a lot easier than c extensions.. )

27. Code Samples/Workshop

28. So who is interested in Quercus now? Drop a line at xmpp:deathy@deathy.info or [email_address]

29. Moving on…

30. Who here has programmed in JavaScript?

33. Introducing SSJS Server-Side-JavaScript

34. For the love of God, WHY?! Geeky reason: Because we can.

39. Code Samples/Workshop

40. Questions?

41. The end. Of the presentation and of common language barriers.