Embarcadero's new RAD Studio XE5 introduces unified, single source cross platform Development for Win32, Win64, Mac OS X, iOS and Android. This is currently the best way to write cross platform applications over all these platforms. Certainly Mono, can work to hit most of them; but deployment of such apps along with their performance is extremely complicated. RAD Studio provides native level code on all of these platforms. At some point, I hope to post more on this in detail.
In addition, they've implemented a new REST Client API supporting the REST Protocol and Open Authentication 1.0/1.1 and Open Authentication 2.0 this allows easy connection to most of the modern web API's.
Unfortunately there is a bug in the OAuth1 client that causes OAuth1 authentication to fail in the western hemisphere for Twitter, Tumblr and other 1.1 API's I've tried.
Increase developer efficiency, shorten project times and create more stable applications by using third party controls.
MSMQ, Microsoft Message Queuing has been around since the days of NT 4.0 and Windows 95, way back to 1997. Initially it was an add on product to windows, but starting with Windows 2000 it was included in the server versions of Windows and with Windows XP it was included in the desktop operating system. It’s a Windows Feature that you can install/enable via the Windows Components part of Add/Remove Programs (or Add Features in W2K8). Yet surprisingly few application developers know about it or how to use it to improve application performance. Tonight we start with an introduction, later posts will talk about improving desktop application performance (everyone who blogs about MSMQ talks about server uses of MSMQ)
While the "art" of being a DBA is something that's often very application specific there are some universal optimizations that can be done to almost any SQL Server. While tailored to MS SQL Server, these optimizations are generally valid for most RDBMS.