se85

Not quite, although your "probably" right.

It's really no where near as simple as that, not even close.

There is lots of politics, and red tape to keep in mind as well that has to be overcome before they can even think about Android, let alone delivering on it.

Getting rid of Elop, really doesn't change this painful process of software migration (which is never, ever "pretty easy") or everyone else that thinks Nokia/Android is a terrible idea from a business perspective (it is).

Nokia has already had to go through all of this recently to accomodate the Microsoft Plan, and it is just extremely unlikely that a company the size of Nokia could survive a second transition and come out the other end smelling like roses.

We are talking at least a year (and thats being very conservative and ignoring all existing and future plans that are currently in place that would need to be dismantled) before there would be a tangible Nokia Android product. There is also the large layoffs and rehires that would need to occur during this transition and this stuff takes time, lots of time when talking about a company at the scale of Nokia. I'd imagine they would lose lots of partners over this transition as well, the list is endless.

My bet is it would be another year or two on top of that before Nokia was at its current state as of today on the market with Android instead of Windows, except the market will be much bigger, and Nokia will be much smaller, but hey at least they have an Android phone right? ;-)

I'm sure Microsoft has Nokia by the balls as well (contractually speaking), which is just another reason amongst many others not to attempt such a transition from the business perspective. Also, it would be a very tough sell to the stakeholders, and upper management, as well as everyone else on the front lines that such a move would yield anything for Nokia besides a quicker path to hard times ahead and/or bankruptcy.

The cards are all on the table, it's too late to make an "effective" transition and they know this.

In an ideal world, business wouldn't get in the way of releasing a good product, but in the real world, business almost always mandates what the product is, and in Nokia's case, the business decision was made years ago and it is not something they can pivot on overnight like your typical Sillicon Valley startup.

Lazy is never a word I would associate with someone who is motivated enough to be a good programmer in the first place.

You can't really call it cross browser when it doesn't support browsers that don't have getUserMedia.

You had me excited for a second there because something like this with a flash fallback mechanism would be really, really useful.

Agreed, pretty much every "average" developer I've worked with, has been average because of a lack of motivation, or interest in pushing themselves, not because of a lack of following a list of steps posted on some website that somehow makes motivation and interest irrelevant.

How so? We aren't even looking out for ourselves let alone platypuses! :-)

I really want to smack that smirk off his face.

Uggh, what a painful video, I couldn't even watch the whole thing!

Beautiful != Consistency

"Because Dex relies on heuristics that don’t take your data into account"

So if you do take your data into account and create indexes accordingly and have a solid non-changing schema, is there any benefits in using dex? Is it smart enough to tell me that my existing indexes might not be as good as the suggested indexes? or is this considered part of the data that it doesn't analyse too?

Just curious where and when this tool is a lifesaver.

The guy just jumped on the bandwagon without having a clue.

Just reading this blog - it's clear that MongoDB was not a good fit for him, if he had bothered to do some research, he would have found this out on day one.

Thats the real lesson he should be taking away from this and blogging about yet somehow MongoDB are trolls and it's all their fault because of a lack of features and they have bypassed 40 years of computer science and blah blah blah blah, excuses, excuses, excuses.

edit: removed a few pointless sentences :-)

In most cases this event wouldn't be too useful because:

a) More often than not, these errors are caused by objects which could not be removed by the Garbage Collector because they are still within an active scope, so by definition the objects consuming all the memory are still very much in use. A better understanding of JavaScript would go much further than an onmemory event to try and monkey patch the memory leaks away.

b) There's no guarantee that you could clean out the objects before the VM crashed anyway, because the event fired would be asynchronous, and the JavaScript isn't going to halt everything else and wait for your code to run.

I know there is plenty more reasons as well when you get deeper into the GC collection side of things - but I won't go there without narrowing it down to a particular javascript platform first ;-)

Javascript being able to hook into things like this so you know more about memory usage and stuff would be great, but there is a number of technical hurdles to overcome, and I doubt that most Javascript developers would care of its existence if all the work was done to make it so.

Thanks, I just read that article.

