Geeks and engineers should have a 3D printer if they do modeling of any kind. Civilians should have them if they're artists or designers, or like to create. And I hope for an open code/free-like model of licensing app code to go with it, 'cause the closed model doesn't evolve the code quickly enough, or ensure portability to varying OS releases quickly.
LibreOffice is reasonably good. Apple's office apps are Microsoft's Apple Office app. It has two advantages, being free of cost or subscription and it's open source.
No, it doesn't have the number of users or integration with other tools, but it works (well) for many user's applications.
False. Think about what you said. You should be ashamed of yourself. Your location and your IP. Should you take a photo and append it to your IP address and where you're going?
You give them statistics of where you're going. Where you are. The time, the date. You don't think they know who's at the destination?? Add all this stuff up. Look at your reply.
If I didn't know better, sometimes I'd believe that 3/4ths of slashdotters were astroturfers fighting the battles of their overlords.
Will Apple make their clientele suffer the death from a thousand cuts by cutting the quality and openness of their devices? That's for Apple to decide. Apple is by no means a democracy.
As for Google, you sacrifice most of your personal info to get the juicy maps. Is there a solution where locational privacy and great maps intersect? Not in the "free" model, but perhaps there is in the "open" model.
Further research says: sampling quantities only. Nothing in real production until perhaps next year. No one's talking grafts yet, and no one knows the outcome. Only proof of concept hardware is out there, and it's so far, not really testable.
Like vCenter, yes. More power & functionality? Different, and different with an enormous variety of third party product, script, and intellectual support-- not that vCenter doesn't have that. A different model of looking at virtualization of resource instanciation.
If you're looking for production use, OpenStack is a methodology that allows you to deploy VMs, which do work for you, into either your own hosts, or external hosts, in automated ways, with high customization potential (Windows or Linux). These can be persistent or non-persistent apps, on-premises or in the cloud, or both (subject to your security models and HA needs).
The second angle is to use the method for dumb, simple farm expansion and contraction models. You can add load tolerance to web farms. Etc.
It's the methodology-- the stack-- that enables the automation steps, and the flexibilities, and the third-party recipes that do the job. Some people have no need for this kind of VM manipulation capability.
So far, yes. But when will the need for grafted cores into a 64bit memory model and computational strength start? In the early 2000s, everyone thought: 32 bit is great! Look how fast it goes! Now you can't find a 32-bit server except as VM.
A bit of digging says that there 64-bit ARM CPUs out there. I don't know if they're available in quantity, or how they're sold. I looked for applications using them, and there are LAMP stacks, but nothing that appears "optimized" for the foundation.
No one seems to know about power consumption, except that there's L1-3 support onboard on two of them, and beyond that, I'm still fishing for information. Why? Because it's there.
The web page sucks. The tools, however, are reasonably powerful VM stack controllers that use stuff you probably know, like REST, XML, and communications like marionette and puppet, etc etc. You bring up lots of stuff, make it do work, cough the results into storage, rinse, repeat.
If you're a developer of systems-grade apps, OpenStack saves you steps, talks to lots of providers (especially AWS and Rackspace) and you get a lot of work done. Don't be superficial and look at the website. Dive deeper and try it; it's profoundly simple if you're a modern systems coder with a little time to learn. Best background: learn Ruby, Rails, heavy scripting language, and the principles of VMs. Mix, pour.
Hmmmm. Then why hasn't it been done? Power consumption, mostly. Ease of supply chain. More easily grafted support chips than Intel/AMD family chips in current ARM architectures. There is no data on how much power a 64-bit CPU will pull, but I'll look around and see if someone's studied that.
AppliedMicro is a foundry, and it does indeed seem to have a v8 64-bit chip-- at least a prototype. I'm checking to see if it's shipping, and if so, who the customers are.
As I mentioned up thread, there are limitation when multimedia comes into play.
Two suggestions come to mind. I use a heft HP MM machine that has direct outs. Hooks up to a 32" LCD. Gets its data itself (disk, cd, stick) or streams it over broadband.
It has two VMs. One does DVR very well, and stores stuff natively so that the base OS can stream it to screen. The other VM flips to the office and catches what's going on there. I can flip thru them with a wireless keyboard and a wireless mouse (not bluetooth.....yet).
There's more stuff I could cram in there, but even this one is three years old now and needs more disk than I want to invest in it, so maybe during the end of year holidays, I'll recycle it and get something heftier still. It replaces four machines and seven devices. And people think I'm a geek. VNC is not very nice and sadly or happily, there are VDI apps that can indeed stream low-data-rate HD, and there are better commercial solutions available. It's an obese client. And it's going to get obeser;)
Many apps don't draw 100% CPU.... and when they do, then it's not for long. Yes, there are exceptions as you cite. But nine systems, unless highly refined, is often unneeded these days, and a duplication of resources. Yes, HA systems and others are mandated to be separate hardware, but again, not often.
As otherwise noted, perhaps the chip will emerge when the need is demonstrated. Oh, wait, there really is nothing like a 64-bit 6502. Much work would need to be done to change the math, the memory vectors, timing, bus bandwidth and various timings, ad infinitum. Oh, might be more like Atom then? I wonder. The loveliness of the ARM family is that it's easily modified and graftable with other functionalities/features. Will a 64-bit version have the same nearly pluggable ease? We'll get to see, I'm guessing, soon enough.
Dedicated hardware, might be nearly 100% efficient. Most machines are not.
Virtualizing sound and video and certain other streams can be difficult with virtualization. Sometimes.
There might be a platform mismatch. First one I'd have seen in a long time, but might be a possibility, remote as that is.
Might need fast disk channel. Yup. We can do that. Same for network and CPU. Ok. Scratch that.
Except for multimedia redirects and certain graphics functions, there's not much left, really. Nine machines is sloth, generally speaking. Might be a reason, but usually it's: can't be bothered.
Let's say you have but one legally licensed copy of Windows. Do a P2V and then run it on VirtualBox. When doing the initial bring-up with Windows, just re-register it. Little fuss or muss. However, if you were doing luscious, GPU-enabled fast graphics, lower your expectations unless you're optimizing your Linux host and perhaps, using a better hypervisor than VP.
Then, with the saved money, go on eBay and get a nice FlightSim controller kit, and have at it. I used to enjoy flying a lot, and had lots of Flight Simulator stuff, then for a while, x-frame (which has an evolved ecosystem worthy of investigation).
I can't vouch for the GPU or hefty graphics card you're using, but you could do the same thing with lots of heft for under 150watts, including the freaking LCD monitor. There are a number of nice, high stroke CPUs out there that don't need a 500w supply.
Yes, Flight Simulator is a pig. But it seems to like AMD's math over AMDs, and in terms of graphics, I haven't kept up, so can't address that particular piece. Nonetheless, 500w can power a decent electric scooter.
I don't think you're trolling, just living in the early 2000s. If Intel doesn't release ATOM power settings, no big deal. Easily.Avoided. Atom 64-bit is still a few years away until practical implementations are made. Atom is their answer to a bridge between ARM and fat Xeons. As a design, it's a compromise, and is unlikely to live long.
That Intel doesn't release specs is a questionable assertion. That we care is also questionable. It's more of the Intel-Microsoft boogie-man propaganda meme that's rooted in some false premise. ARM is really good and graftable-- in low power apps in a 32-bit space. Currently, that's a sweet spot for entrant/basic computing devices. Intel (and to an extent, AMD) can't write a sufficient amount of basics that allow operating systems to use all the cores that they can slab into a socket, so virtualization has become the strength of multi-core devices, and there's plenty of current popularity in *that*.
Atom is fun, but isn't a big deal, and IMHO, won't be around very long. Getting one's feathers ruffled over it is nihilistic and distracts from other, deeper rivalries between F/OSS and Microsoft and Google's models.
Slashdot Mirror
Sure. Google doesn't record it. Like they don't manipulate browsers, or destroy WiFi information garnered in their StreetView processes.
Yeah. Truth. Your trust of Google is ill-placed.
Geeks and engineers should have a 3D printer if they do modeling of any kind. Civilians should have them if they're artists or designers, or like to create. And I hope for an open code/free-like model of licensing app code to go with it, 'cause the closed model doesn't evolve the code quickly enough, or ensure portability to varying OS releases quickly.
LibreOffice is reasonably good. Apple's office apps are Microsoft's Apple Office app. It has two advantages, being free of cost or subscription and it's open source.
No, it doesn't have the number of users or integration with other tools, but it works (well) for many user's applications.
False. Think about what you said. You should be ashamed of yourself. Your location and your IP. Should you take a photo and append it to your IP address and where you're going?
You give them statistics of where you're going. Where you are. The time, the date. You don't think they know who's at the destination?? Add all this stuff up. Look at your reply.
Ok, different metaphor: Fight Club.
You need to want a slice of the smartphone market and be willing to throw punches, even if ultimately, it's your own nose you break.
Mod parent up, not down.
If I didn't know better, sometimes I'd believe that 3/4ths of slashdotters were astroturfers fighting the battles of their overlords.
Will Apple make their clientele suffer the death from a thousand cuts by cutting the quality and openness of their devices? That's for Apple to decide. Apple is by no means a democracy.
As for Google, you sacrifice most of your personal info to get the juicy maps. Is there a solution where locational privacy and great maps intersect? Not in the "free" model, but perhaps there is in the "open" model.
Further research says: sampling quantities only. Nothing in real production until perhaps next year. No one's talking grafts yet, and no one knows the outcome. Only proof of concept hardware is out there, and it's so far, not really testable.
Like vCenter, yes. More power & functionality? Different, and different with an enormous variety of third party product, script, and intellectual support-- not that vCenter doesn't have that. A different model of looking at virtualization of resource instanciation.
Yes, in two vectors.
If you're looking for production use, OpenStack is a methodology that allows you to deploy VMs, which do work for you, into either your own hosts, or external hosts, in automated ways, with high customization potential (Windows or Linux). These can be persistent or non-persistent apps, on-premises or in the cloud, or both (subject to your security models and HA needs).
The second angle is to use the method for dumb, simple farm expansion and contraction models. You can add load tolerance to web farms. Etc.
It's the methodology-- the stack-- that enables the automation steps, and the flexibilities, and the third-party recipes that do the job. Some people have no need for this kind of VM manipulation capability.
Perhaps things can get better. Taco-- get back on the horse, dammit.
So far, yes. But when will the need for grafted cores into a 64bit memory model and computational strength start? In the early 2000s, everyone thought: 32 bit is great! Look how fast it goes! Now you can't find a 32-bit server except as VM.
A bit of digging says that there 64-bit ARM CPUs out there. I don't know if they're available in quantity, or how they're sold. I looked for applications using them, and there are LAMP stacks, but nothing that appears "optimized" for the foundation.
No one seems to know about power consumption, except that there's L1-3 support onboard on two of them, and beyond that, I'm still fishing for information. Why? Because it's there.
The web page sucks. The tools, however, are reasonably powerful VM stack controllers that use stuff you probably know, like REST, XML, and communications like marionette and puppet, etc etc. You bring up lots of stuff, make it do work, cough the results into storage, rinse, repeat.
If you're a developer of systems-grade apps, OpenStack saves you steps, talks to lots of providers (especially AWS and Rackspace) and you get a lot of work done. Don't be superficial and look at the website. Dive deeper and try it; it's profoundly simple if you're a modern systems coder with a little time to learn. Best background: learn Ruby, Rails, heavy scripting language, and the principles of VMs. Mix, pour.
Hmmmm. Then why hasn't it been done? Power consumption, mostly. Ease of supply chain. More easily grafted support chips than Intel/AMD family chips in current ARM architectures. There is no data on how much power a 64-bit CPU will pull, but I'll look around and see if someone's studied that.
AppliedMicro is a foundry, and it does indeed seem to have a v8 64-bit chip-- at least a prototype. I'm checking to see if it's shipping, and if so, who the customers are.
As I mentioned up thread, there are limitation when multimedia comes into play.
Two suggestions come to mind. I use a heft HP MM machine that has direct outs. Hooks up to a 32" LCD. Gets its data itself (disk, cd, stick) or streams it over broadband.
It has two VMs. One does DVR very well, and stores stuff natively so that the base OS can stream it to screen. The other VM flips to the office and catches what's going on there. I can flip thru them with a wireless keyboard and a wireless mouse (not bluetooth.....yet).
There's more stuff I could cram in there, but even this one is three years old now and needs more disk than I want to invest in it, so maybe during the end of year holidays, I'll recycle it and get something heftier still. It replaces four machines and seven devices. And people think I'm a geek. VNC is not very nice and sadly or happily, there are VDI apps that can indeed stream low-data-rate HD, and there are better commercial solutions available. It's an obese client. And it's going to get obeser ;)
This is what VDI is for.
Many apps don't draw 100% CPU.... and when they do, then it's not for long. Yes, there are exceptions as you cite. But nine systems, unless highly refined, is often unneeded these days, and a duplication of resources. Yes, HA systems and others are mandated to be separate hardware, but again, not often.
As otherwise noted, perhaps the chip will emerge when the need is demonstrated. Oh, wait, there really is nothing like a 64-bit 6502. Much work would need to be done to change the math, the memory vectors, timing, bus bandwidth and various timings, ad infinitum. Oh, might be more like Atom then? I wonder. The loveliness of the ARM family is that it's easily modified and graftable with other functionalities/features. Will a 64-bit version have the same nearly pluggable ease? We'll get to see, I'm guessing, soon enough.
Alright then. Let's see.
Dedicated hardware, might be nearly 100% efficient. Most machines are not.
Virtualizing sound and video and certain other streams can be difficult with virtualization. Sometimes.
There might be a platform mismatch. First one I'd have seen in a long time, but might be a possibility, remote as that is.
Might need fast disk channel. Yup. We can do that. Same for network and CPU. Ok. Scratch that.
Except for multimedia redirects and certain graphics functions, there's not much left, really. Nine machines is sloth, generally speaking. Might be a reason, but usually it's: can't be bothered.
Careful, there's a bit of the Bill Gates in your statement.
Dude. We have to educate you about virtual machines. Time to recycle and reclaim!
Let's say you have but one legally licensed copy of Windows. Do a P2V and then run it on VirtualBox. When doing the initial bring-up with Windows, just re-register it. Little fuss or muss. However, if you were doing luscious, GPU-enabled fast graphics, lower your expectations unless you're optimizing your Linux host and perhaps, using a better hypervisor than VP.
Then, with the saved money, go on eBay and get a nice FlightSim controller kit, and have at it. I used to enjoy flying a lot, and had lots of Flight Simulator stuff, then for a while, x-frame (which has an evolved ecosystem worthy of investigation).
Then, wild-abandon-time, on the cheap.
I can't vouch for the GPU or hefty graphics card you're using, but you could do the same thing with lots of heft for under 150watts, including the freaking LCD monitor. There are a number of nice, high stroke CPUs out there that don't need a 500w supply.
Yes, Flight Simulator is a pig. But it seems to like AMD's math over AMDs, and in terms of graphics, I haven't kept up, so can't address that particular piece. Nonetheless, 500w can power a decent electric scooter.
Let me correct: ARM 64-bit is still a few years away.
I don't think you're trolling, just living in the early 2000s. If Intel doesn't release ATOM power settings, no big deal. Easily.Avoided. Atom 64-bit is still a few years away until practical implementations are made. Atom is their answer to a bridge between ARM and fat Xeons. As a design, it's a compromise, and is unlikely to live long.
That Intel doesn't release specs is a questionable assertion. That we care is also questionable. It's more of the Intel-Microsoft boogie-man propaganda meme that's rooted in some false premise. ARM is really good and graftable-- in low power apps in a 32-bit space. Currently, that's a sweet spot for entrant/basic computing devices. Intel (and to an extent, AMD) can't write a sufficient amount of basics that allow operating systems to use all the cores that they can slab into a socket, so virtualization has become the strength of multi-core devices, and there's plenty of current popularity in *that*.
Atom is fun, but isn't a big deal, and IMHO, won't be around very long. Getting one's feathers ruffled over it is nihilistic and distracts from other, deeper rivalries between F/OSS and Microsoft and Google's models.