sorted by: recent | see : popular

Content Tagged with languages + python

A talk and many resources on concurrency and Erlang

When you say “scripting language” these days, most programmers think of Perl, Python, Ruby, PHP, ASP, or JavaScript. But the history of scripting languages starts much earlier than any of these.

This is the basic problem with learning how to program computers these days (the Hello World program for Java, arguably one of the most popular programming languages.) Encapsulated in the above three lines are several different concepts ranging from static functions to return types to stdout and to the entirety of object oriented programming in general.

One interesting session at JavaOne 2008 was hosted by Raghavan aka Rags from Sun Microsystems. The session was called the Script Bowl and was a war between the scripting gurus from Groovy, JRuby, Jython and Scala. All the four languages are dynamic scripting languages that run on the JVM. LaForge represented Groovy, Nutter represented JRuby, Wierzbicki represented Jython and Jorge Ortiz represented Scala...

I wanted a picture of a chessboard. Rather than boot up some drawing software and cut and paste black and white squares I decided to write a program to create the picture. If you’d like to know why anyone would ever create work for themselves in this way, skip to the end of this article, where you’ll find justification and a more challenging follow-on problem. Otherwise, please read on from top to bottom in the usual way.

Given a good test suite the return on investment simply does not justify the use of static typing. In 5 years, we'll view compilation as the weakest form of unit testing. -- Stuart Halloway Type verification provides very little confidence that an application works.

A discussion attempting to define attributes of programming languages along a meaningful continuum.

Some many developers aren't object oriented developers. Every candidate out there has Object Oriented Design on their resume in spite of the fact they can't define polymorphism or worse encapsulation! If you can't define polymorphism or encapsulation without resorting to examples then you can't write Object Oriented Design as one your skills. You don't even know what object oriented is! Here are some techniques to show you how to reform your imperative ways and say good bye to singleton and static utilities.

This sounds bad, but it needs to happen if Java is to ultimately stay in the mainstream. That is, if feature accretion hasn't already irreparably damaged the language

I’ve labeled the pagination tag "auto adjusting" because it is designed to give up to three easily readable ranges of pages for the user to click. Range one will always be page one through some configurable number (more on this later). Range two appears only if enough pages exist and the current page is far enough out, it shows a subset of pages in the neighborhood of the current page. Range three appears only if there are enough pages and shows the last few pages, also configurable. The three ranges are automatically created if required to ensure the user can easily navigate through large page numbers. For details on how to configure the ranges see the "Using The Pagination Template Tag" section at the bottom.

This sounds bad, but it needs to happen if Java is to ultimately stay in the mainstream. That is, if feature accretion hasn't already irreparably damaged the language.