4 ms·
Neither Mozilla nor Google are particularly keen to faff around designing languages for the hell of it. :) Google needed to ease the burden of hours-long Java/
by kibwen 14y ago
Neither Mozilla nor Google are particularly keen to faff around designing languages for the hell of it. :)
Google needed to ease the burden of hours-long Java/C++ compile times on massive projects. Hence Go.
Mozilla needed a language that was as fast as C++, but safer and trivially parallelizable. Hence Rust.
Beyond these goals, the fact that the rest of the world is excited for these languages is just gravy.
- zobzu 14y agoWell, that makes Mozilla's language goals a lot sexier to a lot of us i believe =P
- nightski 14y agoSeems weird. Google especially is a company that relies so much on programmer productivity & getting things right. Getting them wrong typically means lost revenue. I mean they spend crazy amounts of money on all kinds of projects that have no directly viable monetization scheme, yet for some reason you think it would be weird for them to explore programming languages? Odd.
- neilk 14y agoYou attribute too much to these entities called "Google" and "Mozilla". They're made of people. No executive asks for a new programming language. However at some enlightened organizations, they are willing to let hackers explore radical approaches. At some point, in order for them to become "official" projects, the hackers have to align the language with the organization's goals. But the imprimatur of their creators is unmistakable. In any case, I doubt there is any plan to move everything in Google to Go. They're willing to let the creators and some enthusiasts play around with it, maybe deploy a few apps internally. But for Rust to be a success, Mozilla's going to have to use it extensively in their main product.
- kibwen 14y ago"No executive asks for a new programming language." Not that I think you're wrong, but I think the histories of Javascript and Ada stand as exceptions. :)
- neilk 14y agoHm, you're right. There's also the scripting languages in Office, which were definitely management-driven. They share something with JavaScript - a strategy to differentiate an already dominant platform from competitors. That said, managers usually have little say in defining what the actual language is going to be like or what its other applications will be, because so much has to be deferred to the language designers. Even though Netscape's execs specifically requested a Java-like language, they got something rather different.
- InclinedPlane 14y agoVisual basic. C#. Powershell. F#. Javascript. Erlang. Fortran. Objective-C. All languages developed intentionally by corporations. Additionally, there have been languages developed by committees, such as ALGOL, COBOL, CPL, Haskell, Ada, and many others.
- neilk 14y agoYeah, I admit my comment was not all that well thought out. I was reacting to the usual dumbass theory that $BIG_ORGANIZATION is executing some master plan which explains all of their actions. It explains how they filter and rank ideas, but it doesn't explain why those particular ideas happened to be floating around in their organization. When it comes to things like new frameworks and languages, in my experience, it's usually some employee going off on their own. And the reason why the language is the way it is has more to do with that person's obsessions and interests. They later justify it to the organization by producing results and getting peer buy-in. FLOW-MATIC (ancestor of COBOL), Perl, Java, Sawzall, Go, and Rust seem to be like this. The other pattern is when companies intentionally make a language to compete, or lock-in a developer platform. Now this move really is predictable, and any MBA can draw you a 2x2 matrix showing why Microsoft had to create C#. Likewise VB, PowerShell, F#, and JavaScript. It doesn't mean they are bad languages. But they are often platform specific since their whole purpose is to corral developers into one camp. I don't think Haskell counts at all. That was an academic project amalgamating other academic projects. I don't know enough about the others you mention. Maybe this isn't a useful way to think about programming languages, but I was just exploring the idea by rambling about it. ;)
- cgh 14y agoObjective-C was developed mostly by one guy (Brad Cox) back in the '80s. He was inspired by Smalltalk. He didn't do it on behalf of any corporation that I know of, though he and a partner did try to commercialize it later.
- bmnbug 14y agoF# is so close to OCaml that it hardly counts as being "designed" at all.
- ww520 14y agoI understand C++ project can take a long time to compile. Does Java project really take hours to compile?
- Arelius 14y agoIf any project takes hours to compile, it needs to seriously be refactored.
- kibwen 14y agoRob Pike, on justifying the development of Go: "today's server programs comprise tens of millions of lines of code, are worked on by hundreds or even thousands of programmers, and are updated literally every day. To make matters worse, build times, even on large compilation clusters, have stretched to many minutes, even hours." http://splashcon.org/2012/program/404 http://splashcon.org/2012/program/404
- tedunangst 14y ago99% sure that remark is in regard to C++. If it's about java, then it's just not true...
- zaphar 14y agoYou've obviously never compiled java at google :-)
- ww520 14y agoI think that's because they have a lots of Java code to compile. When there are a lot of GO codes to compile, it will take hours as well. I doubt GO's compile speed is significantly faster than Java. Both of them don't have the dependency problem plaguing C++. It would be interesting to compare the two.
- zaphar 14y agoI'm pretty sure that go's compile speed is significantly faster than java. It's hard to compare though because java compilation is not the same thing. There is the bytecode in the class files and on the fly compilation in the vm. As well as some stuff that happens when the bytecode is loaded and run. A lot of go's compile speed comes from how simple it's syntax is besides the gains it gets from avoiding C++ dependency issues. Java's syntax while less complex than C++ is still complex compared to go's. And it won't have go's parse time savings.
- Arelius 14y agoYou know, I've worked on some pretty large C++ projects, and the only time I've seen an hour long compile time, it was due to some include hell that was pretty trivially optimized.