I hate it when museums do this kind of thing to aircraft (or in this case spacecraft). Nothing is more uninteresting than a hollow shell body. Once the problematic liquids are drained there is no reason they can't leave the engines in place. The parts that make things like this interesting are all the mechanical components and displays that make up the actual vehicle. Every time I see this done to an aircraft, I can't help but think of how much of an utterly boring display it makes. They might as well erect a cardboard cutout equivalent, it's nauseating.
I think it's pretty common, and not just with test logic like scan chains. I've worked on numerous ICs where some later project wants to reuse a part of the design, without necessarily using everything. If time and budget allow the unused bits get removed and a smaller design results, but more often the unused logic is tied off (at the board level or via metal mask - board level being cheapest and metal mask being cheaper than cutting a new set of diffusion masks for a potentially small runner) and the same die and package are reused (this may allow test fixture reuse also).
I've seen some pretty egregious cases of this however. I recall opening up a 4-port USB hub once (the cheap $10 ones) only to find a gigantic controller chip on it (something like 80 pins) of which about 10 pins were connected. It was obvious the chip didn't start life as a USB controller, but apparently it was cheap enough to throw down as-is. I always wondered what else was on the chip, perhaps part of something that normally has an embedded USB hub (monitor or keyboard maybe).
IMO, look and feel is hardly the biggest failing of the GNOME system. There are more fundamental problems with their user philosophy. Years ago when a new set of workstations were deployed where I work everyone had the option of running either GNOME 2 or KDE 3. Officially the admins only wanted to support GNOME, but within a short time everyone in our location was on KDE 3.
Why? Well it turns out the admins never really did a thorough test of our tool flow on GNOME. We use a lot of expensive tools that come from legacy Unix backgrounds (they aren't recent GTK devel), so it turns out we had major problems with things like focus stealing. This would be where the app would pop up a messagebox and GNOME would happily yank you from whatever desktop you were working on to wherever the messagebox was. At the time there were no options in GNOME to handle this kind of thing, whereas KDE had a number of focus stealing controls.
Then there was the issue of resizing windows. At the time GNOME had one method of resizing windows, and that was to continually redraw the content in it - no wireframe or outline methods, only continuous redraw. That's great and all if your most complex app is a web browser, but when you got an app showing a couple gigs of visual data and every window resize event triggers a redraw, it quickly locks up the machine.
And then there was the question of the right-click menu. WTF was with this menu. It was loaded with a bunch of useless options for creating folders and crap. It was like someone who had never used a Unix machine before just decided to shoehorn in some crap there so the menu did something. KDE at least allowed the menu to be customized into something useful.
This is all regarding GNOME 2 at the time, but it gets to the core of what I perceive as GNOMEs problem - and as I understand it, this is both widely understood, and truly a development target of GNOME (and I fully expect GNOME 3 to be no different) - and that is that the GUI is not designed to be flexible or changeable, it is designed to be rigid and idiotproof. They are providing a fixed GUI interface for the lowest common denominator of user, and anyone who wants something different can STFU.
This is of course further compounded by their method of burying the GUI settings in a hundred different files across a dozen hidden directories, perhaps wrapping it in some obscure XML pseudo-code, so nobody can figure out WTF the options really are or what they do (perhaps it's some kind of subtle method of eliminating those annoying hacker types who might undo their GUI "vision"). KDE is no better in this regard. I remember when at least one GUI I used to use kept its menus in plain text format that was easily understood and modifiable, what the heck ever happened to that concept?
I'm sure if I were to relate to a GNOME dev the problems I had with focus stealing, he would turn around and tell me the problem was with my app, not the GUI. And if I were to relate how I like to launch programs from the right-click menu I would be told I'm doing it wrong and I should learn how to do it the "right" or "better" way. And thus I become yet another alienated user who has moved on to something else. Radically changing an interface and then pushing it as a rigid right-and-only way is going to piss off a lot of people. Lots of people left KDE when they did it, and the same will happen to GNOME.
Overall terrible news IMO. I wish they wouldn't have focused on the electric aspect so much. Same body design, but with a normal internal combustion engine and a decent price, and I probably would have gotten one as a commuter vehicle (very similar concept to say a T-rex motorcycle, but without the high price). I think there is definitely a market for vehicles like this, lightweight like motorcycles, but enclosed (not always exposed to the environment like on a bike).
I can't believe no one has suggested one of the many MAME interface boards. Arcade enthusiasts have a myriad of inexpensive interfaces for connecting custom controls to a computer. They are cheap and easy to use: http://www.ultimarc.com/ (follow U-HID links, or the I-PAC, Opti-PAC, etc links) http://groovygamegear.com/ (follow the controls interfaces link)
Buttons, spinners, joysticks (optical, microswitch, etc), and analog controls - there is almost certainly an off the shelf interface for any kind of basic control like that. Beyond that a microcontroller kit (arduino or other) could fill in anything more exotic. I'm going a similar route to this for a custom CNC control panel I'm building, fun stuff.
Free subscribers to the game will be able to play, but will not get the same benefits as paying subscribers still get.
Most importantly, non-paying customers only get red shirts and generic names. They also have to be one of the first people to beam down to the planet, and the only sound they can make is the Wilhelm scream.
Indeed. I heard an interesting argument a week or so ago, where one businessman said that one of the problems with banks in the US is that the government insures all deposits (up to a limit). On it's face it sounded possibly terrifying, can you imagine giving your cash to a banker with no gov't insurance. However since the gov't backs the holdings the banks do not need to operate in a low risk manner with that money, since they know regardless they will get bailed out. It made for an interesting thought, in that if the gov't did not insure any of the holdings you can be sure people would only put their money in a bank with an absolutely solid reputation and no tolerance for risk.
There was a similar argument I heard a few years ago regarding insurance companies, in that they also have large holdings which they were investing in ever more risky ventures. The fact that the gov't backs up all deposits implicitly indicates their distrust in the banking system (after all, if it were trustworthy, why would it need backing), but yet they do things like repeal Glass–Steagall which encourages ever more risky behavior. There is a lot the gov't could do to rein in bad bank and investment behaviors. After all if things like derivatives are indeed equivalent to financial mass destruction tools, why not ban them outright. Just because things can be done, doesn't mean they should be allowed.
I saw that in one of their videos and couldn't figure out if the wall of unconnected bricks was just storage for them to be used properly later on, or if they were really intending that to be a structural wall. It was so wrong on so many levels. It was unreinforced, it had no running bond or tie pattern in it, there was little to no "mortar" between the bricks, it didn't even look like they had been dried properly. Even with a proper tie pattern and bricks, from what I've read unreinforced masonry is a lousy construction method anywhere that might have an earthquake risk.
the start menu is an easier way of locating programs than anything else that MS has provided. The only reason I can think of for people not using it is that they already have the 3 programs they use pinned to the task bar.
Seriously, this is another example of GUI design based on the average idiot user. Misguided and idiotic GUI redesigns serve no purpose but to annoy the userbase (ex. KDE4 and GNOME3). I find that I use the Start menu far less often because I've moved the apps I use to the PA menu. It's my way of doing what MS should have done a long time ago - separation and modularization of the apps from the OS (no install, no registry crap, etc). Seriously all this GUI rework and MS has yet to implement truly useful and fundamental changes to the OS. They still by default cram all the OS, apps, and data into a single place on a single drive (seriously 'My Documents', 'My Music', etc.. argh, does anyone actually use this idiotic and stupidly placed directory structure for managing their data?) Tying all that together insures when an OS gets corrupted/infected/whatever a reinstall will become a painful and long process.
But no, instead of something useful like eliminating the registry, they spend their time unnecessarily reinventing the GUI. Perhaps at least they will finally discover multiple desktops. Of course just looking at the tile-based monstrosity I can just imagine how they will play the hide-the-system-settings game. Instead of something useful I'm guessing they will play the usual game of shuffling the settings and burying them several layers deep (you know as far as possible from the user).
Lawyers will make sure laws are enacted to protect their jobs.
Then the robot lawyers will move in and enact laws to protect the robot jobs. And just wait until the robot unions get involved, those parasites - but of course where there are unions, soon there is the mafia - thats right, the robot mafia. Where does it all end - let me tell you, it's not pretty. Soon we will be paying our tax dollars to support the robot welfare state, while those deadbeats leech off government at our expense. The epi-center of this disastrous robot future world - Detroit naturally. But there is hope, a man who can save us from the robot tyranny, I think his name is Neo...
You can't produce quality code at 80hr a week in a sustainable way. The only type of code that can be produce at that constant rhythm with a reasonable level of quality, would be the kind of code best left to a generator.
I heard a phrase a long time ago along these lines - If you are working 80hr/wk for a certain wage, it is the same as working two 40hr/wk jobs for half as much each. How many people would trade their 80hr/wk job for two 40hr/wk jobs at half pay? Perhaps some, who are highly motivated by the money or who really like their job, but for many when it is put in that context the drudgery of two jobs versus one becomes more apparent, and they would not make such a trade (of course, not all people have the flexibility for that in these times though, it could be 80hr/wk versus 0hr/wk).
It's not just pure drudgery of work though - people should not be motivated to do such levels of work unless reward is clearly tied to, and scales with, effort. I could relate many stories of management flushing everyone's hard work down the tubes by canceling projects on the verge of production, but perhaps one has to live it to believe it, so I'll refrain. On the flip side I have been in situations where such work has paid off and quite well. Overall though if there is no clear connection between extra work and extra reward then there is no such connection, and people are just burning their life away for a corporation which will never recognize or acknowledge their effort.
I already probably do half to two thirds of my browsing, email, and related tasks on my smartphone these days. An awful lot of what we do with computers is arguably trivial stuff that doesn't need screen real estate or big computing power.
For basic content viewing, and simple web browsing small touchscreens work ok. However for anything requiring more precision than the finger sized blob a touchscreen sees, they absolutely blow. I can barely stand editing a couple sentences on a smartphone, and I can't imagine using it to do the things you would do on a regular computer. Try writing a thesis on a smartphone, or here's one - does anyone code android apps using only an android touchscreen device? That would be agony. At minimum I think one would want some kind of dock with an actual keyboard/mouse to do any kind of real work on such a device. Even then you would also want to plug into additional storage. Perhaps someone will make a killing with a low cost docking station.
While still a great game I can't help but feel that the multiplatform release is holding it back from being a really great PC game for the ages.
I was hoping someone would expand on this. When the second game came out with "universal ammo", crap level design, and overall short game length, they managed to kill many of the things that made the PC original great. All done presumably to make it more accessible on consoles. My main concern on this one is what kind of tradeoffs, if any, were made in that context.
I have used Linux since 1994, and worked exclusively with Unix-like operating systems since approximately the same time. Also I have demonstrated knowledge and familiarity with systems that goes that far while you have absolutely nothing but your idiotic claims to back up this ridiculous assertion.
Well, I've been using Unix-like OSs since the late 80's, including Solaris, HPUX, and even Linux when it first entered the scene, so apparently I was right after all. Your "experience" doesn't count for shit apparently, obvious by the immensely stupid comments that keep coming out your mouth. Despite your assertions otherwise you don't have "extensive" knowledge about anything discussed in this thread, although the fact that you haven't used any of this "once over the last 20 years" is probably true, since you know nothing about it.
I am doing it to discredit you, to demonstrate to others how wrong you are, how your opinion is worthless, and your insults are pointless, and how everything you recommend is likely a bad idea.
And yet you have accomplished none of this, the virtualization works fine, it's efficiency is higher, and it works quite well. Everything I've said is based on actual tried and tested setups. Your assertions are based on nothing but your raging stupidity and have no basis in fact. Why the rage, who knows, perhaps Microsoft backed the car over your cat, I don't care or give a shit. All you have accomplished in this thread is to demonstrate your complete ignorance on the subject, you've discredited yourself, you made yourself look like a complete raving fool, you imagined a bunch of bullshit regarding an imaginary XP install, you've established how biased and worthless your comments are, and you've proven that over 20 years you learned absolutely nothing. Congratulations, you are truly an idiot.
However there is a solution for this for me. I can mark you a foe, and all your utterly worthless comments will be modded to -5, an appropriate level for the inane comments you spew out, and I won't have to be bothered reading your vile worthless vitriol ever again.
Yes, and it works quite well. And if you think that's amazing you'll be quite shocked when you find out how a great many websites work - here's a hint: they aren't all running individually on their own separate machines. I'm guessing if you ever find out how cloud computing works your head would explode.
You have claimed that you run Windows XP in VM, and use Windows 7 as a host.
I said no such thing, all my virtual guests are running Linux. I don't run XP at all. This is just more imaginary crap made up in your tiny idiot mind.
I can assure you, you have not.
I can assure you, I have.
Look ma, I copy pretend-IP-packets in pretend-Ethernet-frames back and forth in memory every time I am trying to access a file
Right from the mind of a 4yr old. Don't worry, you've fully demonstrated your complete ignorance of both virtualization as it's used all around these days and the specific Virtualbox software described in the thread. Go back to your anti-Microsoft raging bullshit, I'm done arguing with your idiocy.
In the mind of Microsoft marketdroid everything that threatens Windows dominance gives people a bad name.
Wow, it's like a Microsoft powered troll - you mention the word and you go off for hours on end. You should invent some kind of powerplant powered by your idiocy and anti-Microsoft fanaticism, you could probably do something useful with it. Seriously, you make Apple fanbois look good in comparison.
How did it happen that you NEEDED three physical machines in the first place? Oh, right, to run your beloved Windows, and not just one but two versions at once!
Pretty simple really, a Linux file server, a Linux work machine, and a Windows home machine. Oh that's right, like a dumbass you assumed there were multiple Win boxes. I've probably been using Linux longer than you have, certainly long enough to know that each of the OS's have their place. Maybe one day if you get over yourself you will learn that.
Linux does not need standardized hardware, leave alone crippled shit that VMWare provides.
Yeah, here is another clue - Virtualbox is from Sun not VMWare, but again you demonstrate your lack of intelligence. Perhaps you should do some research into virtualization, you don't seem to know much about it. And for the record, from a cold start the Virtualbox machine will boot faster than the physical hardware due primarily to a lack of BIOS wait screens and such. Since you are unaware of this it's quite apparent you haven't tried running it before.
Now go ahead and spew some more anti-Mircosoft BS, you know you can't help yourself.
Hah, what a troll. Here is a clue retard - get over your zealot fanaticism, your giving Linux users a bad name.
My method has consolidated three physical machines into one, yielding an actual power savings. It makes management easier, and has multiple nice side effects, including standardized hardware from the viewpoint of the Linux installs. If the setup could have worked in a reversed configuration (Win on Linux) I would have run it that way, but graphics performance goes to shit that way, so it didn't happen. So no, you are both wrong and a fucking retard because it is not "the only possible purpose of such setup".
Not exactly the parent's point, but in a similar way I've virtualized all my Linux machines on virtualbox running on Win7. Win7 can handle the games, and virtualbox supports graphic acceleration so even compiz and such work on the Linux machines. No more screwing around with VNC or NX or whatnot. It also yields somewhat faster boot times - no BIOS or peripheral card wait screens at startup.
There are side benefits - encryption is easier, just Truecrypt the Win7 system and data drives. No need to maintain dmcrypt setups or such on the Linux installs as the host is already encrypted. Further, partitioning the Linux setups into separate system/data virtual drives and maintaining decent backups makes a botched upgrade trivial to recover from. This has saved me a couple times recently when the ext4 system drive blew out on one of the Linux installs - just dropped a backup vdi in its place and was back and running in a few minutes. Similar thing just the other day, did an upgrade on one which swapped in a 3.0 kernel and killed the graphics, dropped in the system vdi from the previous days backup and was back and working. So much easier than having to swap in/out actual hard drives.
Overall backups are easier too - backup the encrypted Win7 data drive and in the process you end up backing up all the Linux machines. Can't complain about that. Only real penalty is you need a more powerful box (particularly as much memory as you can pack in the thing), but if it doubles as the game machine it's sort of a one stone, two birds thing.
I'm kind of curious why everyone is so up-in-arms wanting HL2:e3. HL2 was brilliant. HL2:e1 was a solid extension of that. HL2:e2 was a good game that started to feel a bit redundant. But neither of them reached the brilliance that was HL2.
People want EP3 because they want to know the rest of the story. These games are essentially interactive stories. You don't go to the movies and get up and walk out 2/3rds into it do you? It's not about how "brilliant" the game is, in the same way you don't generally judge a movie about how brilliant the middle of it is relative to the beginning and end.
The thing that irks me is the way they seem to delay working on the actual storyline and instead spend time upgrading the engine. Frankly I don't really care if the water or fog looks a little more realistic, I'm more interested in the content of the game (this is similar to the original Deus Ex, which had a lame graphic engine but fantastic storyline). I would have been fine with it had they developed the entire HL2 series using the original engine. Other titles seem to have no problem generating DLC material (Fallout3), so I really don't get why it takes Valve so long.
The government will shut these places down as soon as Apple calls them up and says "So, do you like us producing all of our products at Hon Hai?"
Unlikely, the gov't there is so corrupt and moves so slow it could never effectively shut all these operations. The real takeaway here is that Apple now gets to realize the true benefits of outsourcing all its manufacturing to China. Namely that they have little power to really control their inventory and supply chain.
Seriously, only in an environment where the gov't was complicit or completely corrupt and lazy could you have enough grey and black market goods to supply not only a single store, but an entire chain of retail stores.
It shouldn't matter if they spun it off, the Newton itself constitutes prior art. According to the timeline it was out in 1993. You can't patent something 3 years after it hits the market.
I hate it when museums do this kind of thing to aircraft (or in this case spacecraft). Nothing is more uninteresting than a hollow shell body. Once the problematic liquids are drained there is no reason they can't leave the engines in place. The parts that make things like this interesting are all the mechanical components and displays that make up the actual vehicle. Every time I see this done to an aircraft, I can't help but think of how much of an utterly boring display it makes. They might as well erect a cardboard cutout equivalent, it's nauseating.
I think it's pretty common, and not just with test logic like scan chains. I've worked on numerous ICs where some later project wants to reuse a part of the design, without necessarily using everything. If time and budget allow the unused bits get removed and a smaller design results, but more often the unused logic is tied off (at the board level or via metal mask - board level being cheapest and metal mask being cheaper than cutting a new set of diffusion masks for a potentially small runner) and the same die and package are reused (this may allow test fixture reuse also).
I've seen some pretty egregious cases of this however. I recall opening up a 4-port USB hub once (the cheap $10 ones) only to find a gigantic controller chip on it (something like 80 pins) of which about 10 pins were connected. It was obvious the chip didn't start life as a USB controller, but apparently it was cheap enough to throw down as-is. I always wondered what else was on the chip, perhaps part of something that normally has an embedded USB hub (monitor or keyboard maybe).
IMO, look and feel is hardly the biggest failing of the GNOME system. There are more fundamental problems with their user philosophy. Years ago when a new set of workstations were deployed where I work everyone had the option of running either GNOME 2 or KDE 3. Officially the admins only wanted to support GNOME, but within a short time everyone in our location was on KDE 3.
Why? Well it turns out the admins never really did a thorough test of our tool flow on GNOME. We use a lot of expensive tools that come from legacy Unix backgrounds (they aren't recent GTK devel), so it turns out we had major problems with things like focus stealing. This would be where the app would pop up a messagebox and GNOME would happily yank you from whatever desktop you were working on to wherever the messagebox was. At the time there were no options in GNOME to handle this kind of thing, whereas KDE had a number of focus stealing controls.
Then there was the issue of resizing windows. At the time GNOME had one method of resizing windows, and that was to continually redraw the content in it - no wireframe or outline methods, only continuous redraw. That's great and all if your most complex app is a web browser, but when you got an app showing a couple gigs of visual data and every window resize event triggers a redraw, it quickly locks up the machine.
And then there was the question of the right-click menu. WTF was with this menu. It was loaded with a bunch of useless options for creating folders and crap. It was like someone who had never used a Unix machine before just decided to shoehorn in some crap there so the menu did something. KDE at least allowed the menu to be customized into something useful.
This is all regarding GNOME 2 at the time, but it gets to the core of what I perceive as GNOMEs problem - and as I understand it, this is both widely understood, and truly a development target of GNOME (and I fully expect GNOME 3 to be no different) - and that is that the GUI is not designed to be flexible or changeable, it is designed to be rigid and idiotproof. They are providing a fixed GUI interface for the lowest common denominator of user, and anyone who wants something different can STFU.
This is of course further compounded by their method of burying the GUI settings in a hundred different files across a dozen hidden directories, perhaps wrapping it in some obscure XML pseudo-code, so nobody can figure out WTF the options really are or what they do (perhaps it's some kind of subtle method of eliminating those annoying hacker types who might undo their GUI "vision"). KDE is no better in this regard. I remember when at least one GUI I used to use kept its menus in plain text format that was easily understood and modifiable, what the heck ever happened to that concept?
I'm sure if I were to relate to a GNOME dev the problems I had with focus stealing, he would turn around and tell me the problem was with my app, not the GUI. And if I were to relate how I like to launch programs from the right-click menu I would be told I'm doing it wrong and I should learn how to do it the "right" or "better" way. And thus I become yet another alienated user who has moved on to something else. Radically changing an interface and then pushing it as a rigid right-and-only way is going to piss off a lot of people. Lots of people left KDE when they did it, and the same will happen to GNOME.
Overall terrible news IMO. I wish they wouldn't have focused on the electric aspect so much. Same body design, but with a normal internal combustion engine and a decent price, and I probably would have gotten one as a commuter vehicle (very similar concept to say a T-rex motorcycle, but without the high price). I think there is definitely a market for vehicles like this, lightweight like motorcycles, but enclosed (not always exposed to the environment like on a bike).
I can't believe no one has suggested one of the many MAME interface boards. Arcade enthusiasts have a myriad of inexpensive interfaces for connecting custom controls to a computer. They are cheap and easy to use:
http://www.ultimarc.com/ (follow U-HID links, or the I-PAC, Opti-PAC, etc links)
http://groovygamegear.com/ (follow the controls interfaces link)
Buttons, spinners, joysticks (optical, microswitch, etc), and analog controls - there is almost certainly an off the shelf interface for any kind of basic control like that. Beyond that a microcontroller kit (arduino or other) could fill in anything more exotic. I'm going a similar route to this for a custom CNC control panel I'm building, fun stuff.
Free subscribers to the game will be able to play, but will not get the same benefits as paying subscribers still get.
Most importantly, non-paying customers only get red shirts and generic names. They also have to be one of the first people to beam down to the planet, and the only sound they can make is the Wilhelm scream.
Indeed. I heard an interesting argument a week or so ago, where one businessman said that one of the problems with banks in the US is that the government insures all deposits (up to a limit). On it's face it sounded possibly terrifying, can you imagine giving your cash to a banker with no gov't insurance. However since the gov't backs the holdings the banks do not need to operate in a low risk manner with that money, since they know regardless they will get bailed out. It made for an interesting thought, in that if the gov't did not insure any of the holdings you can be sure people would only put their money in a bank with an absolutely solid reputation and no tolerance for risk.
There was a similar argument I heard a few years ago regarding insurance companies, in that they also have large holdings which they were investing in ever more risky ventures. The fact that the gov't backs up all deposits implicitly indicates their distrust in the banking system (after all, if it were trustworthy, why would it need backing), but yet they do things like repeal Glass–Steagall which encourages ever more risky behavior. There is a lot the gov't could do to rein in bad bank and investment behaviors. After all if things like derivatives are indeed equivalent to financial mass destruction tools, why not ban them outright. Just because things can be done, doesn't mean they should be allowed.
I saw that in one of their videos and couldn't figure out if the wall of unconnected bricks was just storage for them to be used properly later on, or if they were really intending that to be a structural wall. It was so wrong on so many levels. It was unreinforced, it had no running bond or tie pattern in it, there was little to no "mortar" between the bricks, it didn't even look like they had been dried properly. Even with a proper tie pattern and bricks, from what I've read unreinforced masonry is a lousy construction method anywhere that might have an earthquake risk.
If only Netcraft had confirmed it instead...
Well at least we can all agree BSD is dead.
the start menu is an easier way of locating programs than anything else that MS has provided. The only reason I can think of for people not using it is that they already have the 3 programs they use pinned to the task bar.
Seriously, this is another example of GUI design based on the average idiot user. Misguided and idiotic GUI redesigns serve no purpose but to annoy the userbase (ex. KDE4 and GNOME3). I find that I use the Start menu far less often because I've moved the apps I use to the PA menu. It's my way of doing what MS should have done a long time ago - separation and modularization of the apps from the OS (no install, no registry crap, etc). Seriously all this GUI rework and MS has yet to implement truly useful and fundamental changes to the OS. They still by default cram all the OS, apps, and data into a single place on a single drive (seriously 'My Documents', 'My Music', etc.. argh, does anyone actually use this idiotic and stupidly placed directory structure for managing their data?) Tying all that together insures when an OS gets corrupted/infected/whatever a reinstall will become a painful and long process.
But no, instead of something useful like eliminating the registry, they spend their time unnecessarily reinventing the GUI. Perhaps at least they will finally discover multiple desktops. Of course just looking at the tile-based monstrosity I can just imagine how they will play the hide-the-system-settings game. Instead of something useful I'm guessing they will play the usual game of shuffling the settings and burying them several layers deep (you know as far as possible from the user).
Lawyers will make sure laws are enacted to protect their jobs.
Then the robot lawyers will move in and enact laws to protect the robot jobs. And just wait until the robot unions get involved, those parasites - but of course where there are unions, soon there is the mafia - thats right, the robot mafia. Where does it all end - let me tell you, it's not pretty. Soon we will be paying our tax dollars to support the robot welfare state, while those deadbeats leech off government at our expense. The epi-center of this disastrous robot future world - Detroit naturally. But there is hope, a man who can save us from the robot tyranny, I think his name is Neo...
You can't produce quality code at 80hr a week in a sustainable way. The only type of code that can be produce at that constant rhythm with a reasonable level of quality, would be the kind of code best left to a generator.
I heard a phrase a long time ago along these lines - If you are working 80hr/wk for a certain wage, it is the same as working two 40hr/wk jobs for half as much each. How many people would trade their 80hr/wk job for two 40hr/wk jobs at half pay? Perhaps some, who are highly motivated by the money or who really like their job, but for many when it is put in that context the drudgery of two jobs versus one becomes more apparent, and they would not make such a trade (of course, not all people have the flexibility for that in these times though, it could be 80hr/wk versus 0hr/wk).
It's not just pure drudgery of work though - people should not be motivated to do such levels of work unless reward is clearly tied to, and scales with, effort. I could relate many stories of management flushing everyone's hard work down the tubes by canceling projects on the verge of production, but perhaps one has to live it to believe it, so I'll refrain. On the flip side I have been in situations where such work has paid off and quite well. Overall though if there is no clear connection between extra work and extra reward then there is no such connection, and people are just burning their life away for a corporation which will never recognize or acknowledge their effort.
I already probably do half to two thirds of my browsing, email, and related tasks on my smartphone these days. An awful lot of what we do with computers is arguably trivial stuff that doesn't need screen real estate or big computing power.
For basic content viewing, and simple web browsing small touchscreens work ok. However for anything requiring more precision than the finger sized blob a touchscreen sees, they absolutely blow. I can barely stand editing a couple sentences on a smartphone, and I can't imagine using it to do the things you would do on a regular computer. Try writing a thesis on a smartphone, or here's one - does anyone code android apps using only an android touchscreen device? That would be agony. At minimum I think one would want some kind of dock with an actual keyboard/mouse to do any kind of real work on such a device. Even then you would also want to plug into additional storage. Perhaps someone will make a killing with a low cost docking station.
While still a great game I can't help but feel that the multiplatform release is holding it back from being a really great PC game for the ages.
I was hoping someone would expand on this. When the second game came out with "universal ammo", crap level design, and overall short game length, they managed to kill many of the things that made the PC original great. All done presumably to make it more accessible on consoles. My main concern on this one is what kind of tradeoffs, if any, were made in that context.
I have used Linux since 1994, and worked exclusively with Unix-like operating systems since approximately the same time. Also I have demonstrated knowledge and familiarity with systems that goes that far while you have absolutely nothing but your idiotic claims to back up this ridiculous assertion.
Well, I've been using Unix-like OSs since the late 80's, including Solaris, HPUX, and even Linux when it first entered the scene, so apparently I was right after all. Your "experience" doesn't count for shit apparently, obvious by the immensely stupid comments that keep coming out your mouth. Despite your assertions otherwise you don't have "extensive" knowledge about anything discussed in this thread, although the fact that you haven't used any of this "once over the last 20 years" is probably true, since you know nothing about it.
I am doing it to discredit you, to demonstrate to others how wrong you are, how your opinion is worthless, and your insults are pointless, and how everything you recommend is likely a bad idea.
And yet you have accomplished none of this, the virtualization works fine, it's efficiency is higher, and it works quite well. Everything I've said is based on actual tried and tested setups. Your assertions are based on nothing but your raging stupidity and have no basis in fact. Why the rage, who knows, perhaps Microsoft backed the car over your cat, I don't care or give a shit. All you have accomplished in this thread is to demonstrate your complete ignorance on the subject, you've discredited yourself, you made yourself look like a complete raving fool, you imagined a bunch of bullshit regarding an imaginary XP install, you've established how biased and worthless your comments are, and you've proven that over 20 years you learned absolutely nothing. Congratulations, you are truly an idiot.
However there is a solution for this for me. I can mark you a foe, and all your utterly worthless comments will be modded to -5, an appropriate level for the inane comments you spew out, and I won't have to be bothered reading your vile worthless vitriol ever again.
You run a FILE SERVER IN A VM ON A CLIENT???
Yes, and it works quite well. And if you think that's amazing you'll be quite shocked when you find out how a great many websites work - here's a hint: they aren't all running individually on their own separate machines. I'm guessing if you ever find out how cloud computing works your head would explode.
You have claimed that you run Windows XP in VM, and use Windows 7 as a host.
I said no such thing, all my virtual guests are running Linux. I don't run XP at all. This is just more imaginary crap made up in your tiny idiot mind.
I can assure you, you have not.
I can assure you, I have.
Look ma, I copy pretend-IP-packets in pretend-Ethernet-frames back and forth in memory every time I am trying to access a file
Right from the mind of a 4yr old. Don't worry, you've fully demonstrated your complete ignorance of both virtualization as it's used all around these days and the specific Virtualbox software described in the thread. Go back to your anti-Microsoft raging bullshit, I'm done arguing with your idiocy.
Exactly. Hide the status bar, hide the full URL, hide the version number. Obscuring things is apparently their new development model.
In the mind of Microsoft marketdroid everything that threatens Windows dominance gives people a bad name.
Wow, it's like a Microsoft powered troll - you mention the word and you go off for hours on end. You should invent some kind of powerplant powered by your idiocy and anti-Microsoft fanaticism, you could probably do something useful with it. Seriously, you make Apple fanbois look good in comparison.
How did it happen that you NEEDED three physical machines in the first place? Oh, right, to run your beloved Windows, and not just one but two versions at once!
Pretty simple really, a Linux file server, a Linux work machine, and a Windows home machine. Oh that's right, like a dumbass you assumed there were multiple Win boxes. I've probably been using Linux longer than you have, certainly long enough to know that each of the OS's have their place. Maybe one day if you get over yourself you will learn that.
Linux does not need standardized hardware, leave alone crippled shit that VMWare provides.
Yeah, here is another clue - Virtualbox is from Sun not VMWare, but again you demonstrate your lack of intelligence. Perhaps you should do some research into virtualization, you don't seem to know much about it. And for the record, from a cold start the Virtualbox machine will boot faster than the physical hardware due primarily to a lack of BIOS wait screens and such. Since you are unaware of this it's quite apparent you haven't tried running it before.
Now go ahead and spew some more anti-Mircosoft BS, you know you can't help yourself.
Hah, what a troll. Here is a clue retard - get over your zealot fanaticism, your giving Linux users a bad name.
My method has consolidated three physical machines into one, yielding an actual power savings. It makes management easier, and has multiple nice side effects, including standardized hardware from the viewpoint of the Linux installs. If the setup could have worked in a reversed configuration (Win on Linux) I would have run it that way, but graphics performance goes to shit that way, so it didn't happen. So no, you are both wrong and a fucking retard because it is not "the only possible purpose of such setup".
Not exactly the parent's point, but in a similar way I've virtualized all my Linux machines on virtualbox running on Win7. Win7 can handle the games, and virtualbox supports graphic acceleration so even compiz and such work on the Linux machines. No more screwing around with VNC or NX or whatnot. It also yields somewhat faster boot times - no BIOS or peripheral card wait screens at startup.
There are side benefits - encryption is easier, just Truecrypt the Win7 system and data drives. No need to maintain dmcrypt setups or such on the Linux installs as the host is already encrypted. Further, partitioning the Linux setups into separate system/data virtual drives and maintaining decent backups makes a botched upgrade trivial to recover from. This has saved me a couple times recently when the ext4 system drive blew out on one of the Linux installs - just dropped a backup vdi in its place and was back and running in a few minutes. Similar thing just the other day, did an upgrade on one which swapped in a 3.0 kernel and killed the graphics, dropped in the system vdi from the previous days backup and was back and working. So much easier than having to swap in/out actual hard drives.
Overall backups are easier too - backup the encrypted Win7 data drive and in the process you end up backing up all the Linux machines. Can't complain about that. Only real penalty is you need a more powerful box (particularly as much memory as you can pack in the thing), but if it doubles as the game machine it's sort of a one stone, two birds thing.
I'm kind of curious why everyone is so up-in-arms wanting HL2:e3. HL2 was brilliant. HL2:e1 was a solid extension of that. HL2:e2 was a good game that started to feel a bit redundant. But neither of them reached the brilliance that was HL2.
People want EP3 because they want to know the rest of the story. These games are essentially interactive stories. You don't go to the movies and get up and walk out 2/3rds into it do you? It's not about how "brilliant" the game is, in the same way you don't generally judge a movie about how brilliant the middle of it is relative to the beginning and end.
The thing that irks me is the way they seem to delay working on the actual storyline and instead spend time upgrading the engine. Frankly I don't really care if the water or fog looks a little more realistic, I'm more interested in the content of the game (this is similar to the original Deus Ex, which had a lame graphic engine but fantastic storyline). I would have been fine with it had they developed the entire HL2 series using the original engine. Other titles seem to have no problem generating DLC material (Fallout3), so I really don't get why it takes Valve so long.
The government will shut these places down as soon as Apple calls them up and says "So, do you like us producing all of our products at Hon Hai?"
Unlikely, the gov't there is so corrupt and moves so slow it could never effectively shut all these operations. The real takeaway here is that Apple now gets to realize the true benefits of outsourcing all its manufacturing to China. Namely that they have little power to really control their inventory and supply chain.
Seriously, only in an environment where the gov't was complicit or completely corrupt and lazy could you have enough grey and black market goods to supply not only a single store, but an entire chain of retail stores.
No, you can't. Companies have at most one year from release to market. The prior art status could even predate the actual release to market as described here regarding the term "on-sale".
It's a good thing Apple didn't spin off Newton...
It shouldn't matter if they spun it off, the Newton itself constitutes prior art. According to the timeline it was out in 1993. You can't patent something 3 years after it hits the market.
Not trying to be an Apple shill, there are many things they do that I'm not particularly fond of, but Time Capsule is one thing they got right.
Ah, well get back to us in 18 months.