Absolutely no point in having these be separate projects - with the rise of 'superphones,' there's not that much difference in horsepower anymore, and one platform target is better than two from a developer standpoint (usually).
Wiki reader chrome app github android#
I'd like to see Chrome OS & Android merge sooner rather than later. Seriously - Chrome OS or Android running on a nice 1-2gHz dual-core ARM beast with hardware accelerated HD video w/ 4GB of memory is probably all that most people need at home, as long as it's got a decent screen, keyboard and mouse, they're set.ĭownload your Android apps, of which there *are* thousands (though many different versions of a much smaller number of TYPES of applications) for expanding into more obscure things. IM & email clients can be handled by the browser. You got your web browser and your IM client (maybe), (maybe) an email client, a DVD player, and I bet that's it for the vast majority of computer users outside of work.
Most people don't even use dozens of apps.
Wiki reader chrome app github software#
The software you need to write and run on the device could do allot by simply offloading the thinking to the oh lord dare I say it? cloud.Īnd you also mean the porting of thousands and thousands of x86 apps as well?īut most people don't USE thousands and thousands of apps. Hell use libcacca to render images as ascii art. Get send html no problemīecomes 13 and 10. There is all kind of infrastructure around, let the POP or IMAP server do the thinking, just add a command like TXTPLZ to the protocols that would instruct the server to render messages sent in other formats out as plain characters. We don't live in the same world that 80x86 lived in.
Things like e-mail would be very doable as well. Something that could connect to the internet wireless-ly and run lynx and those kinda of apps would be just perfect, even if the screen refresh was slow an e-ink based. I would be very happy with a device that was inexpensive enough to leave on the back seat of my car for weeks on end that would be just there if I needed it and ready to go. I had to go back because I was afraid I might miss SMS alerts from critial systems because the things battery went flat. The batter never goes flat over that time frame. I charge it Sunday night before I go to bed and I talk and text on it as much as I want to all week long. I have cell phone, not a facy smart phone. You know what we were like pigs in s**t happy too. I not so sure, it was not all that long ago most of us who even had a computer were working on an 80x86 or 80x88 with a 512k of memory, connected to a 80x25 character monocrome display, with no network interface, and primary storage consisting of a box next to the unit filled with 360k floppy disks. Best thing to do would be to jailbreak an existing e-reader, its simply a bad business decision to make a product with almost no market. Really, other than you, this wouldn't appeal to a large enough audience of people. What apps would make sense to port to this device? Lynx? Most other things would need more CPU power (making it non-energy efficient) or a colour screen. Even if they sell it at a profit they still can buy parts in bulk and make them cheaper than a product with a run of only ~1,000 units or less.Ĭ) There aren't enough apps.
Amazon can afford to produce the Kindle at-cost or even with a bit of a loss because they will gain sales in e-books and such. well anything unpleasant to look at other than text.ī) It will be expensive. Yes, it does ease strain on eyes and increase readability, but has the other side of making most of. Look at how well monochrome TVs are selling. Lets see hereĪ) Monochrome displays (other than E-ink) are generally considered to be low-tech, cheap, pieces of junk. Because there is almost no market for it.
0 kommentar(er)
