51–60 of 82 posts
Posts like these are fun. OP, I am now curious about using Docker to manage dotfiles and some installs. Could you tell us more about it, or give some resources to get started?
MacBook 12” works great, has a better keyboard, is probably lighter/smaller than an iPad Pro Why not use that instead?
Docker is a million times better on Linux than any other platform, so if all the work you do is through Docker, it seems insane not to make that as a base-optimization.
Should be titled, "I remotely tunnel to a server using my iPad Pro for programming" very misleading. Furthermore to the point: what's the benefit of tunneling to a remote machine for dev work? The latency would suck as would the overall slowness of things, it would drive you insane. You can hammer nails into a piece of wood using a rock, but why would you when you can use a hammer?
The latency really doesn't need to be that bad. If you can play games on an internet connection it's definitely good enough to type on. (Someone will now come out of the woodwork to remind us of when they did all their development over a 300-baud serial teletype, uphill both ways)
However, at home, I would routinely login to the same remote computer and the latency was horrible, every typed letter was delayed a tenth of a second or so. I wasn't about to spend a fortune on a dedicated line to the work servers.
The point is, when you're working remotely, you're totally at the mercy of the network. If the network is down or flaky, you can't get anything done.
The title should really say "Using an ipad to be able to develop in one's underwear"... Outside of this key element, there is really no upside over using a laptop!
From the article:
> Even though the MacBook's retina display is a really great display, the iPad Pro's display is another big step up. I don't know if it's the Pro Motion, the True Tone or the Wide color (P3) but the iPad Pro display just looks a lot better than my 2015 MacBook Pro's.
When you are sshing into server you are using the server, not the local machine (beside the terminal and ssh app itself). Please correct the title.
The "but it's not local and therefore not programming!" style reactions make little sense to me. Programming is an activity; where the code resides or executes doesn't change that fact. How would you have the title "corrected"?
1. that "main computer for programming" is the one running the stack and software used for programming and
2. that this device is $X.
In this case the main computer for programming is a machine in the cloud ($Y, not $X), and $X is a terminal connecting to the cloud ($Y).
The title for this submission is clearly inaccurate and misleading.
Should be titled, "I remotely tunnel to a server using my iPad Pro for programming" very misleading. Furthermore to the point: what's the benefit of tunneling to a remote machine for dev work? The latency would suck as would the overall slowness of things, it would drive you insane. You can hammer nails into a piece of wood using a rock, but why would you when you can use a hammer?
The latency really doesn't need to be that bad. If you can play games on an internet connection it's definitely good enough to type on. (Someone will now come out of the woodwork to remind us of when they did all their development over a 300-baud serial teletype, uphill both ways)
I could imagine a middleware doing similar cheating for shell, but in general, you'd have to have a stripped local version of software doing local simulation to ensure videogame-like smooth experience.
http://yieldthought.com/post/12239282034/swapped-my-macbook-...
Wait, what? This isn't about using an iPad as a development machine, it's about using a server as a development machine and an iPad + keyboard to access said development machine. I get that the author wants to use his iPad for day-to-day stuff, and that's fine, but it's a stretch to say it's their main programming machine when it's not actually running the "local" setup. Heck, it would drive me bananas having to stop…
Hardware terminals are back! \o/ Everything that's old is new again.
Today, I believe the push to terminals is due to the slow death of Moore's law. Computer performance today is not getting much faster, and it's certainly not growing at the exponential rate it was from the 1970s-2000s.
Previously, if you wanted to double your performance, you would just wait 18 months or so, and some manufacturer would provide it. Now, we don't have that luxury. If you want to double performance, you basically need to double the number of computers. Unfortunately, doing that takes up physical space and power. So the solution is to create massive server farms with big beefy computers that can run in parallel.
The death of Moore's law is depressing.
Should be titled, "I remotely tunnel to a server using my iPad Pro for programming" very misleading. Furthermore to the point: what's the benefit of tunneling to a remote machine for dev work? The latency would suck as would the overall slowness of things, it would drive you insane. You can hammer nails into a piece of wood using a rock, but why would you when you can use a hammer?
> Furthermore to the point: what's the benefit of tunneling to a remote machine for dev work? You can do it from anywhere; you don't need a powerful local machine; controlling what devs do is easier; etc. 3 of my last 4 contracts have been development on remote machines. It's perfectly fine unless you somehow have abysmal networking (and then you really have bigger problems.)
That's not exactly a benefit for the dev.
> You can do it from anywhere; you don't need a powerful local machine
That's fair, but arguably, that's an argument for CEO to own an iPad, so that they can log in to company network from whatever country they happen to be in this week. For regular employees, that seems like introducing a stupidly huge amount of pointless friction into the dev process, which will directly impact productivity.