Slashdot Mirror
Why Apple and Google Made Their Own Programming Languages
Gamoid writes: This Business Insider article looks into the state of Google Go and Apple Swift, highlighting what the two languages have in common — and why tech companies would bother involving themselves in the programming language holy wars. From the article: "One fringe benefit for Google and Apple is that making your own programming language makes recruitment easier — for instance, since it builds a lot of its own server applications in Go, Google is more likely to hire a developer who's already proficient in the language since she would need less training."
From wikipedia
Go's "gc" compiler targets the Linux, Mac OS X, FreeBSD, NetBSD, OpenBSD, Plan 9, and Microsoft Windows operating systems and the i386, amd64, ARM and IBM POWER processor architectures/ A second compiler, gccgo, is a GCC frontend.
So there are two major compilers for Go already, one of which is gcc based which targets just about every platform under the sun. I'm not saying go will run everywhere gcc will compile code because the runtime also needs porting, but it is very cross platform.
I developed one of my command line apps in Go http://rclone.org/ and I release binaries for it which run on Windows, OS X, Linux, *BSD and even Plan 9 all cross compiled from my Linux workstation.
Every man for himself, all in favour say "I"
Anyone who is proficient in Swift has hundreds or thousands of companies outside of Apple looking to hire them. Apple has to compete with every iOS software development shop in the world for those people.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
Of course, C# has a much larger ecosystem, which is also kind of the point.
Of course, C# is also Microsoft's baby, which is enough to disqualify it from use inside Apple and Google all by itself. Nobody at either of those companies is going to risk relying on Microsoft's intellectual property for anything mission-critical.
I don't care if it's 90,000 hectares. That lake was not my doing.
"I'm still scratching my head over the use of "she" instead of "they" in that sentence."
It's Corpspeak. You have to use a precisely equal number of male and female pronouns, even when that means shifting gender confusingly back and forth throughout your Powerpoint presentation. But if your presentation contains a example of bad procedure, you have to use a male pronoun at that point ("If the nurse were to stick his finger in the 220V socket during Step 5...")
Masculine pronouns can be used in the gender neutral sense in English. Feminine pronouns cannot. Posting as AC because I don't want saying obvious fucking truths archived on my slashdot account, thanks to the witch hunts political shitfucks will inevitably engage in.
He means "I tinkered with this new thing and it seemed pretty easy enough, so that was enough - I never needed to use it, so I never found out all the edge cases I know about in the mainstream languages I use every day".
No, that's not what I meant. After spending a week learning Go, I wrote a couple of applications in it, but after the first week I was not learning Go, I was learning libraries and patterns.
Read the Go spec: these is almost nothing to it. The language has ridiculously few features. The main design goal of the language was to make code very readable and maintainable which means all devs basically know the entire language spec.
Don't read the C++ spec. You don't have time for that and it keeps growing. C++ has lots of features, which is both a good and a bad thing, but not all languages are like that.
Very well, actually. ADA is very good at what it does well, which is creating deterministic code that can be procedurally validated. It was created for a design environment that is the exact, deliberate opposite of Agile. If you think you should build once a day or week, then ADA is not for you. If you can not simulate your live environment because it's a thousand miles up in orbit and a bug costs half a billion dollars and 2 years to the next launch window, ADA is for you. If virtually memory machines are a pointless risk and dynamic memory allocation is anthema, then go for ADA. If not, stay the fuck away, because it will make you a grey beard, one way or another.