Language Barriers

2,019 views
1,944 views

Published on

Common language barriers in web development and how to bend/break them.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,019
On SlideShare
0
From Embeds
0
Number of Embeds
75
Actions
Shares
0
Downloads
30
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Language Barriers

  1. 1. Ă
  2. 3.
  3. 4. Language Barriers
  4. 9. PHP vs. Java Java vs. PHP Rails vs. PHP Python vs. Rails Etc..
  5. 10. Enter Web-Development
  6. 11. Language Barriers
  7. 12. Client-Side (Everyone) HTML,XHTML,CSS,JavaScript,Flash, Flex …
  8. 13. Server-Side (Normal People) PHP(Cake/Zend/other), Perl, Python(Zope/Turbogears/etc.), Ruby(Rails/Merb)
  9. 14. Server-Side (“Enterprise”) Java (JSP,JSF,Seam), ASP.NET(C#,…)
  10. 15. Clear limits to most people
  11. 16.
  12. 17. Let’s bend (break) them.
  13. 18. Who here programmed in PHP?
  14. 19. Who here hates PHP ? By free-will or other reasons.
  15. 20. Introducing Quercus http://quercus.caucho.com/
  16. 21. Quercus <ul><li>PHP5 Interpreter implementation </li></ul><ul><li>… </li></ul><ul><li>IN JAVA! </li></ul>
  17. 22. Quercus <ul><li>Open Source (GPL) </li></ul><ul><li>Implements most common php extension functions. </li></ul><ul><li>Can run non-trivial php apps: Wordpress,Drupal,MediaWiki,phpMyAdmin </li></ul>
  18. 23. Why use it?
  19. 24. 1. It’s FAST Same as PHP+APC, but with more potential for improvement
  20. 25. 2. It’s “Enterprisey” Deploy on your company’s existing J2EE servers/infrastructure.
  21. 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.. )
  22. 27. Code Samples/Workshop
  23. 28. So who is interested in Quercus now? Drop a line at xmpp:deathy@deathy.info or [email_address]
  24. 29. Moving on…
  25. 30. Who here has programmed in JavaScript?
  26. 31. JavaScript + <ul><li>Nice language </li></ul><ul><li>Multi-paradigm, prototype-based, functional, imperative, scripting.. </li></ul><ul><li>Very powerful but very easy entrance level. </li></ul>
  27. 32. JavaScript - <ul><li>Browser-incompatibilities </li></ul><ul><li>You only use it in the front-end </li></ul><ul><li>Can be disabled on some clients. </li></ul><ul><li>A lot of libraries (problem of too many choices) </li></ul><ul><li>And did I mention.. Browser incompatibilities ? </li></ul>
  28. 33. Introducing SSJS Server-Side-JavaScript
  29. 34. For the love of God, WHY?! Geeky reason: Because we can.
  30. 36. Actual Reasons <ul><li>You already know JavaScript </li></ul><ul><ul><li>Why use it only on the client? Make your skill more valuable. </li></ul></ul><ul><li>Become a better programming by knowing server-side programming. </li></ul><ul><li>Access to: databases, files, system commands, server-side DOM, etc. </li></ul><ul><li>NO Browser-incompatibilities! </li></ul>
  31. 37. Two major players <ul><li>Rhino (by Mozilla, Java) </li></ul><ul><li>SpiderMonkey (by Mozilla, C/C++, APIs for a lot of languages ) </li></ul>
  32. 38. Some more advanced solutions <ul><li>Aptana JAXER </li></ul><ul><li>AppJet </li></ul><ul><li>Phobos </li></ul>
  33. 39. Code Samples/Workshop
  34. 40. Questions?
  35. 41. The end. Of the presentation and of common language barriers.

×