Doesn't flash slow down everyone's connection? That's why I hate it as a video player, as opposed to quicktime. Navigating away from a youtube, vimeo, or gametrailers page with a flash player takes about 10-12 seconds. Navigating away from a quicktime video takes perhaps 0.25 seconds.
However, if you asked how many XBox360's have been returned to Microsoft, it would be in the range of 60+% manufactured.
Why so high? For a long time, Microsoft repaired the old units (it's just defective solder, right?) and shipped them back out to people. And then they failed again.
Ultimately it's cheaper to ship units back and forth a few times than it is to fully replace the hardware. They probably gained more in reduced manufacturing cost than they lost on shipping.
Microsoft got it to the point that they make a slight profit on the hardware - but can you imagine how much they lose on shipping and repair costs? Billions! Way more than Sony ever lost on the initial hardware.
I disagree about the Genesis. I remember playing Gunstar Heroes on that, and nothing SNES came close to that at the time.
But the SNES had all the great RPGs, so it's definitely my favourite. But anyone claiming that the Genesis was weak is just comparing bad ports, rather than the games that made it great.
Re: N64
The N64 had something ludicrous like 4KiB of GPU memory, of which you could only use half for textures, or something crazy like that. It had insanely high bandwidth RAM, and a very fast CPU. Because of that, impressive games like Blast Corps were released - gaudy textures, but loads of fun and destructible objects. I liked my N64 more than my PS1, but I did have both.;)
The cartridge thing was actually liked by some developers. Yes, it added cost, but it also made it harder to pirate, and the access times and transfer speeds were very good. This allowed complex levels, as seen in Donkey Kong 64, Blast Corps, and other games. In effect, the N64 had 64MB of "slow RAM", so as long as you could make do with less space, you could still do something innovative.
Not everyone has an eSATA connection. A USB 3.0 drive can be used slower on a USB 2.0 port.
I figure, plop one of those dual-head WD multi-TB drives in there and you'll easily hit 120MB/sec read/write for large files like game patches or maps.
I prefer LXDE to all the other window managers. Gnome is okay, aside from being a bit unstable and slow, and KDE's double-high taskbar just doesn't sit right with me. XFCE feels primitive for some reason, and is still pretty bogged down compared to LXDE. Fluxbox is just weird - I've gotten too used to having a desktop, and fully featured taskbar.
The menubar is one of the reasons I still use Windows rather than OSX. I like having all my options laid out and easily findable. The ribbon may be an improvement for some, but I would say at the worst it should be the default option in the installer, which can be turned off with a single click.
I always view the Control panel in classic mode. Why? Non-classic mode doesn't display all the options - just a few common tasks. Classic mode is essential if you actually need to configure something, and can't remember the filename.cpl for a direct run command. One other advantage of classic mode is you can find the control panel applets that other programs place there. (Quicktime, your sound drivers, your RAID drivers, etc.)
The ribbon does have some valid reasons for existing. Beginner/Advanced/Expert interfaces for programs are quite common. It just shouldn't be mandatory.
Can you defend this claim? Because based on my experiences *using* CSS over the last 7 years, there hasn't been a time when any version of IE could even claim they weren't maddeningly, brokenly worse.
IE properly requires the tbody element when adding DOM tables to a document!:P
They, like the US, have detection systems in place for nukes. They will have warning that something is coming. Just not enough warning to do anything about it, which is where this retaliatory doomsday machine comes in.
When a high up military officer gets woken up and told that a missile is about to hit in 6 minutes, it doesn't give much time to wake up and think. This helps ensure they don't make the wrong decision, because if they are too cautious, someone else can "correct" it later.
But he also caused damages, which necessitated the security cameras.
What's happening here is, some guy comes into your garage and sits on your old couch and drinks beer, and your girlfriend finds it totally creepy that he's down there all the time, but he leaves afterwards.
2) The thing is, Java can be debugged/developed on a Windows box and deployed on a Linux box, without any further testing.
I mean, you'd be nuts to actually do it without testing, but if your coders are smart and multi-OS aware there won't be any problems.
I myself wrote a calendar app for personal use, on Windows 2000. One day I tried it on Ubuntu, and everything worked fine - although it looked like shit because Gnome skinning didn't work. Not the same category as a business app, but it didn't even need a recompile. When you can write something java in 2002, and it runs flawlessly on a 2009 OS that didn't exist when it was created, without a recompile... you have to factor that in as a feature.
3) Python?:P
Java's VM is impressive. When flipping from C-based to JVM-based, Python gets about a 2-5x speedup. At this point, Java is "the wheel", for a lot of non-business apps. Re-inventing the wheel in other languages is pointless - just build on top of it.
4) I agree with you here. Although Java encourages readable syntax, it's certainly not the best language available for it.
5) Java running in Server mode is effectively compiled. That's why it starts so slow. Java running in Desktop mode is quasi-compiled. Quasi-compiled works okay, because the Java interpreter is very fast, and it lets Java apps start quicker than C# apps.
6) Python and C/C++ are more popular for front-end apps - probably because there are more front-end apps than back-end apps. Java is extremely popular for DB stuff that connects with webservers. There seems to be a lot of government, banking, and business sites running on Apache Tomcat - but because of the nature of the JVM, each site is running its own unique applications.
public class Record { public byte[][] Names = new byte[2][15]; public byte[] Address = new byte[40]; }
But java encourages self-explanatory methods attached to a struct/class.
public byte[] getFirstName() { return Names[0]; } public byte[] getLastName() { return Names[1]; } public byte[] getAddress() { return Address; }
But, truth be told... byte[] are rather primitive. Java encourages String use, so you'd never see this unless you designed it this way for a reason. I'm also inclined to believe that easier higher level code leads to less limitations on what software can do. Why limit to a first and last name? Why only 40 byte addresses? Why not add some setter methods that do length/validity checks, and then let the record store longer addresses, middle names, etc.? Anything nulled out(not used) is just handled as a null pointer/reference in java, so allowing up to say 5 names would only cost a max of 12 bytes per record - unless those names actually get added.
Doing a straight port from Cobol to Java would be pointless. When doing something like this, the shortfalls of the old software have to be examined, and corrected. You lose on performance and memory usage, so you had better gain on scalability, features, and perhaps ease of use.
But the notion of seeing men sexually has always been fascinating to me because I stretch my mind and still cannot see it.
It was a couple years ago that I had a similar realization. I remember I was watching a TV show and a guy took his shirt off. Big pec muscles, like all shirtless actors, and I didn't think a thing about it. But a nearby woman in the show seemed to be distracted by it. The scene took a minute or two to go by, so I took note.
Later that year in the summer I noted lots of people running around without shirts on. Most were older people with huge beer guts, mowing the lawn and stuff. Some were scrawny teens, and others muscular teens. Didn't feel a thing for any of them, but I can't help but wonder what a woman feels - in particular, women of different age groups. I can't imagine anyone being attracted to the beer gut guys, but the teens didn't look bad.
Does looking at a chest (muscles or not) really push thoughts from a woman's head? I know I'd be very distracted if I came around a corner and all these topless women were standing there. Is it the same in reverse, or is it just on TV?
Javascript used to have a really nice scoping mechanism, called eval(); It was blazing fast too, in every browser. The basic idea was when you create an object, you tell it its name.
var myPlayer = new Player('myPlayer');
Then it uses eval to generate methods that point to itself. This was necessary because all callbacks are global in Javascript. Unfortunately, FF3 disabled this fine use of eval, so now, you have to do weird scoping shit that slows it down.
I like how lax Javascript is. A variable can be both an integer, float, and a string depending on how you use it. It's the same thing that attracted me to asm - where an int can be a value, a pointer, or part of an object like a String. And what's really neat, is you decide how you handle it by opcode. There's none of that typecasting shit.:P
Slashdot Mirror
You can tinker with software without having access to the source. Game modders are a fine example...
Highly customizable software like Apache is software that most people won't ever compile themselves.
Doesn't flash slow down everyone's connection? That's why I hate it as a video player, as opposed to quicktime. Navigating away from a youtube, vimeo, or gametrailers page with a flash player takes about 10-12 seconds. Navigating away from a quicktime video takes perhaps 0.25 seconds.
50% and 33% are false statistics.
However, if you asked how many XBox360's have been returned to Microsoft, it would be in the range of 60+% manufactured.
Why so high? For a long time, Microsoft repaired the old units (it's just defective solder, right?) and shipped them back out to people. And then they failed again.
Ultimately it's cheaper to ship units back and forth a few times than it is to fully replace the hardware. They probably gained more in reduced manufacturing cost than they lost on shipping.
Microsoft got it to the point that they make a slight profit on the hardware - but can you imagine how much they lose on shipping and repair costs? Billions! Way more than Sony ever lost on the initial hardware.
I disagree about the Genesis. I remember playing Gunstar Heroes on that, and nothing SNES came close to that at the time.
But the SNES had all the great RPGs, so it's definitely my favourite. But anyone claiming that the Genesis was weak is just comparing bad ports, rather than the games that made it great.
Re: N64
The N64 had something ludicrous like 4KiB of GPU memory, of which you could only use half for textures, or something crazy like that. It had insanely high bandwidth RAM, and a very fast CPU. Because of that, impressive games like Blast Corps were released - gaudy textures, but loads of fun and destructible objects. I liked my N64 more than my PS1, but I did have both. ;)
The cartridge thing was actually liked by some developers. Yes, it added cost, but it also made it harder to pirate, and the access times and transfer speeds were very good. This allowed complex levels, as seen in Donkey Kong 64, Blast Corps, and other games. In effect, the N64 had 64MB of "slow RAM", so as long as you could make do with less space, you could still do something innovative.
Fullspeed runs 12mbit. LowSpeed(Mouse, keyboard, etc.) runs 1.5mbit. HiSpeed runs 480mbit. SuperSpeed runs 5.0gbit.
You joke about ExtremeSpeed, but it's actually possible USB 4.0 will be called that.
Not everyone has an eSATA connection. A USB 3.0 drive can be used slower on a USB 2.0 port.
I figure, plop one of those dual-head WD multi-TB drives in there and you'll easily hit 120MB/sec read/write for large files like game patches or maps.
they will be able to toggle between the old and new interface by holding the Alt key.
I think I speak for everyone when I say... WTF?
Proper implementation:
1) Installer, radio buttons -> Ribbon or Classic UI
2) Options menu -> Ribbon or Classic UI
I prefer LXDE to all the other window managers. Gnome is okay, aside from being a bit unstable and slow, and KDE's double-high taskbar just doesn't sit right with me. XFCE feels primitive for some reason, and is still pretty bogged down compared to LXDE. Fluxbox is just weird - I've gotten too used to having a desktop, and fully featured taskbar.
The menubar is one of the reasons I still use Windows rather than OSX. I like having all my options laid out and easily findable. The ribbon may be an improvement for some, but I would say at the worst it should be the default option in the installer, which can be turned off with a single click.
I always view the Control panel in classic mode. Why? Non-classic mode doesn't display all the options - just a few common tasks. Classic mode is essential if you actually need to configure something, and can't remember the filename.cpl for a direct run command. One other advantage of classic mode is you can find the control panel applets that other programs place there. (Quicktime, your sound drivers, your RAID drivers, etc.)
The ribbon does have some valid reasons for existing. Beginner/Advanced/Expert interfaces for programs are quite common. It just shouldn't be mandatory.
Firefox doesn't need an Office Ribbon. It needs a way to open tabs and windows that you just closed by accident!
Lots of cores, but very little memory. For stuff like climate simulations, the 960GB is going to help more.
Can you defend this claim? Because based on my experiences *using* CSS over the last 7 years, there hasn't been a time when any version of IE could even claim they weren't maddeningly, brokenly worse.
IE properly requires the tbody element when adding DOM tables to a document! :P
Right, but what can you list for Microsoft that was created solely by Microsoft?
They, like the US, have detection systems in place for nukes. They will have warning that something is coming. Just not enough warning to do anything about it, which is where this retaliatory doomsday machine comes in.
When a high up military officer gets woken up and told that a missile is about to hit in 6 minutes, it doesn't give much time to wake up and think. This helps ensure they don't make the wrong decision, because if they are too cautious, someone else can "correct" it later.
But he also caused damages, which necessitated the security cameras.
What's happening here is, some guy comes into your garage and sits on your old couch and drinks beer, and your girlfriend finds it totally creepy that he's down there all the time, but he leaves afterwards.
B&E, yes - but please point me to the damages?
Starting wage is over $17/hr at a nearby Costco. (I'm in BC, Canada)
Apparently it goes up quite quickly beyond that. Certainly makes Walmart's starting wages look horrible!
2) The thing is, Java can be debugged/developed on a Windows box and deployed on a Linux box, without any further testing.
I mean, you'd be nuts to actually do it without testing, but if your coders are smart and multi-OS aware there won't be any problems.
I myself wrote a calendar app for personal use, on Windows 2000. One day I tried it on Ubuntu, and everything worked fine - although it looked like shit because Gnome skinning didn't work. Not the same category as a business app, but it didn't even need a recompile. When you can write something java in 2002, and it runs flawlessly on a 2009 OS that didn't exist when it was created, without a recompile... you have to factor that in as a feature.
3) Python? :P
Java's VM is impressive. When flipping from C-based to JVM-based, Python gets about a 2-5x speedup. At this point, Java is "the wheel", for a lot of non-business apps. Re-inventing the wheel in other languages is pointless - just build on top of it.
4) I agree with you here. Although Java encourages readable syntax, it's certainly not the best language available for it.
5) Java running in Server mode is effectively compiled. That's why it starts so slow. Java running in Desktop mode is quasi-compiled. Quasi-compiled works okay, because the Java interpreter is very fast, and it lets Java apps start quicker than C# apps.
6) Python and C/C++ are more popular for front-end apps - probably because there are more front-end apps than back-end apps. Java is extremely popular for DB stuff that connects with webservers. There seems to be a lot of government, banking, and business sites running on Apache Tomcat - but because of the nature of the JVM, each site is running its own unique applications.
Java:
public class Record
{
public byte[][] Names = new byte[2][15];
public byte[] Address = new byte[40];
}
But java encourages self-explanatory methods attached to a struct/class.
public byte[] getFirstName() { return Names[0]; }
public byte[] getLastName() { return Names[1]; }
public byte[] getAddress() { return Address; }
But, truth be told... byte[] are rather primitive. Java encourages String use, so you'd never see this unless you designed it this way for a reason. I'm also inclined to believe that easier higher level code leads to less limitations on what software can do. Why limit to a first and last name? Why only 40 byte addresses? Why not add some setter methods that do length/validity checks, and then let the record store longer addresses, middle names, etc.? Anything nulled out(not used) is just handled as a null pointer/reference in java, so allowing up to say 5 names would only cost a max of 12 bytes per record - unless those names actually get added.
Doing a straight port from Cobol to Java would be pointless. When doing something like this, the shortfalls of the old software have to be examined, and corrected. You lose on performance and memory usage, so you had better gain on scalability, features, and perhaps ease of use.
It's a safe bet that that's only a few hours after they found out, and 3 days after the first student did.
But the notion of seeing men sexually has always been fascinating to me because I stretch my mind and still cannot see it.
It was a couple years ago that I had a similar realization. I remember I was watching a TV show and a guy took his shirt off. Big pec muscles, like all shirtless actors, and I didn't think a thing about it. But a nearby woman in the show seemed to be distracted by it. The scene took a minute or two to go by, so I took note.
Later that year in the summer I noted lots of people running around without shirts on. Most were older people with huge beer guts, mowing the lawn and stuff. Some were scrawny teens, and others muscular teens. Didn't feel a thing for any of them, but I can't help but wonder what a woman feels - in particular, women of different age groups. I can't imagine anyone being attracted to the beer gut guys, but the teens didn't look bad.
Does looking at a chest (muscles or not) really push thoughts from a woman's head? I know I'd be very distracted if I came around a corner and all these topless women were standing there. Is it the same in reverse, or is it just on TV?
Reminds me of Turbo Cache. Who else remembers those slow as dirt GF6200's?
Sure. Just stick it on an Aptera and you're half-way there. Just missing the flying bit.
Javascript used to have a really nice scoping mechanism, called eval(); It was blazing fast too, in every browser. The basic idea was when you create an object, you tell it its name.
var myPlayer = new Player('myPlayer');
Then it uses eval to generate methods that point to itself. This was necessary because all callbacks are global in Javascript. Unfortunately, FF3 disabled this fine use of eval, so now, you have to do weird scoping shit that slows it down.
I like how lax Javascript is. A variable can be both an integer, float, and a string depending on how you use it. It's the same thing that attracted me to asm - where an int can be a value, a pointer, or part of an object like a String. And what's really neat, is you decide how you handle it by opcode. There's none of that typecasting shit. :P
And the Pandora has been measured at under half that. ;)
http://www.gp32x.com/board/index.php?/topic/49385-current-drains-by-speed-and-device/page__p__751966&#entry751966
Here was an idling kernel with various backlight settings:
100% - 507mA
88% - 484mA
70% - 456mA
53% - 424mA
35% - 390mA
18% - 364mA
0% - 337mA
They use a separate chip which is accurate to single digit mA. At 3.6v, 500mA is 1.8 watts?