The ideal viewport doesn't exist

Post by kube-system » Tue, Aug 22, 2023, 2:55 PM UTC

ghusto wrote: post #190

kube-system wrote: post #84

Earlier quoted context omitted.

I presume you're talking about maximized windows, but that still does not equal "filling the entire screen", because browsers have their own user interface around the viewport. Go maximize your browser and enter this into your dev tools: console.log(`${window.innerWidth}x${window.innerHeight}`) Does that equal your screen resolution?

I did differentiate here ;) and even mentioned that I "sometimes even [see] the entire screen (in fullscreen mode on MacOS) [being used]"

Post by eddd-ddde » Tue, Aug 22, 2023, 4:09 PM UTC

ncallaway wrote: post #145

kyleyeats wrote: post #129

Earlier quoted context omitted.

You're mad at the wrong people here. I've never met a frontend dev who doesn't hate moving stuff vertically or scrolljacking. It's the marketing people that want it.

The one that hurt me the most was making a page that started at the bottom and scrolled up. I left a comment somewhere in the JavaScript apologizing for it.

Post by creole_wither » Tue, Aug 22, 2023, 4:33 PM UTC

beeslol wrote: post #152

> If you’re on a desktop device reading this, how many windows are filling the entire screen? How much screen space does the browser you’re reading from take up? > It’s safest to presume that users on desktop or laptop devices are not filling their entire screen with a browser. Is this true? If you're reading this casually (and you are reading this casually) is your browser not at full size? I almost exclusively use…

Post by zlg_codes » Wed, Aug 23, 2023, 7:24 PM UTC

thrashh wrote: post #165

zlg_codes wrote: post #132

Earlier quoted context omitted.

I'm trying to learn some JS in my spare time, if only to show in interviews that I can do it, but I understand why one wouldn't want to. I'm just doing bare JS for now, but even with a framework, there is so much to manage in the DOM to make consistent interfaces, and CSS3 is so much more complex (but also convenient, in some ways!), putting together good interfaces is legitimately hard. Responsiveness is the big hur…

Web dev frontend has a thousand quirks but has a billion more hours of human hours development time spent on it. CSS is annoying but way better than trying to jiggle random attributes and subclassing stock components to do something basic like right align a label. You'll notice that a lot of GUI toolkits have already adopted something like CSS (Qt Style Sheets, JavaFX CSS, etc.). Yet they will never become as good, j…

Post by hddqsb » Sun, Aug 27, 2023, 12:11 PM UTC

avmich wrote: post #92

The visualization, I think, could be improved. Make a graph of points, where X and Y coordinates correspond to width and height of the viewport, this is like imagining all those viewports having the same left top corner and recording bottom right corner. Those points on the graph which correspond to more frequently occurring viewports should be brighter (if not bigger circles). Many points for large number of small v…

    import csv
    from math import sqrt
    import sys

    csv_reader = csv.reader(sys.stdin)
    headings = next(csv_reader)
    data = [tuple(map(int, row[:3])) for row in csv_reader]
    max_w = 7100 # max(row[0] for row in data) + fudge
    max_h = 7100 # max(row[1] for row in data) + fudge
    max_count = max(row[2] for row in data)

    margin = 200
    svg_width = max_w + 2*margin
    svg_height = max_h + 2*margin
    max_r = 90
    min_r = 4

    print('')
    print(f'')
    print('Visualization of viewport sizes from https://viewports.fyi/')
    print(f'')

    print(f'')
    print(f'')
    for i in range(0, max_w, 200):
        print(f'{i}')
        print(f'')
    for i in range(0, max_h, 200):
        print(f'{i}')
        print(f'')

    print('')
    for w, h, count in data:
        r = max(min_r, sqrt(count) / sqrt(max_count) * max_r)
        print(f'')
    print('')
    print('')