I honestly don't know how anyone can tolerate waiting more than a second or two before they start using a computer. I never shut my computers off (and reboot perhaps once or twice a year) because I always have tons of stuff open at any given time, when I walk away and come back I pick up right where I left off. It'd drive me absolutely insane if I had to recreate my desktop state every time I walked away.
It's a similar situation with laptops too. Most people I see do a full shutdown and power off every time they move their laptop, meaning it takes them several eternities to boot up again and reopen whatever it is they previously had open. I just suspend my laptop to RAM (no, not hibernate or suspend to disk, they're worthless junk) when I move it and then resume it later, which takes all of a second or two both ways and preserves all application state.
I understand that some people do prefer to shut off their computers with startling frequency for a variety of reasons (conserving power, busted ACPI implementation, etc), but doing that on Windows would be even worse, as it doesn't even offer an option to restore your state when you log back in, unlike competent DEs such as KDE which have done this for years (which isn't perfect, but is at least a thousand times better than nothing).
So really, I probably spend way less than 15-30 minutes waiting for computers to boot/resume per year (a rough estimate suggests that 15-30 seconds per year is probably closer). I can't even begin to imagine utterly wasting half an hour each day just waiting for a computer to start up.
Am I just a vim noob? After doing a search and loving the nice highlighting, is there a way to unhighlight the search term without doing a "/lkasjdfkjdfdf"? In less(1), you'd hit u but haven't found anything for vim.
Typing 'emerge moonlight' is your own arbitrary test for being cross-platform -- it doesn't really mean anything.
It may be an arbitrary test, but it's a very good one. If it's not present in the largest and most complete package repository for Linux, it's probably not relevant.
ZFS offers a lot of capabilities, from no need to worry about a LVM layer, to snapshotting, to excellent error detection, even encryption and compression hooks.
...and that's it's biggest problem. ZFS duplicates a lot of functionality that belongs outside of a filesystem. All of the above can already be done using any Linux filesystem, so why keep around a second copy of all that code that implements those features for just a single filesystem?
ReiserFS was (is) in a similar situation, where it also duplicates a lot of functionality that doesn't belong in the filesystem. Not only does this make it harder to maintain, but it makes a lot of features filesystem specific that shouldn't be.
As someone who's actually made a game (Game! - The Witty Online RPG) I'd say that balance is very tricky to maintain, probably even the hardest aspect of designing a game, but yet extremely central to having a fun and challenging game. You can plan out a scale of progression initially, but unless you plan out everything in advance (which is basically impossible), you'll still end up with things that are tricky to effectively balance later on.
You mentioned the idea of giving particular classes more abilities than others, and just by chance at least some of those will be overpowered, making the character overpowered. That's true, but you also have to consider the interaction between different abilities, and with more abilities, the number of combinations grows exponentially.
Starcraft is a great example of balance done correctly, and I think that's the main reason it's still popular today. Speaking of Starcraft, I doubt Blizzard anticipated that people would become so adept at microing just about everything (try watching a game between two good players these days!), and that changes the balance of the game a lot too.
RHEL 4 and CentOS 4 are 99.9% the same, there's no point in counting both. Plus, the number of people who use either on desktops are in the extreme minority, I would think, as they're not desktop oriented distros.
Interships are probably a good option. I did a CS degree with Co-op (four 4 month work terms integrated with regular classes, but the degree only takes 1 extra semester, as you don't get summers off), and I had no trouble at all finding a job after graduating (above entry level even, or at least well above entry level pay scale). For me, the already existing relevant job experience was pretty valuable.
Though, job experience isn't the end of the story, if you don't have job experience, you can still work on related stuff in your spare time. When I was applying for my one of my Co-op positions, I was able to show off Game! as something substantial that'd I'd already done, and that pretty much clinched the job offer. Game! wasn't something I created with the intention of putting on my resume, I just wanted to make a game, but it certainly turned out pretty well.
So, code something you like in your spare time. If there's nothing that interests you that you want to develop, perhaps a programming job isn't actually what you want to be doing.
Even though I've created a purely browser based online game (Game! - The Witty Online RPG), I'm on the fence on this matter.
On one hand, many people put a lot of real life time into earning said virtual property, and in many cases it clearly holds actual monetary value in the real world.
On the other hand, should I be liable if I accidentally delete a player's data in Game!? I don't think that's realistic, especially when you keep in mind that Game! is completely free of cost. So does that mean they really own the things they've earned, or no? I'm not sure.
Do I own this Slashdot comment? Slashdot says I do, and they don't claim any responsibility for it, but what happens if Slashdot deletes it on me? I've lost something I own, and there's nothing I can do about it. That doesn't seem right.
Ultimately, I think we'll see that virtual property is legally blessed to have real life monetary value, in much the same way that software is.
This doesn't surprise me. Anyone who wasn't already assuming that anything you sent via wireless was already in the hands of your enemies (unencrypted) is a bit naive.
The article also shows that among famous programmers, the ratio of males to females is much larger than among normal programmers.
Which is sad, because I just realized that I can't think of any famous female programmers off the top of my head. Of course, the regular ratio isn't terribly different...
Probably the most important thing you can keep in mind when writing new code is to think about the poor sap who has to maintain that code somewhere down the line. Especially because in a lot of cases, that poor sap will be you. Pretty much everything else follows naturally from there.
The issue has nothing to do with JavaScript so turning JavaScript off in your browser will not help you.
Ebay, for example, would be vulnerable to this since you could embed javascript into the web page, although, javascript is not required to exploit this.
In the meantime, the only fix is to disable browser scripting and plugins. We realize this doesnt give people much technical detail to go on, but its the best we can do right now.
So, the exploit has nothing to do with Javascript, but Javascript makes it easier, and the only way to protect yourself is to disable Javascript (and plugins). Wonderful!
I honestly don't know how anyone can tolerate waiting more than a second or two before they start using a computer. I never shut my computers off (and reboot perhaps once or twice a year) because I always have tons of stuff open at any given time, when I walk away and come back I pick up right where I left off. It'd drive me absolutely insane if I had to recreate my desktop state every time I walked away.
It's a similar situation with laptops too. Most people I see do a full shutdown and power off every time they move their laptop, meaning it takes them several eternities to boot up again and reopen whatever it is they previously had open. I just suspend my laptop to RAM (no, not hibernate or suspend to disk, they're worthless junk) when I move it and then resume it later, which takes all of a second or two both ways and preserves all application state.
I understand that some people do prefer to shut off their computers with startling frequency for a variety of reasons (conserving power, busted ACPI implementation, etc), but doing that on Windows would be even worse, as it doesn't even offer an option to restore your state when you log back in, unlike competent DEs such as KDE which have done this for years (which isn't perfect, but is at least a thousand times better than nothing).
So really, I probably spend way less than 15-30 minutes waiting for computers to boot/resume per year (a rough estimate suggests that 15-30 seconds per year is probably closer). I can't even begin to imagine utterly wasting half an hour each day just waiting for a computer to start up.
Much easier is to use :a! (or :i!), paste your text and then end the paste with a line containing just .
IE7's Javascript is painfully slow, it'd be an embarrassment if Sony couldn't do better than IE7.
Wake me up when they're on par with some useful browsers.
It may be an arbitrary test, but it's a very good one. If it's not present in the largest and most complete package repository for Linux, it's probably not relevant.
For every Windows user who's willing and able to switch, there are hundreds of others who can't, because it's impractical for them.
For many 'professional' users, the lack of an Outlook-ish program is probably a huge deterrent. :(
This is a silly complaint, mail clients don't belong in office suites. Use one of the bazillion mail clients out there if you want one.
It's in Gentoo; I have been compiling it for a few days...
There, fixed it for you
Actually, it took Portage less than 2 hours to compile OOo 3.0 for me, and that's on a 2 year old laptop.
You could always try sending a message to the gaming industry by playing Game! - The Witty Online RPG. It's DRM free and you don't need to pirate it.
...and that's it's biggest problem. ZFS duplicates a lot of functionality that belongs outside of a filesystem. All of the above can already be done using any Linux filesystem, so why keep around a second copy of all that code that implements those features for just a single filesystem?
ReiserFS was (is) in a similar situation, where it also duplicates a lot of functionality that doesn't belong in the filesystem. Not only does this make it harder to maintain, but it makes a lot of features filesystem specific that shouldn't be.
Actually, it's sunday.
No, Stardock started as an OS/2 game publisher in 1993, they didn't touch Windows until 1998. See: http://www.stardock.com/stardock/articles/article_sdos2.html
As someone who's actually made a game (Game! - The Witty Online RPG) I'd say that balance is very tricky to maintain, probably even the hardest aspect of designing a game, but yet extremely central to having a fun and challenging game. You can plan out a scale of progression initially, but unless you plan out everything in advance (which is basically impossible), you'll still end up with things that are tricky to effectively balance later on.
You mentioned the idea of giving particular classes more abilities than others, and just by chance at least some of those will be overpowered, making the character overpowered. That's true, but you also have to consider the interaction between different abilities, and with more abilities, the number of combinations grows exponentially.
Starcraft is a great example of balance done correctly, and I think that's the main reason it's still popular today. Speaking of Starcraft, I doubt Blizzard anticipated that people would become so adept at microing just about everything (try watching a game between two good players these days!), and that changes the balance of the game a lot too.
RHEL 4 and CentOS 4 are 99.9% the same, there's no point in counting both. Plus, the number of people who use either on desktops are in the extreme minority, I would think, as they're not desktop oriented distros.
Interships are probably a good option. I did a CS degree with Co-op (four 4 month work terms integrated with regular classes, but the degree only takes 1 extra semester, as you don't get summers off), and I had no trouble at all finding a job after graduating (above entry level even, or at least well above entry level pay scale). For me, the already existing relevant job experience was pretty valuable.
Though, job experience isn't the end of the story, if you don't have job experience, you can still work on related stuff in your spare time. When I was applying for my one of my Co-op positions, I was able to show off Game! as something substantial that'd I'd already done, and that pretty much clinched the job offer. Game! wasn't something I created with the intention of putting on my resume, I just wanted to make a game, but it certainly turned out pretty well.
So, code something you like in your spare time. If there's nothing that interests you that you want to develop, perhaps a programming job isn't actually what you want to be doing.
Even though I've created a purely browser based online game (Game! - The Witty Online RPG), I'm on the fence on this matter.
On one hand, many people put a lot of real life time into earning said virtual property, and in many cases it clearly holds actual monetary value in the real world.
On the other hand, should I be liable if I accidentally delete a player's data in Game!? I don't think that's realistic, especially when you keep in mind that Game! is completely free of cost. So does that mean they really own the things they've earned, or no? I'm not sure.
Do I own this Slashdot comment? Slashdot says I do, and they don't claim any responsibility for it, but what happens if Slashdot deletes it on me? I've lost something I own, and there's nothing I can do about it. That doesn't seem right.
Ultimately, I think we'll see that virtual property is legally blessed to have real life monetary value, in much the same way that software is.
This doesn't surprise me. Anyone who wasn't already assuming that anything you sent via wireless was already in the hands of your enemies (unencrypted) is a bit naive.
There IS no UID 666. You must be new here...
Actually, ACs internally are uid 666, they just don't display.
La-tech is actually the correct pronunciation of LaTeX, not lay-tex as most people probably assume initially.
That's true. I forgot because after being forced to program in Ada, I permanently purged Ada and anything Ada related from my memory.
Which is sad, because I just realized that I can't think of any famous female programmers off the top of my head. Of course, the regular ratio isn't terribly different...
A beowulf cluster of these!
And the first thing they do after connecting, is of course, load up Google! I'm sure none of this surprises anyone.
It's Microsoft, surely you knew you wouldn't be able to escape Clippy's wrath for long.
Probably the most important thing you can keep in mind when writing new code is to think about the poor sap who has to maintain that code somewhere down the line. Especially because in a lot of cases, that poor sap will be you. Pretty much everything else follows naturally from there.
But here's the best part (from the article):
So, the exploit has nothing to do with Javascript, but Javascript makes it easier, and the only way to protect yourself is to disable Javascript (and plugins). Wonderful!