Entries:
Comments:
Discussions:

Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

Bass Bass Knows the way the wind is flowing.
  • Microsoft Kill Off Windows Phone

    , Ray7 wrote

    *snip*

    i don't think he said it was a new idea; he was just explaining how it works.

    I don't think I claimed that he was claiming that it was a new idea claim...

  • DeepMind's AI masters Go

    DeepMind is going to challenge Lee Sedol next (one of the best Go players in the world).

  • Microsoft Kill Off Windows Phone

    , bondsbw wrote

    *snip*

    What you linked is "Auto Layout", and it appears to be roughly equivalent to the margins and padding that have been in XAML since the beginning.  No, that is not what I'm talking about.

    I'm talking about changing any part of the layout or content you want.  If the windows is less than 800epx wide, content that was layered horizontal becomes vertical.  Buttons get moved from the right to the bottom.  A sidebar of selectable content is moved into drop-down.  Description text is trimmed or eliminated.

    Sounds more like Bootstrap. Bootstrap is what ALL hipster startup websites use. Bootstrap's philosophy is mobile-first. In that they care more about providing the best usability on mobile. Maybe passable usability on desktop.

    The W10 "desktop" apps I've used so far all smell like mobile apps and generally feel like a novelty more then anything else. In fact, now that I think about it, they look and feel and generally are designed like Bootstrap-powered web pages. Now I realize that's a symptom of Microsoft adopting the Bootstrap philosophy. Unfortunately, mobile-first only makes sense when your mobile platform is dominant. Maybe that is what Microsoft was hoping for. :)

  • Microsoft Kill Off Windows Phone

    , svelasquez1‚Äč23 wrote

    I don't really think this steep decline in phone sales is going to be limited to MS.  The differences between generations of phones for all 3 ecosystems are getting harder to identify.  You can only come up with some new design term so many times before people get bored.  This cycle of new functionality -> techno lust -> commodity is a short one and is nearing the end for tablets and phones. 

    MS is going to be hardest hit because they are the smallest but Apple is going to be hit pretty hard as well as they do rely on hardware revenue.  Google's position is the most envious because their model is primarily service based and in many ways already very platform neutral.  MS is heading that direction now which is why you are seeing more x-platform stuff from Redmond.  In the end, the only factor that matters is which app/service, not device, is getting your screen time.

    Well Google beat revenue expectations and Apple didn't meet expectations, and that pushed Google's market cap above Apple. So it's already happening..

  • Microsoft Kill Off Windows Phone

    , bondsbw wrote

    @Bass:  Wait, didn't Microsoft invest in $300 million in B&N's Nook subsidiary?  I think the Nook failed due to competition.

    That money was not a charity grant. As part of the settlement, Microsoft made B&N spin off Nook into some external company that had chartered goals to bolster the Windows ecosystem and accomplish MSFT serving stuff that had nothing to do with making an awesome e-ink device. Of course Amazon steamrolled it.

    Moral of the story, if you are going to play in the tech industry don't be a B&N, be an Amazon. You need some obnoxious patents of your own to force a conventional cross-licensing deal or MAD with the Microsofts of the world.

  • Microsoft Kill Off Windows Phone

    , bondsbw wrote

    *snip*

    It's about choice and options.  Just because I can write one platform-independent UWP app that gets deployed everywhere, that doesn't mean I have to.  I can certainly write platform-dependent UWP apps with shared libraries if that is a better fit for my needs.

    I don't see the value at all. Like what actual problem it solves, if I want to write a desktop app and a mobile app that are similar I can already share tons of code, esp. in the Apple ecosystem.

    Anyway this whole discussion is pointless because none of this works on Android and iOS. BeOS's dev environment is far far superior to anything ever made. You might as well extol the virtues of that.

  • Microsoft Kill Off Windows Phone

    I think the patent system needs some major reform because the value of shitty/obvious/broad 'valid' patents is actually higher then innovative/non-obvious/narrow patents. It's not all one sided though, Google is currently the largest company in the world and they have a ton of their own super broad patents. And these deals end up being cross-licensing deals, where both companies license each other patents, it's not as one sided as Microsoft's press reports make it seem. The ones who really get fucked are companies that have no tech patents of their own to cross license, like Barnes and Noble who got fucked back into the stone age by Microsoft. That's the only one I'm personally irritated about, because the Nook had serious potential.

  • Microsoft Kill Off Windows Phone

    , bondsbw wrote

    *snip*

    It mostly depends on how much shared functionality there is.  Much shared functionality = single universal binary, little shared functionality or major differences in app size = separate binaries (but with some shared code and libraries).

    Continuum makes this a single universal binary more likely since a phone can run the app full-screen, where more functionality would likely be exposed, and where it may be common to start the app in mobile mode but hook up a monitor and keyboard to finish.  In theory these apps could contain the full functionality of the traditional desktop app but show a reduced UI in mobile mode.  (I'd be curious to know if the binary can be optimized to only load into memory the compiled code that is required for the current device mode, which could make it an easier choice to build and deploy a single app.)

    Also consider that complex web apps like TurboTax can run adaptive UIs and be very successful, and that UWP is even more adaptive by having access to more device capabilities.

    If it's about having two binaries that share code, that's nothing special at all. Phone and desktop sync is solved by "the cloud". Continuum only serves to encourage people to crap their pants even harder if they ever forget their phone at home.

  • So Joe Belfore is using iPhone right now.

    , Ian2 wrote

    @Bas: ++

    But I heard from quite a reliable source inside MS that they offered Xamarin a ridiculous amount already - and Xamarin don't want to sell. 

    I highly doubt that. Xamarin is funded by a carrier-load amount of VC money and VCs <3 selling off companies.

  • Microsoft Kill Off Windows Phone

    , MasterPi wrote

    *snip*

    Isn't that what Islandwood is for? Although, I guess that's taking an iOS app and shoving it into UWP... But, it does seem like the fundamentals are there.

    It's a more massive undertaking. It seems like there is still not many developers working on Islandwood.