|
And Douglas Crockford sayeth: https://plus.google.com/118095276221607585885/posts/MgzNUSTwjRt[^]
Quote: Microsoft's TypeScript may be the best of the many JavaScript front ends. It seems to generate the most attractive code. And I think it should take pressure off of the ECMAScript Standard for new features like type declarations and classes. Anders has shown that these can be provided nicely by a preprocessor, so there is no need to change the underlying language.
I think that JavaScript's loose typing is one of its best features and that type checking is way overrated. TypeScript adds sweetness, but at a price. It is not a price I am willing to pay.
PS: the comments on Crockford's G+ thread are fantastic. Lots of interesting insight.
Director of Content Development, The Code Project
modified 2-Oct-12 22:52pm.
|
|
|
|
|
OK, so why do I think JavaScript sucks? Well first off, as an enterprise web application developer, I don't like any scripting or dynamic languages. I like code that compiles for lots of obvious reasons. It is messy to code with and lacks all kinds of modern programming features. We spend a lot of time trying to hack it to do things it was never really designed for. Ever try to use different jQuery based plugins that require conflicting jQuery versions? Yeah, that sucks. Maybe we should all go back to FORTRAN...
|
|
|
|
|
I have to agree that JavaScript sucks. I think there is still a place for inline code, but JavaScript does not play nice in HTML. It also is a very different language than what Web programmers tend to program in, which is Java or C#. It is also true that JavaScript was not designed for what it is used for. I do not think that it not being a complied language is neccessarily bad. In fact it might be good since do not have to worry about the platform, and the executed code is human readable. What would be much better is being able to organize the code as one does in C# and Java where classes are put into files, and objects are supported (which both C# and Java developers are familiar with). This could be managed by the development environment packaging the code in the web page when deployed, or having it included when sent to the client.
Read article about TypeScript, and it sounds really good.
|
|
|
|
|
With Java SE 8, Oracle will not have Project Jigsaw's modularity capabilities, which will be postponed until Java SE 9. Java Development Kit 8, though, which would be based on Java SE 8, will feature Project Nashorn capabilities for JavaScript programming. "This is a modern implementation of JavaScript that runs on the JVM," said Georges Saab, Oracle vice president of development. Cloud features have been postponed, but that's just a passing fad anyway, right?
|
|
|
|
|
Information has come forward to Windows Phone Central that demonstrates Microsoft does have their own Windows Phone hardware in the works; in fact, we’ve heard it already exists and is in testing. The source(s) are known to us and not anonymous, though for obvious reasons we must keep them off the record. Details about what it looks like, hardware specifications, launch times, etc. have not been shared with us by the person(s) who have provided the information. The only thing we do know is when compared to current WP8 hardware it’s something unique. What could Microsoft do to make a "unique" smartphone?
|
|
|
|
|
To celebrate this milestone guide, we asked the leaders in computer science to share their thoughts about The C Programming Language. Read on to discover what Bjarne Stroustrup, David Patterson, Andy Tanenbaum, and many others have to say. One of the most important books ever published in computer science?
|
|
|
|
|
Yeah, in concert with "The Art of Computer Programming" by Donald Knuth, these two are definitely in A-list.
|
|
|
|
|
The algorithm for merge sort is based on the idea that it’s easier to merge two already sorted lists than it is to deal with a single unsorted list. To that end, merge sort starts by creating n number of one item lists where n is the total number of items in the original list to sort. Then, the algorithm proceeds to combine these one item lists back into a single sorted list. The merging of two lists that are already sorted is a pretty straightforward algorithm. Here's how it works.
|
|
|
|
|
A few weeks ago Microsoft silently launched a new home page. It was meant to be a temporary launch for the purposes of some preliminary testing. But as fate would have it, it became the talk of the Internet. Twitter was abuzz with opinions. Several blogs and online news sites, including The Verge, wrote about it. And, the reviews were overwhelmingly positive. The new Microsoft.com home page is designed with a multi-device future in mind.
|
|
|
|
|
|
That is for Indonesia. When you believe what you read, make sure you know what you are reading.
Worldwide the picture is VERY different.
The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo
|
|
|
|
|
Quote: That is for Indonesia. He says that specifically in the article. In fact, that is what the article is about!
Quote: make sure you know what you are reading ...precisely!
- Life in the fast lane is only fun if you live in a country with no speed limits.
- Of all the things I have lost, it is my mind that I miss the most.
- I vaguely remember having a good memory...
|
|
|
|
|
I was just trying to make sure that was clear to CodeProject users that didn't click on the link and read the article. It floored me when I read that and was wondering in what context that is true.
The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo
|
|
|
|
|
Expert Coming wrote: Worldwide the picture is VERY different.
Might want to try reading the article more closely...the point was that it can vary greatly from place to place, and that you should know the statistics of your target audience.
|
|
|
|
|
Might want to not read so closely...
How about I say it this way?
The picture is VERY different from place to place worldwide.
The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo
|
|
|
|
|
Expert Coming wrote: How about I say it this way?
The picture is VERY different from place to place worldwide.
Again, that's exactly what the article is saying.
|
|
|
|
|
Exactly. The article talks about statistics.
Wonde Tadesse
|
|
|
|
|
|
That's exactly his point.
Looking at world wide statistics isn't good enough if you don't know your target demographic.
|
|
|
|
|
I don't know who voted you down, but there are some really good information in this article. I always like to point out that billion does not necessarily mean a thousand million, but (and this is much more logical in bi-million means 2-millon) can also mean a million million, or a thousand times what some people think that billion should mean.
|
|
|
|
|
Clifford Nelson wrote: I don't know who voted you down Certainly few people among nine million CP members. I thought it's interesting and want to share with the members.But who ever did, he/she must a good reason.
Clifford Nelson wrote: I always like to point out that billion does not necessarily mean a thousand million ... You are right, The article talks about statistical output. It may be a wrong generalization based on certain data.
Wonde Tadesse
|
|
|
|
|
What is the Challenge? To write an Ultrabook enabled Windows 8 application and have it posted on the Intel AppUp store by December 1, 2012. That's a total prize package for the big winner of $31,000, plus additional promotion and visibility for you and your app, plus you are sent an Ultrabook! Get your Ultrabook enabled Windows 8 app in the Intel AppUp store and win.
|
|
|
|
|
You often hear people advocate that writing tests (unit, functional, etc.) when building software leads to less bugs in production. How can one verify this statement? Usually, those people are already using TDD or BDD and might be working for companies that have a strong testing culture from day one. Then, how can one measure the impact of NOT writing tests? How can we verify that practicing TDD is actually producing less bugs? Can we stop writing tests for a period of time and look at the consequences it has on the defect count? That doesn’t seem very realistic. Let's test our assumptions... and our code.
|
|
|
|
|
Terrence Dorsey wrote: Let's test our assumptions... and our code.
The way I read that graph, the number of bugs in the UI became less simply because the product matured and there were probably fewer UI implementations. Furthermore, the graph is misleading - it's a ratio of server to UI bugs. This gives one absolutely no indication of the actual bug counts, which would have been a lot more telling.
So, the moral of the story is - don't let a UI designer play with statistics.
Marc
|
|
|
|
|
In addition to supporting industry-standard programming languages, such as C++, Python, and JavaScript, Microsoft has always been at the forefront of creating great programming languages – Visual Basic, C#, and F# being the most recent examples. We create programming languages to solve problems and to enable a broad set of people to build software. Today, we’re introducing a new programming language that solves a very specific problem – getting JavaScript development to scale. That language is TypeScript. What's next, typeQuery, a strongly typed jQuery alternative?
|
|
|
|