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.
TypeScript: a language for application-scale JavaScript development
271–280 of 316 posts
Re: TypeScript: a language for application-scale JavaScript development
#272All of these compile-to-JS efforts are great, and as much as I love things like CoffeeScript I have to say I definitely worry about language fragmentation. JavaScript is full of flaws, but its monopoly in the browser space has brought about one intriguing and welcome side-effect: a VERY efficient market for both employers and employees. It's easy to overlook how important this common denominator has been for everyone…
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.
JavaScript has minor flaws but in general when understood it's outstanding. However it's not the style that you've been taught in school (OOP) and that's the problem for many newcomers.
It looks that you're just frustrated with something and want whole world to be as well, it won't work. Try CoffeeScript, it's much more approachable when coming from OOP world, then when you get how JavaScript works and understand it makes sense, you'll be ready to program in it directly.
Re: TypeScript: a language for application-scale JavaScript development
#273Re: TypeScript: a language for application-scale JavaScript development
#274Re: TypeScript: a language for application-scale JavaScript development
#275Re: TypeScript: a language for application-scale JavaScript development
#276Re: TypeScript: a language for application-scale JavaScript development
#277var x = "lol" - error found : http://pastebin.com/R1wqp0CS var x; x = "lol" - accepted : http://pastebin.com/0vc68RbY
Re: TypeScript: a language for application-scale JavaScript development
#278Earlier quoted context omitted.
Roughly the same story here. At the risk of sounding like a fanboy, I feel that while most tech BigCos (e.g. Google, Apple) have become more evil over time, MS has actually become less evil, to the point that using their tech (and some major tech at that) is relatively free of any lock-in risk. TypeScript seems very much in line with this trend, and I love it. This is exactly what I wanted - JavaScript but with decen…
Magic strings can be avoided by always using a viewmodel ,using the lamda overloads on HtmlHelper (@Html.*) also T4MVC is a godsend strongly typing routes, url lookups, viewnames, filenames. Most of these have been around since MVC 1.0. Hope these pointers will keep you magic string free :)
Re: TypeScript: a language for application-scale JavaScript development
#279Earlier quoted context omitted.
The language itself is broken, especially when it comes to equality, type coercion, `arguments`, and Date processing.
I think you mean, when only looking at those things. Outside of hoisting, you just listed all of the issues. Even hoisting is only an issue when you start polluting the global namespace.
Re: TypeScript: a language for application-scale JavaScript development
#280Earlier quoted context omitted.
Interesting. On Microsoft's own site they have http://support.microsoft.com/kb/93362 which does not list 4.0. I see 4.0 listed on the page. It's right at the bottom -- twice.
Yes, they list the advice in the article as applying to NT 4.0. And the advice on access controls does apply there. But the only sentences stating that specific versions have actually received C2 type certifications are in the summary. And the statement there is that 3.5 was certified as of 1995 in the USA, and 3.5.1 was given a E3/F-C2 rating in the UK. Nowhere in that article does it say that any version of 4.0 eve…
"SAIC's Center for Information Security Technology, an authorized TTAP Evaluation Facility, has performed the evaluation of Microsoft's claim that the security features and assurances provided by Windows NT 4.0 with Service Pack 6a and the C2 Update with networking meet the C2 requirements of the Department of Defense Trusted Computer System Evaluation Criteria (TCSEC) dated December 1985." [1]
Anyway isn't all of this missing the point that the TCSEC C* requirements didn't really amount to much anyway? It's a pity no general purpose operating systems were ever evaluated to A1 criteria, and that that the Common Criteria haven't lead to systems like EROS/Coyotos/Capros receiving more development attention.
[1] http://web.archive.org/web/20060503192159/http://www.radium....