How Long Will We Need To Keep Developing For Web Browsers?

This is a thought piece for web developers.

Between my tablet and my smart phone, I don’t really pick up the laptop as much as I used to – not by a long shot. The big monolithic desktop sits back in my office, and sees even less of my face than the Laptop.

It’s a new age – we’re on the go more, we’re at the desk less – and what about that office? Do we need it anymore? We’re finding out now that the more you actually sit at a desk, the sooner you’re going to die, so really we don’t even need the office anymore.

As I go from place to place, I see less and less upper management who even have offices, and more people working from home anyway.

So back to this computer based web browser – how long will we continue to develop for it? And at that point, who exactly will we be developing for?

Who can’t get away from the computer, probably ever?

Maybe writers. Graphics editors? I can see them doing their work on tablets. Video production? Maybe. Programmers? Guys, we programmers might actually be the last ones to abandon the computer. The only people who will probably stay on the laptop are those who benefit from the keyboard / mouse, and those who absolutely need that giant screen – or possibly two screens.

So what will become of the web browser now? “Mobile First” is actually a goal for many companies who have popular websites. Now when you pull their site on a web browser, you get a responsive mobile version of the website – for the most part.

In 2014, internet access did a flip – there are now more people accessing the internet via mobile technology than by fixed internet access. The mobile devices are everywhere.


So when will web developers basically become mobile developers? Will we even retain the concept of the mobile browser on mobile devices?

All we are really interested in these days is the transfer of information, and yes browsers are good at that, but so is Facebook, and other social media.

When will we break away from the idea that the browser represents the content of the internet?

There have been times when I have learned plenty by skimming a topic in twitter – without ever clicking on a link and going to a web page.

My RSS reader does me the same way – and RSS itself – just a standardized way of delivering information – not unlike REST – which most of the other apps are using to move information around.

Just stuff to think about. As a developer – where are you focusing your time? Are you learning (a) mobile technology yet? Are you paying attention to the way the landscape is changing?

And Even More Than That Is Changing

Even within the realm of mobile development itself – things are changing fast from an application based experience to a more holistic view of data moving around within the mobile device, not so much connected to the app that it originated from – becoming a more streamlined and connected experience.  You can now interact with apps via the (OS) notification they produce, without having to go to that app.

These shifts in thinking are even more likely to spell doom for the browser as an entity and will certainly keep us developers and engineers on our toes. Just stuff to think about – time to prepare. Have you ever taken a Java class? ;)

Beginners Tutorial On Git

Git Basics

I found this great video tutorial on Git, which was created by someone known only as ConnivingCanadian – a person that I wish would create more tutorials. If anybody knows her, let me know, or just encourage her to create some more tutorials!

The tutorial also includes some information on how to use and share with GitHub. If you are a complete beginner, you’ll learn the basics first:

git init

init allows you to create a new repository.

git status

Gives you a bunch of statistics and lets you know where you are as far as all your files’ statuses. It’s similar to ‘svn stat’

git add

Is like svn add, if you’re used to svn. It allows you to add files to your repo.

git clone

Allows you to get a copy of a repository. It’s like a checkout for you svn people.

Also, she covers creating a new repository on GitHub (public or private), how to connect your local repository with your GitHub repository, and more.

Finally, she covers branching and merging.

Things to Consider When Web Site Scaling Becomes An Issue

What Web Site Scaling Means

There is a point in every company’s timeframe, when things get big – maybe it’s when the first round of investors come along, or maybe it’s an unexpected surge of traffic due to a viral hit or a big syndication.

Either way it happens, there is a point in time at which you’ve got to learn a few things about scaling.

In this article, I want to give you an overview – a starting point, and some definitions of some of the words you’ll be hearing – and hopefully using in the near future.

Along with “scaling” comes three other words – “reliability”, “cost”, and “manageability”. We’ll talk about those first real quick before we get into scalability.


Whatever you do, you need to make sure your site is reliable when you make any changes – new efforts in scaling can’t break existing functionality in other areas.

Reliability means that you can count on your data – whether thats from a database or a webpage – you can count on it to be consistent. Retrieval works properly, persistence of data that should persist, you can count on changes to be reflected in subsequent queries, and pretty much that everything works as expected.


Your scaling solution can’t make the system unmanageable. Along with scaling a system, the team (operations) needs to be able to scale as well. You can create a powerhouse system that can handle billions of requests, but if it takes millions of IT guys to staff it – you really have just moved the problem.

Updates should be easy to make – it should be easy to maintain. Diagnosing issues should be as easy as possible. That’s a tough one to get perfect as we know – but it should be considered. Also, general operation of the system should not be unwieldy.


Cost is pretty basic and easy to understand – the general idea is that you need to consider cost when you talk about scaling. If your company had all the money in the world, you could scale pretty easily – but your company doesn’t – probably – so you need to consider this as well.

In the next article, I’ll talk more specifically about scaling. It’s a topic on its own, but these items – cost, manageability, and reliability, are important to consider before you talk about exactly how you’re going to scale anything.