It functioned as a phone with a touchscreen to deliver the experience that had now become the dominant one.
But also, by sliding up the screen, it had a fully featured keyboard, and essentially transmogrified into a "pc that fits into your pocket".
So you could with a one handed push go from the touchscreen-only experience back to edit documents by using a combination of the keyboard and the touchscreen (with a stylus if neccessary).
I stopped using it because it lost software support and then the touchscreen stopped working, but I have it sitting here at my desk.
Every phone I have used since has been worse.
* Phone calls
* Video calls over XMPP
* Text/XMPP messaging
* Web browsing
* Document editing
* Writing and receiving email
* Playing music ( it had a built in FM transmitter - how cool was that!)
* Setting Alarms
* weather widgets
* Writing PHP programms
* Writing python programms
* ssh-ing into servers
* gps navigation
* take and share pictures
* multi-colored status LEDs
* it had usb-otg so you could use as a flash drive
* share an gsm internet connection via USB
> * Writing python programms
Honest question: what is a real world use case for writing PHP or Python programs on a tiny laptop with a 7" display that wouldn't be better served by a 13" laptop. I can't imagine writing code while standing on a train, for example. But more important, I'm having trouble imagining what kind of work situation would require that.
A computer you can take everywhere when you need to squeeze in extra computer-time into any unplanned free moment opportunistically (e.g. Leetcode practice, dissertation crunch), or being on call and only need ssh & chat access 24/7.
I carried a high-DPI 7" tablet with a keyboard case to good effect. It was less of a physical burden than lugging around a 13-incher, and was inconspicuous when outdoors or places I may have felt unsafe carrying a laptop
I guess this is a very personal thing, but I've always found the weight difference between a 7" tablet and a slim 13" laptop to be pretty minimal, and I walk-commute on average 3 miles a day carrying a laptop.
> and was inconspicuous when outdoors or places I may have felt unsafe carrying a laptop
It's probably a lifestyle choice, but if I were to feel unsafe using a laptop in a space, I probably wouldn't be able to focus enough to work, and instead of using a less conspicuous device, I would relocate somewhere that I felt safe. Also if I were on-call I would doubly want to be in a place where I felt I could focus completely on my work. I don't doubt that the market niche for inconspicuous general purpose computing devices exists, but I don't think it's huge.
You may have misunderstood the premise. I don't want to live my day-to-day life with a laptop on me 24/7, but I can tolerate a pocketable computer. Regular life involves activities in places without lockers - like typing up a dissertation chapter on the train to a ball game, or parking on streets that have occasional car break-ins, to have dinner with friends.
The idea is to make spontaneous computing on the go possible; so the device pretty much has to be on you all the time and everywhere, and I don't think a 13" laptop is a reasonable choice for that.
This made me smile, because that used to be my morning commute. I had around an hour on a usually full train, and I could already start writing things that were on my mind. Everybody is a bit different.
Nevertheless, I have since learned to keep a better work-life balance. I also stopped commuting.
Things like "writing PHP/Python programs" and "document editing", while things that you can do on a pocket-sized laptop, are much better to do on a real laptop or desktop. A tiny PC will strain your eyes, decrease your reading, typing and interaction speed, hurt your neck, and react slowly relative to a full computer - regardless of whether you're using a soft-keyboard or a physical (but tiny) hardware keyboard.
Although ElCheapo may have thrown a lot of unnecessary junk into their comments, their point "The medium is the message, the form is the functionality." is still true - you don't want to use C# for tiny (kilobytes RAM) embedded devices and you don't want to use this pocket PC for writing code, even though you can.
I've ssh'd in to fix issues from my phone many times because I was in locations where carrying a laptop would have been annoying and my phone let me. In that respect having a device that was suboptimal but serviceable saved me from carrying around a device that'd be better to use but a pain to drag around.
I've written short stories on my phone or my tablet because I happened to have an idea in a situation where I didn't carry a laptop with me.
In other situations I'd carry with me a tiny chromebook to be able to do more things without having to carry my full 17" laptop.
There's space for many form factors of devices which would be horrible for short term use but fine as an option for occasional use.
This may well fit into that mid-point to me as something more convenient and open than my phone, yet substantially smaller than my laptop to the point that it can fit in my jacket pockets at least the times of year where I'm wearing a heaver coat (and I'm in the UK, so that's a lot of the year).
I just wanted to point out that these devices are still significantly less efficient than a laptop or a desktop, because it's non-obvious to some people - including the throw10920 a decade ago, who thought that doing development on a phone when they had access to a desktop was a good idea. I wouldn't want to give other people that same impression, just like I wished I had never gotten it myself.
For many people with good eyesight it is just fine to use a small screen for programming.
It's also not fine to use a small screen for programming even if you have good eyesight, as it will worsen your eyesight even if you hold it as far away from your body as you can with your arms straight - the constant focusing on an object near your face will cause your eye muscles to weaken and give you myopia. You'll also damage your neck unless you hold your phone at eye (or at least chest) level - something that I've seen literally nobody do.
By that measure, looking at any screen or reading strains your eyes but I don't think you'll be switching exclusively to voice control programming and audiobooks any time soon because oh right this is not habitual or productive for you. (And if you do, now it strains your ears... I guess life itself is unhealthy, after all it's known to cause death.)
And no, it does not mean it causes nearsightedness. This is grandma's tale. Plenty of people have 100% vision while spending inordinate amounts of time in front of screens. Research points out this is more about spending too much time indoors, no matter screen size get enough sunlight on your retina especially as child.
I can only imagine how much nicer would it be to do the things I often do on the go (messaging, issue management), possibly more (programming), with proper physical keyboard. Swipe typing is just not helping much.
No, it's quite clearly not. In my comment, I stated "While all of these things are possible on a tiny PC, many of them are very sub-optimal" - explicitly stating that the domain of the comment was about efficiency (and then later brought in the topic of healthiness). If you start responding to that comment with arguments about what is "habitual", then your comment is off-topic.
> I hate large screen setups and I love drafting emails on the go
I don't care about what you like doing. This comment thread is not about that. It's about what is efficient and healthy. If you want to talk about what you like doing, find a thread where it's on-topic.
> your opinion that it is somehow less healthy
It's not an opinion - there's actual research that shows that smartphone use is linked to myopia[1]. As for being relatively less healthy, the only intrinsic difference between smartphones and desktops is screen size, and therefore how close you have to hold it to your face - which is worse for smartphones than desktops. So, smartphones are as bad or worse than desktops along all relevant axes.
> probably sitting, too
Because the vast majority of people do none of these productive behaviors consistently on a phone while walking, this just means that there's no difference between smartphones and desktops - doubly so because you can (but very few people do) set up a standing desk for a desktop - with a treadmill, even!
Furthermore, there's evidence that staring downwards (at a smartphone) for extended periods of time alters the shape of the spine in bad ways[2]. This health issue ranges from "much better" to "nonexistent" for desktops, depending on how they're set up.
> By that measure, looking at any screen or reading strains your eyes
Not "strains" - trains. Maintaining a constant focal distance causes your eyes to start to adapt to that focal distance, at the expense of others. And yes, it does. Humans aren't mean to read or look at screens for long periods of time either - it's just better to use screens that are larger and further from your face.
> but I don't think you'll be switching exclusively to voice control programming and audiobooks any time soon
Correct, because those things are less efficient. I want to try to maximize both efficiency and healthiness. Because those two things are in tension, this leads to an efficient frontier[3] where I have to pick a point on it, and voice control solutions are not on that efficient frontier.
> because oh right this is not habitual or productive for you
Again, this is not about "habitual" or "productive", this thread is about "efficient" and "healthy" and if you want to comment about other stuff, then find a relevant place to put it.
You also seem to be trading critical thought for sarcasm - I would advise against that, as it is neither efficient nor healthy.
> I can only imagine how much nicer would it be to do the things I often do on the go (messaging, issue management), possibly more (programming), with proper physical keyboard.
Yup, I'm not saying that a phone-sized hardware keyboard wouldn't be better than a soft keyboard - just that both are massively inferior to a full-sized hardware keyboard. I can hit 100 WPM on a desktop keyboard - which is faster than every single volunteer in this European study of 37k people[4]. I can virtually guarantee you that, for any amount of effort spent practicing, you'll be able to type faster on a normal keyboard than a phone keyboard, hardware or not.
[1] https://aru.ac.uk/news/screen-time-linked-to-risk-of-myopia-...
[2] https://www.thespinejournalonline.com/article/S1529-9430(17)...
[3] https://en.wikipedia.org/wiki/Efficient_frontier
[4] https://userinterfaces.aalto.fi/typing37k/resources/Mobile_t...
> In my comment, I stated "While all of these things are possible on a tiny PC, many of them are very sub-optimal" - explicitly stating that the domain of the comment was about efficiency (and then later brought in the topic of healthiness).
And I stated that you're wrong.
If it is suboptimal/inefficient/unproductive to you as it is not how you are accustomed to do things, then sure. But not in absolute terms. Don't deny the experience of other people, it is as real as yours. It is optimal for me, and what is habitual is key. I would not trade being able to do work on the go for being chained to a desk, a chair, four walls and a large display because it is less efficient (it's all individual, I need fewer visual distractions, being able to fit more stuff on screen is harmful, and same reason I don't do video calls).
Furthermore, health is not orthogonal but an important prerequisite for sustainable efficiency and performance. To take it to extreme, some people would drug themselves to be more efficient in short term, so what?
Being able to do things on the go is not only more productive (or efficient if you like) because I can do it anywhere, but because fresh air, improved blood flow, and everything else helps me maintain the health that underlies that whole efficiency business you are discussing.
And I countered every one of your arguments, and you never responded to any of them. Your statement means literally nothing.
> Don't deny the experience of other people, it is as real as yours.
It's an extremely well-known fact of human psychology that human experience and subjective perception are extremely skewed and unreliable. I encourage you to peruse the list of cognitive biases on Wikipedia[1] as you clearly aren't familiar with them.
Furthermore, it doesn't matter that the experience of other humans is as real as mine, because we're not discussing something subjective like what flavor of ice cream tastes best - we're discussing objective topics - namely, efficiency and ergonomics.
> It is optimal for me
It is not optimal for you. Your subjective perception is not an indicator of optimality, which is an objective measurement.
> being able to fit more stuff on screen is harmful
False. Having a larger screen does not require you to put more stuff on it, and allows your eyes and brain to not work as hard to see things than on a tiny screen.
> To take it to extreme, some people would drug themselves to be more efficient in short term, so what?
I don't see how that's relevant? I neither said nor implied that anyone should pursue maximum efficiency at the cost of their own health, and that's not related to anything we've discussed so far. I'm just stating that phones are both less efficient and less healthy for you than desktops - that's it.
> productive (or efficient if you like) because I can do it anywhere
You're substituting your own definition of "efficient" for mine, the one we were originally using. Bad form.
The definition of "efficient" being used in this comment thread is, roughly, "work done per unit time":
> Things like "writing PHP/Python programs" and "document editing", while things that you can do on a pocket-sized laptop, are much better to do on a real laptop or desktop. A tiny PC will strain your eyes, decrease your reading, typing and interaction speed, hurt your neck, and react slowly relative to a full computer - regardless of whether you're using a soft-keyboard or a physical (but tiny) hardware keyboard.
...and for that definition, no, you will not be more productive "on the go" with your tiny phone than I will be at my desktop with my multi-monitor setup and full-sized mechanical keyboard.
If you want to use your own definition, find someplace where it's relevant.
> because fresh air, improved blood flow, and everything else helps me maintain the health that underlies that whole efficiency business you are discussing
Is there some law of physics that prevents me from standing up from my normal desk to get up and walk outside, or even set up a treadmill desk outside with my desktop? No? Then why are you bringing it up?
Regardless, the claim that those things will somehow overcome a massive difference in CPU performance, productivity software, screen real estate, and input mechanisms is somewhere between "absurd" and "insane". I know people that have lived horribly unhealthy lives for decades and can still easily out-perform someone on a phone. (I shouldn't have to say this, but apparently I do: I'm not advocating for this, merely pointing out that your claim isn't backed by reality)
Your comment is composed entirely of ridiculous claims, denials of basic mechanics of human cognition, and logical fallacies. Notably missing from it are responses to the points that I made.
[1] https://en.wikipedia.org/wiki/List_of_cognitive_biases#Egoce...
In short: You can pull it out of your pocket anywhere, type something with both thumbs on a full keyboard, then fold it down again in seconds.
There are Android phones with a full keyboard as well, but they are closed source/hardware.
First you say that with "android" (as if they made hardware) you can't have an integrated keyboard.
Then you say that Android phones with a full integrated keyboard actually exist.
But then you move the goalpost saying that they aren't open source/hardware. Which is false, by the way, since this device [https://wiki.lineageos.org/devices/pro1] runs LineageOS, and phones with completely free software down to the firmware level don't exist, including the N900 which needs a binary blob to start the wifi module (as far as I know) and whose hardware is not open source in the slightest.
And even after all of this I've been given zero use cases that an Android phone can't provide with the proper application installed.
Let us be fair here: you moved the goalposts first by going from “it is an absolute fantasy” to, once people pointed out that they already exist, “but I can't see a use for one”.
Why even say this if you immediately proceed by not being fair?
Pocketable computers are not a "fantasy" in the sense that there aren't any devices capable of running a desktop OS while being pocketable. This was never the argument, as also demonstrated by my other replies in the thread. My argument is that using a pocketable device as a desktop or laptop is a fantasy. It's something that sounds very cool on paper and which has a small cult following, but in reality all these people would fare even better if someone wrote an Android app tailored to their use case.
Of course that's true. In fact, I'd go as far as to say that if you wrote an entire gnutils userspace for Android, and gave me a slide out keyboard instead of obliterating half my screen if I need to do input, you would have given me something that is almost identical to an N900.
It's not. My GPD Micro PC is currently my daily driver laptop, and it fits in my back pocket. I have done CAD work on it with no trouble at all. There's no "Android app" that can compete with the universe of PC software.
You should try one before you make sweeping judgements about what is and isn't possible.
Pointing it hypocrisy is fair in my book. If you significant change of wording isn't a shift of the goal posts then neither is the others posters clarification.
Also no it most definitely contains blobs.
https://community.fxtec.com/topic/3326-pro%C2%B9-x-%E2%80%93...
I possibly misunderstood what you were getting at. You are right - an android with a a keyboard is certainly not all that different.
Pass. I'll take a laptop.
The Maemo distribution that the N900 ran was based on debian, and you could point apt to the standard package repositories to install pretty much any Linux software. This opened many, many possibilities - for example, I had an always-on computer in my pocket with WireShark installed. I could (and did) occasionally sniff wireless traffic to troubleshoot something. If you couldn't find a mobile app that would do what you wanted, you could usually install a desktop app and it'd work (though sometimes the UI was awkward on that small screen).
While most of the functionality can be replicated on a modern Android device, these pocket computers were different in a special way. The integrated physical keyboard, the tab key, the full Linux kernel and apt, all combined to create an experience that was distinctly different from Android. It really felt like a pocket-sized workstation - it was a full computer first, and pocket-sized second. Android smartphones are pocket-sized mobile devices first, and potential workstations second.
The only good point about it was that it had a full and integrated keyboard, and a Linux based OS you could use to manage your servers over ssh in extreme cases.
Answering calls on it was a hit or miss, the UI just froze for several seconds from the incredible stress of suddenly starting up the phone app when someone called you.
I'd much rather 1) separate my work from my personal life and 2) have a laptop in a backpack for when I know I might have to do work.
at being general purpose computer
I'm almost sure that with enough swearing and elbow grease I could replace the entire GUI with something that I can write myself to be tailor-made to my needs. Doing anything even close to this for Android seems like a daunting task.
I wish it was only about the i/o: pocket Bluetooth keyboards, mice and other i/o devices would be just a few bucks away. No, the problem is rather that phones/tablets use crippled dumbed down and tight closed operating systems that offer only a small fraction of the power a real computer offers, not to mention the huge privacy and security issues involved. Having the same hardware performance and storage of a good laptop means nothing if the OS doesn't offer a way to use it in a transparent and trustworthy way.
No, because it isn't fantasy and i want those PCs that "fit in my pocket" - after all they do exist, see GPD's pocketable PCs.
> Smartphones have been "pocketable PCs" for more than a decade already
Smartphones have their on OSes, UX, applications, etc. The point of projects like GPD Win or the one linked above is to run the same programs, OS, etc as you'd run on a regular laptop or a desktop PC.
And this is something that can be useful, even if it isn't at the same frequency as a smartphone - they do not have the same use after all.
Personally i have a GPD Win 1 which is pretty much the same form factor as the pocketable PC linked in the article (actually it is better IMO because the joysticks and back buttons it has are used very naturally to move the mouse cursor on the desktop and act as a mouse). I do not use it daily but whenever i want to go somewhere briefly and need a PC (e.g. i need to show a project of mine to someone), i pick that up instead of my laptop: it is much lighter (its weight barely registers), it fits in my fanny bag next to my smartphone and provides pretty much the same functionality as a regular laptop - it is just weaker and slightly more awkward to type on. But i'm not going to write code for hours straight on it anyway, so it doesn't matter. However i do use the keyboard frequently, for command line or shortcuts or whatever, and it is miles better than something like Termux and/or the virtual touchscreen keyboards you'd find in smartphones (which with swipe typing are decent but fail at everything else).
The main issue with the linked PC is that it is ARM instead of x86 which IMO limits its utility. I can run any old application on my GPD Win 1 and for my own applications i can just copy the binaries to it directly but for something like the MNT Pocket i'd need to cross compile just for it and it is limited to stuff that i can do that.
The most limiting bit about phones is the OS itself. You could hypothetically get most of these things working on phone OSes, but only for a massive amount of effort to port something for a single-digit number of users. I don't even know how you'd get a compiler going, but I suspect it would be a non-starter on iOS.
> Smartphones have their on OSes, UX, applications, etc. The point of projects like GPD Win or the one linked above is to run the same programs, OS, etc as you'd run on a regular laptop or a desktop PC.
Sure, an Android device could probably be hacked to do that. But most Android devices are usually locked-down, whereas the GDP & friends make it a point to be open.
I guess we should probably push for more openness from smartphone vendors (including Apple) instead of having yet another different device. Especially since now everything and the kitchen sink connects via USB-C. I'd absolutely love to be able to plug my phone in the USB-C dock at work instead of lugging around a laptop (which I use on top of a desk tethered to some fat screen and external keyboard like 99% of the time anyway).
At one point, I remember Samsung had something like that on their Galaxy line (DEX? can't remember the name). I was actually ready to pull the trigger on a tablet with that feature. Luckily, I found out they had just or were about to remove it.
You could, in theory, use a smartphone for this but the software situation is so terrible that you really can't.
Yes. After struggling with every single type of Smart TV platform (Google TV, Apple TV, Amazon Fire TV). I settled for a Linux HTPC that I control with a Logitech K400. I finally found what I needed and I'm never going back to looking for crappy apps on some semi-empty store. Walled gardens are really sad.
You just need a remote with QWERTY and trackpad, and a few adjustments to the OS (e.g. 125% UI scaling works pretty well for me).
Sure, if you change your requirements and sidestep mine then everything becomes easy. Now try doing the same with an actual TV remote, which my question actually asked about.
GP adapted the the form factor to his needs.
The remote form factor was created for a long gone use case of 'zapping' through channels coming from an analog source.
Home theater nowadays has no similarity with the interface needs of cable/satellite TV, so why would you be hung up on using the same remote control interface?
Remote controls have been tortured into fitting smart TVs with ever more ridiculous tiny buttons and confusing silk labels the remote control concept needs to be retired anyway.
My point is that drastic I/O adaptation almost always require UI/UX adaptations, which doesn't happen with these enthusiast projects.
>Home theater nowadays has no similarity with the interface needs of cable/satellite TV, so why would you be hung up on using the same remote control interface?
Because that's what people use. If we went by some "blank slate" argument then we could make a ton of things possible, but that's not what this problem is about. Additionally, even if you had a keyboard+touchpad combo, would you rather use your TV from your couch with GNOME or XFCE or would you prefer Kodi's interface?
I don't understand the distinction you're trying to make between having an Intel NUC on my desk connected to a monitor and a keyboard, or having one mounted to the back of my television (or monitor placed in the room as if it were a television), and controlling it with my remote keyboard. They're both general-purpose computers, they both do exactly the same thing, the TV runs Debian Stable and my PC runs Debian Testing.
They cost about the same. Some machines come with IR receivers, some need them added on via USB. If you need one, I can highly recommend the FLIRC: https://flirc.tv/
I flip between the devices depending on what I'm doing. Mostly, it's the remote.
My point is that minor adaptations can lead to surprisingly pleasant functionality. Past failures are not reasons to stop trying new things; they're reasons to try other new things.
None of these devices attempt doing something similar. They offer less options than normal computers and their desktop is left unchanged.
Lastly, what you wrote actually proves my point. You are not using your linux system to do everything a computer does. Your set of functionalities is limited to media consumption and as such you just had to find a workaround for your use case. Could you browse (or even write) your emails on your TV? Sure, but you'd have to use a heavily customized UI and UX if you don't want people to squint their eyes and take ages to navigate everything. And who's going to write such a program? And what about all the other applications that we expect a complete system to have such as a general purpose web browser, a video player, a file browser, etc.? My whole point is that these "pocketable PCs" might be great for a subset of problems, but they have to be tailored for them. They are terrible general computing devices.
> None of these devices attempt doing something similar. They offer less options than normal computers and their desktop is left unchanged.
They have swappable SoCs at their cores, including available on-board FPGA, and the existing product ships a customized Sway UI by default. They are far more configurable than other laptops. One person already modified her mainboard to include a different charging circuit and added an ergonomic keyboard. You have gone from pessimism to outright misinformation in pursuit of your argument. Ask yourself whether you're here to discuss the topic or just win internet debates.
Wrong. Smartphones are dumbed down because the manufacturers would greatly prefer that you not run any kind of software that they or their partners did not directly provide.
The iOS App Store would have been barer than a Soviet grocery store if iOS supported Flash.
The fact that a full computing device in your pocket cannot be used to build and deploy applications makes it not much more useful than a color PDA from 2005.
You do have to bring your own peripherals, but being able to move your computer around previously set-up work points is already an improvement from not being able to carry it at all, or carrying around a laptop.
The parent likes to use an "old fashioned" (I disagree with that judgement, but fine) paradigm of portability, so what? Does that make it a less valid choice? "Portable" is a generic term that's not reserved for discussions of any specific kind of portability, so why not coin/use a specific term for "fits in your pocket and is usable on the train" if you need one, rather than silently assume?
While it is possible to cram PC features into a pocket-able design. And other commenters here have given examples such as the old pocket pc standard. Its not very good and didn't stick around.
The user interface and format will in large part define the kind of work you will do on a device. Pocket sized devices suck for a lot of "real work" use cases because small and limited inputs combined with small screens don't make for a pleasurable or productive work experience.
Big displays and comfortable full sized keyboards are necessity.
There has been on and off talk about dock-able pocket sized devices that can transition between being mobile and being proper PCs with the use of a dock that expands its IO options. But the software has always seemed to be lacking there. Apps on my Pixel 5a sometimes get the screen orientation wrong. How can I trust them to seamlessly switch between a mobile and desktop experience and not freak out in the process?
That sounds only slightly more dreadful than the touchscreen keyboard experience we have currently; I seem to be in a minority but proper tactile keyboards, even tiny ones, are worlds better IMO. The best phone I ever had for input was a Blackberry Bold 9700, and I miss that keyboard almost literally every single time I type something on my magic screen.
I have been there. Speed and battery do not seem to be much of a problem - even with the not-recentmost technology I use, there have been laptops which "do" and last less. While having a quite decent resolution, the displays do not replace the real world experience for offering virtual keyboards - better input systems must be adopted.
Mobile systems are not «"dumbed down"»: they have more frequently found leaner options depending on the main purpose of the device, but you do e.g. control Android with physical keyboards, complete with shortcuts and function keys.
You're reminding me of how nice it would be if smart TV remotes did come with thumb boards built in.
More likely because low-level artificial limitation are in place, preventing the full use of the device.
Yes. We've been doing it for years since we cut the cord from cable TV. We switched to a plain PC (Lennovo low end laptop for $200) running Ubuntu and use an Air Remote (combination mouse/keyboard) around $15 on Amazon and watch all content in Chrome. It's great! I can get a shell and change things if I want, ssh in from my office desktop, etc.
Or you could buy a GPD Micro PC and save a lot of trouble. It's a full x86 laptop the size of a chunky smartphone, and it's totally practical to use it as a PC.
We have been talking about ubiquitous computing for a long time, but instead of doing that, it seems we have settled on using smartphones for everything, retiring specialized or underpowered devices in their favor, even if they are just 60% as good as their predecessors.
When a company tries to build something in this niche, it seems we need as much power as possible to make it potentially as mass appealing as possible, which in turn means tradeoffs in many other areas (size, heat, battery life, software etc.) that make it unappealing to most but a small minority.
Now, it would seem easy to create a specialized device by putting some constraints on it, right? Make a computer optimized for writers! Make one optimized for day planing! Make one that is not good for playing video or games but great for spreadsheets etc. These devices could excel at their given niche and give us back advantages like weeks long battery life or incredible small size etc. But it seems, no one is willing to work with these constraints. Of course, also no one seems to be capable to create custom software, which I guess these devices would also need to be good at what they were supposed to do.
Sometimes you find these things in small, specialized markets, but even then they always seem to be not really much better or even worse than what we had in the 90s. I am not sure if it is because of market dynamics or lack of vision, but all we ever seem to get are compromises.
Now we know what sells, and it's an iPhone or an iPhone wannabe. Nobody wants to spend tens of thousands of dollars on something that isn't a phone, so nobody does the development to mass-produce these items.
Notice how phones were wildly insanely weird before the iPhone and very quickly afterwards they were all black slabs?
You'd probably have more luck cannibalizing the 200LX and shoving a phone inside it.
[1]: I used this one for a while: https://smile.amazon.com/gp/product/B07D2BG6R5/ref=ppx_yo_dt...
[2]: This one is awesome too with android TV: https://smile.amazon.com/gp/product/B07WJGSXT8/ref=ppx_yo_dt...
Kinda, if the remote had a useable keyboard (I think some do).
Mostly I would like a universal search: to be able to type the name of a show, channel, or other media source and have all relevant apps or TV functions that can play it come up. Also it would be cool to enter something like "seek MM:SS" to tell the current media to go to that precise point, and universal commands across all players/apps would be pretty keen, like "captions off", "language XXXX", etc. Just need a TAB key for autocomplete.
I agree with the general sentiment and want a device like this, but I’ve never had one that worked as well as my old N900.
The medium is the message, the form is the functionality.
Smartphones have been "pocketable PCs" for more than a decade already, but are dumbed down because their inputs and outputs are limited. You can't type effectively, your screen is small, your battery is limited. Would you want a command line interface on your Smart TV using only a remote? How about XFCE? Or GNOME? No, for a Smart TV we have purposefully made OSs that are limited in functionality such as Kodi, LibreELEC and others specifically because of the type of inputs and outputs needed.
I think the only way we could ever get a portable PC experience on the go is by having AR glasses project a full desktop in front of us and let us control it with an imaginary keyboard and touchpad by somehow analyzing our hand movements on a hard surface in front of us. But that's only if we get to a point where said devices are fast and hold a decent battery, which, with current technology, is impossible.