The new iPhone 6 and iPhone 6 Plus needs more storage

The new features of iPhone 6 and iPhone 6 Plus are nice. I particularly like the updates they’ve made on the photo camera and video camera. The move to 60 fps video is amazing but is also cause for my biggest issue with the phone.

The 16GB of storage is simply not enough space to hold the operating system, your apps, the data for those apps (the pictures from your iMessage history will take up gigabytes of spaces over time), and these HD videos will fill up all of your storage in no time. This back of the napkin calculation assumes you don’t have any music on your phone.

Why are the lowest option 16GB but the next option is 64GB? The base model should have been 32GB. If this wasn’t an option, then the iPhone needs to catch up with all of the other phone and allow for external storage.

Is Node.js better than ASP.NET, ASP.NET MVC?

Is Node.js better than ASP.NET, ASP.NET MVC?

What I’m writing is in no way a ciricism of Node.js but the hype that some have blindly bought into. Javascript is a great language and Node.js is a good API built on Google’s V8 engine but it’s not the end all and be all that some people make it out to be.

But isn’t Node.js faster than ASP.NET? Well is depends.
Are we talking about development time?
Are we talking about time to first byte?
Are we talking about

But isn’t ASP.NET slow? Efficient, asynchronous .NET code can run circles around blocking Node.js code any day. Remember that while Node.JS allows you to develop non-blocking code, it is possible to still write blocking, synchronous code with Node.js.

Yes, Node.js makes writing non-blocking code easier, but so does .NET. I can write efficient, non-blocking code in .NET just as well as I could write in-efficient, blocking code in Node.js.

Javascript is a great, minimalistic language.
V8 is an amazing virtual machine…similar to Sun/Oracles JVM (Java) and Microsoft’s .NET framework and CLR.
Node.js is a phenominal set of libraries that have been built acount Google’s V8 engine.

It is a good language and platform, but it’s not the end all and be all that some people make it out to be.

BUT but…NPM!!

  • Java has maven and ivy
  • .NET has Nuget
  • Node.js has NPM

The package manager pattern has been around for a long time and has made things much easier for developers. NPM is a great package manager but it’s nothing new.

The dominance of Node.js (the new hotness) over ASP.NET and other (lets say older) server side technologies is accepted as canon in certain circles. Which is better? Like most open ended questions such as this one, the answer is depends?

Many people like to ask questions like “What’s the best language to use for XYZ?” and the answer is always the same…’It depends!’

Further Reading

  • http://www.haneycodes.net/to-node-js-or-not-to-node-js/

Deploying LESS changes to a Windows Azure Website via Git

In developing vacashare.com, I am using LESS to generate my CSS as I have found the technology to be a developer-friendly way of generating clean, flexible CSS. The Web Essentials extension for Visual Studio 2012 automatically compiles my LESS files into a .css and .min.css files ready for production use. The automated CSS generation combined with .NET Bundling allows for clean CSS for development and debugging purposes and a minified version for my production site. Having Web Essentials generate my .css file(s) doesn’t work, though, if the .less file is modified outside of Visual Studio.

Git publishing has been set up to the Azure website but any modifications to the LESS files are not compiled into a new CSS file until the project is opened in Visual Studio and Web Essentials does its thing. Any CSS changes made can be deployed by the Git publish but the changes will be overwritten when the .less file is modified in Visual Studio and the .css files are generated anew.

We are testing out MSBuild tasks that will allow the LESS files to be compiled into CSS files at compile time so that styling changes can be made without requiring Visual Studio (or even a Windows PC) and can be deployed via a Git Push. Installing .Less Msbuild Tasks into the Visual Studio project exposes a new build action “DotLess”. Look through the entire list of possible actions as the list is not in alphabetical order and may appear to be missing at first glance.

Build Action - DotLess

Once the tasks are installed into your project and the DotLess build action is set for the .less files, you can test things by making a change to the .less file and compiling the solution directly by command line using Msbuild.

The next test is to checkout our Git repository on non-Windows PC (in this case, Mac OSX Mavericks), making a modification to the .less file, kicking off a new build of the site using Git Publishing, and confirming that the site reflects the new styles.