Ask HN: What is your fav “I can't believe in 2022 this still doesn't work right”
Mine is iPhone as hotspot/'net sharing feature, for other mac products (macbook pro, macbook air, etc.), be it bluetooth or wifi, let alone non-mac clients == ongoing failures/stoppages, regardless of iPhone or macbook models.
293 comments
[ 1.9 ms ] story [ 352 ms ] threadGood times.
The use of depth and colors is streets ahead of the contemporary flat GUIs. You never have to guess the type or state of a widget, or where it begins or ends. Buttons typically have both icons and text. Icons to make it quicker to navigate, text makes it accessible without being fluent in Linear B ideograms.
Implementing a progress bar that works for things like "bytes uploaded" or "number of tasks in the queue" on the frontend is fairly trivial. The hard bit is how to transmit a progress value from the backend to the frontend. Typically that requires setting up either a socket or a keepalive connection, or polling an endpoint from the frontend, which is enough of a pain that very few web apps bother.
Ultimately everything required for this sort of feature is right there in every browser. It's the backend that's usually lacking.
Just check it: https://www.youtube.com/watch?v=kPv1gQ5Rs8A
It's not an intractable problem, just tricky and annoying. If a progress bar is a tiny fraction of an app's lifecycle it's a lot of work to make it accurate for little payoff.
The hate for power users is real.
Users have become an instrument, rather than ends in themselves. You're attempting corral them so they do something you want instead of empowering them and offering them tools they may need to do what they want to do.
The very notion of power users is deeply incompatible with this.
Now power users are merely an inconvenience, since they usually advocate against dark patterns and prefer purely functional software.
I'm not sure how to really combat this. It might be too late.
Biggest offender is a large OS upgrade on Mac and it sits on that black screen. It often doesn't even say how long is left, but when it does the 'remaining time' is laughably wrong. Not really excusable when Apple have such a small range of hardware configs.
I've seen some Windows installers 'x remaining' consistently count upwards instead of downwards...or the other classic, it sits at 10% for a while and then suddenly jumps to 100
It's basically printers all over again. It sucks!
[0]: Assuming you don't need color or images. Black and white images look awful.
Apart from that the whole display servers world is just not working well. Some things still don't support Wayland, you can't share screen easily, X has it's own issues etc. HiDPI is still problematic with both; you get weird scaling issues with apps and and the occasional humongous mouse cursor. Using multiple displays with different DPIs you again get scaling issues. Setting up multiple displays still requires fiddling with xrandr, xinerama etc.
Just let me know if you need more examples. I tried to fully switch to Linux many times spending lots of time + money (bought one of the "recommended" devices).
HDR is just a marketing term for software that increases the colour and black saturation of content beyond the actual input. For photography that means more saturation than what you see in real life, for video that means tweaking it after you receive the signal.
An OS can't "support" or not support HDR; if a video has HDR and your display has the dynamic range then you'll see it in "HDR". Unless you actually want your OS to post-process everything on the screen to have marginally higher contrast than normal?
https://support.microsoft.com/en-us/windows/what-is-hdr-in-w... https://www.pcworld.com/article/546269/auto-hdr-deep-dive-ho...
> Setting up multiple displays still requires fiddling with xrandr, xinerama etc.
Dunno what you're doing but you can literally just plug in another display and it'll work... And per-monitor scaling works on Ubuntu/Gnome.
Not even remotely correct. It is definitely not a marketing term. HDR is set of specifications and formats for capturing, storing and displaying visual data with a higher than "Standard" dynamic range. It basically carries more data and it requires proper color management. It has to be supported by relevant drivers and the display server. Right now there is no way to view HDR content (video, photos or games) under Linux.
If you are interested; there is some effort going on to enable this but it will probably take a couple more years.
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...
https://gitlab.freedesktop.org/pq/color-and-hdr
"HDR" is just metadata to pass along to the device to tell it how to optimally adjust the colours (or not adjust them). It's main use seems to be so that HDR displays can oversaturate "SDR" content in HDR mode.
> carries more data
Not really. The metadata isn't more colours or something, it just passes info to the device about certain aspects of the video.
HDR content will be HDR if the display has enough range regardless of whether or not the OS has HDR "mode". It's more about adjusting all the other content.
Dunno if you ever had a plasma TV back in the day but they could display way more contrast than LCDs of the day so you could adjust the settings to change the way all content looks. HDR metadata is basically that, but on a per-video basis. Useful enough but not some game changer... Which is why there's tons of articles about what HDR does and doesn't do.
Edit - where HDR really is great is photography... You take multiple photos of the same scene with different ISO and shutter settings then stitch them together for more colours than would otherwise be captured. But a screen can either display colours or it can't.
HDR content "will not" be HDR if you're playing it under Linux. It will however be HDR if you play it under Macos or Windows (keeping everything else like the screen and content same). There is no way around this right now. So in basic terms you will not see the dark blacks and bright whites under Linux.
> Edit - where HDR really is great is photography... You take multiple photos of the same scene with different ISO and shutter settings then stitch them together for more colours than would otherwise be captured. But a screen can either display colours or it can't.
It's the same for video or games really. With HDR you can record and display more details and contrast.
And that HDR photo you just described will not be shown as HDR even if your display supports HDR if viewed under Linux
But anyhow, Ubuntu supports 10 bit colour and has for awhile:
https://wiki.ubuntu.com/DeepColourDepthSupportPlan
edit: and 10 bit color support on its own is not enough for HDR. I mean I don't know why we are even discussing this honestly. HDR under Linux is not supported at all. It's not an opinion; it's an objective fact which you can confirm in a couple of different ways. You can not view HDR content if you're using Linux no matter what content or display you have. There is an active effort in the community to have HDR support in Linux but it will take a couple more years probably.
You mean "works if you don't actively try to break it".
Most stories about Linux breakage involve esoteric distros (especially bleeding edge "rolling" distros or one-man Ubuntu-derived distros) and users trying to "customize" shit they shouldn't.
Install Ubuntu and it's fine.
No I mean "if you don't want to share your screen"
I've "tried" Windows too and simply can't deal with how terrible it is.
Ever checked in on the youth lately? It's all smartphones, game consoles, iPads.
Students will use MacBooks/Laptops/Chromebooks for school if their course requires one but "devices" are the main computing device nowadays. Heck, even many non-technical business people have switched to iPads. Kiosks? Tablets.
The PC is no longer "the" personal computing device...
It might sound like a joke, but AirPrint on my iPhone has been the most reliable way to connect to my printer by far.
Specifically I volunteer for a group that uses SMS with embedded links for the volunteers to tap to check in and out of a job. Frequently these links are truncated or divided in a way that makes their URL structure invalid. This happens all the time due to the difference in message length and how iOS handles longer messages.
I know this boils down to an SMS character limit kludge, but our Android users do not experience this. The message comes as one block or "bubble" but the iOS users see multiple bubbles that are frequently out of order.
Fahgettabouttit.
Word is also remarkably bad with long (100+ page) documents and lots of different content sources. If you're not pasting as pure text into Microsoft Word, you're playing with fire.
Also, I suspect it's cruft inside the program that has made this problem actually worse over time, not just "still a problem". Thank god Markdown is now more widely supported, including on Microsoft-owned Github.
Could not for the life of me get it working. Had to dig up a usb thumbdrive.
I used to have this working fine in 2002.
It's a credit card. It doesn't have a damn PIN in the US, and I have to go inside to pay for gas every time. I've quit buying gas at the area Mobil stations because of the hassle. Most of the other chains seem to get it right.
How is it that Europe has been doing chip cards (with PIN) for decades, and we can't get this right?
It’s not perfect, but it’s pretty good.
Lots of other things mentioned piss me off too, but I can usually see (to my dismay) where the perverse incentives lie, or the lack of a market drive, or whatever.
This seems like a problem people would like to see solved, where nobody has reason to get in the way of solving it, and that should be solvable by now.
Google's keyboard is great for exactly this (I type in 4 different languages regularly).
It goes "0 Days, 1 Day, 2 Days".
Not "0 Days, 1 Days, 2 Days". Or, worse, "0 Day(s), 1 Day(s), 2 Day(s)".
• are there 3 or 4? (Plural isn't just zero/one/many in every language.)
• is the quantity small-ish, or large-ish, compared to normal?
• what's the grammatical position of the noun you want to pluralise?
You'd have to have something a lot more sophisticated than string substitution. And there isn't really a pressing need for it. Day(s) works fine.
Most solutions rely on sending a file to some server in probably a different country, and then downloading said file on the other computer. Or, using a USB stick to pass the file from one to the other.
So a discord server with just me in it is ... also gives you handy direct links for files up to 8mb.
https://kdeconnect.kde.org/download.html
(It's also great as a remote control for your laptop when watching a movie or series on a projector)
I feel your pain, I tried tons of other solutions before discovering KDE Connect. It works well for my laptop/phone combination, but I'm not surprised if it doesn't work for others, given how horrible each other solution was that I've tried.
edit: I wonder if perhaps some part of your phone hardware overheats after N megabytes because it's not built for constant file transfer, or constant file transfer using these protocols at least? What if you try throttling it on purpose?
I think it is the fault of the network stack of one those two devices, otherwise I can't explain that. Maybe that the devices receive/send data faster than they are able to process. (Is this even possible?)
But I could be awfully wrong
Regarding your edit: That's a good idea, but I never attempted that. I can't test that, because I'm in a Wifi where no device is allowed to talk to another :(
$ python3 -m http.server 1337
Then just connect to the IP and Port of the machine hosting the python http server and transfer away.
Aside from Bluetooth I'm not sure how you'd do this without using a LAN or WAN.
Pythons web server is single threaded I believe so any simultaneously connections break.
https://github.com/schollz/croc
Would be great with local network discovery of p2p peers but seemingly browsers are not really interested in enabling that...
Of course all of these solutions have some serious pre-requisites...
Bluetooth doesn't consistently work for connecting I/O devices to my computer, though. Only peer-to-peer file transfer.
Yes it was slow, but it worked straightforwardly and reliably, every, single, time.