Do you have something personal against C5? Because you did almost exactly the same comment to two posts with completely different points?
Anyway, whether or not drupal did it a few years ago, it's about implementation. I actually DID explain what I liked, but whether you understand what I meant or not, it doesn't mean my points were invalid. The last time I checked (admittedly a few years ago) only one other cms did in context editing. Like, if you had a blog, you could drag a block of content, or an image slider in on that page, right there, while looking at it, tweak the content, and see how it will work. With most things, there is no need to go to the dashboard/backend.
I arrived at this "need" for a customer that literally said he wanted his website to be as easy to use as his fantasy football site he frequented. Now, the issue is, that site was very good at only one thing, but he liked being able to see the changes inline, as they would appear. And not just having to go into a wysiwyg editor to do all that, but be able to add custom areas with different specialties wherever they wanted. Drag and Drop, tweak the content in a logical fashion (for an image slider, add the images, text, titles, etc, and then just hit save).
The page centric paradigm C5 had some use cases where data objects would help, so they added it. So, you are offended because they are adding features that you have had, but yet your CMS still doesn't have some features or implementation they do have? This is the WHOLE POINT! Each CMS has it's benefits and drawbacks. Some did X first, others, Y. I pick android as my platform for my phone, you may pick iOS. They both evolve differently. Some people here may be desperate for a feature in one that they didn't realize was native to another. It may be that the implementation of data objects is more or less flexible or usable than in Drupal, frankly, I don't know. If you would like to show me how their in context editing in drupal blows the lid off c5, I'd love to see it. But frankly, like I said, for end users, and I've had a good number of them, they seem to pick up C5 really fast and like the customizing options and flexibility.
So, you enjoy Drupal for what it does have, and I like C5 for what it has. I was pointing out they were eliminating a pain point in a nice way in the next version, which some people who have evaluated C5 in the past would likely want to know. I was providing info.
Finally, your point falls on it's head. You asked for a reason that is the case? I said it clearly: "I look at how easy it is for end users to pick up and customize". That's the important part, and when I last checked, C5 beat Drupal by a lot. That could have changed, admittedly, but in just checking a v8 video demo on youtube, it's no where NEAR as elegant and clean and usable for users. It's night and day.
See for yourself: https://www.youtube.com/watch?...