You forget the interactive nature of WYSIWYG editors- if you have tooling enough to throw together a UI in front of a group of people as part of requirements ga

You forget the interactive nature of WYSIWYG editors- if you have tooling enough to throw together a UI in front of a group of people as part of requirements gathering and just 'do you like how this looks' it can be very powerful- especially when you can show up a few hours later and have the broad strokes mostly working. It is also a natural design constraint- if it is not easy to do with a the generator it's probably going to require to do extra work so you can give a near equivalent that is less expensive but easier to do. Without WYSIWYG and current web dev you can bring it to a whiteboard and hash out a design and then find out that for some reason that it is really annoying to make work well on everything you need to support. It's really the consensus driver that makes WYSIWYG always a very helpful tool.