|
Glosse wrote: Could it be
... most are using some flavor of *nix? 
Windows has become a consumer product, and that's what all the crappy new look & feel, starting with W8 (and then sort of shoved out of the foreground) is targeting.
The fact that businesses use Windows is because it's a choice they made a long time ago - either as a platform for their employees or because they write Windows apps as a product (or both.)
In case of the former, I wonder what the decision would be now if they were starting from a blank IT slate.
Marc
|
|
|
|
|
I see Windows 10 as complete malware not to mention the security nightmare it has become for companies.
Heads should roll for ignoring customer wants and needs in this way.
|
|
|
|
|
Glosse wrote: At a claimed 350 million installations
It is a counter of the downloads of W10. Has nothing to do with actual installations... For instance in my company we installed about 20 VMs (for different tests) but none of the actual machines got an update...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Microsoft needs to grow some brains! They seem to have all their brain cells with way too much good quantity of good quality coffee.
|
|
|
|
|
The main issue with W8 and newer is the whole idiotic concept of a unified OS for all devices. Unifying Windows Mobile and Windows Desktop into one and the same UI is like unifying a lawn mower and an electrical shaver into one device!
What MS should have been doing is to cleanly separate the device-dependent UI layer from the rest, create core libraries for the latter, and independent UI libraries for the former.
The second issue os the forced update. That's the second example where MS threw out the baby with the bath. What they should have been doing is strictly separate security fixes from updates, and make only the former automated. They should leave the updates (i. e. anything that adds new or changes existing functionality) to the user. Yes, that complicates matters. But that's what many users want from an OS. What they absolutely don't want is an OS that could decide all by itself to change how their system works in such a way that it is no longer usable for its intended purpose. That may not be the proclaimed intent of Microsoft, but it's already happend. A lot!
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
That's a good analysis, (although I do think that some of the emerging touch-based UI idioms can teach the mouse-based UI state-of-the-art a thing or two).
In my latest system purchase, 'can this hardware run an OS other than Windows if I need to?' was a leading criteria. And that's me who's been with Microsoft since DOS 3.1 through Windows 3.0, Win NT 4.0, Win2K, Win 7. I had a happy flirtation with Linux a few years either side of The Matrix (1999!) but I value binary-compatibilty on a week-to-week basis so very much when trying to do real work, that I put up with Windows for its relatively low admin-effort. (Yes, the Linux distros have now largely sorted this). But just knowing that somewhere along the line, Microsoft decided to pinch a few GB of my bandwidth and storage (precious, on my Win 7 Pro laptop) to prime its Win 10 installation files without my desire, consent, or invitation, really speaks loudly to me. The nag adverts for the Win 10 upgrades are insulting in both their frequency and their content.
So the latest machine would have been 'Linux host OS', 'Windows guest OS', except I got scared off because of a photo-editing workflow and I wasn't sure how the monitor calibration (and graphics performance) would work out running the Adobe apps in a VM. (I briefly considered *nix-underneath MacOS/X, but that felt like it would be jumping into the fire from the frying pan *and* getting fleeced along the way). I'll have my calibration questions sorted out soon, so that I'm able to make the jump when they get too much for me.
Because Win 10 in a sense 'requires' touch, and me purchasing a desktop, I'll be getting a Wacom tablet as well. Fortunately, this makes sense for the photo-editing workflow, and it's probably work out OK. However, one does feel forced into it.
|
|
|
|
|
DT Bullock wrote: one does feel forced into it
And that is the third problem: Microsofts current marketing strategy forces you into a decision that you may not yet be comfortable to make: a one year period to upgrade for free, a one month period to revert to the previous OS installation. Those may be reasonably long periods, but it still imposes pressure on the users. And pressure invokes resistance!
The irony is that it wouldn't be quite as bad if Microsoft would simply sell their 'upgrade' like they always did: at a price, with no pushing.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
You'll be surprised how many bad applications you can find in big corporations or government agencies. Once they purchase the application they must use it forever, and that is the main reason why you can see more then one computer per desk. For certain (stupid) tasks they need an old application that can work on Windows XP only. In addition, in huge systems the application division is separated from the admin-security division so the admins have no clue how the new OS would impact the old applications. And never forget this, banks and government agencies can't stop working! Maybe it sounds ridiculous but it is a common practice to buy a new computer with a new OS and retain the old computer with the old OS (for old applications). Changing OS on live computer is almost never an option in huge systems.
|
|
|
|
|
I'll get Windows 10 when I get a new machine; I run a business; I don't need a new machine right now; when I do, I'll network it: XP; Vista; Windows 8; Windows 7 Virtual; IOS; Android; Xbox(es); PlayStation(s); etc.
|
|
|
|
|
Legacy apps don't last forever, and microsoft has no real incentive to help out those companies who don't want to upgrade. After all, legacy companies already have their copies of windows and are attempting not to purchase and upgrade.
In the modern world of web apps, it is easier to let desktops be dumb, concentrating attention on a relatively few servers to upgrade. Legacy apps are being flushed from the ecosystem gradually. Microsoft is just front-running this trend.
Getting customers onto a subscription-based O/S will be a gold mine for microsoft.
I hate to say it, but it looks like they know what they're doing.
|
|
|
|
|
I want to create 34 ounces of the hottest water I can make; i.e., 212 degrees F.
I want to do this in the microwave.
Is there a real live way to estimate the amount of water to put into the bowl before I put it into the microwave ?
|
|
|
|
|
Why 34 ounces? And what is the point?
|
|
|
|
|
34 fl oz in Americanese = 1 liter in the rest of the world.
Sounds more natural that way, nothing special about the number.
|
|
|
|
|
Yes, that is the pedantic answer. I'm just curious as to the purpose of doing it What is the end goal?
|
|
|
|
|
R. Giskard Reventlov wrote: Why 34 ounces? And what is the point?
Approximately 443 days ago, I was trying to figure out a formula. That quest is detailed in this thread here[^]
Through trial and error, I came up with workable quantities for the dish washing liquid and the water.
My foaming hand soap dispensers hold 10 fluid ounces each.
It so happens that when I make the stuff, it can keep for weeks at room temperature in a capped jar.
It is therefore more efficient to make a batch of the stuff all at once and refill from the reservoir.
I chose a plastic mayonnaise container for the reservoir. These formerly quart containers have now been reduced to 30 ounces. (The moment one of those companies goes back to a full quart, I am buying even if it costs twenty percent more; another topic)
So anyway, that gives me...
- 10 ounces in the bathroom soap dispenser
- 10 ounces in the kitchen soap dispenser
- 30 ounces in the mayonnaise jar under the counter for refills
Or 50 ounces total
Now, it so happens that the ratio of dish washing liquid to water ranged between 2-to-1 and 3-to-1, with the higher concentration typically producing the best foam.
So that would be sixteen and two-thirds ounces of liquid and thirty three and one third ounces of water.
Since that is the max concentration I need, and lower levels had been shown to be less than optimal but still effective, I decided that I would be willing to allow a variance of one third of an ounce, and mix the stuff as 16 and 34 ounces.
This gave me a mixture which was 99.33 percent as good as the perfect two to one ratio. I considered that acceptable. I eschew perfectionism which I consider to be a character flaw.
Okay now, 16 ounces plus 34 ounces equals 50 ounces.
Therefore, I seek to get the exact quantity of water to produce the desired result.
This time I came up short about 3 or 4 ounces. Next time I'll just boil a few more ounces, and whatever doesn't fit into the mayonnaise jar can go into the spray bottle, as it makes a half-way okay surface cleaner.
That way I can eschew perfectionism.
That is, until I figure out the exact quantity to make the stuff add up to precisely 50 ounces; bwahahaha 
|
|
|
|
|
Oh how I wish I hadn't asked... 
|
|
|
|
|
Why not heat then measure?
|
|
|
|
|
I assume you mean fluid ounces. So, 34 ounces is 4 1/4 cups. If you've a 1 cup measuring cup, then it should be easy.
Actually, you can create water that is hotter than 212°F in the microwave. It can become superheated. So before heating it, put a straw or something in it in order to avoid a boiling splashover.
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Superheating is a good point.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
A fluid ounce of water weighs 1oz. Thus if you have kitchen scales put your container on it ( I would choose an insulating container such as polystyrene ) and zero the scales. Then slowly pour in water until you have 34 oz (if the scales are metric just do the conversion).
Now put the container in the microwave and start heating it (on high) for periods of maybe 2 minutes. The steps allow convection to circulate the water to achieve even temperature. Carefully observe. As the water gets hotter you can reduce this interval. When the water just starts to boil you are at boiling point (212F). In this way you will avoid superheating the water. Superheating and microwave ovens[^]
Whatever you need the water for it is unlikely to still be at 212F when you actually use it. This is the real world remember.
All the above applies to pure water at sea level.
Impurities in the water will raise the boiling point (tap water ain't pure) and rising above sea level will lower the boiling point.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
modified 9-Jul-16 1:23am.
|
|
|
|
|
Weigh it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Are you trying to estimate how much you will lose to evaporation?  We can't help with that.
|
|
|
|
|
PIEBALDconsult wrote: Are you trying to estimate how much you will lose to evaporation? We can't help with that
Basically yes.
I start with "X" times 34 ounces, and remove the bowl from the microwave with exactly 34 ounces.
Well, that's what I want to do.
My first total guess left me about 3 or 4 ounces short.
|
|
|
|
|
C-P-User-3 wrote: is there a real live way to estimate the amount of water to put into the bowl before I put it into the microwave ?
No.
Put 40 oz of water in the microwave and set the machine on High. When it boils, remove the container and pour off 34 ounces. Add 1 packet of lime Jello and 8 oz of tequila; refrigerate and consume according to your personal compression ratio. After that, you're on your own, and probably having a much better time than I am on this Saturday night.
Will Rogers never met me.
|
|
|
|
|
Smirk.
 
That was basically my approach, probably not the exact numbers.
Anyway, I got close but not perfect.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
