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


Blue Ink Blue Ink
  • WP7 and IMAP emails

    , blowdart wrote


    They don't have to expire every year you know. You just need to create them right Smiley

    I don't have troubles believing that. But since that's the default for Exchange Server, both for creation and renewal, that's the setup I invariably find. Hence the irritation.

    The excellent reasons why a company should stop trusting its own certificates every 12 months by default are way out of my depth...

  • WP7 and IMAP emails

    A word of warning: if your email server requires SSL, expect problems.

    I had my fair share thanks to self-signed certificates (Exchange Server and an IMAP server of unknown pedigree), and for other unexplained certificate problems (a Lotus Domino, with a certificate that appears to be valid and trusted all the way up).

    Needless to say, an iPhone will just ask you (once!) if you want to accept the certificate, install it and just work. With a WP7 you have to get hold of the actual certificate, email it to the device, install it from the attachment, reboot the phone.

    And since self-signed certificates expire every year, you never run out of fun...

  • These seem like compelling reasons not to work for Microsoft to me

    @1001001: Yeah, why not go back to - say - Renaissance and get Da Vinci fired for being an incompetent?

    Seriously, I don't think many of us would succeed against these guys (and gals), in 1975, using their weapons of choice. We had the benefit of decades of training on computing they couldn't possibly get, but we were also spoiled rotten in the process.

    The most advanced workstation back then was an 80x24 terminal, a crappy editor, and some 8-bit assembler. Manuals (the dead tree version) you had to contend with your coworkers, no internet to find information or ask questions, compile times that ran for hours. And all this to produce code that had to fit in a handful of KiB.

    We could relearn, but I doubt we would stomach it.

  • These seem like compelling reasons not to work for Microsoft to me

    @JohnAskew: I believe Maddus was referring to something different: there's nothing wrong in getting a job you aren't qualified for, as long as you are willing to bust your arse to learn and catch up.

    That's not the Peter Principle: that's what keeps the world interesting for the rest of us.

  • Interesting question

    @ZippyV: as I recall, the Prius I looked up on that site was rated about 66mpg (UK) or something like that... "Your mileage might vary" was never more appropriate.

  • Interesting question

    @ZippyV: 60 mpg is nothing to write home about these days. Leaving alone pure electric for the current range problem and battery lifetime, there are countless diesel and petrol options that easily exceed 70 mpg (there's a VW Golf 1.6 TDI that makes 74, for istance) and you can exceed 80 mpg on some models (source: www.nextgreencar.com ).

    I would have expected hybrids to do a lot better in comparison, and given that diesel engines are more efficient than their petrol counterparts, I would have expected that there would be a lot of diesel/electric hybrid cars by now.

    100mpg isn't unrealistic for one of those and that would be an excellent stopgap while we mull over how we get to recharge and manage batteries...

    EDIT: for what it's worth, diesel fuel is also extremely safe: its flashpoint is high enough that it's not even rated as flammable.

  • Thought provoking article by Rob Pike that C++, Java and C# (especially) devs should read

    Ok, as an old time C++ programmer I'm biased. And opinionated. Take with a grain of salt.

    First of all, the whole point about the bloat of C++ is a fallacy. True, C++11 did result in adding a lot of features to the already gargantuan specs, and it couldn't be otherwise given the unprecedented codebase that must not break. Noblesse oblige. Yet, once you start writing "pure" C++11 code, you end up using a relatively small subset of the specs, which results in a lean and clean language, without renouncing any of the power and efficiency of the language.

    Second, there's the preposterous idea that a GC is needed for parallelization or that it makes a language intrinsically better. There's nothing wrong in using a GC, of course, I just don't see it as an advantage, not against modern C++. Conversely, lack of deterministic destruction, RAII and the like is a serious limitation for a "systems programming language", where fine-grained resource management can be paramount.

    Dissecting each and every feature of the language is beyond the point, let's just say that the language doesn't innovate enough, with respect to C++, to generate more than a mild interest; on the other hand, it has a number of "features" that I just find irksome, when not altogether misguided. Postfix typing, overloading well-known symbols from other languages with totally unrelated meanings, implicit interface inference (interesting, but that's an accident waiting to happen), the egregious short-sightedness of using case to determine visibility (not to mention cultural chauvinism... ironic for someone who has developed UTF-8). Just to name a few.

    And all of this syntax sugar just to save keystrokes. Might have made sense in the '70s; nowadays it's the task of a decent IDE to take care of that, not the language design.

    Which takes me to the most important reason why I haven't taken up Go for a ride beyond the online demo: features (or lack thereof) are but a facet of what makes a language the right tool for the job. You must factor in IDE support, ease of debugging, unit testing, documentation, libraries, tools. For a language that is apparently all about "getting the job done", Go doesn't offer any of that, not up to modern standards anyway (gdb? seriously?).

    I'll leave it at that, for brevity <g>

  • It's Geeks all the way down

    @cbae: Poor lady Lovelace got her name smeared by the unfortunate association with a particular language that won't be named. May I suggest Grace Hopper in her stead?


  • Windows Phone 7.8

    , Proton2 wrote

    [...] With the caveat that your carrier mileage may vary.

    Not necessarily. According to Paul Thurrot the update should be delivered directly by Microsoft. Fingers crossed.

  • Stephen Elop makes me angry

    , fanbaby wrote

    1. Do you understand the Silverlight is now completely gone from the last place it was used? (again i have nothing against SL on the phone). That future developement on WP will not be sl?

    Don't let marketing monikers fool you: the future development of WP will still be based on XAML + C#/other languages. Transitioning won't amount to much, and you can still use SL to develop for WP7 and WP8. Using your metrics, C++ developers should slit their wrists with rusty blades over C++11 (hint: we aren't).

    2. As new apps will not work on wp7, for example only IE9 and not IE10  is available and will ever be, so it seems, would you recommend buying WP 7/7.5 today?

    It depends. WP7 is still more than good enough for most users, so yes, I would recommend it for some users. And I would suggest others to wait. Of all things, I don't think I would consider IE10 as a factor though: poorly designed websites have a lot more to do with the bad experience you get on smartphones in general than the merits of the individual browsers.

    3. Will Nokia see sales declining b/c of this?

    Good question... intuitively I'd say yes, but I'm afraid I have to ask "compared to what?". WP8 isn't the only competitor of WP7: with looming announcements from Apple's and Android camps, there's a possibility that what looked like an untimely announcement to many (me included) could be just a preventive measure. I don't have all the details and projections it takes to make that kind of call.

    4. Had nokia gone with android/also with android things would be less problematic?(no need to answer this if you think everything is groovy.

    No. That move would have prevented any cash investment by Microsoft, the low estimate of which is 1B$. With the low profit margins recorded for Android devices, that means that Nokia would have had to sell tens of millions Android devices to be exactly where it is now, not an easy feat when some of the largest competitors (e.g. Samsung) do not rely on the mobile market for their survival.

    5. Is elop a genius (just kidding)

    No. I reserve that title for the likes of Da Vinci, Feynman and very few others. But I think he's a pretty good pilot flying in extreme weather.