The big languages are popular for a reason: They offer a huge foundation of open source code, libraries, and frameworks that make finishing the job easier. This is the result of years of momentum in which they are chosen time and again for new projects, and expertise in their nuances grow worthwhile and plentiful.
Stories by Peter Wayner
Whether you think it's wired into the human mind or an inevitable product of society's formation, dualism defines much of our lives: Communism vs. capitalism. Savory vs. sweet. Passing the ball vs. running the ball in football. Everywhere we look, pairs are locked in an eternal battle, presenting us with myriad opportunities to define ourselves by which side of the line we favor at any given time.
Faster innovation, better security, new markets -- the case for opening Swift might be more compelling than Apple will admit
A long time ago, developers wrote assembly code that ran fast and light. On good days, they had enough money in their budget to hire someone to toggle all those switches on the front of the machine to input their code. On bad days, they flipped the switches themselves. Life was simple: The software loaded data from memory, did some arithmetic, and sent it back. That was all.
Swift's clean and modern syntax makes it quick and easy to get started, but mastering this new language will take a while
Apple's new programming language modernizes iOS development by synthesizing great ideas invented elsewhere
Hot or not? From the Web to the motherboard to the training ground, get the scoop on what's in and what's out in app dev.
Massive leaps in computing power, hidden layers, hardware backdoors -- encrypting sensitive data from prying eyes is more precarious than ever
The tech world has always been long on power and short on thinking about the ramifications of this power. If it can be built, there will always be someone who will build it without contemplating a safer, saner way of doing so, let alone whether the technology should even be built in the first place. The software gets written. Who cares where and how it's used? That's a task for somebody in some corner office.
Slow startup times, null pointers, security flaws -- Java's ongoing success leaves plenty to complain about
A long time ago, a computer program was a stack of punch cards, and moving the program from computer to computer was easy as long as you didn't drop the box. Every command, instruction, and subroutine was in one big, fat deck. Editors, compilers, and code repositories have liberated us from punch cards, but somehow deploying software has grown more complicated. Moving a program from the coding geniuses to the production team is fraught with errors, glitches, and hassles. There's always some misconfiguration, and it's never as simple as carrying that deck down the hall.
The cloud computing sales pitch is seductive because the cloud offers many advantages. There are no utility bills to pay, no server room staff who want the night off, and no crazy tax issues for amortising the cost of the machines over N years. You give them your credit card, and you get root on a machine, often within minutes.
A diverse set of real-world Java benchmarks shows that Google is fastest, Azure is slowest, and Amazon is priciest
If hitting a target is hard and hitting a moving target is even harder, then creating a new hit technology is next to impossible because the shape and nature of the target morphs as it moves. Think of building a swish new laptop just as laptops are heading out of favor, or a must-have mobile app just as smartphones plateau, or a dynamite tablet experience just as the wearable future takes hold.
Cloud-based back ends for mobile applications combine key services with varying degrees of complexity