Topics

Featured in Development

Peter Alvaro talks about the reasons one should engage in language design and why many of us would (or should) do something so perverse as to design a language that no one will ever use. He shares some of the extreme and sometimes obnoxious opinions that guided his design process.

Featured in AI, ML & Data Engineering

Today on The InfoQ Podcast, Wes talks with Katharine Jarmul about privacy and fairness in machine learning algorithms. Jarul discusses what’s meant by Ethical Machine Learning and some things to consider when working towards achieving fairness. Jarmul is the co-founder at KIProtect a machine learning security and privacy firm based in Germany and is one of the three keynote speakers at QCon.ai.

Featured in Culture & Methods

Organizations struggle to scale their agility. While every organization is different, common patterns explain the major challenges that most organizations face: organizational design, trying to copy others, “one-size-fits-all” scaling, scaling in siloes, and neglecting engineering practices. This article explains why, what to do about it, and how the three leading scaling frameworks compare.

Scala has been getting a fair amount of press recently (see InfoQ’s roundup of the discussion) and Neward starts his article with a section on how Java is showing its age, specifically in regards to Moore’s Law.

Actually, it’s Moore’s Law that has many in the industry particularly concerned. Since 2002/2003, the growing trend in microprocessors has been to create CPUs with multiple “cores”: In essence, multiple CPUs within a single chip. This obviates Moore’s Law, which says that CPU speeds will double every 18 months. Having multithreaded environments executing on two CPUs simultaneously, rather than doing the standard round-robin cycle on the single CPU, means that code must be rock-solidly thread-safe if it’s to survive. …The concurrency crunch is a real concern, and some of the new languages offer powerful answers, but too many corporations and enterprises remember migrating from C++ to the Java platform just 10 years ago. To move to a new platform is a risk that many companies just aren’t going to seriously consider. Many, in fact, are still nursing the scars from the last move to the Java platform.

Neward’s tutorial goes through an overview of functional concepts, then discusses how Scala provides for them and wraps up with closures. Spiewak’s series is more lengthy and goes into a lot more detail. He targets his at experienced Java developers who have heard the noise about dynamic languages but are worried about dynamic typing for building enterprise applications.

The good news is that there’s light at the end of the tunnel. There’s a new language on the scene that’s taking the developer world by storm. Scala seems to offer everything you’ve been looking for in a language: static typing, compiled to bytecode (so you can run it on all those ancient Java-capable servers), a succinct and expressive syntax. …You can write your Java applications in Scala. You just need the right introduction.

Spiewak begins with a simple Hello World example and goes on to cover iteration and built-in types in his first article. His second article covers object oriented concepts, including classes, abstract methods, and constructors. His third dives deeper into access restrictions, method overloading and Scala’s approach to statics and his most recent covers pattern matching, case statements, and exception handling.

Market support

Your message is awaiting moderation. Thank you for participating in the discussion.

Scala it's not the only language with actors and actors are not the only good solution for concurrency. E.g. you can use Groovy with actors extensions (groovyactors.org/), or build your solution on SCA intra-jvm middleware (incubator.apache.org/tuscany/).But the real issue for Scala (like every other language) is the support of one of the big-three of IT (aka IBM,MS,Oracle). Without a strong "sponsor" there are no money for develop a real market and so Scala could be the future Smalltalk: amazing for purist programmers but no market share.

Re: Market support

Your message is awaiting moderation. Thank you for participating in the discussion.

Yeah, but there is no other viable alternative as a language on the JVM that has static typing.

Groovy has static typing as optional - and all the tutorials for Groovy (and its proponents) illustrate using it in a mostly typeless manner - much like JavaScript.

The next flagship language for the JVM that can take Java's place, will need to be like Java where static typing is the intrinsic nature of the language all the time.

So far Scala is the only viable language on the JVM where that is the case.

Also, I think a lot of Java developers are agreeing with Bruce Eckel that should no longer try to evolve Java into a functional language, as is getting too complex to change the language without unpleasant consequences/side-effects.

So far on reason Scala is emerging is simply because there is no other suitable contender.

Re: Market support

Your message is awaiting moderation. Thank you for participating in the discussion.

It's very exciting to see that IBM is publishing articles on Scala. I know that doesn't spell endorsement. But maybe it's a step in the direction of one of the big parties that were mentioned above picking up Scala and donating resources and generating momentum in the market place.

I like Scala's typing of methods for instance. Not only because it reminds me of Russells typing solution for self-referential statements from Logic courses in university.

Re: Market support

Your message is awaiting moderation. Thank you for participating in the discussion.

Just for information, on IBM developerWorks you can read an entire column about alternative language for JVM(search "alt.lang.jre").At the moment, IBM is using Jython (WebSphere scripting lang), Javascript (Lotus products) and Groovy (ProjectZero). If you are interested about concurrency/parallelism take a look at X10 language (www.research.ibm.com/x10/).About static typing: it's easy to say that is more fast than dynamic approach but the code that a "normal" programmer use to write is less than the entire running application (e.g. think about J2EE environment) so for middleware like ProjectZero a dynamic lang is good enough and write logic is more "agile".