2 ms·
Believe it or not, there's some internal projects done in LISP and Haskell. Obviously there are limits to what you can do. If you work on some new big customer
by cromwellian 13y ago
Believe it or not, there's some internal projects done in LISP and Haskell. Obviously there are limits to what you can do. If you work on some new big customer facing project, it's a lot harder to get a big team of people to agree to use Haskell, but if you are working on a 20% project, it's a lot easier to just use whatever you want.
With Google production servers, there's only a few "approved" languages. I can't just go deploy a Rails app in one of Google's datacenters, for good reason, especially when you consider security.
With app-engine or compute-engine there's slightly more freedom.
- michaelwww 13y agoI worked in Dart for a few months and loved it, but recently had to look for something else for older browser support. I started writing code in TypeScript a few days ago and, face palm, why didn't anyone think of this sooner? Visual Studio with TypeScript and jQuery type definitions gives me most of what I need from Dart (80/20 rule). It's really fun to code with. JavaScript with types feels like a sunny day. I've been complaining a little about Dart js-interop (size and speed) and now feel my instincts were right; if Google doesn't fix js-interop, then I'm struggling right now trying to understand why I should use Dart, unless Google is more clear about a different use case for Dart on the client (Android.) If all the JavaScript 'Ninjas' discover TypeScript and have the same reaction I just did, then Dart is going to struggle on the client because it doesn't operate well in the current JavaScript eco-system like TypeScript does. Someone high up in the company and outside the Dart team needs to make a strong statement about where the Dart VM is going before the window closes.