Battlefield is Battlefield. The monikers they add after the colon don't matter to me.
really don't agree with this statement. using the name 'battlefield' is just a marketing ploy - this bc2 is nothing like bf2. by your logic, are you saying that windows phone 7 is windows 95? you have to look at the whole name, not just focus on the first word you see.
personally i don't see bc2 as the successor to bf2 at all - that will be bf3, i do believe. i think of it more as a sort of stepping-stone between bf2 and bf3 - test and iron out frostbite engine (and other things) for the pc before they release the BIG game that i hope bf3 will be.
so it is not surprising that bc2 < bf2 in a lot of respects - it's a totally different game -they only called it battlefield for marketing/branding purposes.
i know it's kool to slag off ea/dice - but bear in mind that they are two different companies, with different agendas. also remember that dice released patch 1.5 for bf2 years after it was making any money in the shops. it was late, and it wasn't perfect (what is?), but my point is that they didn't have to do it at all. how does that compare to your rat's ass?
Whether or not you agree with the statement is irrelevant.
To me, Battlefield is Battlefield. Agree, disagree; it doesn't change how I feel about the series.
I'm not really going to get into your take on my logic because I'm not comparing a video game to something that is not a video game. Suffice it to say your iPhone/OS analogy is a non sequitur. A more appropriate analogy would have been Win ME to Win 7. If you had, we could have then debated whether ME was a real OS or not; whether it was a natural successor to 98 or 2k, and we might have agreed that it wasn't (a real os that it).
Whether or not the term Battlefield is just marketing is debatable. I disagree. DICE has just made another in a series... a series I might add that began before BF2... and, in my opinion, BF2 wasn't their best effort either. That honor goes to the original, 1942.
That they, DICE, decided to also market the series to a burgeoning console market doesn't change the core of the game, or the series; it's still a big vehicle centric war game... that's how it differs from CoD and Red Orchestra. Maps are still open, unlike CoD and RO, where gameplay is dicated by predetermined paths... which make me feel trapped, like a rat in a maze.
It's your opinion that BC2 is "a stepping stone to iron out Frostbite"... that's fine by me. It's my opinion that we're dealing with Frostbite because on the console Frostbite works (it was developed for the console) and consoles are where the money is at. Like it or not, we're forever stuck with it... the rat's ass thing comes in because no matter what, from here on out all our PC titles will be crap console ports. There is no way they're ever going to get Frostbite to play well with the PC, and this is something both DICE and EA have known for a long time.
Given the realities of the gaming world, any DICE created Battlefield title is just that: another in the series. Whether we can play it on the PC or the console is irrelevant: it's still a Battlefield game as long as it has some aspects of the original... and to date, they all do, from 42 to Vietnam to BF2, to Bad Company to 2142 to BC2 to BF3... and whatever they happen to push out after that with the name Battlefield.
I'm fully aware that DICE and EA are two different companies...

But that doesn't mean the parent company doesn't exert influence over the child company. EA owns DICE.
Yes, DICE and EA have been getting a lot of flack lately, but given events, they've brought it all on themselves. True, they didn't
have to patch BF2 with 1.5, but since they weren't putting any energy into a PC game, someone with a really nice suit who spends his day counting money probably thought it might be a good idea.
The day a Battlefield game comes out that doesn't have vehicles and that doesn't let you go anywhere you want on the map... that's the day I'll agree that Battlefield isn't Battlefield.