Okay y'all, so there's this app on iOS called A-shell.
-
@pixelate does it have any packages at all? i see no mention of a package manager on the app store or GitHub repo
@Willow It has pkg but I've not found any packages from there yet. Like no info or rust or anything.
-
@Willow It has pkg but I've not found any packages from there yet. Like no info or rust or anything.
@pixelate what if you do like , `pkg search .`? -
@pixelate what if you do like , `pkg search .`?
@Willow Tried that with Emacs, nothing. Although I haven't tried with an empty search before.
-
@Willow Tried that with Emacs, nothing. Although I haven't tried with an empty search before.
@pixelate yeah hence the dot. i suppose a hyphen would work too -
@pixelate what if you do like , `pkg search .`?
@Willow Okay "pkg search" does give a list of packages.
-
@pixelate LOL you just go with whatever looks good at the time. Sometimes you're mad hella complaining about iOS and bragging about android, sometimes like now you're doing the complete opposite.
@Bri @pixelate Isn't that the reasonable thing to do? Accessibility on Android is a disaster, but the OS itself and what people can do with it is great. iOS is far worse as an OS, and slightly better in terms of accessibility. If anyone talks about one and never complains about it, or talks about the other and never praises it, I would know he didn't really understand. To point out the good and bad bits of both is basically what you have to do as a user, isn't it? I wish I could have the accessibility of iOS with the capability of Android but,as it stands, that isn't on the list of possibilities. That, BTW, is not saying that iOS accessibility is anything wonderful. 5/10 where Android is 3/10, at least with Talkback.
-
@Bri @pixelate Isn't that the reasonable thing to do? Accessibility on Android is a disaster, but the OS itself and what people can do with it is great. iOS is far worse as an OS, and slightly better in terms of accessibility. If anyone talks about one and never complains about it, or talks about the other and never praises it, I would know he didn't really understand. To point out the good and bad bits of both is basically what you have to do as a user, isn't it? I wish I could have the accessibility of iOS with the capability of Android but,as it stands, that isn't on the list of possibilities. That, BTW, is not saying that iOS accessibility is anything wonderful. 5/10 where Android is 3/10, at least with Talkback.
@techsinger Yeah, I think @Bri was pointing out that this exact nuance didn't exist in the original post. To say that nobody mentions Talkback in Android app updates/descriptions is just completely false. And it's often the small obscure projects that do pay attention to accessibility, on both operating systems.
I'm certainly excited to try this out though. Maybe I can rangle it into behaving as an adequate SSH client. -
@techsinger Yeah, I think @Bri was pointing out that this exact nuance didn't exist in the original post. To say that nobody mentions Talkback in Android app updates/descriptions is just completely false. And it's often the small obscure projects that do pay attention to accessibility, on both operating systems.
I'm certainly excited to try this out though. Maybe I can rangle it into behaving as an adequate SSH client.@simon @Bri Is it completely false? For every mention of TB in an app update on Android, I see maybe three or four mentions in iOS apps. I always feel like many, if not most, Apple devs treat accessibility as a nice to have so long as they don't have to do any actual work. Most Android devs, though, treat it as something they might have heard of, at some point, maybe... My point is that it's an afterthought on iOS and not a thought at all on Android. Granted that this isn't always the case, what I'm saying is that it's the common case, the usual thing. As I said, 5/10, if that, on iOS, but there is a difference between that and 3/10 on Android. Again, one of the greatest disappointments of the past twenty years. So much potential wasted.
-
@simon @Bri Is it completely false? For every mention of TB in an app update on Android, I see maybe three or four mentions in iOS apps. I always feel like many, if not most, Apple devs treat accessibility as a nice to have so long as they don't have to do any actual work. Most Android devs, though, treat it as something they might have heard of, at some point, maybe... My point is that it's an afterthought on iOS and not a thought at all on Android. Granted that this isn't always the case, what I'm saying is that it's the common case, the usual thing. As I said, 5/10, if that, on iOS, but there is a difference between that and 3/10 on Android. Again, one of the greatest disappointments of the past twenty years. So much potential wasted.
@techsinger @simon nevermind forget I even commented. Lmao
-
@techsinger @simon nevermind forget I even commented. Lmao
-
Okay y'all, so there's this app on iOS called A-shell. It's a local terminal emulator, just with far fewer packages than Termux. No, it doesn't have Emacs, sadly.
So, a few days ago, they released a new version with some update:
Version 2.0.0, 2d ago, - new terminal rendering system (SwiftTerm), much faster than the previous one, but with incompatible changes - better integration with VoiceOver - better autocomplete - new config options, for blinking cursors - multi-arrow buttons on iPhones - better user interface for the internal browser - added Python package: curl-cffi
Did y'all catch that? It works with VoiceOver. Yeah, it's because of a library they're using, but when does some random app on the Play Store ever mention TalkBack? This is why iOS accessibility feels so good: because of the app developers who know about VoiceOver and make their apps feel good to use and sensible.
#A-shell #apple #iOS #accessibility #blind
-
-
Okay y'all, so there's this app on iOS called A-shell. It's a local terminal emulator, just with far fewer packages than Termux. No, it doesn't have Emacs, sadly.
So, a few days ago, they released a new version with some update:
Version 2.0.0, 2d ago, - new terminal rendering system (SwiftTerm), much faster than the previous one, but with incompatible changes - better integration with VoiceOver - better autocomplete - new config options, for blinking cursors - multi-arrow buttons on iPhones - better user interface for the internal browser - added Python package: curl-cffi
Did y'all catch that? It works with VoiceOver. Yeah, it's because of a library they're using, but when does some random app on the Play Store ever mention TalkBack? This is why iOS accessibility feels so good: because of the app developers who know about VoiceOver and make their apps feel good to use and sensible.
#A-shell #apple #iOS #accessibility #blind
@pixelate Can you please send the link to the app? I'm not able to find it on Appstore.
-
@simon @Bri Is it completely false? For every mention of TB in an app update on Android, I see maybe three or four mentions in iOS apps. I always feel like many, if not most, Apple devs treat accessibility as a nice to have so long as they don't have to do any actual work. Most Android devs, though, treat it as something they might have heard of, at some point, maybe... My point is that it's an afterthought on iOS and not a thought at all on Android. Granted that this isn't always the case, what I'm saying is that it's the common case, the usual thing. As I said, 5/10, if that, on iOS, but there is a difference between that and 3/10 on Android. Again, one of the greatest disappointments of the past twenty years. So much potential wasted.
@techsinger @Bri I mean, false is an absolute. If *some* app developers are mentioning Talkback, it's still happening, so to say it never happens is still wrong.
Also, I've noticed that Android seems to have fewer completely invisible controls, though it could just be my experience with the apps I've used. I've seen interfaces that are essentially identical across Android and iOS, with VoiceOver completely unable to see a particular control even though Talkback can find it. Maybe the control isn't labeled, but even then, there's a built-in option to describe it.
So the more iOS continues to degrade in stupid ways, the more it starts to feel like they're on a level playing field. And I still think there's an adoption problem, where most people have to choose one or the other and they choose iOS, so there aren't as many people trying to get app developers to implement Talkback support. If there's only one mention of Talkback for every five mentions of VoiceOver, there's only one full-time Android user for every 25 blind iOS users. Not enough people are willing to be part of the change they want to see. I honestly think it's impressive that we have so many accessible apps available to us on an OS which is very much the "other" option in this community. -
@techsinger Yeah, I think @Bri was pointing out that this exact nuance didn't exist in the original post. To say that nobody mentions Talkback in Android app updates/descriptions is just completely false. And it's often the small obscure projects that do pay attention to accessibility, on both operating systems.
I'm certainly excited to try this out though. Maybe I can rangle it into behaving as an adequate SSH client.@simon @techsinger @Bri Wait, did I say no apps do? Okay, yeah that was too far, but I've maybe only seen one.
