I Am Developing Solely on a No-Brand Android 5.1 Tablet
tbf-rnd.life
tbf-rnd.life
Does that make it clearer?
There is no conclusion or resolution to what was introduced so I still can't fathom what you are trying to share. It feels like a situation where only half the thoughts hit the page and since we don't know the context we can't fill in the gaps.
Our issues are in the actual writing of the post, not as much what you are trying to say because we can't even get to that.
When desktops became popular in Sweden computers where rare in say South America.
Now computers are not rare in South America, which is good. The bad thing is that they are common in a consumption only format.
The problem is UI in particular text input. The solution use say gloves as input and VR systems which I predict will be cheaper and broadly available.
Until that happens a huge amount of people are stuck with smart devices, so I'd like to improve the situation. To get there I'm doing my work on a tablet to get a good idea on what works and what doesn't. Why? Because I want teenagers in the rest of the world to be able to have fun with computers as I did.
As a blog post for a random tech friend people follow, sure, that's fine. But I don't understand why this was posted to hacker news, and I don't understand why people voted it up.
Why: because desktops aren't widely available in the developing world
The "unrelated" link is a suggestion on how to write fast without a keyboard. Something that might come in handy for a non-desktop machine, don't you think?
[0] http://tbf-rnd.life/blog/2019/06/16/0-learning-curve-chorded...
So I'm looking into alternative ways of doing this.
The chorded input method is interesting in conjunction with say a all in one android VR-headset and haptic glove input, where you have all ten fingers.
What kind of software did you develop was it on a commercial basis or on open source projects?
> So my idea is to follow the principles of universal design, that is that optimizations done on extreme cases translates over the whole spectrum. Also I’m getting valuable qualitative data on current implementations. Let me tell you this, for someone developing / administrating with the lingua Franca of computes i.e. UNIX/shell computing power is not the issue. Here I’m dealing with a 512 mb tablet.
I'm not sure I understand what that means, but that's all the answer we get. (The writing quality is as poor as the reasoning.)
Also had this not been written with two thumbs, maybe the result would've been better. Embarasing as it may seem, it just goes to show the unsuitability of tablets for productive use!
Normally I have spellchecker for times like these but unfortunately she's sick :( Didn't expect to hit HN frontpage before she had time to look at it.
It's good to have feedback and in the future I'll take into account that some people have problems comprehending text.
But to say that you can not parse a sentence and that it's illogical doesn't make sense. That is like saying that you read a book in Greek, didn't understand it and still claim that the content is invalid. Do you follow?
That's kinda the best thing about Apple, they are brutally focused on solving a problem at any cost. Thats why AirPods are so small, the apple watch is so incredibly featured and why they build their own CPUs. Making choices like that sometimes means realizing opportunity cost, you can't have the best of everything.
Meanwhile, in fairness, the Mac is actually a pretty great development platform.
"
Especially with the Macbook Pro they seem a little confused whether it should be a good dev machine or a super thin high end laptop.
Except replaceable batteries, anything related to right to repair, or even calculator apps that reliably work beyond 1 digit per second
Which can be a great experience if/when you fit their priority profile. If you don't, they're permanently frustrating.
Really the takeaway should be that making things cheaper runs into diminishing returns quickly. Frugality doesn't make you less poor. Using that crappy 500MB RAM tablet might save you only $60 over the Thinkpad with 4GB RAM but it requires an incredible amount of effort compared to simply earning $60 more.
For me, a much better small and cheap dev setup is the Raspberry Pi, particularly the new Raspberry Pi 4. Pair it with a bluetooth keyboard, a portable Monitor, and a battery pack, and it's nearly as good as a laptop, but much more hackable. And you get an actual GNU/Linux development environment.
It works great and brings familiar and powerful tools to your Android devices for development and IT needs.
Lack of dev tools in chrome and firefox is an issue though.
Also a better window manager would help a lot. Less animated transitions and more i3/fluxbox like functions.
Now I'm "dogfooding" in a sense so that I can hopefully get some input on how to create a better prototype.
I don't expect to be able to make an equivalent of an desktop IDE or whatever but rather to create experimental solutions to whatever problems that might appear.
First of all an autocomplete that works on the input and output of the terminal would be great. Say if you run ifconfig the output would be automatically added to autocomplete.
Key sizes ia a problem as well where it's easy to miss keys. So I'm toying with the idea of a dynamic keyboard (which has draw backs) with sizes in accordance with Fitt's law.
I should blog about it.
internet archive to the rescue: https://web.archive.org/save/http://tbf-rnd.life/blog/2019/0...