Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I miss WYSIWYG UI design IDE's. One can waste sooo much time fiddling with browser UI's to get it to work right on different browser brands/versions/sizes. It's a time sink that must cost the world billions. Can't we have a WYSIWYG browser standard instead of client-side-auto-flow crap?

Most internal work-related projects don't need "responsive" (resizing) anyhow; and the server could re-calc widget sizes & spacing if needed for small screens such that you don't need a fat client to manage flow engines. And they waste screen real-estate: WYSIWYG was more compact. I could point to the screen and tell it EXACTLY where to drag somebody off my lawn ;-)



How would that work? The developer would have to generate and approve a rendering for every permutation of width, height, and pixel density?

That may have worked back when everyone was using an 800x600 CRT, but it sounds unfeasible today with so many devices and orientations to consider.


You have to do such testing now with JS/DOM-based resizing. The only real difference is that it's done on the server side, which simplifies things because you have only 1 rendering engine instead of say 50 client versions. And, often 2 sizes are usually fine, and 3 if you have a big audience. And it can increase the general resolution (magnification) to fill the current screen. JavaScript resizers, such as bootstrap often do similar now: you reach a threshold before they reshuffle, and in between the thresholds, they just multiply width by a constant factor to fill the screen. And bootstrap is buggy and inconsistent.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: