Skip to main content

POST Desktop Era — Are we there?

Back in 90s when I worked at IBM, I used to use dumb terminals connected to Unix servers that had some amazing specifications. Then we went into the direction of having powerful desktop computers and powerful laptops.
With the introduction of Chromebooks (with ChromeOS), we are back to those dumb terminal days but still at the infancy phase. With Chromebooks, you can be almost 100% productive if you are not in IT industry, but when it comes to IT professionals, we are slowly getting there.
More and more tools are becoming available online through web browsers. One of those tools is Cloud 9 IDE that I have used for software development. I can do Linux commands/scripts, Node.js, Javascript, HTML5, and Python programming all through my browser on my Chromebook. Yes, I have my IDEs for my Windows and Macbook machines, but there is something fun about developing in a cloud IDE. Maybe it is just the nerd side of me.
The message in the above image is what I saw one day when my Cloud 9 IDE was loading; it’s awesome.
You can even set up an Amazon WorkSpaces service in AWS and install the Chromebook client app for Amazon WorkSpaces and your Chromebook turns into a proxy for a Windows 10 machine in the cloud. With the elegance of the client app, it makes you believe that your Chromebook is a Windows 10 machine.
So are we there yet? If you are an early adapter, then we are there. I think we are still a few years away from web browser tools being as good as desktop tools, but some VDI solutions are already a great substitute for your full OS laptops. There are exciting times ahead of us.
Thank you for reading this article and Happy Cloud Computing :)
Almir Mustafic

Comments

Popular posts from this blog

Brand New programming language and one solution OR …

Brand New programming language and one solution OR Two existing programming languages, one solution for EACH? I understand that there is no right or wrong. It all depends on your software architecture, team structure, team skills and other factors, but I still want to explain the scenario as it may look familiar to some. Let me explain. Let’s assume that you have microservices and common libraries in two major programming languages. You have some teams who are experts in one and some teams experts in the other programming language. Now you need to come up with a solution for a scenario that all teams will need to leverage. Let’s assume that your cloud platform has an off-the-shelf approach for this but it is supported by a 3rd programming language that your teams do not have much experience in. What is the right thing for your organization and not just from the technical point of view? A) Do you embrace what your cloud platform gives you off the shelf and implement thi...

Architecture Diagram for ...

ARCHITECTURE DIAGRAM representing interactions of your family of microservices is one of many important things to achieve the enterprise-level microservice architecture and microservices. After going through the design and contract definitions of your APIs/microservices, your team needs to put together a single diagram that explains the interaction among microservices (owned by your team) and how these microservices interact with other teams’ microservices. This is basically the blueprint for your team’s work and this picture needs to be constantly updated as you are evolving your services. What does this give you? It gives you the big picture view and it allows you to detect good or bad patterns that you cannot see when you are deep in your code. For example, you may be able to see that you are doing too many direct API calls for something that could be done with pub/sub approach. Almir Mustafic

AWS CodeStar — this is how the cloud computing will work in the future

AWS CodeStar service ?? AWS launched two new important services: * AWS CodeStar * AWS Cloud9 IDE After AWS Re:Invent, I spent some time setting up AWS Cloud9 service. I was a user of Cloud9 before Amazon acquired them. I really like the IDE and I was wondering how it integrates with the rest of the AWS services. Then I did some more learning and setup and here are the results: You can use  AWS CodeStar  service as an orchestrator/workflow that allows you to: (1) Code an application (different templates with different languages) using AWS Cloud9. (2) Manage the source code via AWS CodeCommit. (3) Deploy it using AWS CodeDeploy. All of this is managed through the AWS CodeStar dashboard. As part of creating a project within AWS CodeStar, I had an option to set it up with just one EC2 or with Elastic Beanstalk. For simplicity I chose the EC2 flavor and successfully deployed the “Hello World” Python Flask application using AWS CodeStar. After I deployed ...