There is exactly a zero percentage chance that I will ever use MongoDB in another project. On the surface it was great. I evangelized my friends about it and the whole NoSQL thing. But as time went by I realized that it wasn't made for people to use. Almost nothing was intuitive. For each new feature that I wanted I had to look up a tutorial and generally found a list of gotchas. If you design your project around MongoDB then it will work. But if you try to wrap MongoDB around your project then you are completely screwed.

Basically MongoDB halved the initial quarter of data storage design and programming. But as the project progressed the time spent screwing with Mongo went up exponentially until the project was shoved out the door and primary feature in version 2 was the complete removal of MongoDB.

I could make a mile long list of places the project stumbled. But a few key ones would be that there are no good data management tools for accessing a MongoDB. The second was that huge schema screwups were way too easy. It was very hard for programmers to get a mile high overview of how data being stored was being structured. That is a data layout was easy but putting the results into your head was really hard.

I am finding other NoSQL approaches are far superior. Things such as use of JSON, memcaches, MariaDB (or the excellent PostgreSQL) working together allows the project to dictate how things function instead of Mongo very quickly shaping the project architecture because of its marked strengths and weaknesses.

Redis is the environment presently being explored for version 4 and so far it is looking very interesting. But I am not joking when I say that at this point I would use access on windows as my backend datastore before I would use MongoDB.

Most of my computer friends write down the passwords but alter them in some pattern that works in their head. So ShittyIceCream8456 is ChapmansIceCream5684

I learned Objective-C so that I could deploy on iOS and otherwise wouldn't have given the language a second look. Then I discovered Cocos-2d which makes C++ on iOS, Android, etc very easy so boom I happily made the leap back to C++ and haven't looked back. There is pretty much zero chance that I will write more than a few dozen lines of Objective-C again in my life. There is also pretty much zero posibility that I will write any swift and I certainly have dodged the Java bullet for Android.

About the only problems that I have encountered are some artificial ones where some API features are cut off from me without a tiny bit of Objective-C or Java. But those tiny bits get wrapped in a C++ class and forgotten.

I don't know how many people that I know who use one of these things that I say over and over, it is just too juicy a target to hack. Way too juicy.

Simply pretend that the old ones didn't exist and go back to the awe and wonder of having the restart and discover the whole thing again.

What made this movie far less enjoyable was that they built a park full of angry dinos and oddly enough the angry dinos got way out of control. Sort of hard to believe when they are literally sitting on the remains of a park destroyed by out of control angry dinos.

Minimally I would think that they would have layer upon layer of solutions for any one of the dinos getting out and rampaging. This would include something like an implant that explodes/incapacitates on command or if there is an attempt at removing it.

The next layer would be lots of heavy calibre dino killing munitions.

Next in the future the walkie talkies could talk to space let alone around a large zoo.

Lastly why would some loves-the-people CEO have an angry military department one step away from a coup d'etat? Plus one helicopter and one pilot in that huge mountainous facility?

Basically the entire plan seemed to be to build the worst zoo ever and keep pushing it until it broke apart.

Even if the giant dino hadn't gotten out then they would have had one a year later that was a full on fire breathing dragon. Then the next year they would have cooked up the worm things from Tremors. Or tribbles for the gift shop.

Why would the festival cooperate? Basically they are saying to their customer that their privacy is of no value. Not only is this cruel but it also indicates that the festival will probably sell on any data they have gathered on the festival goers.

It is this callous disregard for privacy that screams for laws that clamp down on any organization, including the police, from being able to gather data. Quite simply I want a law that prevents any organization from gathering data that isn't crucial for the transaction and to not be able to share that data without a warrant. Thus I want this reaching the point where the power company can only gather the minimum amount of data to send me a bill and deliver my service. I don't even want them noting my gender. Then I pretty much want them not to be able to share that data with their own marketing department, let alone "trusted third parties".

Other's wrongs don't make this sort of thing right.

I wonder how pissed off all the various countries of the world will be when they find out the details of what has been going on?

Can you imagine how pissed off some people like the French would be if it turned out the US meddled in a French election? Or stole technological secrets from one of their national darlings and handed it to US companies?

It is one thing to find out that there is a program called Operation French Fry that was to monitor French politics. But if it turns out that they did specific things on specific dates to specific people; then the gloves will come off.

The article cost problem is much like the computer book problem that I had in the days that I bought computer books. Nearly all computer books suck. Thus for every 20 computer books I bought maybe 1 really did it for me.

Thus I would much prefer sifting through stackoverflow at a small but steady burn instead of the probable rip off at a higher price. So while any given article might save me a pile of money most would be a waste of money.

