Microsoft Build 2014 Day 1 live
channel9.msdn.com
channel9.msdn.com
Windows Phone 8.1
Windows 8.1 (big update)
New Nokia models
Surface 3
I would also not be surprised to see an announcement of an acquisition in the dev space, Xamarin comes to mind but I dont think that will happen (yet).
TS has been in release candidate for some time now, and it feels ready for stable 1.0. I suspect we'll see that announced today.
They're all the same OS (and the same OS release) with names tacked on to differentiate between minor releases.
MS probably feels they are significant enough to keep calling it "Windows 8.1" as the product name. At the same time, Update 1 might be insignificant enough that it's not worth calling it "Windows 8.2".
Xamarin's twitter feed has been kind of quiet today.
Am I wrong?
So, for example, maybe Azure upgrades/SDK changes. Visual Studio updates, .net framework, etc... All the other sessions are deep dives into the tech and how to use it
Windows is a behemoth that needs to support a ton of different hardware configurations, and it can't come out until it works very well on almost all of them. That means a year of development is a very short amount of time for Windows, and they can't add too much to it. Look at Windows 7 vs Vista. It took 3 years just to improve its performance a bit.
It's a little difficult to hear.
edit: Looks like they fixed it now. (2:27:00)
chrome and IE.
I was expecting Herb Sutter or Bjarne giving a talk.
[1] http://channel9.msdn.com/events/build/2014?sort=sequential&d...
And Eric Brumer will present a bunch on compilers and code optimization.
Why? What's wrong with js?
>This rapid growth [of javascript] has outpaced the growth of the language itself, which lacks features that allow teams to communicate requirements and build applications safely.
what? I guess I'll just have to wait for the announcement.
edit: After further investigation: http://www.typescriptlang.org/Playground/
It seems kind of cool, but aren't they just reinventing the wheel?
There are two answers to this: at runtime, there's nothing wrong with Javascript. That's why TypeScript compiles to Javascript. At design time, however Javascript doesn't have features of modern languages. For example, class-based programming. Some of these features are planned for in future Javascript releases, but as a language it's really behind other languages and will likely remain so. This makes large-scale Javascript programs more difficult to maintain.
And there is plenty wrong with JavaScript at runtime. Lack of proper arrays is just one of the many things that come to mind. It's just a convenient runtime because it's good enough and ubiquitous.
they had Jscript.net , refused ECMASCRIPT 4 which was basically Jscript.net, and now come up with Typescript?
And people still trust Microsoft after all this...
but as a language it's really behind other languages and will likely remain so. This makes large-scale Javascript programs more difficult to maintain.
You can thank Microsoft for that. They refused ES4 spec.
Do not forget to thank Yahoo and Google as well.
"Yahoo, Microsoft, Google, and other 4th edition dissenters formed their own subcommittee to design a less ambitious update of ECMAScript 3, tentatively named ECMAScript 3.1"
-- Wikipedia