Post-Microsoft, post-PC programming: The portable REVOLUTION

Code jockeys: count up and grab your fabulous tablets

Some years back, when Microsoft was mired in Windows Vista and open source issues, and web developers were on an accelerating trajectory, a quiet revolution took place.

In the corridors and anterooms of tech conferences, scrunched deep into beanbags and huddled next to power outlets developers were at work, nose down, in PowerBooks. It was one of those changes that one day you suddenly just became aware of.

Apple laptops had replaced Windows laptops as the code jockey’s steed of choice, with the very act of programming itself having become decoupled from the client's operating system. It was said, and it was written, how Microsoft had lost a generation of developers.

Today, a new revolution is taking place. PC sales, and even laptops, are down, and manufacturers are pulling out of the market. The future is all about the device.

For most, the "PC" will become a thing that fits in your palm - or, in the case of the iPad, your comically oversized jacket pocket.

That's fine for consuming information. An iPad is a great way to browse the web, check email, stay in touch with friends, and so on. But what does a post-PC world mean for creating things? What does programming in a post-PC world look like?

Received wisdom is tablets such as the iPad can't replace whatever it is that the author does - creatives must switch back to a laptop or desktop with a keyboard. In many cases that's true, but is it true for programming?

The answer is: it depends. It depends what you do and how willing you are to give up your old tools in favour of something new.

If you're writing platform-specific mobile apps in Objective C or Java then no, the iPad alone is not going to cut it. You'll need some kind of iPad-to-server setup in which your iPad becomes a mythical thin client.

If, however, you're working with scripting languages such as Python and Ruby or building web-based applications, the iPad is tantalizingly close to being a great development environment.

You’ll need a real keyboard to any serious programming on one of these

Before I dive into the specifics of my setup, I should note that to really get any development done on an iPad you'll need a real keyboard. Tapping glass is fine for short emails, but will quickly drive you nuts trying to write code. I used an Apple wireless keyboard because I had one, but there are some much slicker options out there that can also act as screen covers and protect your iPad when it's bouncing around in your bag.

Code and go

Now for the software. What started me on the road of trying to work solely on an iPad was a brand new iOS 8 application, Working Copy, which became the cornerstone to the development environment I managed to create on the iPad.

Working Copy is a Git client with support for just about every Git operation you need on a regular basis - cloning, editing, committing and pushing. The app is free to download, so you can test it out, but to push back to the server you'll need to buy the $9.99 in-app purchase.

It lets me check out my code, view recent changes, browse through old revisions and edit the files. The actual editing of files is not Working Copy's strong suit, though. The included editor, while perfectly functional, lacks syntax highlighting and other niceties. Part of the reason is that the editor was not intended to be a full-fledged text editor.

Similar topics

Other stories you might like

  • Everything you wanted to know about modern network congestion control but were perhaps too afraid to ask

    In which a little unfairness can be quite beneficial

    Systems Approach It’s hard not to be amazed by the amount of active research on congestion control over the past 30-plus years. From theory to practice, and with more than its fair share of flame wars, the question of how to manage congestion in the network is a technical challenge that resists an optimal solution while offering countless options for incremental improvement.

    This seems like a good time to take stock of where we are, and ask ourselves what might happen next.

    Congestion control is fundamentally an issue of resource allocation — trying to meet the competing demands that applications have for resources (in a network, these are primarily link bandwidth and router buffers), which ultimately reduces to deciding when to say no and to whom. The best framing of the problem I know traces back to a paper [PDF] by Frank Kelly in 1997, when he characterized congestion control as “a distributed algorithm to share network resources among competing sources, where the goal is to choose source rate so as to maximize aggregate source utility subject to capacity constraints.”

    Continue reading
  • How business makes streaming faster and cheaper with CDN and HESP support

    Ensure a high video streaming transmission rate

    Paid Post Here is everything about how the HESP integration helps CDN and the streaming platform by G-Core Labs ensure a high video streaming transmission rate for e-sports and gaming, efficient scalability for e-learning and telemedicine and high quality and minimum latencies for online streams, media and TV broadcasters.

    HESP (High Efficiency Stream Protocol) is a brand new adaptive video streaming protocol. It allows delivery of content with latencies of up to 2 seconds without compromising video quality and broadcasting stability. Unlike comparable solutions, this protocol requires less bandwidth for streaming, which allows businesses to save a lot of money on delivery of content to a large audience.

    Since HESP is based on HTTP, it is suitable for video transmission over CDNs. G-Core Labs was among the world’s first companies to have embedded this protocol in its CDN. With 120 points of presence across 5 continents and over 6,000 peer-to-peer partners, this allows a service provider to deliver videos to millions of viewers, to any devices, anywhere in the world without compromising even 8K video quality. And all this comes at a minimum streaming cost.

    Continue reading
  • Cisco deprecates Microsoft management integrations for UCS servers

    Working on Azure integration – but not there yet

    Cisco has deprecated support for some third-party management integrations for its UCS servers, and emerged unable to play nice with Microsoft's most recent offerings.

    Late last week the server contender slipped out an end-of-life notice [PDF] for integrations with Microsoft System Center's Configuration Manager, Operations Manager, and Virtual Machine Manager. Support for plugins to VMware vCenter Orchestrator and vRealize Orchestrator have also been taken out behind an empty rack with a shotgun.

    The Register inquired about the deprecations, and has good news and bad news.

    Continue reading

Biting the hand that feeds IT © 1998–2021