Skip to main content

Learning iOS development on @MacinCloud

I have been wanting to learn and develop iOS apps or a while. The price of a good developer's Mac was a little unreasonably high and I am quite sure I am not ready to switch over 100% to a Mac anytime soon. I found MacinCloud.com and their pricing is very reasonable. I didn't want to own a Mac, I didn't want to spend a lot of cash, but I wanted to use a Mac for a few hours a day just to learn iOS development. MacinCloud.com just worked out fine.

I signed up for the $20 per month service to access a real Mac (not a Virtual Machine) for three hours a day. The device they gave me is a high end Mac Mini with 16GB of RAM and preloaded with all the popular app development tools and platforms out there, including XCode, PhoneGap and a lot of others that I am not even familiar with. Google drive and Dropbox are already installed and so is Chrome and Firefox. Save all your data in Google Drive or Dropbox, share with your team or move your content to your personal laptop. Too many options, but there is no admin access. I was fine with that because they had everything I needed pre-installed and ready to go.

I have options to login through Remote Desktop or login via browser. I didn't even try the browser option. There are other options for accessing from a iOS device, but c'mon why would anyone want to do that?

The customer service is great too. I was having issues with performance at night time. I sent an email to them, they responded by next day morning, asked me to run some speed tests and traceroutes. The next day, they moved me to a different server and it has been working great since then.

Brand new Mac Mini with 2.6GHz processor and 16B of RAM: $899

Yearly cost of the same device on MacinCloud: 20 x 12 = $240

It is a better deal than owning a Mac for what I want to do with it. I think I will stick with MacinCloud.com for now.

Popular posts from this blog

Create #VirtualPrivateCloud, NAT Instance and NAT Gateways on @AWSCloud

Create a Virtual Private Cloud, NAT instance and the new NAT Gatweay ... and making it all work. This is a YouTube playlist of three videos.

Cheat sheet to create a #VPC and Subnets on @AWSCloud

One of the critical things to remember for working with a AWS VPC is creating and using it. I had hard time remembering how to do it, so, I wrote down a cheat sheet for myself.  If anyone wants to follow along, just navigate to the VPC page on the AWS Console and start with 'Create VPC' button. Please note that this may cost some dollars if you are not on the free tier. If you are on the free tier and make mistakes, it may cost some dollars. In the steps below, we will be creating the following on a new VPC: An internet gateway One public subnet with routes for accessibility from the internet One private subnet without any routes One EC2 web server with Apache installed in it and serving a sample html page - using the public subnet. One EC2 server with the private subnet and security group that allows access to resources running on the public subnet only.  Create VPC Name tag: myVPC CIDR Block: 10.0.0.0/16 Tenancy: default (Must have default. Otherwise, it

SQL Server tables with JSON

We can indeed store json data as-is into a traditional Microsoft SQL Server database. The document hosted on Microsoft's site left a lot of questions and unknowns that I had to explore and experiment to figure out the right recipe for creating a table to store json, inserting the data as json and querying for the values of individual keys within the json. Here you go:  --Create a table with an identity column and a nvarchat(max) column to store the individual json documents create table dbo.logs (     _id bigint primary key identity,     json_log nvarchar(max) ); --Add a constraint to the json_log column of the table to ensure that the table accepts only json as value to store ALTER TABLE dbo.logs ADD CONSTRAINT [json_log record should be formatted as JSON] CHECK (ISJSON(json_log)=1); --Insert json into the table insert into dbo.logs values ('{"key": "value"}'); insert into dbo.logs values ('{"key": "value1"}'); --Query for al