vinnyp
https://docs.google.com/document/d/1nF8FH-5f-51-Q_Hzt06jhYMN...
I'm wrapping up week 5 tomorrow and I'm down 25lbs (~14% of my body weight)! They promise 2-5lbs of fat loss a week. I generally drop around a pound a day, but I'll get stuck a few days here and there. This method really works for me.
The best part is how fast you lose it. When I did South Beach years ago, it took me months to hit my goal. I have 14lbs left now and I should be able to hit my goal by Labor Day.
Give it a try.
During my time there, I did not see any anti-competitive practices the author is speaking of. Those days are long gone. I know first hand we were committed to compatibility and growth of the platform, new and old. That being said, it's clear that building on Win32 is painful and not cheap. Win32 is great if you want direct system access and complete control over everything, up and down the stack. This works well for large enterprise applications and games. The tradeoff here is that you must roll your own everything and work hard not to do stupid shit.
During the Vista days, we saw that the Windows app ecosystem was struggling because we didn't have a good platform story. You had to choose between Win32 and .NET. If you're a native developer, it was Win32. Win32 didn't provide a great app and UI framework (have you ever tried to owner draw a control or do fluid layout?). This is why many app developers during that time built their own app and UI framework, used MFC or leveraged a 3rd party framework. I was only familiar with the app platform so I can't speak to the options for building a game. I'm sure it was limited as well.
Microsoft introduced many platforms since Vista - WPF, Silverlight, XNA, Win8 Apps (Windows XAML and WinJS), and UWP. I'm sure there are more :) Even with all of those new platforms in the mix, Win32 is still alive and well.
I believe UWP is a huge win for developers. You don't need to roll your own everything. For the companies that want complete control, Win32 is still there. It is true that certain things are only available to UWP developers. There is no malicious intent, it's really only about priorities. The new thing comes first. The developer community needs to speak up if they want something. Microsoft will listen.
This UX pattern does have benefits for the user. It has a low cognitive load with very little friction to show more items. All the UX challenges he calls out are solvable.
In addition, this has been solved on the desktop. File browsers and Media players with large collections already do this well. The challenge is building a great scrolling experience on the web.
I've seen many folks try to solve this with a repeater control and they quickly find out that there's a long way to go to get something with great performance. What's really needed to solve the problem is UI & data virtualization, which is something that native app developers have a lot more experience with.
A bottoms up approach where we put the protocol first instead of experience is the "Architect Astronaut" way of looking at solving this problem and should be avoided - http://www.joelonsoftware.com/articles/fog0000000018.html