TypeScript: a language for application-scale JavaScript development

Post by mcosta » Tue, Oct 02, 2012, 10:25 AM UTC

edwinnathaniel wrote: post #265

georgemcbay wrote: post #60

Earlier quoted context omitted.

JavaScript is forever stuck in design-by-committee hell, which dooms it long-term. Developers who do nothing but pure JavaScript and don't at least play around with the other options (Dart, TypeScript, Haxe, CoffeeScript, et al) are just going to be hurting themselves long-term. It is always a bad idea to tie yourself too strongly to any single language.

Conversely it's a bad idea to spread yourself thin in multiple languages but master of none. Having said that, I'm pretty much tied to Java since 2000 and haven't seen anything wrong... yet. In fact, I'm determined to get better in Java everyday (memory model, JVM, concurrency, better design, etc). Side note: I'm also learning pure "modern" JS just because there's no choice on the client-side.

Post by marknutter » Tue, Oct 02, 2012, 12:09 PM UTC

esrauch wrote: post #251

aaronblohowiak wrote: post #125

Earlier quoted context omitted.

The language itself is broken, especially when it comes to equality, type coercion, `arguments`, and Date processing.

Equality (and that portion of type coercion) is pretty much solved by using === and the rest of type coercion is solved by only using + when both sides are numbers or strings. I don't see how that gets as much ire as it does

Post by PommeDeTerre » Tue, Oct 02, 2012, 12:22 PM UTC

pacomerh wrote: post #108

camus wrote: post #57

Earlier quoted context omitted.

Javascript is dreadfull , and its flaws are counter productive and intolerable. It has good things like closures and first class functions , and that's it. Most of js developpers hate javascript , but are forced to work with it. So they dont care what they use as client language provided it gets the job done. few people cares about Javascript. most of the devs hate it. But the browser as dev plateform is a fact.

Nah, you're generalizing. I know many JS developers and they all love Javascript in one way or another.

Post by nkohari » Tue, Oct 02, 2012, 1:23 PM UTC

skrebbel wrote: post #233

nkohari wrote: post #219

Earlier quoted context omitted.

Trust me when I say that if you use .NET, you're always going to be stuck with Microsoft. Mono, the only other somewhat viable implementation of the CLR, just doesn't really cut it in practice -- at least for ASP.NET.

hmm, mind sharing why? My limited Mono experience was that getting a simple ASP.NET application running on a Linux VPS was, without prior Mono experience, one hours' work. I was pretty impressed by this.

Post by [deleted] » Tue, Oct 02, 2012, 1:44 PM UTC

masklinn wrote: post #268

wingspan wrote: post #91

Earlier quoted context omitted.

Yes I see what you mean, it'd be interesting to see what the exact rules around type checking are; especially when dealing with []. The string type for example, always give you a string when indexed, even when incorrect: var s = 'foo'; var l = s['length']; // type of l is `string` I also agree about non-nullable types, and I've found even with TypeScript, having to make sure your vars are defined and not-null is stil…

> var s = 'foo'; > var l = s['length']; > // type of l is `string` beg pardon? $ js js> var s = 'foo'; js> s['length']; 3 js> typeof s['length']; number $ node > var s = 'foo'; undefined > s['length']; 3 > typeof s['length']; 'number'