shaydoc

This is such a nonsense article. But within it there is grain of truth albeit very small.

Taking my circle, several of my family have migrated to iPad or android tablets from PC/laptop setups and are not looking back because iPad fulfills all there computing needs. For me, my laptop recently passed away so I bought a nexus 7 to replace it, and you know what its brilliant for me. I do obviously still have a development PC, but for personal use its tablet all the way. So I think desktops and PC sales will suffer loss long term in the consumer market. So Microsoft do need a good product here, and they have a lot of catch up to do, but they have done it before!

The security blanket for Microsoft remains new innovation enterprise, business and maybe cloud. I think they have a long way to go to win back the consumer space.

Recently downloaded your webapi pdf, it was a very good primer. Have recently been building a spa architecture, and purely restful back end webapi. Frontend pure HTML/CSS/js ( sammy for routes, knockout for databinding amplify for store, pub sub mediator and request!)

Another great tech company!

Got to say, disqus is great!

Yip, awesome!

Thanks Microsoft, after fixing the image/screenshot, to remove the alleged "offensive" image/news item, "Hacker8News" is officially live in the windows store...it implements both search and share charm functions!

Turns out the failure reason is quite funny, they pointed me to a screenshot I had created of the application for advertising in the store, it is basically a point in time image of what's trending,

one of the articles trending was : I amlost feel obligated to pirate Office for Mac ! http://rys.sommefeldt.com/2012/10/01/i-almost-feel-obligated...

I am appealing it, furthermore, there is a little Substance to this in that it demonstrate s the absurdity of the current approval mechanism.

I am a member of this community and I wanted to share an experience, so please lay off with the antagonism.

P.S. I am not bothered one way or another with 'the game', just trying it out for fun!

Yeah, maybe, I think the Win8 approval process probably leaves alot to be desired at the moment, all things considered.

I am surprised by the crassness of the failure reason, the app evaluation obviously has no "context", very production line!

Javascript is certainly addictive and fun to program with. Obviously the driver is, that it is part of every browser, and now the server. While flawed, it is so very expressive as a language. I think now that we are seeing some serious architectural concepts implemented and documented in the various libraries, it is making development much easier and faster.

I recently discussed this with a colleague, and we agreed, that the ability to do JavaScript client and server (node) side has made it a no brainer, end to end javascript over RESTful services is the best way for "us" to go.

I like that in windows 8 you can reference class libraries written in c# directly in your is project also.

So I see a bright future for JavaScript :-)

Its more like, a user interface that helps beginners, than a beginner's user interface. It's the first iteration of a UI that will improve and evolve. I really like it, particularly the emphasis on consistency in the metro app design guidelines. I like the search and share charms, the live tiles also work nicely. The emphasis on typography, space and no app chrome may not be new, but it certainly feels new and fresh on an O/S. The touch screen design guidelines are also well thought out, a simple example being the placement of common actions on the bottom right of this the screen when you swipe up, easy reach for the old right thumb! Regarding the hybrid desktop/metro situation, I think that is much ado about nothing, things can still be pinned to the task bar, I am not crying at the loss of the start menu.

Congratulations on this news, that's great to hear, you have the opportunity to evolve typecast! Good to see a tech company from northern Ireland doing well!

yeah, you could almost validate reincarnation with it, by searching for past lives ;-)

I think Apple should just stick with innovation and pioneering great new products that made them insanely huge as a company. It would also serve them better than the lawsuits, there are always new markets to be created!

I would say 100% pair programming would be a highly draining experience! may result increased productivity, but at what cost!

I was only referring to your bad "pair programming" experience, in that you felt it held you up from actually getting stuff done, that's just wasted effort.

However, my experience is that pair programming would work well in a senior/not as senior pairing, with the caveat, you need to have capacity on your projects to roll with this also technique.

regarding you choosing to sweat on your startup, fair play thats your choice, and possibly a good one if that's what you are passionate about. hopefully your end goal/mission is not just to make loads of money though!

then you need to confront your situation and resolve it satisfactorily, because staying in late to get your "real" work done is means to an end, remember you have a "life"!

ya see, this is what I don't get about capitalism sometimes.

I mean what do you do with such an astronomical figure of money like that as an individual ?

or you could use http://developer.yahoo.com/yql/console/

"there ain't no money in poetry, and that's what sets the poet free"....

Nice work, i must invest some time looking into angular, your article is convincing

This is interesting on first glance. It does look similar to knockout.js, with a little Reactive Extensions behaviour also thrown in for good measure!

I have done alot of knockout.js work recently and I love it. Also really like sammy.js and amplify.js.

What advantage would anyone say AngularJS has over KnockoutJS ?

It may disgust you, but Microsoft deserves its place at the table, Microsoft were there right at the start competing with Netscape, and that was a good thing healthy competition in browser development. And didn't Microsoft win their battle with Netscape. In turn hasn't that inspired Mozilla to come back fighting with Firefox and didn't that lead to chrome et al, not forgetting opera and safari and others. I rest my case for big softie.

