I learned Logo in 4th grade. We mostly had fun with it by making the turtle wrap the screen and change colors. It certainly helped produce an interest.

According to Linus Torvald's book "Just for Fun", he learned to program by typing in his grandfather's assembly code and moving on from there.

So all-in-all, I don't think logic skills are necessary to start learning to program, but they should at least be developed along side it. Really what you need to do is foster an interest in programming using some tool that kids like - whether Logo or a OLPC or Arduino or Lego Robotics or whatever. Spark the interest and it'll go on its own from there - and they'll get into the logic stuff (Algebra, Boolean Algebra, Calculus, etc) on their own as they realize the need.

Well, theoretically (and only theoretically) photons could have a gigantive rest mass that is 100% converted to energy when in motion. The problem we normally face is that we cannot convert (or think of how to convert) 100% to 100% energy in a manner required to do that - t0 at rest, t1 in motion, a=c over t0 to t1 and (t1-t0) is nearly zero (e.g. 0.000.....0001 or 1*10^-infinity).

That has nothing to do with my statement. My statement was purely that they could in fact go back to MeeGo/Maemo if they wanted. There's nothing preventing that.

The objective of any business is to make money. Whether or not that includes Linux or Qt or whatever - even Microsoft Windows - is different matter based on what products and features the company thinks they can sell to others (corporate or not) to make money. Often the case is more aligning to Linux now than it is to Microsoft Windows; but as I noted that is an entirely separate issue than the comment I made pertaining to MeeGo/Maemo and Nokia's ability to continue with that platform if they so chose.

Honestly, while having users authenticate a self-signed cert in a browser did help with security, etc it also broke a lot of devices. I still cannot use my WRT54G with any modern browser aside from the default browser on Android 2.3.6; same with my newer model router with latest firmware.

And honestly the problem IS NOT the hardware I'm accessing - its the stupid browsers.

They're only going to cause the same kinds of headaches for everyone.

P.S. I'm not in favor of Java or Java Appletes, but it still seems like a bad thing given how it impacted browsers accessing valid websites with self-signed certs.

My point was that comparing RIM/BB and Nokia is not valid - its an apples-to-oranges comparison.

Nokia is where it is today because of Elop and numerous things he did as CEO - from declaring symbian/meego/maemo dead and their move to WP. Prior to all of that Nokia was relatively healthy and in a good position to make a transition; after those things they were not. Please take off your revisionist history glasses.

RIM/BB is where they are because they had a technical failure in their network that severely hurt their customers. Up to that point in time, they were doing extremely well. When that occurred, people realized how tied their own communications were to RIM/BB itself. I don't think people realized how centralized the RIM/BB network was until then.

Please share what inside information you have? Having participated in the Qt mailing lists at that time ( and I still do ) there was quite a lot going on. Qt for Symbian was doing well, and people were doing Qt for various platforms - including Symbian - and recompiling to go between them. Not saying everything was perfect or that they weren't fully ready to push it out migration wise, but it was something they had - unlike the complete and utter drop of all their partners, app developers, etc for the move to WP. (I would actually have been quite surprised if it was 100% perfect.)

So what? N97 was not the N900.

The N900 is what Elop completely killed before it was released, and outsold Lumias without any issue; it was a very high demand phone that Nokia under Elop decided they would only do a limited number of because they were doing WP instead of MeeGo/Maemo.

The N900 was originally released with Maemo5 (presented Sept 2009, released Nov 2009), and later released with MeeGo (May 2010). Just prior to its MeeGo release, Elop did exactly as I noted.

Please share your inside information.

What myth? It's in numerous sources backed up by financials and information from Nokia itself.

Sure they could. They don't have to control Qt to do MeeGo - they could just buy back Jolla and what MeeGo became - SailfishOS.

Funny how they were still selling quite a lot of them until Elop came around.

FYI - All those Symbian devs and their Symbian apps had a migration path from Symbian to Maemo/MeeGo.

Also Nokia didn't have the same issue BB had in having a central network that was essential to the platform and have a major crash that took weeks to fix and caused headaches for their customers. That is really why BB fell in market share - everyone was looking for something more reliable. BB10 is a great little platform, but they have a reputation they have to fix - something that takes a long time to do and they may not be able to recover from.

In 2010 MeeGo wasn't out. It was just about to be released when Elop wrote the "burning platform" memo; and during the presentation to the press he stood up on stage and said "We're not doing this; look I have another one running Windows Phone and that is our future" - intentially sabotaging it before it even hit market. Yet, as others have pointed out, with no marketing the MeeGo Phone outsold the Lumias wherever they were both sold in the same markets - and not by small margins - by 3:1 ratios. Every review of the MeeGo phones compared it to the iPhone; it would have been a killer - and at the very least a very strong third, leaving everyone else to fight for fourth - had it not been for Elop.

The Qt Developers at Qt-project.org are making sure that does not happen for the official Qt itself.

Now whether developers pull in enough KDE Frameworks to effectively make that happen is a different issue, and one Qt developers cannot help aside from pulling more from KDE into the official Qt releases.

Another good example is the Democrats and Obama with APA, aka ObamaCare - escalating in commitment to the destruction of everyone else.

I don't know about any previous bailouts to the ones just a couple years back, but Ford did not participate in those bailouts. They requested the option if necessary, but they did not participate and advocated that they should be available for GM and Chrysler, both of which did use them.

Google doesn't fully control Android. Sure they're the primary sponsor but Android is mostly controlled by the Open Handset Alliance.

FYI - the courts require that web content have screen shots taken with time-date stamps to avoid this exact issue. The screen shots must also contain the information in a certain manner, only then can it be used as evidence/exhibits. If the lawyers are not doing that, then they are not properly writing/citing their court paperwork (briefs, etc).

And no, it does not amount to a copyright violation.

IANAL, but that's my understanding thanks to Groklaw and other sources.

While true there are many devices that are simply not maintained by the hardware vendors, which does cause an issue..

That is not really the problem. Most hardware will work under Linux without any issue. The vendors typically took shortcuts and used common chipsets that Linux quickly picked up on and implemented support for. Many vendors still are starting to provide direct support too; more and more devices are starting to ship with a little Tux logo on them. ;-)

So the hardware is not the problem.

The problem is mainly software and compatibility. Too much software is tied only to Windows. My wife honestly doesn't care if she uses Mac or Windows or Linux; but she has to have MS Office for her CPA work, and nearly all Accounting software is Windows only, some offer Mac ports. And it's the same in the majority of the software fields.

So really it's the same reason why Win8 is failing - too big a change with too little support for legacy software.

DST was never about saving energy. It was about aligning workers to shifts for production in a manner that made sense for war time.

Yes, there are people that claim it would save energy - not burning candles at night when you could just get up a little earlier kind of thing; but it was really about making the most of the daytime for war efforts when enacted (WWII). It made sense for the manufacturing economies of that era, but now we run 24/7, so it really doesn't make sense any more.

Good post.

They dont. Which is why that church has a very negative light on it even among the rest of the Christian Churches. No one condones what they do.