2 years for that? Thats embarrassing as hell, I can see why he is lying through his teeth and deferring the blame.

It seems that every time Zuckerberg talks, he's just more and more full of shit, can't say thats surprising though! Its a trend that has been around since before FB was even in existence.

Name one skill that everyone can do regardless of the number of neurons in their brain and the capacity to use them, and ignoring any other underlying conditions that may impact ones ability to learn or retain knowledge?

This can't even be said for the basics like language, maths and science, why would computer programming be any different?

The 7 billion plus human brains on this planet are not created equally to each other (nor do they remain equal over time)! So how come everyone apparently has the ability to learn programming?

This is all scientific fact, so I really can't agree with your viewpoint on things that we all somehow have equal capacity to learn, it sounds a little out of touch with reality to me.

Unsupported and self evident assertion?

What about people with mild mental difficulties?

What about people who suffers from extreme mental difficulties?

What about someone who no longer has a concentration span due to past substance abuse?

What about someone who is still using drugs heavily?

Hows about a 5 year old kid who's brain has not yet fully developed?

Or perhaps a 15 year old kid who is in the middle of puberty and has little concentration as a result?

Or a 90 year old suffering from dementia?

Or someone suffering any level of depression?

Do all these different groups of people in society (and the many others I have not mentioned) have the same capability to learn programming (or anything else for that matter) as any other group in society?

Didn't think so.

There are many different levels of intellectual intelligence.

As a result of this not everyone can be a programmer, just as everyone can't be a rocket scientist or a microbiologist either.

While I do agree with what your saying about WHQL licensed machines, it doesn't mean the problem goes away, it just means the problem is less likely to happen, your still at the whim of all the other weird and wonderful behaviour that can cause XP to crash.

The kernel pissing over your memory without it knowing any better is not the be all and end all of data loss problems in XP.

I've seen many "brand" name machines crash in many weird and wonderful ways, so the argument simply does not stand up when you extrapolate it across dozens of different configurations.

It doesn't make sense to me to base an opinion on a couple of brand name machines, instead of the actual reality, which is that XP as a piece of software (hardware aside) is just not that great and you should never trust your data with it.

Cheers for the clarification on the 9x vs XP though - that explains why XP was never as bad as 9x with data loss.

Very well said, in my experiences with building mobile apps that HAD to perform at close to native speeds with HTML/CSS/JS and Nitro/PhoneGap this is exactly how you need to treat the mobile web if you want things to perform.

You really cant blindly rely on any 3rd party code, or take first party code as a given without means testing it, you need to be able to build functionality from the ground up ensuring that performance is the number one priority, or extensively test and research each library before introducing it into your codebase to make sure it doesn't have any future gotcha's with performance - and more often then not, you will find multiple gotchas, till they start adding up and you end up with something like the old Facebook App.

There is no sandboxing in JavaScript, so one mistake can mean the difference between an app that performs and an app that lags, and hundreds of mistakes accumulating with no quality control at all, as seen in the old FB app, is just completely unacceptable.

I really can't understand why this is so difficult for Facebook to comprehend, did they not have any JavaScript specific developers assigned to the project? Did they assign a bunch of php developers to do this? What really caused this failure?

The fact they are using the technology as a scapegoat for their own incompetence is a pretty dishonest way of going about shifting the blame for their failures away from themselves, but I'm not one to believe in company wide conspiracies.

I think it is more likely that this whole thing probably got escalated by a bunch of "web" developers who were in over their head and decided to blame the technology stack and escalate that message to management, instead of the truth, which is that they messed up really really bad!

Don't blame the technology, blame the implementation!

edit: some minor edits to the phrasing of a few sentences.

My pin number is 99990

I prefer the node.js example given over the Go example.

Sure, the go example is shorter, but the JavaScript version reads much nicer (at least to me).

Japan will figure it out!

I personally think it's a good idea.

I don't have a problem with Nuclear energy (under the right conditions).

I can't help but remind myself that having so many older nuclear reactors in such a small country that is densely populated (relatively speaking of course) and also sitting on a fault line, is NOT a good area to be using nuclear energy

