It's not what you see with Touchwiz that is the issue, it's the legacy files and redundancy that is under the touchwiz GUI.
There are system files that are remnants of older touchwiz features that are still lingering and duplicated services running that are simply redundant. Their are legacy files that are remnant from 4-5 generations / iterations ago still lingering like a dirty STD that won't go away.
It's why Samsung's System usage always hovers over 2gb or greater without anything else running and despite 'sliming down the launcher' system usage has increased year on year.
Even skins like Sense which offers just as much features and customisation over stock keeps its System ram usage below 1gb (usually around 750mb), LG which has a very heavy skin around 750mb-1gb and likes of Moto & Sony around 700mb too which is very similar to stock android system memory usage. By keeping system memory in check, more memory is invariably available to apps.
Samsung whilst improved the front end of Touchwiz over the years has simply swept all the detritus under the carpet and now we feel the problems that this can create. It's why we have the ram management issues on their 3gb devices and why even with an extra 1gb the Note 5 & Edge+ still can't keep as many apps open as the likes of the HTC M9 or LG G4 devices despite them having a gig less to spare.
So when people are asking for Touchwiz to debloat it's not the GUI or the 'what you see' that is the problem, it's a desire to see Samsung lift up their carpet and give it a good cleaning and remove those dozens of services & legacy files from the OS. There is no reason for Samsung's OS to use more than twice the resources of its competitors, and giving it a good thorough clean - even if it means rebuilding what it offers now from the ground up to get rid of the deadwood, it would only serve the end user better regardless of which model Samsung device they buy.
Samsung for too long has been throwing hardware muscle at the mess in order to budge & shove it's way through it, rather than just simply sweep it up in the first instance.
I'm on board with all this. I wonder what it takes to dig deep like what you're describing to overhaul the legacy files. Is it that simple as "going under the rug" and cleaning it out? And if it is, why hasn't Samsung done it? Are there any online articles about this I can learn more about? Not that I'm not taking your word for it. It's just interesting and I want to find out more about what's going on and exactly why Samsung isn't doing this specific move.
Maybe they are with the rumored Google's help?
Either way, my point remains, Samsung has year to year done near exactly what everyone has been asking them to do both on the hardware front and software front. And as far as I can tell regarding the software, it's working. I disagree they're just throwing hardware at it, but even if that's all they're doing, bring it on. Larger battery, 4GB of RAM, better SoC, etc. is all going to at the end of the day make the user experience better. So what's wrong with this exactly?
If they can do that AND couple that with continued focus on software, which is something they've been saying they'll focus on in 2016, it's as if they're solving the issue on both ends of the platform.
Isn't it inten that intentional? If their advances in hardware/software is enough to make the S6 and Note 5 run the way they do, I still don't believe they necessarily need to turn the entire software ship around and "build from the ground up" as you say. How many people exactly are that dramatically affected by the way TW runs apps or memory management? And why does it only afflict few S6/Note 5 users and not everyone across the board? Who is switching between 8-9 plus apps at a given time (that was about the number where the RAM started closing apps, right? 8 or 9 or more)? It just feels to me this whole RAM management thing is overblown and/or afflicting only a subset of extreme power users.
Again, I would never argue for anything getting better, and if indeed when/if Samsung builds the software back from the ground up and it leads to an excuse-less experience of TW, then I'm all for it.
I'm simply saying, until then, they've been doing the right things. And if the rumors pan out that they're doubling down on software improvements even more this year, then the potential is there.
Touchwiz runs amazingly well for me on a day to day driver. It hiccups here and there on rare occasions, but all OS-es do. This is not exclusive to TW (I know two people with Nexus 5X's -- heck, I bought it for them. And even online, there have been stories of lag. Ditto iPhone users and my own iPhone experience. I use to have the iPh6). But is it lagging and having issues that require Samsung to completely turn their ship around? I don't know. I don't think so. Is the RAM issue so bad that they can't solve it any other way than to obliterate their current OS structure and rebuild from the ground up (again, what does that entail? What resources? What are the costs?). I don't know. I don't think so again. Why isn't it as simple as changing the software's RAM management? Is building from the ground up the only way to solve the RAM issue?
TL;DR:
I'm all for it. I upvoted your post and agree it'd be great if that happens one day. But I'm also okay if it doesn't happen given what they're already doing and promising with their hardware/software. It's been going in nothing but the right direction, even if it's not all the way there yet.
[doublepost=1454175574][/doublepost]Did the RAM management not get any better at all (I'm saying literally unchanged from TW of S6) in the S6 Edge Plus and the Note 5? I didn't follow Edge Plus or Note 5 rumors/stories very closely cause I decided those devices weren't for me, but I thought there were stories of better RAM management?
Is the RAM management thing fixed or improved in any early preview Marshmallow builds of TW?
Everything I'm reading about it says it's a mystery why Samsung manages RAM this way but it sounds intentional. Does this really have to do with legacy files, and is the only fix to rebuild from scratch their software? Shouldn't it be as simple as changing the way RAM is managed in the software? It really needs an overhaul to achieve this?
It really is weird, and I'd love to see Samsung fix this. But in my day to day use of switching between a few apps, I don't feel the affects so dramatically. It's literally a split second before apps are ready to go when switching on my S6.