Netflix is also a betterish model to compare to. Their cost to provide me Netflix is low. Thus they charge me far less than the stupid and dying networks/cable companies. I would be happy spending lots of little money instead of the occasional gouge.

The key problem is that I don't generally trust online payment systems. As a class I don't trust them to get it right, and I don't trust them to protect my data. Thus I would love a single system where I can trust it and then be able to dole money out from it in ways that I completely control.

In theory I just described paypal but the problem there is that they aren't really conducive to micropayments. They love their macro fees thought.

So the wall between me and anything like forrestor would be that even if I wanted the article I am loth to giving them my data more than giving them my money.

I also suspect that because of this barrier they have fewer customers and then have to charge more for each article.

I would be happy to pay stackoverflow a penny or so per use. But I won't pay them $2 per answer; even if that answer will save me a day's work.

I can't be that far off seeing how many people are willing to do in app purchases.

I recently read an article where blackberry's market share has stabilized. At 0.5%. While I would love to own a company with 0.5% market share of such a vast market that simply doesn't produce enough revenue to keep developing quality products.

So while all your arguments seem sound the simple fact is that the people have spoken. All the large organizations that I deal with that had mono-deals with BB for all their employees have abandoned those deals because their employees yelled that BB was basically employee abuse. Most of these companies will still give their employees a BB if they want one and there are the die hards who do.

But back to my main argument. An interesting factoid is that I have seen senior managers be issued a BB, take out the SIM and put it into a BB that they bought. This go get away from their IT department's disabling their phone.

The problem is that BB now probably almost 100% relies upon assholes for customers and to make a good phone they would have to screw that last 0.5% while waiting for some of the other 99% to realize that the phone wasn't abusive anymore.

I love the planitif bleating of the millionaires and billionaires who will complain that this is going to kill them and their "free" business models. The simple reality is that if I were offered a great micro payment system I would be happy to pay for quality websites. Not much but enough that the truly great websites would make money.

The crap SEO whores and whatnot of the type that have 50%+ advertising and sell my data wouldn't get a cent.

I will turn this feature on in a second and never look back.

From the moment I heard that they were going with QNX I knew that they were making a massive mistake. But when I said this all kinds of people jumped on me and got all buthurt defending QNX. I thought that Android was the way to go from the moment iPhone started to eat their lunch. My main problems with QNX were that the only person that I knew who loved it was a complete tool. Plus why not do effectively what Apple did when they adopted BSD as the core. Pick something that works and run with it. Apple had their old creaky OS, had just failed doing a deal with another OS company and then just jumped into BSD. That gave them magical powers such as being able to easily make the leap to Intel and ARM or whatever they want. Android would provide the same magic power of portability.

But I still think that BB doesn't know what their customers really want. They are still trying to please the IT departments, the telcos, and their enterprise customers. They should instead be trying to win over the individual even if that individual happens to be in the enterprise. So don't allow things like security profiles where the IT department can effectively trash the phone. Otherwise the modern executive will go buy an iPhone/Android and not put up with that crap.

Then there are other features that they should offer by default such as massive batteries. The BB users that I know would happily add a few mm to triple or more their battery life. I know there are addons but why not just make them a default option. BB people are on the road and can get fired or lose business if their phone goes dark. Plus screw all the touch screen BBs. People buy them for their keyboards. As long as the font is large enough for blind boomers the phone will sell in droves.

Most of us tinkerers with this sort of stuff can't afford $100 boards, especially if we are going to be leaving them behind in projects, or damaging them when our robotic submarine sinks, or our robotic plane flys over the horizon. Plus we might do nothing with them. Or we might ruin them while tinkering.

Thus offering a "better" board for only $20 more or $80 more is just stupid for the vast majority of those who are going to use the Pi. If anything the Pi is mostly going to be used as a really powerful Arduino.

Now I did read about one competitor who is planning on a $9 board that looked pretty competitive. But we'll see. The other thing that I think that people love about the Pi is that it is pretty damn open and boring. Some of the other boards just have a hint of trying to pull you into an ecosystem. Galileo would be a near perfect example of this. Instead of open and for everyone they played all kinds of games where they tried to get it into schools and other restrictions on the initial signups. I could just see some marketing person with their powerpoints behind that one.

I personally have exactly one complaint about the Raspberry Pi. All the main companies selling them use UPS to ship to Canada. UPS wildly rips Canadians off with crazy unannounced "brokerage fees" and often charges crap terriffs that I don't think exist. Because of this I would not be surprised if Raspberry Pi usage in Canada is unexpectedly low.

+3 imaginary votes in the category "burned"