I sure hope so but i'm not entirely convinced that this effort wasn't at least partially driven by developers without all the facts behind the business side of the equation (which seems to have been overlooked or ignored for whatever reason, unless their IE8 usage statistics are much lower than elsewhere), I doubt it, IE8 is still important enough to worry about for most things, especially when your selling productivity related tools to businesses who are less likely to have upgraded beyond IE8 (statistically speaking).

I like the idea of putting product before business, but I can't see Google being the kind of company to do that intentionally.

I would really like to know more about their internal reasoning that led to this decision.

You have to figure out if its even worth your time dealing with the dramas clients like this bring to the table.

More often than not, it's not worth taking on clients like this, especially if you keep accumulating clients like this and end up having to deal with multiple people who behave like this.

My suggestion is to gently let them go as a client (unless you have a really good reason not to) and focus on working with clients who aren't going to be a pain every step of the way.

I think HP rebounding from the Palm "incident" and somehow still managing to release a hit smartphone would be more miraculous then Apple rising from the Ashes.

I look forward to seeing what happens, but I'm very skeptical that a company such as HP has any chance at this.

I do remember those days, and 9x to XP was a big upgrade so I'm sure they fixed some of the issues however It was not until Vista that Microsoft finally fixed the memory management architecture that was a large source of the blue screens of death messages in XP.

I'm not sure how similar the architecture was in this respect between 9x and XP, so I'm not sure exactly what was and wasn't fixed during this upgrade.

I do know that in my own experiences across dozens and dozens of windows xp powered machines across many different companies who unfortunately still use XP, blue screens of death still run rampant, and if not a blue screen of death, then the screen randomly freezing or apps randomly crashing and taking your data with you.

"99.9% of the Windows reliability problems are related to buying trash hardware. Just pay some more."

Yes, because windows xp, windows vista, windows 7 and windows 8 are all equal to each other, and no matter what software is installed, as long as it is microsoft certified you will only have a 0.1% chance of windows crashing on you and losing data (blue screen, screen freeze, app crashes, take your pick).

Me talking crap? :-)

b) No data loss is acceptable. Any data loss is simply "product doesn't work".

So Windows XP never worked for me because of all the blue screens of death where I lost data from time to time?

Consumer grade technology can and does lose data, too bad! but its the reality we have to live with for now until better hardware/software floods the consumer market that handles the data loss problem at an enterprise level.

In this day and age, if you lose data because you didn't take the necessary backup precautions, I don't see that as being Microsoft or Apple's fault, it's your fault!

I understand the authors experiences and how that may have tarnished his thoughts on Apple products.

Under normal operating conditions however which applies to the majority of iOS users out there, iOS is just as easy to use as it was when it first came out, it really hasn't changed that much from a UX point of view at all.

In regards to his gripes with OSX, well.... It is silly to expect any OS to be magical, even an Apple one. From a UX point of view it is better than every other OS, but from a package management point of view, Debian/Ubuntu is far superior to OSX and from a hardware support point of view, Windows beats both of them.

It seems the author wants the perfect OS, where problems never happen, unfortunately it doesn't exist yet, and it may never exist!

In the meantime, if you specifically want "ease of use", regardless of the authors troubles, your best bet for the meantime is the Apple ecosystem.

Could someone please explain to me how such conditions could be present on the surface of mars or the deserts here on planet earth to trigger the same results as the lab results?

Control is control, I agree! Did I ever disagree?

We all have our own motives behind keeping control and I find it hard to believe that Zuckerberg's motives were as pure as claimed in the article (given the history of the guy and all).

I believe there is a high likelihood that the young Zuckerberg of 8 years ago may have had other motives behind keeping that control, far more personal motives than the original article implies.

Also, Based on Zuckerberg's stronger focus on product as opposed to business, which I feel is a pretty big weakness when your a CEO, I have my doubts he was even thinking about IPO back then, and I'm sure he is regretting thinking about IPO now.

Thanks, I misread the first time, made sense the second time! My mistake!

I still have my doubts as to how readable such an approach like this would be in large JavaScript application's when taking into account the already very dynamic nature of JavaScript, but thats more of a personal opinion than anything else.