• 0 Posts
  • 12 Comments
Joined 11 months ago
cake
Cake day: September 7th, 2023

help-circle
  • Interesting! Sorry, I don’t know why I thought you were using swipe keyboards, it must have been stuck in my memory from reading other comments. I definitely agree that pressing the buttons was a little annoying, but manufacturers could probably make softer buttons if they were willing to put the money into developing them.

    Anyway, I really miss the phone I had from about 2008-2010. It had two sliders that moved in orthogonal directions. One of the slide directions revealed a standard 12-button phone pad, while the other had a 4-row keyboard. And yet, I’m pretty sure it was under 1.5cm, so not too large. It was definitely easier to keep in my pocket than current phones!

    If it weren’t for reading Lemmy/RSS feeds and a camera, I’d probably be going back to dumb phones for my next one…


  • But what’s the error rate? I could type at 200 words per minute (even on a phone!!) if I didn’t care about how many typos I was making. And swiping keyboards get confused incredibly easily. The error rates are especially bad when you’re writing words that only use a single row of keys - on QWERTY keyboards for example, try writing something like “type”, and you could get that, or you might get something else, like wipe/write/ripe. Other groups could include things like tip/top, pit/pot, wit/wire and the selected word will be wrong almost as frequently as it’s right. And autocorrect systems can’t really correct for things like when you mean to press enter and hit the backspace key instead. Plus, their suggestions are generally just very stupid. So while buttons take longer to press on physical keyboards, the reduced error rate makes typing speed about the same in my experience.

    Plus, with physical buttons, you get tactile feedback, so you can tell when your fingers are slightly off and adjust them, whereas on a flat surface, you have no idea whether you pressed the correct button or not. You have to stare straight at the screen to make sure every press is correct, which is exhausting and bad for your eyesight. I feel a lot more eyestrain from simply typing on phones, whereas with physical buttons, I didn’t even have to look at the screen, and I could look at something else around me while typing. And don’t get me started on how many calls I’ve missed because I accidentally hit the hang-up button, or couldn’t find the accept call button - not a problem when you have physical buttons!

    Regarding screen real estate, all you need is a slide-out keyboard. They work great!

    There are a few downsides to physical keyboards, but in my experience, they’re far superior to non-keyboard devices. But what can you do - in the 21st century, practicality never matters, it’s just all about aesthetics and nothing else…




  • I think this is a misrepresentation. What more can Linux really do to get companies like this on board? It already has pretty much all anyone would need to support the platform: GUI toolkits, graphics drivers, etc. As far as I can see, Linux provides all the same functionality that other platforms do to support this, and considering that plenty of other companies support Linux just fine (Zoom, Steam, WPS office, etc.), in my opinion, it’s unfair to point fingers and say Linux is bad because other actors pointedly ignore it.


  • Agreed. My rule of thumb is: if it takes enough more than a second to figure out why I had the tab open, then I might as well just close it and re-open it if the need to have it available reemerges. It takes a lot of effort (several seconds and a lot of mental energy) to create the mental context that I need to make use of the tab. On the other hand, opening it takes a few seconds and requires little to no thought whatsoever.

    So I just close them. In fact, having too many tabs open just makes it take longer to find the open tabs that I’m actually currently using.



  • The inevitable fate of any useful software that’s not GPL.

    When will people learn???

    Edit: Ironically, KHTML was originally LGPL. So modifications to KHTML were required to be open source by the license, but Chrome itself isn’t required to be open source (at least as far as I understand it, I am not an expert here). Nevertheless, if it were stronger GPL, then it probably wouldn’t have been impossible to write features like DRM in chrome. So I would have been a bit of an idiot to say that KHTML isn’t GPL (because LGPL is a weaker version of GPL), but in effect, the outcome is the same - all because of that big fat L at the beginning.