4 ms·
I have a Macbook Pro (though 15") and a PC, but also a ridiculously underpowered Chromebook with a crappy 11" 1366x768 screen. Lately I find myself when I'm on
by hawski 5y ago
I have a Macbook Pro (though 15") and a PC, but also a ridiculously underpowered Chromebook with a crappy 11" 1366x768 screen. Lately I find myself when I'm on the run in the city to grab the Chromebook and ssh to my desktop (I've got Zerotier set up). This is my ultimate portable duo. It could be better, but it is lightweight, battery runs full day and I have all power I need. Then when I get back I have it even better with less latency.
- TedDoesntTalk 5y agoWhat’s old is new again! This is how mainframe terminals worked.
- hawski 5y agoThat's a setup I wanted for quite some time and I know it was available for some time, but ubiquitous fast and cheap wireless Internet is something new I guess, also with all-day batteries all in a lightweight package.
- my_usernam3 5y agoCan you explain further? I'm guessing you mean once a mainframe's resources were outdated, it became a terminal?
- Macha 5y agoNo, the users had crappy devices (terminals) which worked because they could access the compute resources of a bigger device (the mainframe)
- Jtsummers 5y agoNo. In the heyday of mainframes people would remote in, with a terminal. That's where the terminal protocols many people still use on a daily basis actually come from. Sending text over the wire to display on your terminal screen, you type into a keyboard which transmits your input across the wire to the mainframe which responds with new screen updates. Using your desktop remotely from a cheaper but more portable device is pretty much the same model (not the same thing, but model) as the way many people interacted with mainframes last century.