Skip to main content

microsoft extends windows XP's lifecycle

heres a good news to XP fanatics . last year the rich guys from Richmond also collectively known as Microsoft announced that they will stop shipping windows XP to hardware vendors starting January 31 , 2008 fortunately because of some moves from PC makers , they took back their statement and reschedule it for june 30 , 2008 . now heres another shocker , realizing how resource-hungry their new flagship product is ( we all know it by the name of Vista ) they made another statement saying that they are extending Windows XP for another two years ! but , only PCs which Microsoft deems ultra-low cost will be able to use Windows XP. so you would expect that most of the machines coming out this year will carry Vista . what ? yes , we may not want it but Vista will be on them .

on a personal note , i am using Vista Ultimate now on my development machine with 3.5G of RAM . its not that i asked for it , its by coincidence . the interface is nice but performance wise , i'd rather be developing on XP machines . unfortunately , this is just one of the many changes that we have to accept and we have to live with everyday . as i always say , if you hate how microsoft runs the industry , be open and grab yourself a linux . a move that i have always been dreaming about but i could not make it happen . why ? my job requires me to love microsoft !!
Labels:

Comments

Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

The Story Behind the Name C#

I remember one time in an exam for employment , the first question was - who is the father of C#? I have been working with the language but never did I ask myself who actually started the language ( of course Mirosoft was the brainchild , right? ) . After a googling expedition I found out who was the culprit - Microsofts Anders Hejlsberg . I was not interested why it was called C# then , but opening my VS2008 today , I stumbled on one of the articles being shown at the VS2008 opening page - "Computer World: The A-Z of Programming : C#". Its an interview with Anders discussing the history and beyond of C# . Heres the cool part , the name for C# prior to its release was actually COOL (C like Object Oriented Language) . Below are some lines taken from the interview: Why was the language originally named Cool, and what promoted the change to C#? The code name was Cool, which stood for ‘C like Object Oriented Language’. We kind of liked that name: all of our files were called .coo...
Post a Comment
Read more