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

    , MasterPi wrote

    *snip*

    Er...the bay area is hardly representative. Most choices there stem from the latest and greatest on Hacker News, in addition to what pairs well with gluten free coffee. You'd find positions in Boston, NY, and major financial sectors.

    It's not just gluten-free coffee. Silicon Valley is the center of technology on planet Earth. Don't hate bro. That's just fact. 

  • Microsoft Kill Off Windows Phone

    TOML is the best format in the world.

  • Microsoft Kill Off Windows Phone

    , magicalclick wrote

    btw, what does iOS use? And what does Android use for the apps?

    Web tech is a legit and well used option for apps on either platform. Unless you have the source code for an app, it's hard to know what it is made in. Cordova is actually a pretty big thing all around. 

  • Microsoft Kill Off Windows Phone

    @vesuvius:

    Just a quick search on Indeed.com pulled a single job posting for the entire bay area that had "WPF" in its title. Maybe you can all fight for it. Or just avoid the entire bay area I guess (is that really an option?). Don't worry it's mostly $15 fair trade organic vegan latte drinking hipsters with $9001/mo rents.  

  • Microsoft Kill Off Windows Phone

    , fanbaby wrote

    *snip*

    Not sure about JSON vs xml, but efficiency alone doesn't settle debates like this one. TCP/IP might have been the least efficient vs its competitors, and it won. Same for text-based configuration vs The Registry :) 



    I've only seen XML/HTML parsers measured in microseconds and that's for very large documents. It doesn't make any legit difference at all to a computer. Things that make a website slow is bloated adverts and animations (especially Flash, which btw is a binary format).

    , vesuvius wrote

    JSON Vs Xml is probably another example where the closing braces in Xml mean extra bytes of data down the wire so JSON won

    The reason JSON won is because XML is a pile of oververbose/human-unfriendly crap. I would have said the exact same thing when XML was 'all the rage' in the late 90s. I never liked it. When there are literally 1000 page books written on a data format, you know something is horribly wrong.

    The only places employing Xaml developers in the UK is the Stock Market where latency is an issue and the desktop applications responsive nature is important where milliseconds mean millions in their real-time systems.

    I remember on this forum people complaining about how much memory and performance costs WPF had, somehow I doubt it's suddenly became the fastest option in the new incarnation. If performance really mattered you'd use C++ and FLTK, preferably rendering directly to a kernel framebuffer. Even complex FLTK apps run like grease lightning on a Pentium Pro.

    If there is something that requires quick reaction also, getting rid of the human in the loop with its 250-300ms lizard brain/type I/'fast' reaction time is probably the best performance enhancement one could make.

  • Joe Duffy started blogging about Midori

    , bondsbw wrote

    *snip*

    Are you sure it's not the opposite?  That management never provided clear direction?

    Besides, much of the research has resulted in ideas that are now in use or will be in some future product, even if the specific product they were working on never makes it directly to market.  Joe Duffy states in his blog, "Now, I am helping to bring many of those lessons learned back to the shipping products including, perhaps surprisingly, C++."

    Corporations tend to be horrible incubators of innovation in general. If you are some researcher working for AverageBigCompany(tm) and stumbled on a potentially billion dollar idea, are you going to give it away to your employer and probably get a pat on the back and a $10k bonus? Everyone buys startups for this reason. Acquisitions is how innovation enters a big tech company.

  • A great tool for writing OS agnostic desktop applications

    This helps make really beautiful desktop apps. Golden age desktop application stuff.

  • Microsoft Kill Off Windows Phone

    , bondsbw wrote

    *snip*

    You must be looking for magic.  In any real programming exercise, you always are expected to specify all your needs.  The only thing that could be better, as Bass suggested, is to reduce the verbosity of XML.

    *snip*

    I agree that the verbosity of XAML is bad and have previously advocated for something better.

    But that syntax you suggested doesn't make sense because this isn't defining a control.  It is defining a Setter, which modifies a property of a control, in the same way that CSS styles modify HTML definitions.

    XAML control definitions are more succinct than style setters and look very similar to what you suggested.

    *snip*

    That's not inside the markup, but within a separate Style.  Like HTML+CSS, XAML has distinct ways of defining structure and layout.  But in XAML both parts are XML-based (unlike CSS which is just a completely different language).

    Cool thanks for the information. QML looks great. I'll just say the example comes off as complicated and super verbose for someone used to HTML/CSS, and it's not even very clear to me what it is doing. CSS is obvious once you get the basic syntax:

    selector { property: value; }

    It's hard to make it less complicated/verbose then that, although people have managed. Besides this simple syntax what I like is the language is rich and obvious, and it's simple to have complex effects. Like maybe make it so all single column text fields in an app have a drop shadow when hovered over by the mouse.

    input[type=text]:hover { box-shadow: 7px 7px 20px; }

    "input type text hover box-shadow" <-- These are all simple words that directly relate to the task at hand. There is almost no superfluous language at all, except maybe "box" (if I designed this, I'd just call it "shadow", and probably introduce named parameters and defaults). How do you do something similar with XAML?

    I've used Swing, WinForms, VB6 and I don't remember any UI framework making such a task so trivial. In fact it would be nearly impossible to do what CSS can do in one small line.

  • Microsoft Kill Off Windows Phone

    , fanbaby wrote

    @magicalclick: So the XAML language/tooling are better and easier to use then HTML/CSS/JavaScript?

    That's highly debatable. If what bondsbw posted is "XAML" it looks way too verbose (also why XML in 2016?) and just like missing any kind of thought in the design of the markup. This:

    <Setter Target="MySplitView.DisplayMode" Value="Inline" />

    Should be something like this:

    <mysplitview display="inline">

    But even then there is stuff talking about pixels and layout properties in the markup which is kinda gross to me. The whole CSS and HTML separation is something I have taken advantage of in the past, and arguably the source of HTML's device universality. It's actually a great idea and I'm surprised Microsoft didn't like steal this when they designed this XAML/UWP thing.

    Anyway I'm much more comfortable with HTML. Maybe others see a giant XML wall of AbstractPropertyCollectionFactory and get really excited. It's a personal preference and accumulated experience matters far more. 

  • Microsoft Kill Off Windows Phone

    These apps have unnecessarily huge widgets and UI elements that take up lots of space on a desktop.