How do you propose documenting that for new users that want to try out Linux but aren't comfortable messing around in their BIOS? Getting them to figure out what motherboard/BIOS version they have so you can send them just the right screenshot?
Namely the issue of charging, max speed and battery life.
Current electric cars have comparable performance to equivalent petrol cars and ranges that cover the daily distance the average driver covers (30-50 miles in the US).
Consequently, since for the average person an overnight charge at home is easily sufficient to cover their needs, the importance of charging points outside the home is relatively low.
For the majority of drivers, an electric car is a drop in replacement today for the majority of their journeys.
Wordperfect had their chance. People forget but back then there was a feature war between the two compamies and while Woerperfect was clearly a better product, fewer people used it and the two companies struggled to lock down users by increasing the difficulty for importing files from either competitor into the product of the other competitor.
In actual fact, Wordperfect was the (vast) majority market share holder and Microsoft expended enormous resources modifying their product to make users happy and winning them over. This is why old versions of Word have a "Wordperfect mode" to emulate Wordperfect's shortcut keys and other behaviour (in as much as that is possible).
Wordperfect lost, fair and square. They wasted time creating a Windows product, then wasted time improving the shit one they did release, and by the time they had something decent the horse had bolted.
The main problem is that VM-to-VM traffic doesn't always head out over a physical network. It's easy to put a firewall between different sections of a physical LAN; it's a good deal harder to put it between different sections of a single physical computer.
How are you firewalling traffic between two physical machines plugged into the same switch and on the same vlan ?
Given that this is precisely what we are talking about [...]
No, we aren't.
You are waving your hands and asserting that Lion negatively impacts "creative" workflow.
I am asking you to explain how.
You are not explaining how.
When you do start giving specifics, then maybe we can "talk about" a) whether or not Lion actually does negatively "influences one's workflow", b) how and c) why. Until that discussion can begin, however, how much either of us claims to know about "how one's environment influences one's workflow", is completely and utterly irrelevant.
Further, I've used the platform for all of 5 minutes, I simply sit next to someone who bitches about it for 40+hr/wk; though, in those 5 minutes, I did get the distinct feeling that something was amiss. Do I need to repeat that again?
No, you need to provide more detail on what caused "the feeling".
Well, we're not comparing OSX to Windows, now, are we? We're comparing OSX to OSX, so I'd go so far as to say that your examples would be pretty pointless.
I am trying to make the point that when real UI differences with real impacts actually exist, it is trivial to enumerate and describe them, rather than vague implications about getting the heebie jeebies.
The paragragraph you quoted without context (and replied to out of context -- you see, it's fine to quote without context if you're replying in that same context, which you did not) [...]
The mind boggles at how something can be quoted out of context on a website where all the context is displayed directly above.
Oh, look, I repeated it again, 2 more times.
So all you're doing is parroting someone else's opinion ? Why, then, are you presenting that opinion as a conclusion you have reached yourself after actual evaluation and analysis, based on an understanding of "how one's environment influences one's workflow" ?
The only problem really is that if your external VM gets compromised, it can affect QoS if you're on the same host. Not the end of the world, but once they've got a VM, they can hog as many resources as you configured for the VM (And if it's your outward facing site, you probably are giving it quite a bit of bandwidth already, so they may be able to plug up a NIC entirely)
This is no different from physical servers when you're looking at the environment as a whole..
Because it puts you in danger from "VLAN hopping" attacks.
It's trivial to mitigate vlan-hopping attacks in several ways (the wiki pages covers two, a third is to simply use a physically different set of adapters for DMZ vlans).
And if one of your external servers is cracked then you SHOULD distrust all the systems on that system. If they're all on the same VM host then you have a big problem.
Uh, no. VMs can't just up and communicate with each other through the host at a whim.
Just because it can be done does not mean it is good practice to do it.
It's quite reasonable practice to do it assuming you take simple and obvious risk mitigation measures. There's no reason putting DMZ and non-DMZ VMs on the same host should add more risk than, say, letting your firewall admins get drunk at the Christmas party.
How much do you understand about how one's environment influences one's workflow?
Given you cannot even articulate how Lion negatively "influences one's workflow" compared to Snow Leopard, how much *I* know isn't particularly relevant to the discussion at this stage.
There's nothing specific (that I know of, that my boss has complained about) that you *can't* do in Lion that you can do in Snow Leopard, but the workflow has changed in ways that are very much "less than optimal".
How ? This is about the fourth time I've asked, yet you still haven't answered. It's a pretty simple question. If the problems are that significant, how hard can it be to come up with a few examples ? Heck, I could come up with a few examples of how the OS X is "less than optimal" compared to Windows right off the top of my head.
Because the Liberals (Conservatives) were blameless when they agreed to the US Free Trade Agreement that shoehorned US patent and copyright "treaties" into our body of Law.
On the whole, IP law in Australia was less restrictive after those changes.
Prior to 2006, for example, you couldn't format-shift music (eg: to rip CDs you owned into MP3s for your iPod) and recording just about anything off TV was copyright infringement.
Me? It's not, I've opted to stay on Snow Leopard for the time being. My boss? Well, I'd have to ask him for specifics, but I hear him bitching about it all the time; and he's the reason we're a Mac office.
Lion's a consumer OS with a focus on consumption of media and apps, rather than a general purpose OS, like Snow Leopard. Mountain Lion is only a step further in this direction.
In what way is Lion any less a "general purpose OS" than Snow Leopard ? What would Lion stop you doing that Snow Leopard does not ? How will Lion obstruct a a software developer from developing software ?
In short, why do you keep posting about how Snow Leopard is better for "software development" or "content creation" yet cannot (or will not) actually articulate any *reasons* Lion is worse ?
If it isn't already running in an emulated environment (Java,.net, etc.) then it interacts with the hardware. This makes your statement so watered down that it becomes pointless.
Unless it's running in kernel mode, it doesn't interact with the hardware. It interacts with the OS, which interacts with the hardware on its behalf.
Once Apple starts leveraging its market share in iPhones and iPads to push people towards OS X, Microsoft is going to feel a lot of pain.
So long as the minimum buy-in cost remains twice as much, and Apple's attitude to business and enterprise lies somewhere between apathy and contempt, they're probably pretty safe.
We have a firm quote that the Microsoft TAX on Windows 8 to have Microsoft safely remove the crapware their partners load on top of each copy of Windows 8 will be an additional $99.
Why are you blaming Microsoft for something OEMs are doing ?
Note that the last time Microsoft tried to pro-actively prevent OEMs from installing software on their PCs, they got smacked with an anti-trust investigation.
You've basically described the design of a standard memory-protected, pre-emptively multitasking operating system. Just substitute "kernel" for "VM OS" and "processes" for "VMs".
MS is letting us down by not making the VM the backward compatibility. At this stage of the game, we should be able to run any application all the way back to DOS 1.0 with complete backward compatibility on Windows 7.
If you have an application - even all the way back to DOS 1.0 - that doesn't try to interact directly with hardware and was written to the documented APIs, chances _are_ very good it'll run in Windows 7.
I was refering to the user, not the system. Lion's a consumer OS with a focus on consumption of media and apps, rather than a general purpose OS, like Snow Leopard.
Please tell me about the "general purpose" things I can do in Snow Leopard that I can't do in Lion.
Think about that for a minute...do you HONESTLY think MSFT has THAT kind of clout anymore? That they can force the entire industry to switch, when a 17 inch touchscreen costs $300 and a 27 inch non touch costs $189?
The problem with touchscreens has nothing to do with cost and everything to do with their inappropriateness for most desktop PC tasks.
With that said, your anti-Windows 8 hysteria is ridiculous. On a desktop PC, while it looks quite different to previous versions initially, in actual use the "touchscreen UI" is basically just a full-screen Start Menu and past that it operates basically the same as Windows 7.
So? SSNs don't expire with visas. They are permenant and last forever. You can have a valid dirver license and a valid SSN and still not legally be in the country.
My point was that you can't use an AZ license as a stepping stone to an SSN as the person I was replying to suggested.
Slashdot Mirror
Run it in a VM.
Current electric cars have comparable performance to equivalent petrol cars and ranges that cover the daily distance the average driver covers (30-50 miles in the US).
Consequently, since for the average person an overnight charge at home is easily sufficient to cover their needs, the importance of charging points outside the home is relatively low.
For the majority of drivers, an electric car is a drop in replacement today for the majority of their journeys.
In actual fact, Wordperfect was the (vast) majority market share holder and Microsoft expended enormous resources modifying their product to make users happy and winning them over. This is why old versions of Word have a "Wordperfect mode" to emulate Wordperfect's shortcut keys and other behaviour (in as much as that is possible).
Wordperfect lost, fair and square. They wasted time creating a Windows product, then wasted time improving the shit one they did release, and by the time they had something decent the horse had bolted.
Yes. No foundation in either reality or rationality.
Uhhh. Does the USA not have postal votes ?
Into "people's" tax haven bank accounts.
How are you firewalling traffic between two physical machines plugged into the same switch and on the same vlan ?
No, we aren't.
You are waving your hands and asserting that Lion negatively impacts "creative" workflow.
I am asking you to explain how.
You are not explaining how.
When you do start giving specifics, then maybe we can "talk about" a) whether or not Lion actually does negatively "influences one's workflow", b) how and c) why. Until that discussion can begin, however, how much either of us claims to know about "how one's environment influences one's workflow", is completely and utterly irrelevant.
No, you need to provide more detail on what caused "the feeling".
I am trying to make the point that when real UI differences with real impacts actually exist, it is trivial to enumerate and describe them, rather than vague implications about getting the heebie jeebies.
The mind boggles at how something can be quoted out of context on a website where all the context is displayed directly above.
So all you're doing is parroting someone else's opinion ? Why, then, are you presenting that opinion as a conclusion you have reached yourself after actual evaluation and analysis, based on an understanding of "how one's environment influences one's workflow" ?
This is no different from physical servers when you're looking at the environment as a whole..
It's trivial to mitigate vlan-hopping attacks in several ways (the wiki pages covers two, a third is to simply use a physically different set of adapters for DMZ vlans).
Uh, no. VMs can't just up and communicate with each other through the host at a whim.
It's quite reasonable practice to do it assuming you take simple and obvious risk mitigation measures. There's no reason putting DMZ and non-DMZ VMs on the same host should add more risk than, say, letting your firewall admins get drunk at the Christmas party.
Well, arguably it did given how long home video recorders and personal audio devices were around before Copyright was appropriately modified.
However, that's moot. At no point did I try to "justify" the FTA, so take your straw man elsewhere.
Given you cannot even articulate how Lion negatively "influences one's workflow" compared to Snow Leopard, how much *I* know isn't particularly relevant to the discussion at this stage.
How ? This is about the fourth time I've asked, yet you still haven't answered. It's a pretty simple question. If the problems are that significant, how hard can it be to come up with a few examples ? Heck, I could come up with a few examples of how the OS X is "less than optimal" compared to Windows right off the top of my head.
On the whole, IP law in Australia was less restrictive after those changes.
Prior to 2006, for example, you couldn't format-shift music (eg: to rip CDs you owned into MP3s for your iPod) and recording just about anything off TV was copyright infringement.
On the upside, since the 2006 changes it's now legal to record stuff off TV and put music onto your iPod.
You wrote:
In what way is Lion any less a "general purpose OS" than Snow Leopard ? What would Lion stop you doing that Snow Leopard does not ? How will Lion obstruct a a software developer from developing software ?
In short, why do you keep posting about how Snow Leopard is better for "software development" or "content creation" yet cannot (or will not) actually articulate any *reasons* Lion is worse ?
No worries. The huge range of Windows 7 ARM devices means you're spoilt for choice with hardware as well.
Maybe I need to ask in a different way: what is Lion preventing you from doing as a "developer" ?
Unless it's running in kernel mode, it doesn't interact with the hardware. It interacts with the OS, which interacts with the hardware on its behalf.
So long as the minimum buy-in cost remains twice as much, and Apple's attitude to business and enterprise lies somewhere between apathy and contempt, they're probably pretty safe.
Why are you blaming Microsoft for something OEMs are doing ?
Note that the last time Microsoft tried to pro-actively prevent OEMs from installing software on their PCs, they got smacked with an anti-trust investigation.
You've basically described the design of a standard memory-protected, pre-emptively multitasking operating system. Just substitute "kernel" for "VM OS" and "processes" for "VMs".
If you have an application - even all the way back to DOS 1.0 - that doesn't try to interact directly with hardware and was written to the documented APIs, chances _are_ very good it'll run in Windows 7.
Please tell me about the "general purpose" things I can do in Snow Leopard that I can't do in Lion.
The problem with touchscreens has nothing to do with cost and everything to do with their inappropriateness for most desktop PC tasks.
With that said, your anti-Windows 8 hysteria is ridiculous. On a desktop PC, while it looks quite different to previous versions initially, in actual use the "touchscreen UI" is basically just a full-screen Start Menu and past that it operates basically the same as Windows 7.
My point was that you can't use an AZ license as a stepping stone to an SSN as the person I was replying to suggested.