10 ms·
This. But Go is one in a long line of proprietary languages that those of us who have been around the block know to stay away from. Recently: Java was Sun's, C
by ncmncm 8y ago
This.
But Go is one in a long line of proprietary languages that those of us who have been around the block know to stay away from. Recently: Java was Sun's, C# is Microsoft's, Swift is Apple's, Go is Google's. With any luck, all will be footnotes in ten years. Those of us who knew better than to get invested in them will be fine. Everyone else gets a chance to learn something.
- networkimprov 8y agoSo what would you recommend?
- nicklaf 8y agoAssembler^H^H^H^H^H^H^H^H^HMachine code: http://www.pbm.com/~lindahl/mel.html http://www.pbm.com/~lindahl/mel.html https://research.swtch.com/mel https://research.swtch.com/mel
- saagarjha 8y agoWhat's wrong with C/C++?
- nicklaf 8y agoReal Programmers write in Fortran. Maybe they do now, in this decadent era of Lite beer, hand calculators and "user-friendly" software but back in the Good Old Days, when the term "software" sounded funny and Real Computers were made out of drums and vacuum tubes, Real Programmers wrote in machine code. Not Fortran. Not RATFOR. Not, even, assembly language. Machine Code. Raw, unadorned, inscrutable hexadecimal numbers. Directly. (It's a joke...)
- maksimum 8y agoFor what purpose?
- adrianN 8y agoThere is a mind-boggling amount of Java running around the world and more is still being written. Java won't die for several decades at least.
- airstrike 8y agoJava is a footnote?
- ncmncm 8y agoNot yet. But we can hope. Ten years is a long time in this business.
- meddlepal 8y agoModern Java is a pleasant experience compared to Go.
- grepgeek 8y agoCan you elaborate? In what ways, is modern Java a more pleasant experience compared to Go?
- jacques_chester 8y agoRicher type system, richer concurrency, richer tooling, greatly advanced and advancing runtime, interoperability with multiple languages on the JVM, a naming system that doesn't cause frustrating workarounds a la the Kubernetes ObjectMeta / TypeMeta / "v1alpha1", "v1beta2", "v1" nonsense ... Go is the language that taught me to really appreciate writing things in Java.
- jcora 8y agoLook at what happened to Kubernetes. They rewrote original Java code in Go and it's a mess because of Go's limited abstraction capabilities. Sure there's an element of rewriting in a new language and attempts to force idioms, but there's also the fact that Go literally hacks in special cases for generics, unavailable to users. They recognize the need for generics, but haven't implemented them, which is a problem for a complex project where abstraction might be useful.
- jacques_chester 8y ago
- dtrailin 8y agoEach of the languages you mentioned is wildly popular, well run, and not going anywhere. If you chose not to learn Java a decade ago because you "knew better" you aren't any better off than you were before, given that this language is the core foundation many companies and open source projects, maintaining relevance for 20 years. Not learning Swift now means you won't be able to do effective IOS development. Not learning Go means you're missing out on the language that a lot of important systems software is built in such as Kubernetes and Docker and won't be able to contribute to them. I think also it's inaccurate to call any of these languages proprietary. They are all open source and if you wish you can fork them and make your own. C# in particular is now run by the dotnet foundation which is nonprofit with elected board seats, putting it in a better place for governance than many community driven languages.
- tannhaeuser 8y agoWhether Kubernetes is important for you, and whether Go matters as a language for implementing it is very much the question. Kubernetes was started in Java, and Kubernetes developers themselves describe it as incoherent mess of dozens of daemon programs in various stages of completion in the process of refactoring Java idioms into Go while introducing redundancies due to Go's limited code organization facilities.
- ncmncm 8y agoYou can fork them and become (or remain) irrelevant. Ios development is a walled garden. C# is barely used except to target Windos. Go? Too early to say. If it did fade away, who would miss it, really? Its express design purpose was to be not powerful enough to make big mistakes in. Has it transcended that? If so, what is its purpose now? Java has shown staying power, despite its shortcomings, although its connection to the Apache Foundation ("where projects go to die") offers just a ray of hope.
- Goz3rr 8y agoI write software for embedded Linux devices in C# for a living, not exactly targeting Windows now is it?
- pushpop 8y agoI’m guessing you don’t use C or C++ either then because they were proprietary Bell Labs languages. You should probably rule out assembly too because they will have proprietary instructions for proprietary CPUs. Which means if you really want to be freed from the shackles of using proprietary tools when programming you’re now building your own hardware too, processors and all. Good job ASCII isn’t proprietary otherwise your computing device would have no compatibility with modern computers at all. I know I get a little absurd towards the end but no more so than your remarks about Java.
- ncmncm 8y agoGuess away, but both C and C++ broke out of Bell control very, very quickly by language standards. Now they are driven by ISO Standards bodies, with many, many participants -- ATT not among them anymore, to my knowledge. Even in 1995 ATT had nothing approaching veto power. My remarks lumping Java in with C# and Swift are transparent wishful thinking.
- pjmlp 8y agoThose ISO standards cost 100 euros on average per language version.
- jcranmer 8y agoFor C and C++, you can get effectively equivalent working drafts for free. For C++, you can actually compile the PDF that gets sent to ISO to put the official markings on yourself. Here is C++17: https://github.com/cplusplus/draft/tree/c++17 https://github.com/cplusplus/draft/tree/c++17 . If you have a contractual obligation that requires to exactly use a specific version of C/C++, then you'll need to pay money for the actual specification. In pretty much any other situation, the drafts are sufficient and perhaps even better (because they will have incorporated some errata).
- jstimpfle 8y agoIsn't it that all ISO standards cost money? I'm sure you were perfectly aware of it, but C and C++ working drafts are almost identical (I think? Never bought an ISO version), and available for free from open-std.org. For example, http://www.open-std.org/jtc1/sc22/wg21/docs/standards http://www.open-std.org/jtc1/sc22/wg21/docs/standards
- fathead_glacier 8y agoExperience can differ between companies and languages. I have been involved over the past year with Julia which is mainly ran and developed by the company Julia Computing. One might say that it is the equivalent operating scheme as the companies you mentioned. However, my experience with the community has been vastly different. If you go over the development issues list it is extremely satisfying to see how many are raised by the community and adopted into the language. In contrast to the omnipotent response of Google with the Go community. Having such differences implies that a company ran open source language can indeed be influenced by the community. Having said that, just because it exists in Julia does not mean it can exist in Go. I just wanted to mention that there are exceptions to the rule which begs the question if it is a rule in the first place.
- rincebrain 8y agoC# (and other .NET friends) aren't dying for a while, there's a large base of things written for multiple platforms on it, even though I think Microsoft isn't writing bunches of their core OS components in it. Java isn't dying for a while either - anyone who still needs to support applets aside, or corporate applications written when Java was the fashionable thing to ship apps in, Android's install base will mean it's relevant for a fair stretch yet, even if OpenJDK fell into the sun tomorrow. Swift I don't have much insight into, as I haven't done much with OSX or iOS in a while, and I have indeed not seen much uptake outside of those. Which languages are you suggesting were/are good targets? Python is technically not one company driving it but a bunch of developers on it are employed by large companies to work on it. JavaScript is seeing a bunch of use in a great many places, but originated with one company's implementation and development. Rust is pretty obviously one company's child, even though it is seeing decent uptake from other users. No predictions on whether it would survive said company dropping their work on it, though.
- munmaek 8y ago> With any luck, all will be footnotes in ten years. Java and C# are not going anywhere, especially now that .NET works on OSX and Linux. Swift, unlikely. Go, still uncertain. It's fairly short-sighted to criticize a language and hope it dies out in usage just because a corporation is chiefly responsible for it. [0]: https://dotnetfoundation.org/about https://dotnetfoundation.org/about
- Illniyar 8y agoSwift has garnered little traction outside iOS development, while other languages are gaining traction inside iOS development (javascript mostly, but Kotlin is also trying to make headway into iOS development). I won't put survival rating for it to be very big. I'm sure Apple would keep it for decades to come, but I'm wouldn't bet on it being anywhere near as popular as it is now in the future.
- munmaek 8y agoAs long those languages aren't native, they won't be nearly as popular as swift. Swift doesn't need to be adopted outside of iOS development at all, because when people develop iOS apps the main choice will be Swift. Swift is actually a very pleasant language, and apple provides some pretty good documentation although it could be better. It's going to play out like this: Swift or Objective-C (for legacy codebases/people who already experts in objective-c and don't want to switch), and some other, slower languages that will always be second class.
- cesarb 8y ago> Swift doesn't need to be adopted outside of iOS development at all, because when people develop iOS apps the main choice will be Swift. That would mean its fate would be tied to iOS, which is used only on phones built by a single company. When that company stopped producing mobile phones, or decided to use a different operating system, the language would die.
- munmaek 8y ago
- teddyh 8y agoI agree completely, but good luck convincing people around here; I’ve had no luck for a few years now¹²³. It may be an age/experience thing – you might need to have been burned by it a few times before you learn not to build your house upon the sand. 1. https://news.ycombinator.com/item?id=8733705 https://news.ycombinator.com/item?id=8733705 2. https://news.ycombinator.com/item?id=17162582 https://news.ycombinator.com/item?id=17162582 3. https://news.ycombinator.com/item?id=18370067 https://news.ycombinator.com/item?id=18370067