Programming Languages You'll Need Next Year (and Beyond) 315
Nerval's Lobster writes: Over at Dice, there's a breakdown of the programming languages that could prove most popular over the next year or two, including Apple's Swift, JavaScript, CSS3, and PHP. But perhaps the most interesting entry on the list is Erlang, an older language invented in 1986 by engineers at Ericsson. It was originally intended to be used specifically for telecommunications needs, but has since evolved into a general-purpose language, and found a home in cloud-based, high-performance computing when concurrency is needed. "There aren't a lot of Erlang jobs out there," writes developer Jeff Cogswell. "However, if you do master it (and I mean master it, not just learn a bit about it), then you'll probably land a really good job. That's the trade-off: You'll have to devote a lot of energy into it. But if you do, the payoffs could be high." And while the rest of the featured languages are no-brainers with regard to popularity, it's an open question how long it might take Swift to become popular, given how hard Apple will push it as the language for developing on iOS.
Over at Dice? (Score:5, Insightful)
Over at Dice
But we are at Dice, sir [whois.net]:
Pros: Today's article has more content than the usual Dice front page linkage. Great article if you're not a programmer but feel stymied by the wide assortment of languages out there. Although instead of hemming and hawing before making your first project you're better off listening to Winston Churchill and sticking your feet in the mud: "The maxim 'Nothing avails but perfection' may be spelt shorter -- 'Paralysis."
...
Cons: It barely scratches the surface of an incredibly deep topic with unlimited facets. And when one is considering investing potential technical debt into a technology, this probably wouldn't even suffice as an introduction let alone table of contents. Words spent on anecdotes ("In 2004, a coworker of mine referred to it as a 'toy language.'" like, lol no way bro!) could have been better spent on things like Lambdas in Java 8. Most interesting on the list is Erlang? Seems to be more of a random addition that could just as easily been Scala, Ruby, Groovy, Clojure, Dart -- whatever the cool hip thing it is we're playing with today but doesn't seem to quite pan out on a massive scale
Re:Over at Dice? (Score:4, Funny)
Re:Over at Dice? (Score:5, Insightful)
Re:Over at Dice? (Score:4, Interesting)
There should at least be the obligatory disclaimer "Slashdot is owned by Dice" so that readers can prepare themselves. Presenting it as a neutral article seems deceptive.
I seem to recall Timothy telling everyone that "sponsored" stories would be identified as such. Perhaps it's just a wild coincidence that this article just happens to be from Dice?
Just because a substantial number of Nerval's Lobster's [slashdot.org] accepted submissions are from Dice or Dice properties doesn't mean he's a Dice shill...
Repeat after me... (Score:5, Insightful)
CSS3 is not a programming language. No more then HTML is.
Re: (Score:2)
Re: (Score:2)
No he is not splitting hairs. ... and you will realize: you can not program in HTML, hence it is not a programming language, actually pointing out that ML means 'mark up language' already should made have that clear to you.
Make me an HTML page that calculates 1 + 1
Re: (Score:3)
Re: (Score:3)
ROFL, ...
so you don't even know what 'calculate' means and you want to 'program'?
First there was the void, then there was the word and then there was the light, and the word divided the skies from the earth
Re: (Score:3)
So if you can do a calculation in HTML and CSS, then it is a programming language?
Ok, here: http://experiments.hertzen.com... [hertzen.com]
Ooops.
Re: (Score:2)
Okay, I get it. When you need HTML, you just pull it out of your ass. Well played, sir.
Re: (Score:2)
HTML doesn’t really “do” anything in the sense that a programming language does. HTML contains no programming logic. It doesn’t have common conditional statements such as If/Else. It can’t evaluate expressions or do any math. It doesn’t handle events or carry out tasks. You can’t declare variables and you can’t write functions. It doesn’t modify or manipulate data in any way. HTML can’t take input and produce output. T
Re: (Score:3)
Of course programming language does not include markup language. They're two entirely different things with entirelly different purposes.
Since when is... (Score:2)
Since when is ‘America/Los_Angeles’ a time zone?
Re: (Score:2)
Since interface designers faced with idiots decided "Pacific Time" was too difficult for people to figure out. They've been doing this for a while, actually.
Re: (Score:3)
Re: (Score:3)
Obligatory Programmer Hierarchy image: http://lukewelling.com/wp-cont... [lukewelling.com]
From: http://lukewelling.com/2006/08... [lukewelling.com]
Re: (Score:2)
Re: (Score:2)
CSS3 is not a programming language. No more then HTML is.
True. But for a non-programming language, it somehow manages to present an awful lot of thorny debugging problems ;-)
Re: (Score:3, Insightful)
Re:Repeat after me... (Score:5, Insightful)
I've been writing software for a good 18 years now and I've never been limited by not knowing CSS. However, if I reach that limit I'm pretty sure I can pick it up like every other programming or markup language that I've needed.
Re:Repeat after me... (Score:5, Informative)
Sure, but a programmer that doesn't know CSS is pretty limited!
A _web developer_ maybe, but a _programmer_ surely isn't.
Re: (Score:3)
You mean, limited to writing for any platform that uses something other than a web page as its UI (including embedded development, server-side development, regular PC applications, mobile, video games, etc.)? I think I can live with that limitation!
(Actually, even if you do write things that use web pages for their UI, unless you're the "UI guy" you still might not have to know much CSS!)
Re:Repeat after me... (Score:5, Insightful)
Sure, but a programmer that doesn't know CSS is pretty limited!
The fact that you think not knowing CSS will make a programmer limited showcases that your programming experience is limited to front-end development. And that is sad.
Re: (Score:2)
LOL, what?
How does being familiar with CSS indicate that a persons programming experience is limited to "front-end development"?
I can't rightly comprehend the confusion of ideas that would provoke such a statement!
Re:Repeat after me... (Score:5, Interesting)
HTML5 + CSS3 is Turing complete [lambda-the-ultimate.org], which is the usual criteria.
Picking nits...
Re: (Score:2)
It isn't now, but in the future (which is the point, right) it very well could become a language one might call a "programming" language.
Consider the rise of SASS and LESS. We have these now because they are needed modernizations of CSS. At someone point I wouldn't be surprised to see them become a core component.
Scala (Score:3)
I am surprised that Scala isn't mentioned.
It is strongly typed, object-functional and compatible with java.
Swift syntax is basically a cut and paste from Scala, which benefits from being more mature (and having access to all the Java libraries)
Scala is also much faster than erlang, while also supporting the actor based model.
http://www.scala-lang.org/ [scala-lang.org]
Re: (Score:2)
Scala is too advanced for most of the mediocre crowd calling itself "programmers" these days.
Re: (Score:2)
Scala is too advanced for most of the mediocre crowd calling itself "programmers" these days.
Yeah, but so is Erlang...
Re: (Score:2)
Re: (Score:2)
I don't know about that. Scala is getting more and more popular in "Big Data", and it doesn't get more hip than that?
Apache Spark which seems destined to replace Hadoop is written in Scala:
https://spark.apache.org/ [apache.org]
Re: (Score:2)
Well, it can be. But don't try to be too smart and chain everything into one big statement and you'll be ok.
Listen to Odersky here:
http://www.parleys.com/play/53... [parleys.com]
If you want to earn big bucks... (Score:5, Insightful)
Learn C++, Java or C# and get yourself a job at a big corporate.
But hey, if you want to be a hipster coder and dick about all day doing "groovy" websites at some here today gone tommorow startup and earning fuck all by all means go down the web development route along with every other 14 year old school kid.
Erlang? Nice language but too niche. Never really got momentum outside telecoms and its probably too late for it now.
Re:If you want to earn big bucks... (Score:5, Interesting)
That's terrible advice. If you want the big bucks, get into Python, Node.js, or Go and find a startup that just received VC and has tons of money to shove at developers. C++, Java, and C# are great for long-term "comfortable" jobs, but that's not where the seriously good money is.
Re:If you want to earn big bucks... (Score:5, Informative)
Developers in start ups usually are bad paid and baited with stock options.
Re:If you want to earn big bucks... (Score:5, Informative)
That's terrible advice. If you want the big bucks, get into Python, Node.js, or Go and find a startup that just received VC and has tons of money to shove at developers. C++, Java, and C# are great for long-term "comfortable" jobs, but that's not where the seriously good money is.
Terrible advice also. If you want the big bucks, know your shit in several domains, know how to deliver your shit and be good at analytic skills, troubleshooting, design, architecture and project management.
The VC route is a high-stakes one. For each one that cashes it, there are droves that lick their wounds, specially outside of SV.
Going back to languages, no language guarantees good income, not even comfortable jobs. Being able to deliver shit on time, and have deep expertise on something (say, Oracle Enterprise stack, or embedded development), that's where the sweet spot is, meaning, potential to make close to $200K or more, for years, if not decades. Long hours as a consultant, but the rewards are there, and are more predictable and solid than shooting at the VC/startup stars.
Re: (Score:2)
Re: (Score:2)
The thing is, startups pay lousy money, but sometimes you get compensated in stock options, or even stock, and sometimes that stock turns out to be worth a lot later. Granted it's a crap shoot, but there's no safe way to make lots of money unless you already have lots of money, and even then it's not certain.
Re: (Score:2)
Re: (Score:3)
Re: (Score:2)
... which is basically saying the same thing as "Yeah, but then I'd have to work a corporate job!"
Some people like Texas, some people like other places. Some people like the start-up atmosphere, some people prefer being employee #499329.
That said, if you work at a start-up that is already funded, there's no reason you shouldn't be compensated well.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re:If you want to earn big bucks... (Score:5, Insightful)
Re: (Score:2)
Not that I'm knocking "earning big bucks", but it always kinda pisses me off that people talk about compuer programming or a certain type of programming as being especially lucrative, as if that should be some sort of aspiration in life. It certainly pays better than a lot of other jobs that I've had, but how much money you can earn is a pretty shallow metric for success, if you ask me.
Sure, self actualization is probably what really makes people happy, but as far as metrics go it's crappy. Money is quantifiable, thus it's one of the best metrics.
Re: (Score:2)
Re: (Score:2)
Re:If you want to earn big bucks... (Score:4, Informative)
Been doing Erlang for the past 6 years. It is a small niche but the number of people who are really good is minuscule, much less than the demand. As a consequence, I get hit by recruiters for Erlang-related jobs every couple of weeks, with no advertising on my part other than my linked-in page. Looks like the biggest obstacle for the wider adoption of Erlang is the limited number of talent. Lots of companies would like to get into it, but are afraid they won't be able to attract people.
Re:If you want to earn big bucks... (Score:4, Informative)
Any big company that makes an actual, physical device will use C or C++.
Android? Under the hood it's C++. That Medical Device? C++. Your Water Softener? C++. Your thermostat? C. The industrial controller in roller coasters, factories, power plants, and locks? C++. Pretty much every military system out there? C++ (or Ada...). Pretty much every compiler and Virtual machine out there? Under the hood C or C++.
Re: (Score:2)
IIUC, Android under the hood is largely C with some C++ on top of that. True, the part that makes Android different from Linux may be largely C++...
Re:If you want to earn big bucks... (Score:4, Funny)
My water softener is electromechanical. And the designer looks down on you all.
I don't... (Score:2, Insightful)
Re: (Score:2)
If you knew 20 languages you would know there are real differences between where they excel.
Re: (Score:3)
Erlang is overrated crap (Score:5, Interesting)
Please, no more Erlang world domination news.
I went through that 3 years ago already. We had a project that a fanatic asked us to rewrite in Erlang.
it took 9 months with 2.5 people.
Tons of issues, mostly with very lacking library support, tooling. Obnoxious stuck up community too.
In one case, I had a guy tell me online "hire me as an Erlang consultant and then I will help you".
In the end we set screw it (once the Erlang fanatic left).
We rewrote this 9 months of Erlang development in 3 weeks (!) using one senior Java developer.
it worked like a charm and still runs flawlessly in production today.
Erlang = HYPE
Everything is immutable is beautiful for fairy tales, but not for real-life software (trying building a DOM in a language which is 100% immutable).
All modern languages have learned from Erlang's mistake. They do immutable by default, but allow mutable if there is a need for it (e.g. Ceylon, Rust, etc)
Re: (Score:2, Insightful)
We rewrote this 9 months of Erlang development in 3 weeks (!) using one senior Java developer. it worked like a charm and still runs flawlessly in production today.
Then your project was a very poor fit for Erlang in the first place.
Re: (Score:2, Informative)
That's the feeling I got form the original post to begin with. That the Erlang fanatic was basically applying this antipattern:
Golden Hammer
http://sourcemaking.com/antipa... [sourcemaking.com]
Which is a problem rife within our industry...
Re: (Score:3, Informative)
Erlang is pretty cool for the intended application scenarios. It is not really a general-purpose language. If you need, for example, excellent crash-proofness, updates to running code and massive multi-threading, Erlang is what you want to use. (Ever tried to run 1000 threads in Java? I know people who did, for this Java is a completely unusable toy...)
The second problem is that Erlang is decidedly experts-only. Real understanding of advanced programing concepts is mandatory. Don't even think about doing an
Re: (Score:2)
Tons of issues, mostly with very lacking library support, tooling.
Agreed -- not that I know about about Erlang in particular, but library availability, maturity, (and cost) while not a reflection of the language design itself are HUGE factors in whether or not a given project is practical in that language.
In one case, I had a guy tell me online "hire me as an Erlang consultant and then I will help you".
Pretty sure you can find an example of THAT guy in ANY community.
We rewrote this 9 months of Erlang develo
Web = Garbage (Score:5, Insightful)
Next year, the languages you'll need will still be C, C++ and Java. Maybe some C#, Python or Bash. The year after that, you'll still be using C, C++, and Java. Maybe some C#, Python or Bash.
By 2020, the main difference is that you'll be working with machine-learning DSLs and libraries to program/train memristor based devices. But you'll still be using C, C++, and Java. Maybe some C#, Python or Bash.
Re: (Score:2)
And maybe perl. They forgot to mention that slashdot uses it [IIRC]. And TIOBE to compile the stats [IIRC].
http://developers.slashdot.org... [slashdot.org]
Re: (Score:2)
Re: (Score:2)
Plus some Fortran[year] for numerical applications.
So much Fail. Ignore. (Score:2)
When you write code and declare a variable, dynamic languages let you change the type of data held by the variable when the program is running; those languages that don’t are known as “static” or “strongly typed.” Languages such as C++ and Java are strongly-typed languages, while JavaScript, PHP, and Perl are dynamic languages.
"Staticness" and "strongness" are orthogonal properties. Python, for instance, has strongly typed values (you can't convince an int that it's a str), but dynamic variables (a=123;a='foo' is valid). And while C++ is statically typed, I'd be hard pressed to describe something with void* and unions as strongly typed.
TL;DR: Words have meaning. It's OK to disagree about whether a particular language is strongly or weakly typed, but it's not OK to claim that two different concepts are the same thing. When you mak
Re: (Score:2)
Re: (Score:2, Insightful)
Heh, even if you have a variable that *IS* final, you can *STILL* change it's value at runtime.
Java doesn't enforce final at the bytecode level.... It's a compile-time hint and the values can still be modified at runtime.
It's one of the main differing qualities of C++ vs Java. Const is enforced much more than "Final" in Java.
Also C++ templates aren't by-default type-erased like Java's generics. But in C++ type-erasure is a pattern that I can choose to use or not.
Lately I do work that garbage collection simp
Re: (Score:2)
And the whole riff about GC. It makes out like it's superior in all cases.
It does mention refcounting as a subset [which perl does just fine with]. But, even with GC/refcount, you still have to break cyclic links in a tree (e.g. parent node has a list of children and each child points to its parent) when you're done or it will never GC. Also, sometimes you have to do something explicit to release resources (e.g. files) at a given time, rather than some arbitrary time later.
Further, GC is the bane of anyt
Re:So much Fail. Ignore. (Score:5, Insightful)
GC is not about forgetting to free memory. It's about higher level abstraction removing the need for the programmer to do the bookkeeping that the machine can do. Why don't we still program in assembler? Because it's less productive. It's about productivity. As data structures become extremely complex, and get modified over time, keeping track of the ownership responsibility of who is supposed to dispose of what becomes difficult to impossible, and is the source of memory leak bugs. In complex enough programs, you end up re-inventing a poor GC when you could have used one that is the product of decades of research.
The article fails to understand that you can also run out of memory in a program using GC. Just keep allocating stuff without and keeping references to everything you allocate.
Reference Counting is not real GC. Cyclical data structures will never get freed using reference counting.
One of the major, but under-recognized benefits of GC, which the article fails to mention, is that GC allows much simpler ''contracts' in APIs. No longer is memory management part of the 'contract' of an API. It doesn't matter which library or function created an object, nobody needs to worry about who is responsible for disposing of that object. When nobody references the object any more, the GC can gobble it up.
On the subject of Virtual Machines, the article could mention some of the highly aggressive compilation techniques used in JIT compilers. So every method in Java is a virtual call. But a JIT compiler knows when there is only one subclass that implements a particular method and makes all calls to the method non-virtual. If another subclass is loaded (or dynamically created on the fly) the JIT can recompile all methods that call the method such that they are now virtual calls. Yet still, the JIT may be able to prove that certain calls are always and only to a specific subclass, and so they can be non-virtual.
The JIT compiler in JVM can aggressively inline small functions. But if a class gets reloaded on the fly such an the body of an inlined method changed, the JIT will know to recompile every other method that inlined the changed method. Based on the changes to the method, it may or may not now make sense to inline it -- so the decision on whether to inline the method can change based on actual need.
The HotSpot JVM dynamically profiles code and doesn't waste time and memory compiling methods that do not have any significant effect on the system's overall performance. The profiling can vary depending on factors that vary from system to system, and could not be predicted in advance when using a static compiler. The JIT compiler can compile your method using instructions that happen to exist on the current microprocessor at runtime -- something that could not be determined in advance with a static compiler.
All of this may seem very complex. But it's why big Java systems run so darn fast. Not very many languages can have tens or even hundreds of gigabytes (yes GB) of heap with GC pause times of 10 ms. Yes, it may need six times the amount of memory, but for the overall benefits of speed, the cost of memory is cheap.
Fundamentals of Comp Sci (Score:4, Insightful)
Re: (Score:2)
Re: (Score:2)
Swift RT does not have GC (Score:4, Informative)
Swift is a strongly-typed language, that operates inside a runtime with garbage collection.
There is no GC in iOS. Also the GC in OS X is deprecated. Swift uses Automatic Reference Counting which is something... completely different.
Bullshit, as usual. (Score:2)
Next year, unless you are at the bottom of the skill and payment pyramid, you will need C and derivatives (C++, Objective C) and maybe Python or Perl.
My thoughts on these selections. (Score:4, Interesting)
CSS/JavaScript/HTML5 is plainly obvious. Everything from Microsoft to mobile hybrid development relies on this these days.
C# is the standard language of the Microsoft stack --- in fact, the bulk of MS-stack training is in C#, with only a smattering in VB.NET.
Java is the COBOL of the early 21st Century. It isn't sexy anymore but it will always be around.
PHP is used in a lot of web applications. I wish it weren't. In fact, I'd really rather see Ruby on Rails take over this space.
If you're going to program native code, you could learn Swift, sure. You could also learn Rust [cnet.com] (Mozilla's systems-level language with significant buy-in from Samsung) for device programming. If your goal is to write native apps, your best bet for Android is actually Java. By the way, one can also design native apps in Java (the code is Swing-like) and compile them to native apps for iOS or Android using Codename One [codenameone.com], and I imagine a few shops will pick up that practice.
I like Erlang as an honorable mention. I'd also add two others: Python (especially for data analysis) and PowerShell (which will set the grown-up Microsoft sysadmins from the point-and-click kids).
Re:My thoughts on these selections. (Score:4, Insightful)
Trust me, from a guy who's dealt with COBOL and Java, they're nothing alike in either corporate philosophy or boat-anchor of coding. For better or worse, Java and C# are essentially analogs in terms of what you can 'do' with them. Java sucks more in UI's, and some syntactic sugar that makes your life easier, and C#/.NET lacks the trillion toolkits used in Java for pretty much any common need. Many popular Java lib's are ported to .Net, but still a boat load you'll only find in Java land for now. Lets not labor the point. There will be a millions fan boys to jump on the point, but on a language stand point, they're so close that it shouldn't matter.
PHP is a simple language for beginners and it got its entrenched status because some novice PHP dev's wrote some great sites / tools which people have organically grown around. Its a lousy language, and a very specific use case. I've never used RoR, but sounds about the same but in a more sexy buzz word.
Erlang like all functional languages universally are very useful for their very limited number of business areas where they rock, and enevitably the evangelists of these languages always trump out how they're great for everything and the kitchen sink, but we all know they aren't, and will continually be relegated to areas where they shine. Hybrids like Scala have a chance, but frankly I'd hate to sit down and listen to a dev lead's meeting in a scala shop lay down the laws on when to use strictly functional no matter how broken it makes the code, and when to just use other paradigms that probably just work better, simpler, and faster to develop.
The programming language for the next 20 years... (Score:5, Insightful)
C. Plain old C.
Entire Operating Systems are written in it. Userland tools for those operating systems are usually written in it. Any self-respecting developer knows at least C. The rest is just like fashion tips: next year they're outdated.
Although, as much as I hate to admit it, the same could be said for Java...
Re: (Score:2)
Re:The programming language for the next 20 years. (Score:4, Insightful)
But C is a low level language. Not the best tool for writing applications.
Higher level languages and managed runtime systems have gained so much traction for a reason. They are very productive to use. They protect you from simple mistakes. The relieve the burden of memory management. GC simplifies library APIs by making the question of who should dispose of what become irrelevant. We could still be programming in assembly language instead of C. Why aren't we? Why aren't OSes written in assembly? Because C is more productive and higher level. Similarly, there are higher level languages than C, and they have their place. C is not the end all of abstraction.
IT security wanna-bees, take note (Score:2, Funny)
PHP is forecast to be very popular going forward. That means your employment prospects are good!
Laugh at me, but Flash is still relevant (Score:2)
Flash is a lot like C/C++ and Java, except it allows you to a couple things easier.
I think of all the languages though, Java has to be the winner. It has about the power of C/C++, except you don't need to dot the is and cross the ts. Java is superior to C/C++ in strings, garbage collection and arrays. For most projects you'd take code that has less bugs in it and develops faster than code that executes a sl
Erlang is a tough chew (Score:4, Informative)
I spent over two years working every day with Erlang on a project, and I still don't consider myself to be anywhere near an "expert" at the language. It's just too weird and special case for a lot of the functionality I was trying to code, so while certain tasks were easier than they would have been in Java or another procedural-object language, others were damned near impossible and took obscene amounts of time to get working at all -- never mind working efficiently.
Personally I'd avoid it like the plague unless you have some special case need for it's features. Even with regards to concurrency, it's not really any better than any other language's concurrency features. They aren't really baked into the language as the summary suggests, but provided by frameworks in the API libraries, much as they are by other languages.
The main difference with Erlang concurrency is that the concurrent models are the "normal" way to program Erlang, so you're likely to find a lot of good examples of how to do it. I've found the documentation for other language's concurrency features to be somewhat limited in comparison, and less "real world" in their examples.
The main thing that I found neat about the Erlang framework was the ability to specify auto-restarts of failed threads. It takes all of about 4 lines of configuration to get a thread to be persistent/self-starting. That's the densest code I've ever seen for achieving such a task.
The big downside to Erlang is that it's almost as bad as LISP -- everything is a list. Even "structures" are just lists of objects with tags that identify the list indices for accessing the members. Be prepared for a nightmare of tail recursion if you get into this field of programming.
That said, it can be a fun and entertaining language to work with. For the things it is good at, it can be a joy to use. Much as with any language.
Elixir? (Score:3)
Re: (Score:2)
As a long time Erlang proponent I'm finding that Elixir is an easier sell (admitting to liking Erlang's syntax can bring conversation to a standstill) and no less useful. Really a delightful language to work in.
Functional Programming? (Score:4, Insightful)
A functional language is one whereby the functions themselves can be stored in variables and passed around as parameters to other languages.
What in the actual fuck. That may be the worst definition of a functional language I've ever heard. Even if I try to interpret it as something that could make any sort of sense, I just get that storing functions in variables makes a language functional, which the author goes on to debunk by pointing out that C++ isn't a functional language. Why bother even trying to describe them if you have no idea what the hell they are?
Re: (Score:2, Interesting)
You might want to take a look at http://nimrod-lang.org, like a cross platform swift.
Re:I like Swift pretty well (Score:5, Interesting)
The whole point of Swift is its ability to abstract Cocoa. Lots of Swift's specifics make no sense without Cocoa. Given that Swift in practice is going to be loaded with calls to Cocoa, it is going to be as portable as Visual Basic or Bash.
Re:We'll "need" Swift? (Score:5, Insightful)
Need? No. You can still use Objective C if you want to code iOS/OS X. Want? Yes.
And while the rest of the featured languages are no-brainers with regard to popularity, it's an open question how long it might take Swift to become popular, given how hard Apple will push it as the language for developing on iOS.
Apple does not have to push very hard. After looking at it and Objective C, it doesn't take a genius to see why programmers would prefer it over Objective C.
Re: (Score:2)
Scala is interesting and clearly will be somewhere. Swift has the backing of a major platform vendor with a long history of being able to move their platform.
Re: (Score:3)
While there is a need for strongly typed languages, that doesn't imply that all languages should be strongly typed. More to the point, however, Scala appears to be staticly typed (I'm believing documentation here, I've no experience). Many problems are addressed only with difficulty via a staticly typed language.
Compatible with Java. OK. So is Jython, so is JRuby. Object-functional? Not quite sure what you mean, but I would guess that so are Jython and JRuby. Also Groovy.
This isn't really a response
Re: (Score:3)
Well a quick stat on indeed.com suggests that I am right in mentioning scala over what you suggest:
http://www.indeed.com/jobtrend... [indeed.com]
Take a look at Akka. It mostly fits your description for the "language" you want. Scala is pretty extendable, so the libraries often end up looking more like language extensions than libraries.
Scala allows both mutable and immutable objects, but it favours immutable.
In Akka you have mutable state within your actors and pass immutable messages.
Re: (Score:2)
Re: (Score:3)
How do we even know it's going to be popular in the first place? Does it solve any problem I can't do with C# or Python and/or on more platforms?
Considering that you can't really use C# or Python for iOS or OS X development, I would say that's one major thing you can't do.
It'll be a language for little hipsters who hope to be the next Steve Jobs by releasing yet another crappy useless iOS app. I don't know anyone who still bothers with iOS apps.
Then you must not know anyone who uses an iPhone meaning you live in a rather small world.
Re: (Score:2)
There are python development environments/libraries to write 'native' iOS Apps. ...
Easy to google for
Re: (Score:3)
It is not. Strong typing can be implemented by attaching types to data. Static typing always attaches types to variables and they are fixed. But strong typing can also mean type-less variables, but no implicit conversion of values. For example, Perl is weakly typed, but that is because it will, for example, happily convert a string to a number all on its own. Python, on the other hand, is strongly typed, despite its variables not having types just like in Perl. The values assigned to the variables in Python
Re: (Score:3, Insightful)
Re: (Score:2)
Strong/weak is related to checking the type of variable passed as a parameter vs. the formal type of function parameter. For example, old C compilers had weak typing since they had no function prototype requirement, so you could pass a "char *" variable where a function wanted to work with an "int" type variable. Pascal compilers, on the other hand, had very strict typing where you couldn't pass an Integer variable where the function parameter type was Percent (subrange 0..100).
Static languages require the
Re: (Score:2)
If JIT compilation is your definition of "does not run in a virtual machine", then modern Java doesn't run in a VM, either.
Re:Swift maybe, Erlang, really? (Score:4, Insightful)
the iOS development market is dried up for most developers, unless you can get a job at some company that wants an iOS app.
umm duh? i don't understand the point of this. the nurse market is pretty dried up except for some job in healthcare.