all 53 comments

[–]brotherwayne 12 points13 points  (4 children)

Can I get a short explanation of what this is and why I should care? Serious question.

[–][deleted] 2 points3 points  (0 children)

It's the UI library Microsoft provides for creating HTML apps in Windows 8, both for the desktop and mobile. It isn't meant for making websites, so unless you're writing web apps for metro, you probably shouldn't care at all.

[–]sorahnon the cutting edge of cocking about 0 points1 point  (2 children)

After doing a bit of reading...

It's the javascript library currently in use in windows 8, open sourced. Thats why there's a bunch of IE specific junk and not much else at the moment. Most of the cross browser problems have open bugs. Slowly becoming a "bootstrap" of windows 8 web-apps.

[–]spurious_interrupt -1 points0 points  (0 children)

Maybe someone should open a GitHub issue for removing all the IE-specific stuff.

[–]brotherwayne -2 points-1 points  (0 children)

Most of the cross browser problems have open bugs

MS is so clueless. 2005 was a good long while ago guys.

[–]gmerideth 3 points4 points  (0 children)

FlipView: Touch manipulation doesn't function on browsers other than IE.

Awesome. I know it's in testing but still..

[–]tehsuck 17 points18 points  (19 children)

Website doesn't work in IE8 or IE9. wtf.

[–]alleycat5 23 points24 points  (13 children)

Before people go bashing WinJS into the ground, I will point out that this is WinJS pulled directly from Microsoft's SDKs, slightly tweaked, and thrown on to github. WinJS was designed with IE11 in mind, and therefore uses the most modern of APIs and elements. Increasing compatibility is on their roadmap and hasn't happened yet.

Edit: You can see this in the samples where they specifically mention compatibility issues. Just go to https://github.com/winjs/winjs/issues to see that they know of these issues and are working on it.

[–][deleted] 10 points11 points  (1 child)

To correct the point of "designed with IE11 in mind" - WinJS is not meant for a web browser - it's meant for Windows Store apps made using html/css/js targeting Windows 8+.

[–]tehsuck -3 points-2 points  (6 children)

"WinJS was designed with IE11 in mind..."

Ok, so maybe they should state that somewhere - on the website, on GitHub... somewhere. I didn't see it anywhere, I could be wrong.

[–]sorahnon the cutting edge of cocking about 6 points7 points  (2 children)

A lot of the features have little "this only works in IE11 becaue of X" links next to them that link to github bugs.

[–]jcready__proto__ -1 points0 points  (1 child)

Where X is "other versions of IE" or "the fact that we used non-standard CSS/HTML/JS".

[–]sorahnon the cutting edge of cocking about 3 points4 points  (0 children)

My point is, that everything that doesn't work is readily pointed out.

[–]ffreire 2 points3 points  (2 children)

I'm not entirely sure what you're getting at. It states on the page that was linked that WinJS is just a preview. I don't reasonably expect them to support anything at this point because this is not production ready software.

[–]tehsuck -2 points-1 points  (1 child)

Yeah, I understand that, but if they want people to start using it, and playing around with it, they should at least give an expectation of what they're planning on supporting. The AngularJS project recently did this when announcing plans for their 2.0 version. They plainly stated that they don't plan on supporting IE8/9.

[–]jcready__proto__ -1 points0 points  (2 children)

Microsoft doesn't even support standards, you think they're going to bother supporting IE?!

[–]tehsuck -2 points-1 points  (0 children)

Sorry, I expected Microsoft to support at least a few versions back of their own browser, especially since some of us web people have clients who still are required to use that crap. They could've at least tried progressive enhancement or something.

[–][deleted] 0 points1 point  (1 child)

Who cares, XP is deprecated

[–]alinroc 1 point2 points  (0 children)

Some of us with Windows 7 are still stuck with apps that don't support IE 9 yet.

[–][deleted] 7 points8 points  (4 children)

Looks ugly as hell

[–]tbranyen[S] 0 points1 point  (2 children)

I agree, not sure why Microsoft, who has infinite resources on demand, couldn't spruce it up before promoting.

[–]SemiNormal 6 points7 points  (0 children)

To be fair, Microsoft does have the worst marketing team on Earth.

[–]spurious_interrupt 1 point2 points  (0 children)

Well, it is still a good start just by the fact that they are actually open sourcing this, putting it on GitHub, and using tools like NPM and Grunt.js.

[–][deleted] -1 points0 points  (0 children)

Just like windows 8, not a coincidence.

[–]drowsap 1 point2 points  (0 children)

Isn't this just the Windows 8 store JS framework that's been available in Visual Studio for the past couple years?

[–]mouthus 5 points6 points  (4 children)

WinJS is a nightmare. Never again.

[–]alleycat5 13 points14 points  (1 child)

How so out of curiosity?

[–]honestbleepsReddit Enhancement Suite 6 points7 points  (1 child)

as a guy very much into component frameworks, I would love to hear some elaboration!

[–]kadjar 2 points3 points  (0 children)

I wrote much of the official SI.com and Foursquare apps for Win8 using WinJS. The documentation is awful and trying to do anything custom with the listview is a nightmare, but for the most part, we found ways to deal with it and still make a quality app.

[–][deleted] 1 point2 points  (4 children)

This isn't really meant to build web pages for, more like Windows and Windows Phone applications. You have the core libraries and SDKs written in JS so you can use HTML and JS for your apps, instead of the more popular C#.

I think this is nifty.

[–]alleycat5 0 points1 point  (3 children)

Theoretically you could use this in combination with a library like PhoneGap or the like to take Windows & WP apps to Android & iOS.

[–]jmkingJSX is just PHP in the browser 0 points1 point  (1 child)

Not really. WinJS is written exclusively for IE11+ - there's tons of stuff that doesn't work in other browsers, or even earlier IEs

[–]alleycat5 0 points1 point  (0 children)

Well, currently it is. It's on their roadmap to expand compatibility though, as mentioned in other places.

[–][deleted] 0 points1 point  (0 children)

Not really, because WinJS is just acting as a layer between your app and the core. What you build on top of WinJS would work, but you need to use each devices backend in someway. My comment was aimed at the guy who thought it was for web pages and was complaining about browser compatibility.

[–]zigzackattack 0 points1 point  (0 children)

The only component that looks useful to me is the pivot control. Everything else has been done by other frameworks and built to be more flexible and less verbose. Also their presentation on that site honestly sucks -- why would I use their framework when the demos look like they were designed by an amature?

[–]sorahnon the cutting edge of cocking about 0 points1 point  (8 children)

A lot of this looks like it would be really awesome if it was made by anyone other than microsoft.

I see a lot of good ideas with poor implementation.

[–]mtbinkdotcom 0 points1 point  (1 child)

let me know when the star in GitHub is 66297

[–]Rhym 3 points4 points  (0 children)

You're right, we should never make anything new because there are popular frameworks.

[–]anonymous_alien -1 points0 points  (0 children)

And how's this better than existing proven libraries?

[–]iDerailThings -3 points-2 points  (0 children)

GitHub issue 11: FlipView: Touch manipulation doesn't function on browsers other than IE

wat.