Comment Obviously wrong (Score 3, Insightful) 108
This is so obviously wrong. I don't believe TIOBE for a second.
If this was true it should correlate with stuff like number of github projects and job offerings.
And it just doesn't
This is so obviously wrong. I don't believe TIOBE for a second.
If this was true it should correlate with stuff like number of github projects and job offerings.
And it just doesn't
I also think that there are companies that are closer to the goal of delivering a personalized cancer vaccine.
E.g. Evaxion https://evaxion-biotech.com/ho...
Often a new technology will disappoint in early trials. I think it is too early to dismiss this. If it works it will be groundbreaking!
And guess what? Skepticism is the foundation of actual science - if you claim it's "settled", it isn't science.
Science is about looking at the facts - settled doesn't mean consensus. Some people still belive the earth is flat - and I hope we can agree that that matter is settled.
I preordered one from this kickstarter: http://shop.keyboard.io/
I have been a ergo keyboard nerd for years - looking for the next rethink.
Of course it has no caps lock. But you could get once, if you really really want to.
Stop manipulating the DOM. It is too brittle.
Better to leave that to something like React.
That gives you a much better level of abstraction as a developer and better performance.
Why is it that they keep having two so similar versions of Gnome? I can't really tell the difference.
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/
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...
Well a quick stat on indeed.com suggests that I am right in mentioning scala over what you suggest:
http://www.indeed.com/jobtrend...
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.
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.
Generating HTML on the server is more or less outdated.
So a "web language" on the server doesn't make sense, the way it used to do (like perl cgi, ASP, JSP, PHP and decendents)
What you do now is write the frontend in one of the new JS/HTML frameworks that run exclusivly on the client.
AngularJS is popular and will likely stick around in one form or another. But pick any you like.
For the backend you want to expose REST services, that serves the content in a way that is easy to digest for the frontend (so you don't end up with too much logic out there).
For that I'd recommend taking a look at Scala (10 years old, and not going away) and the Play Framework (http://www.playframework.com/)
What is nice about the Play framework is that it not only makes it easy to expose REST services. It also makes it easier to deploy the client side framework.
Also take a look at using microservices. Using that architecture enables you to write the REST services in smaller components, rather than one big server. That way you can more easily replace each service, when you want to migrate to the next backend technology.
The book that had the greatest influence om me was Domain Driven Design, by Eric Evans.
It really made the difference from thinking like a developer, to thinking like an architect (I still write code every day)
And how much space would you imagine passing a reference to an int would save, compared to just passing the value of the int?
LinkedIn uses it for their mobile backend.
But I more than suspect that the mobile backend is just a simple frontend to the real backend. And that is written mainly in Scala.
As far as I know the closest thing to node.js in Scala would be something like Finagle, which they use at twitter:
http://twitter.github.io/scala_school/
For my current hobby project the backend is written in Scala, Akka and Play! - though I am considering replacing Play with Spray, since all the backed does is serving JSON from REST services.
I have five kids (three are adopted, so no preaching about overpopulating the Earth). Add the wife, and I need a vehicle to carry at least seven people. Good luck finding a 50 MPG car that can do that.
In Europe you could buy a Citroen C4 Grand Picasso, that has 7 seats and in the most economic version does more that 57 mpg.
That mileage is nice, since a gallon of diesel costs more than 7 usd around here
Anyways you guys need to wake up. That 2025 technology exists today, just buy it.
He who steps on others to reach the top has good balance.
