|
|
|
|
|
|
by nostrademons
4154 days ago
|
|
|
Here to stay, but may not end up in the software population that you expect it to. I predict that Go is going to be the new Java: after entrancing a bunch of early adopters, it's going to see strong uptake in enterprise IT departments that need a language that isn't too complicated and leads to consistent code that interchangeable programmers can pick up without much trouble. A bunch of enterprise server frameworks will be built that handle the stuff enterprise developers generally need to do: integrations, RDBMS access, message queues, CRUDscreens, simple webapps. The boilerplate and levels of abstraction needed by these frameworks will drive off the initial Go early-adopters, who will find something newer and cooler like Rust or Julia. It's already started to happen: one of my college classmates runs the IT department for a major school district. He's steeped in IBM mainframes, DB2, Cobol, Novell, all these ancient technologies. He's been looking for something to help modernize the whole mess, and last I talked to him, had settled on Go. |
|
|
I differ though in that I think with Microsoft's recent announcements many enterprises will focus their efforts on C#/.NET for their cross platform development over the next few years. Given .NET (along with mono) has already solved the UI and a ton of the integration level issues that Go is either lacking or still maturing on, but either way it will be interesting to see the outcome.
I would also be surprised to see too many large enterprises or government controlled departments like your friends actually using Go as their primary toolset anytime soon. Only because Government's and large businesses usually still "play it safe". I have seen it before someone like your buddy makes a good decision at the director or manager level and goes to get the funding and then suddenly the County govt, School Board or other moron pulls your funding because you are not "playing it safe" with the tax payers money. Then they "what if" you to death and delay projects until you go the "proven" route, if you even get to stay. I don't think he is wrong, just that the outcome is usually outside of one persons control. In those types of environments, for Go to have a majority presence on even new projects it will need recognized training classes, certifications and a bunch of BS that really doesn't matter but makes large businesses and Governments feel all warm inside.
I am sure there are examples showing the opposite, but when measured against the total they are likely just anomalies for now.