Yeah I totally agree. But still, I feel like there are much more terrible GUI programs out there than terrible CLI programs. The only truly awful CLIs I can think of is that tool for managing MegaRAID controllers that has the weird abbreviations everywhere, and shell interfaces to GUI-first bloatware like Dconf that were probably added as an afterthought. I think with CLI there's only so many things that the developer can fuck up. It's all just text. Meanwhile with GUI there are endless opportunities for truly horrid design. Think of Teams. Think of the github web interface. Think of the rddit redesign. Or go watch that Tantacrul video on Sibelius. CLI could never have such a breadth of terribleness.
This is a good practice tho. The HTTP code describes the status of the HTTP operation. Did the server handle it? No? Was the url not found? Did it time out? Was the payload too large? And the JSON describes the result of the backend operation. So 200 OK with error: true means that your HTTP request was all good, but the actual operation bugged out for whatever reason. If you try to indicate errors in the backend with a HTTP error code, you quickly get confused about which codes can happen for what reason.
I once dragged one of those ceramic powerline insulators across two international borders because I found it lying around and liked how it looked. It took up the majority of the space in my backpack, so I had to buy a second backpack and carry it on the front of my chest lol. Apparently the reason they have that odd shape is so that when it's raining, water can't make a continuous trickle between the wire and the pylon
"The fuck else were these people expecting" is also my visceral reaction whenever shit like that happens, but if I think about for a bit longer, I realize that it's not much different than saying "The fuck else were you expecting" to a rape victim who went alone into a dark alley. Sure, people are stupid for engaging with this obvious scam, but the bad guy is still the scammer, not the victims.
Hmmm interesting. I've never had issues with that. I just mount it once to a mountpoint in my shared storage and it just works. Probably a ROM-specific thing.
Because it's unbelievably broken. Every time I try to set it up it's always a huge pain, and in the end it's extremely flakey at best. I've only ever seen the SMB protocol work as expected with its native windows implementation, third-party implementations like sambda are awful
SSHFS actually works perfectly on android, just needs root. Here's the app I use.
It's funny how the README calls it a "VERY bad solution", but so far it's the only remote filesystem tool I've seen on android that could be described as anything close to usable.
Yeah I totally agree. But still, I feel like there are much more terrible GUI programs out there than terrible CLI programs. The only truly awful CLIs I can think of is that tool for managing MegaRAID controllers that has the weird abbreviations everywhere, and shell interfaces to GUI-first bloatware like Dconf that were probably added as an afterthought. I think with CLI there's only so many things that the developer can fuck up. It's all just text. Meanwhile with GUI there are endless opportunities for truly horrid design. Think of Teams. Think of the github web interface. Think of the rddit redesign. Or go watch that Tantacrul video on Sibelius. CLI could never have such a breadth of terribleness.