The Insider News

Future<bool> writeFile(String data,
                       File file) {
 return file.open(FileMode.WRITE)
   .then((io) => io.writeString(data))
   .then((io) => io.close())
   .then((io) => true)
   .catchError((error) => false);
}

John Papa[^]:

I’m taking my own advice here and responding to some frequently asked questions I receive on SPA on my blog. I get some of these a lot and it just makes sense that I aggregate them and share for discussion. The questions are all good and they cover a variety of experiences. Hopefully by sharing them, they will be of benefit to others.

raywenderlich.com[^]:

For as long as I can remember, I’ve been in love with role-playing games. There’s something so magical about an epic storyline set in a vast, intricate world. But when it comes to actually programming a RPG, it’s easy to get intimidated by that same epic complexity! Well, there’s some good news. There are now some killer tools, frameworks and tutorials to make this a lot easier than it used to be.

wekeroad.com[^]:

I've been teeth-deep in Client-side Javascript frameworks over the last 4 months for Tekpub. This month is Angular, last month was Ember's turn and I gave up. It's the first time I've given up - here's why.... You Keep Telling Me It's MVC... Yes, the concept of MVC has been contorted over the past decade as web frameworks have adopted it and massaged it to their own ends. What does this mean?

LispCast[^]:

I was trained in Java at University. The OOP matrix was firmly implanted in my thinking. I wanted to share some things that I have learned from Clojure that were certainly possible in Java but never became fundamental to my programming practice. Clojure certainly has learned a lot from Java. It might be cool if the learning went both ways. These are universal principles. In fact, these principles are actually well known in the OOP world. You probably already know them, so learning Clojure is not required (but it is recommended!).

Braintree[^]:

Working in Go was tons of fun; the language designers have put a lot of work into making the language a joy to use. We particularly appreciated the first-class focus the language puts on the parts of development that are uninteresting in theory but very important in practice, such as third-party library management, coding convention enforcement, and testing. With that said, we ran into a series of gotchas, irritants, and warts while developing our application, which I’ll elaborate on below. Ultimately, these problems were severe enough that they convinced us that we couldn't justify the gains we saw from using Go...

Made of Bugs[^]:

At Stripe, we rely heavily on ruby and EventMachine to power various internal and external services. Over the last several months, we’ve known that one such service suffered from a gradual memory leak, that would cause its memory usage to gradually balloon from a normal ~50MB to multiple gigabytes. It was easy enough to work around the leak by adding monitoring and restarting the process whenever memory usage grew too large, but we were determined to track down the root cause. Our exploration is a tour through a number of different debugging tools and techniques, so I thought I would share it here.

Sam says you should read this[^]:

When people complain about PHP being a horrible language, not fit for human consumption, they will often talk about how the features of their favourite language are far more refined; have been designed with elegance in mind; are consistent and secure. And you know what? They're right. But PHP is still a better tool. When people write very long blog posts about the horror that is PHP, which lead to double-clawed hammers being created, then they're right. But that double-clawed PHP hammer is still a better tool.

Secure Mac Programming[^]:

OK, I have to admit that I actually missed the party. Brad Cox first described his “Object-Oriented pre-compiler”, OOPC, in The January 1983 issue of ACM SIGPLAN Notices. "This describes the Object Oriented Pre-Compiler, OOPC, a language and a run-time library for producing C programs that operate by the run-time conventions of Smalltalk 80 in a UNIX environment. These languages offer Object Oriented Programming in which data, and the programs which may access it, are designed, built and maintained as inseparable units called objects." Notice that the abstract has to explain what OOP is: these were early days at least as far as the commercial software industry viewed objects.

AnandTech[^]:

Back in late January, I received the TECK for review, a keyboard that goes by the not-so-humble name of “Truly Ergonomic Computer Keyboard”, manufactured by a company that likewise uses the name Truly Ergonomic (hello name space collision). I’m sure other companies that make ergonomic keyboards might take exception to the name, but as far as I’m concerned that’s mostly marketing. The real question is how the TECK fares in day-to-day use, and whether it’s really a better keyboard for serious typists—and particularly typists like me that suffer from carpal tunnel syndrome (CTS)—compared to the other options.

Neowin[^]:

Windows RT was/is positioned to be a variant of the Windows platform that is lightweight, offers great battery life, and has a terrific out of the box experience by shipping with Office pre-installed. One of the arguments behind Windows RT was that Intel was not able to scale its CPUs down quickly enough to be power efficient and at the same time, ARM had found ways to scale up its designs at a rapid pace to compete with Intel in the low-price market. In theory, it sounded great, ARM based devices would dominate the low-end market (netbook-ish category of devices) and Intel/AMD would fight in the upper regions for those who wanted proper Windows 8 and the ability to run legacy applications. While good on paper, this separation has yet to appear in the market.

dev.twiter.com:

Back in September, we released the Twitter REST API v1.1 and announced that API v1 would be retired in March 2013.

Quote: cnet.com[^]

MegaUpload founder Kim Dotcom has the right to sue New Zealand's spy agency for illegal surveillance, a court ruled Thursday.

The New Zealand Court of Appeal rejected the attorney general's request to exclude the Government Communications Security Bureau (GCSB) from Dotcom's lawsuit. The GCSB collected intelligence on Dotcom ahead of the 2011 raid on his house to determine whether he posed any danger to the police who would later swoop in by helicopter to arrest him.

Canadian Developer Connection[^]:

Cross-site Scripting remains one of the most common vulnerabilities found during web application security assessments, I can safely say from my experience professionally performing security code review for tens of ASP.NET applications, the average for me has been at least 9 out 10 web applications had one or more cross-site scripting issues. There are several reasons for the prevalence of this beast. While the lack of input validation and output encoding remain the top two reasons to blame for the dominance of cross-site scripting. The developers’ unfamiliarity with the differences between HTML contexts could definitely score the third place in the list of top reasons.

Gamasutra[^]:

Is one framework really better than the other? Different strokes for different folks, I suppose. If you're looking for a lightweight, high-level JavaScript / HTML5 framework then I'd certainly recommend Impact. Once you learn some of the quirks, it is easy to prototype with, and removing the need to compile each time you want to make a change is a blessing. Something I didn't cover before is Injection.

Visual Studio Magazine[^]:

In the 1990s, Web developers had to test their markup on Netscape Navigator and Internet Explorer (IE). Eventually IE won out (it was even the official browser on the Mac, for a time), and developers could effectively target a single rendering standard. Firefox, Safari and, later, Chrome changed that, forcing developers to test their HTML on multiple browsers once again. But it's a fair bet that most developers would prefer a single standard. Opera's decision means that just such a single standard could emerge, and WebKit could be it.

kellabyte[^]:

There are many different data structures used in databases to create indexes used to quickly evaluate queries. Each one has different strengths and weaknesses based on the tradeoffs they make on memory, cpu and storage (if persisted). One of these types of indexes is called a bitmap index. For the purpose of this post I’m going to be using relational database terminology but the same techniques can apply to different database types like column oriented databases or many others non-relational databases.

onderhond.com[^]:

Though technically links aren't a requirement to make the internet function (you can get by on just urls), they are the primary reason why the web took off so gloriously. Linking is an essential part of every web page out there, without links we would be copying urls the entire time (or we wouldn't because who likes to work like that). But the implementation of links (the html a-element) has been broken since the very beginning of the web and with the addition of block-level links things only got worse.