thanks for taking the time to have a listen, I agree with you on getting them produced a bit better also!

I love audacity, it started me and my bro off on our music recording road. My bro recently produced his album with it! "Shaky Horse" http://declandoherty.bandcamp.com/

Good to see d3.js on the Hacker News first page, I have recently been looking at this, just because it looks so cool.

One of the triggers for me investigating this library, is that I have been looking at some ideas for creating nice visualizations of the world bank data, http://data.worldbank.org/developers/ , mainly for personal interest and learning.

Alot of stuff to get the old noggin' around, but ya gotta start somewhere.

I am not past anything, I am just saying this paradigm is now kinda defunct to me. I would prefer to work a little differently.

No doubt MVC facilitates all of the above, if you favour strongly typed, then that's good, continue that way, but its not necessary ( controller is now basically going to be a restful web service )

"We can already serve JSON or XML data off controller endpoints in MVC3" - true, and you'll probably be using Web API to do that soon.

I am just saying its not necessary to mix, I feel it over complicates the client by making you mix serverside logic a la razor, webform whatever.

I don't particlarly see the point in it now though. If you look for example at the knockout mapping plugin for knockout js, it will take a json source and automatically resolve into your js viewmodel. so on the client all I am doing is thinking about the client. give me a rest api and some json objects and I am off and running.

All I am simply saying, Pure Html/CSS/JS can be done without the need for any knowledge of the server on client side, just the interface contract and like I say a restful wcf service / Web API is good.

I am not an "out lier" when I say I think its a good way to develop, its my opinion. The truth is, I did refactor a load of "webforms" lately and the result was,

1. Html/Js/css - knockout.js and amplify.js

2. JSON Service ( c# in behind serving the data and validating business rules )

I seen this and I downloaded it earlier this week, it wouldn't build straight off, there were bugs in the script references, also EntityFramework 4.1 wouldn't resolve for me locally (had to add web.config ) , etc, not a great start (no biggie, just saying). Resolved these issues anyhow.

On review, its fair enough if you love ASP.NET MVC, but I really don't like the mixing of the View Logic with the Model in ASP.NET MVC, like I already said keep it clean. From a View point of view keep it decoupled I say, keep any server side code out of there. At the end of the day , I have to agree ASP.NET MVC has got rich resources and it is a great offering for developers, no doubt.

And MVC 4 useS knockout js behind the scenes anyhow, which is really great and personally I think that knockout goes far enough.

The only reason I say this, is because I just refactored about 20 Web Form Views to pure HTML/CSS/js on the client side and turned out I had no need for any server side at all except for the restful service (hidden away in my knockout view model, used amplify.js to abstract the service calls) created on top of my domain model. so I am thinking, why do I need MVC if I have Restful WCF/ ASP.NET Web API. Going this way means I am totally decoupled!

I am much happier building a restful service, knowing that any client can consume this, and I think I am happy building client side anyway that I so choose and not tying myself into ASP.NET MVC unnecessarily.

So here's the deal for me if go pure W3C on the client :

1. No mixing in logic

2. Don't care about the server or server side code.

3. I can mock my backend real easy ( e.g. Amplify.js )

4. I don't need Visual Studio for client side dev.

5. There's a growing wealth of open source libraries

6. Makes me think more about the structure of my server side behavioural domain model.

Anyways, just how I see things..always open to more compelling arguments!

Personally from an ASP.NET perspective, its the same. To me ASP.NET is done. Mixing in server side with client side UI is just wrong, they should be decoupled completely. I want to build a html5/js/css UI. I want to keep it clean and I want to talk to a data service/ or mocked out data service to do what I need. Starting out with ASP.NET, I used to think this is just totally the wrong way to do things! Then ASP.NET MVC came along which was much nicer than all the pain of web forms ( viewstate etc..) , but now as I said already, I want my client side to be written with no knowledge of the server side workings, just plain old html(5)/css and leverage the power of javascript and associated frameworks ( i like knockout.js and amplify.js).

Its the convergence on standards and the sophistication of browsers that really matters. We all use browsers, all the big vendors now are appreciating this, enabling progression to standard presentation technology. Innovative successful businesses are delivering great services and UX using these standards and they are showing the rest that they need to move to keep competing.

Responsiveness and performance are strong drivers for a rich/smart/thick client, there really are very little advantages to a thin client in application terms from a UX point of view.

Managing upgrades is a sinch with browsers, so if you have a sophisticated client side javascript UI its easy to re-release.

All in all, I tend to agree poster here!

content is king! as it always has been. If you have fresh, unique content about your passion, damn sure there are a stack other people looking to find out that information.

As cheesey as it sounds,I personally think you are better off not chasing the money, but fulfilling your mission, be that success or failure and learning from that experience and doing better the next time.