Hear hear! A bit of background to the politics of this:
NFTables is brought to you by a group of codes created when Alexey Kuznetsov decided to replaced the low level linux network stack for Linux 2.2 to make it more like what Cisco provided in IOS. The result added whole pile of new functionality to Linux (eg routing rules), and a shiny new highly module traffic control engine. Alexey produced a beautifully written postscript documentation for the new user land routing tools (the "ip" command), and 100 line howto for the far more complex traffic control engine tools (the "tc" command).
Technically it was a was tour de force. But to end users it could at best be called a modest success. Alexey re-wrote the net-utils tools ("ifconfig", "route" and friends) to use the new system, and did such a good job very few bothered to learn the new "ip" command even though the documentation was good and it introduced a modest amount of new features. But real innovation was the traffic control engine, and to this day bugger all people know how to use it.
At this point it could have gone two ways. Someone could have brought tc's documentation up to the same standard Alexey provided for ip, or they could ignore the fact that almost no one used the code already written and add more of the same. They did the latter.
It was also at this time the network code wars started in the kernel. Not many people know that a modest amount of NAT, filtering and so on can be done by Alexey's new ip command. But rather than build on that Rusty Russell just ported the old ipfwadm infrastructure, called it ipchains (and later replaced it with iptables). There was some overlap between Rusty's work and tc, and this has grown over time. For example the tc U32 filter could do most of the packet tests ipchain's introduced over time on day 1. Technically the modular framework provided by tc was more powerful than ipchains, and inherently faster. Tc was however near impossible for mere mortals to use even if they had good documentation. There were some outside efforts to fix this - tcng was an excellent out-of-tree attempt to fix the complexity problems of tc. But in what seems like a recurring theme, it was out of tree and ignored. In contrast, Rusty provided ipchains with the some best documentation on the planet. In the real world the result of these two efforts are plain to see - while man + dog uses iptables, there maybe 100 people on the planet who can use tc.
Another example of the same thing is IMQ. IMQ lets you unleash the full power of the traffic control engine on incoming traffic. (Natively the traffic control engine only deals with packets being sent, not incoming packets - a limitation introduced for purely philosophical reasons). IMQ was very well documented, and heavily used. The people who brought you tc had a list of technical objections to IMQ. I don't know whether they were real or just a case of Not Invented Here, but I'd give them the benefit of the doubt - they are pretty bright guys. So they replaced it with their own in-kernel-tree concoction. (For those of you who don't follow the kernel "in-tree" means it comes with the Linux Kernel. An out-of-tree module like IMQ means at the very least you have to compile the module source, and possibly the entire kernel.) For a while this discouraged the developers of IMQ so much they stopped working on it. If you follow that link, you will see it's back now. Why? Because the thing that replaced it had absolutely no documentation. They never do. So no one could use the replacement. Again, in the end, the thing code that was documented won the day.
By now you might be guess where this is heading. We have two groups in the kernel competing to provide the same networking functions. All sorts of weird modules were added to the traffic control stack - things like mirred, nat, blackholing, ipset. The more observant among us noted they allowed the traffic control engine to replace iptables. No one used them of course, as in the fine and continuing tradition of this group, they weren't documented. So the net effect was to add unused orphan code to kernel. To this day, I don't know why it was tolerated by Dave Miller, the head of the networking stack.
NFTables is that latest attempt by this group to unseat iptables. This time it looks like they will succeed. For the most part this is a good thing. The duplication between iptables and Alexey's framework was always a huge technical wart, and Alexey's framework was always the better one. It will be even better if they backport the classification engine to tc, so we can use it to assign traffic control classes. If they do that most of the duplication will be gone, at last.
The one minor problem is that true to form, there is no fucking documentation.
It appears after consistently having their code ignored by most Linux users for over a decade, these bastards are incapable of learning the lesson. If Linus and his appointed networking stack maintainer, Dave Miller allows this state of affairs to continue with NFTables it will be another right royal mess.
TL;DR: If Dave Miller doesn't grow some balls and say "no user land documentation, then automatic NACK", nothing will be replaced. Instead we will end up with yet more duplication.