Hi Matthew, thanks for the reply. My best justification would be the same that applies to any modern web app. You want the ability to maximize the use of screen real estate. A real-world case for us is reviewing large documents during troubleshooting. The screenshot below shows what the document viewer looks like on no frills 1080p display. The problem is obviously exaggerated substancially for our developers on QHD/4K displays.
To add a little well-intentioned humor, I haven’t seen a data-driven screen limited to 25 lines since IBM’s VT100 emulators on the AS-400 15 years ago
Especially when considering documents with nested arrays (like the example in the screenshot) 25 lines isn’t much. It also seems a little strange to limit the width, especially on the ad-hoc Query screen where real estate is prime for large result sets.
Overall, we work with some pretty big documents with nested arrays. Being restricted to 20% of the screen gets a little frustrating and seems a little out of sync with modern web apps.
Hope that help, thanks Matthew.