We used that opportunity to grab him, put him in a Tiki hut, and chat with him about SilverStripe. We discuss life as an open source company, and the experience and advice based on having ten students enrolled in the summer of code program.
Thanks to Ohloh we have statistics on the code produced by the students. Obviously, the lines of code metric is purely quantitative and doesn't show the actual work involved, but it is great to see how these students have produced:
In the chat below you will hear about some of the really cool additions that SilverStripe has in its trunk thanks to the students.
Seo Master present to you: Posted by Dion Almaer, Google Developer Programs
Eric Enge of Stone Temple Consulting interviewed our own Mark Lucovsky about the AJAX Search API that Mark and his team created.
The interview provides detailed answers to questions such as:
What we learned from the Maps API
How the AJAX Search API came about, and why we built it
How the API aims at a broad spectrum of users, from lifelong programmers to the casual blogger
How the API can be used to perform searches, get back JSON
results, and display them however you like
What the terms of use actually mean
Why the team used JSON output.
The interview also includes interesting examples of real-world users, such as VisualDxHealth, and dispels a few common myths about the AJAX Search API.
Is there anything else that you would like to know about the APIs? Join us on the AJAX Search forums.2013, By: Seo Master
Seo Master present to you: By Dion Almaer, Google Developer Programs
Last year, Steve Yegge posted about Rhino on Rails, his port of Ruby on Rails to the JavaScript language on the Rhino runtime. It garnered a slew of interest, and I have been wanting to talk to him in more detail about the project.
Fortunately, I happened to be at the Google Kirkland office and Steve graciously had time to spend talking about the framework. Steve is an entertaining chap, and manages to keep you interested with long blog entries, and did the same as I chatted with him.
In the conversation we cover the germination of the project, why Steve went ahead with the port, the side effects of JavaScript on the server, how Rhino will be implementing JavaScript 2 / ECMAScript 4 (with Google committing engineers to the project), the intent to open source RnR, and random thoughts from a language geek.
Give it a watch, and let us know if there are any other questions you would have liked to ask