4,014 karma · joined May 31, 2011
Uh, yes they are? That's why they were revolutionary technologies!
It's hard to see why a bike that isn't superhuman would even make sense? Being superhuman in at least some aspect really seems like the bare minimum for a technology to be worth adopting.
Modern icons are not only not comprehensible but not visually distinct (Tahoe making everything the same shape, many apps removing all colour from toolbar icons, various distinct if anachronistic symbolic icons like Save being replaced with slighly different orientations and arrangements of arrows and rounded rectangles...).
This severely impacts the efficiency of user interaction, especially after the first time you use something, at least for me. It's not a knee jerk reaction, it's a reaction to actually feeling it becoming harder to use my computer.
That seems like the kind of feature where the LLM would already have the domain knowledge needed to write reasonable tests, though. Similar to how it can vibe code a surprisingly complicated website or video game without much help, but probably not create a single component of a complex distributed system that will fit into an existing architecture, with exactly the correct behaviour based on some obscure domain knowledge that pretty much exists only in your company.
I think the criticisms of The Hobbit when it came out in 48fps showed that it's not just that.
I don't play flight sims but I imagine most flight surfaces require small adjustments and the effect of those adjustments on the aircraft is naturally smoothed out by the dynamics of the plane (you're adjusting an acceleration).
I imagine the scroll wheel is not suitable for dogfighting.
I would say the opposite, it's basically the perfect interface for a very specific scenario with requirements that don't really occur in much other computer software.
- making sure pixel are square while resizing if the video resolution is too large
("scale=w=if(gt(iw*sar\\,ih)\\,min(ceil(iw*sar/2)*2\\,{})\\,ceil(iw*sar*min(ih\\,{})/ih/2)*2):h=if(gt(ih\\,iw*sar)\\,min(ceil(ih/2)*2\\,{})\\,ceil(ih*min(iw*sar\\,{})/iw/sar/2)\*2):out_range=limited,zscale,setsar=1")
- dealing with some HDR or high gamut thing I can't really remember that can result from screen recording on macos using some method I was using at some point- setting this one tag on hevc files that macos needs for them to be recognised as hevc but isn't set by default
- calculating the target bitrate if I need a specific filesize and verifying the encode actually hit that size and retrying if not (doesn't always work first time with certain hardware encoders even if they have a target or max bitrate parameter)
- dealing with 2-pass encoding which is fiddly and requires two separate commands and the parameters are codec specific
- correctly activating hardware encoding for various codecs
- etc
And this is just for the basic task of "make this into a simple mp4"