The jesus analogy works better I think... he made some copies of fish and bread and distributed it free of charge. People who copy data should henceforth be referred to as "miracle workers."

You == Genius.

You gotta think maybe in 30 years the world will be populated with decent AI robots of various types. [...] This feeling of,"Anything is possible in the future" brings a warm feeling into my heart.

Everything except a decent goddamned flying car.

No, that's because you used a comma instead of a double-colon. a : b :: c : d

You really need to define your problem with much greater specificity to get a valuable answer.

The OP said they were using NoSQL. That alone explains everything.

Solution (to the OP, not the parent who clearly understands what they're talking about): go learn how to use relational databases properly. Normalize your data. Nine times out of ten, if you're repeating information in multiple tables, you're doing something wrong. DO NOT USE BUSINESS KEYS. Surrogate keys only. Why? Because you do not own a crystal ball.

I can't believe this screed got a +5 Informative. Your argument makes no sense.

The root of the problem was that the engineers who started the project didn't know anything about database programming and just used NHibernate as a magic persistance layer.

Really? They didn't know anything about database programming? First off: what does database programming have to do with .NET/Java programming? Second: how does someone who doesn't know anything about database programming go about creating libraries that do database access? I'm serious: how do you do that? That's like accusing Toyota of being full of engineers that don't know how to build a car just because the ride is bumpy.

In order to use it right, you have to know the underlying database programming concepts, which are simpler and easier to learn then the NHibernate library.

You keep using this term: "database programming." What in the hell are you talking about? Are you talking about stored procedures? Are you talking about writing relational database software? Are you talking about the software written by third party developers that uses the libraries?

Or are you just talking about SQL? I think that's it. I think you're using the term "database programming" to mean "SQL statements" which explains a SHIT TON.

My opinion: Stick with a simple ADO -> Object mapper and write queries as-needed

Yeah, named parameters are overrated, too. Just concatenate a big string together. And if you need to check user input, just write your own parsing library because I'm sure it will be better than an open source, freely available version worked on by thousands of contributors. Nothing could possibly go wrong there.

Don't rely on a more complicated library to handle things like transactions, lazy-loading, and relationship mapping.

Sigh.

1. Hibernate doesn't handle transaction management.
2. Reinventing the wheel is reason #1 for getting fucked-up, hard-to-find bugs in your code.

Be very careful introducing relationships into the business objects

Says the programmer. "What the hell are you talking about? You don't touch business objects," replies the DBA.

if you end up working in a project where the senior engineers and/or people who started the project treat NHibernate as a "magic persistance layer," RUN!!!

OK, here you're absolutely right! Please run away! There are plenty of good programmers that can use a job. Let the scared hand-query-writers go whip up a website for their local bands and restaurants.

my experience of ORM so far it is for Newbs who cannot comprehend the data structures by themselves

It's obvious you don't know what you're talking about. Data structures have nothing to do with ORM.

Thank god for all the bitching scripting "programmers" that despise ORMs and would rather use hand-written SQL statements. You keep the rest of us happily, steadily employed.

The three major video game consoles are less open than even an iPhone, yet consoles beat PCs in sales in several genres.

Yeah, but bread is more open than an iPhone, and bread has outsold PCs and iPhones hand-over-fist for centuries .

This is why we should never have gotten rid of analogies on the SATs.

What kind of deal is this? If they turn themselves in, they get to complete the course? That is absolutely ridiculous. If they cheated, they fail. Do not pass go, do not collect $200.

Christ, they SHOULD be expelled.

Yeah, I agree. The GP smells trollish. Java has the benefit of being free and already widely-understood (hell, most CS intro classes start with Java because it gets OOP out of the way right from the start). If I'm hiring for a company, I want to have my pick of a hundred people, not three. D would have to give me magical performance increases in the range of an order-of-magnitude or more before I'd ever consider abandoning Java.

It's like speaking to a person who always tries to finish your sentences before you're done speaking

EXACTLY! I fear that Google is only serving to help miseducate a whole generation of rude, interrupting bastards that think they already know everything.

And we're in debt up to our eyeballs on programs that don't do what they were supposed to do.

Like defense, right? Huge entitlement program for the corporate welfare moms, just so we can create new enemies abroad, or build giant, hilariously expensive floating targets.

Christ, couldn't they think of something better than LibreOffice?

What about "OpenBook"? Or just plain "Libre"?

Why? Is there some software that requires Win7? Oh! Right! IE9.

Chicken... meet egg.

You're right, the Dell is better because it actually fits in your pocket.