Businesses do that. Businesses owned the big computers, aka mainframes.
- We, as programmers, would write code.
- We would test the code.
- We would give the code to a computer operator, who would run the code as a job.
- We would train the computer operators.
All code ran on company owned and controlled computers, over company owned and controlled networks, maintained by company trained personnel. Every change was made, and tested, by people working for the company. Very tightly focused, and controlled.
That was up to 30 years ago.
Enough history, let's look at reality.
Now, we have Blogger. Blogger owns thousands of computers (aka "servers"). The Blogger computers are
- Operated by millions of operators that Blogger neither employs or knows (blog owners / readers).
- Operated from computers that Blogger doesn't own (personal computers owned by blog owners / readers).
- Operated through networks that neither Blogger nor the bloggers control, and running software produced by neither Blogger nor the blog owners / readers.
Many of these millions of blog owners / readers have no concept of computer or network management. Some know just enough to turn their computers on - and not all know that even much.
Strangely, most blog owners / readers think that Blogger is responsible for all problems with blogger "owned" computers. This is despite the Blogger owned computers being used from computers that Blogger doesn't own or control, over networks that Blogger does not control or support. And occasionally, a blogger "owned" computer can become controlled by a third party.
Very few blog owners / readers consider the fact the Blogger provides them use of the Blogger computers, without charging them directly for the service. I say "directly", intentionally, because Blogger is not a non-profit organisation. Nor do they operate at a financial loss. Blogger, and their parent company Google, make a very nice profit, and much of that thanks to the efforts from their millions of these blog owners / readers. And nowadays, people will listen to the wrong advice about blog content.
All of the financial issues aside, most blog owners / readers lack understanding of who is responsible for ensuring that Blogger code runs successfully on their computers. They seem to think that Blogger supports their computers, and there is part of The Problem.
Blogger / Google, though willing to benevolently offer the use of their computers to everyone worldwide, still needs to accept some responsibility for dealing with their users more consistently. I will keep saying that, and writing the same.
Blogger controls and supports the Blogger computers. They don't control your computer, nor how you use it. Nor should they. Very few blog owners / readers do nothing but blog, and very few computers owned or used by the blog owners / readers are used for nothing but blogging.
One of my theories about computers is that, outside large corporations with a very anal Corporate Security Policy, there are not any two computers in the entire world that are identical.
Blog owners / readers absolutely must take responsibility for their computers, and for ensuring that Blogger code runs successfully on their computers. And they need to also take responsibility for the fact that they use the Blogger computers over networks that Blogger / Google does not own or control. Blogger does not have the resources, nor the moral or legal mandate, to support your computer, nor the networks that you use to access the Blogger computers.
Yet, the first time that someone can't access their blog, or post to it, or view someone else's blog, what do we hear?
Is Blogger down again??
If Blogger can do that, surely it can do this too!!?? Why not?? I'm going to find another blog provider, that can do this, that, and everything else. And it better be free too!!!
Never a thought of
What did I just change on my computer, to prevent Blogger from working?or
Maybe I shouldn't have loaded that software. It's interfering with Blogger.
It's more normally
What did Blogger break again??
Please, be aware of problems which are your responsibility. Examine the universal nature of your symptoms, carefully and objectively, before claiming that there is a global problem with Blogger.
Learn the processes of affinity diagnosis and of differential diagnosis. And be aware of the different domains which Blogger and Google use, in allowing us to maintain our blogs, and our readers to view our blogs, safely.