Well, now you know someone who has a fully working PS2. I actually preordered and got a first generation PS2. I use it heavily and have not had a single problem with it. Ever.
Whereas my PS1 started to crap out in about a year, and I had to solve it with the infamous "it works better upside down" trick.
Actually Evangelion wasn't canceled. Like many series in Japan, it was written to be a miniseries of 26 episodes. Almost all series come in multiples of 13. Check out the anime aisle in your local Suncoast for proof of this.
As to why the last two episodes were incomprehensible and barely animated, Lea Hernandez was at a recent Anime Iowa and mentioned that Gainax gets stipulations from whoever requests the contract for the series they're creating. Toward the end of the series, the animators got tired of being screwed and threw the last episodes together, taking advantage of any contract loopholes and budget constraints. A very similar thing happened to Gunbuster, for those wondering why the end was in black and white with no animation.
It only does that if you don't set the option to score all steps. When that option is enabled, even when there are no arrows at all, it'll increment the "calories burned" total.
Of course, it can't take skill into account. Some songs, I could sleep through, and others turn me into a shuddering heap on the floor - yet I've burned the same amount of calories. The complexity of the routines and distance of leg movement can't really be gauged. But one thing is universal: if you want to see high calorie totals, play MaxX Unlimited in heavy mode.
Maybe I'm just not "with it", but could someone explain what Wikipedia is, and why I should care that they need $20k? Such vital information seems to be strangely missing from the article.
This has actually irked me about MySQL for a long time, even though we use it quite extensively.
The first time I noticed it, I actually sat befuddled as to what was going on. Oracle would have rejected the row, since I was trying to insert a NULL value into a NOT NULL column. When I finally figured out what was going on, I adapted our application to the behavior, but that doesn't mean I like it.
To this day, the only reason I don't advocate postgresql at our company right now, is that vacuum doesn't recover index space. We have tables with 90% daily turnover, and without daily reindexes, those indexes reach gigs if we don't catch them. Regardless of any improvements, I will continue to suggest against Postgresql until that little problem is fixed.
Data integrity is nice and all, but retrieving said data in a timely fashion is a tad problematic if indexes are essentially polluted with old data.
We also use RT, and also believe it is crap. Indexing? Shouldn't the program authors have all of that set up in the first place? Have you even seen some of the queries it executes? By God, they're nasty. We don't have half a million rows, but searches are abysmally slow, and even pulling up a known ticket is glacial. We're looking to replace it, or write our own if we have to. Stay away!
Don't forget the cost of a second phone line if you don't want to tie up your main line. That's $20 - $30 more. Doesn't seem much cheaper now, does it? Especially for those who have cell phones and want to get rid of their land lines and save $20 - $30 not having a main line at all.
So, I can either keep my land line and pay $35 - $50 for a worthless modem, or I can just pay $35 - $50 for DSL or Cable. Gee, I wonder which one I'll do.
See, now that's good news. Thank you very much. I actually contributed the current reindex script that's included with postgresql 7.2.3 and above, so I know how annoying this is. The guy above says you only have to reindex every few months, but he's wrong; our turnover was so high, we had to do it every day.
I'm all for maintanence scripts, but this is something central to the database itself. The daemon is a great idea, and I'd say a much bigger step forward than even the replication.
No shit, not that it could even compare in features... The day Postgres replaces Oracle as the defacto standard, I'll start looking at the temperature in hell. I've used both, administered both, and I'm sorry but Postgres comes nowhere near even Oracle 7.3, never mind 8, 8i or 9i.
One thing I like to point out is that if you have high turnover data, not only do you need frequent vacuums to get good performance, but you also have to *reindex your database* because vacuum doesn't reclaim freed index space. This means if you don't reindex, you could possibly run out of *disk space*. The postgres developers like to reference their laudable MVCC Multi Version Concurrency Control system, but that very row reuse is the cause of the problem in the first place.
I mean, I like Postgres and all, but until they get rid of reindex and vacuum and add a whole lot of extra functionality, there's no way in hell it will replace Oracle.
No. You see, ridiculous comes from the Latin "ridiculus" and means something is laughable, or "to laugh". What he really meant was that the article was red-iculous, or "to red". As we all know, people become red when they're angry, and so this person was illustrating that this article made them angry using a little-known derivation of the humble word: ridiculous.
And here you are, insulting the poor irate troll for using said word. Shame!
Holy shit, man... I couldn't have said it better. Mac OSX puts every linux GUI to shame, and makes development easier with a common API. But I guess that's just a crazy idea we should never impliment, because Linux is "better than that".
This is *not* about desktops. We have the LSB, why not some kind of standard base for GUI design? I don't care if you write your fucking GUI in visual basic, so long as you follow common concepts of usability and design. How about a standard specifying the minimum set of features and integration all Linux GUI applications must have? Why do we have POSIX, LSB, and a whole bunch of other standards, but *absolutely nothing* uniting all GUI development?
While I love the middle-click system, I've had multiple instances where I highlight something two or three times before it will paste. The problem above shows that I can't highlight something, and paste over another selection. Why? Why can't I paste from one selection to another? Because the very act of selecting something fills the buffer. And try cutting and pasting between your system and something running in Wine. I can get text from wine, but i can't paste back into it. Yeah, that's useful.
He is right. There is no consistant way to cut and paste between applications in any of the current GUIs, and that's just a shame.
Pico? Gross. Use nano. Pico actually tries to buffer the whole file in memory, so if you accidently or purposefully open a large (5MB+) file, it will be reeeeeeeaaaaallllly sllooooooowwwwww, as it has to fetch all of those blocks from disk, and possibly even swap depending on how much memory you have.
Of course, since the Linux 2.4 VM system assumes a user will never make a request for large amounts of memory, opening a 5MB file *will* result in swapping, since everything else is tied up in buffers and cache.
Yeah, because cost of living is the same across the world. What kind of crack are you smoking, again? It costs drastically less to live in India, hence Indian programmers can get paid less simply because of that fact. Why do Americans want 4x more salary? Possibly because rent, food, and everything else costs 4x as much.
Economics of scale? Bah.
But here's the funny part. As soon as Indian programmers start spending money in their economy and drive prices, standard of living, and various other things up, corporations will move to yet another country with lower costs. Then it will be the Indians bitching about no jobs.
And the cycle will continue, ad infinitum. That's just the way it works.
Someone who understands! Secondly, DDR is excessively addictive. I've been playing for hours a day, and am on 7-foot songs now. Trust me on this, too... you feel a lot better.
Many ISP's also portscan their customers to make sure nobody is running evil services, partly to increase security. With this large of an increase in IP space, it's much easier to hide in the vastness of that space. Hence it'll be much much easier for a black hat to hide, hop addresses, and so on - all within one subnet.
So, while this may get rid of script kiddies as they have no boxes to hack anymore, the really dangerous people will essentially be untrackable. Ouch. Then again, they already are, this just makes it easier for them. Heh.
Forget Katz. I give a hearty "Fuck You" to the nauseating ass-hat "livegoats" for that bullshit introduction. How in the hell does an opinionated smarmy diatribe quallify as a book review?
Seriously... This is like the fifth or sixth story from this month's Wired that's been posted to Slashdot. I got it in the mail and read all of these articles weeks ago, and yet they're still slowly rolling in. At this rate, Slashdot will have summarized each Wired article in the current issue individually over the course of the month.
Can't people just go to Wired and read the articles that interest them?
Dude... that's disgusting, not to mention raping the exception system. Exceptions are meant to handle errors. PHP fixes the break/continue problem by giving those operators a parameter. So if you want to continue 2 loops up, you say "continue 2;".
Doesn't scale... yeah right. That's why we serve over 1000 newspaper websites that make use of our news engine and multiple other applications all written in a PHP class architecture. Go ahead and try to Slashdot any of the sites we host.
This isn't an article about Ruby, so stop whoring out your favorite language and let it wait its turn. Don't slam PHP unless you know what the hell it can do if used properly. I mean, seriously...
It's not just that this isn't merely a season finale in place of a series finale. They could have spent five minutes editing the end to make this a real series finale.
As it stands, this episode has, continues to, and will seriously piss off every fan the show has ever had, should they decide to watch it. It was a cruel way to end the series, and I've actually blocked Sci-Fi on my own TV as a result. It's not just that they canceled the series... that I could handle. But what they did tonight was prove just how evil they truly are.
I hate them now. There is no string of obscenities long or colorful enough to describe just how much they pissed me off with the final few minutes of tonight's episode. If you want some fun, check out their farscape message board... They thought the deluge of mail they got for canceling was bad? I shudder to be anywhere near the Sci-Fi offices right now.
No... it's "TO BE CONTINUED..." here too. Those worthless, evil, disgusting wastes of oxygen didn't have the decency to chop off the last couple minutes of the episode to end the series on a positive note.
If I could cut extended basic and just get comedy central and cartoon network from now on, I would. This was just a straight slap in the face to any and all fans of the series.
Vacuum and reindex, that's why. To run a production system, and avoid filling your disks, you'll need to cron these to run at least daily on all of your databases. In some cases, even a full periodic import/export may be necessary to clean up the slow bloat postgres has problems with. So it's really an issue of missing features vs. maintenence nightmare. Personally, I'll do without the features.
Slashdot Mirror
Well, now you know someone who has a fully working PS2. I actually preordered and got a first generation PS2. I use it heavily and have not had a single problem with it. Ever.
Whereas my PS1 started to crap out in about a year, and I had to solve it with the infamous "it works better upside down" trick.
Actually Evangelion wasn't canceled. Like many series in Japan, it was written to be a miniseries of 26 episodes. Almost all series come in multiples of 13. Check out the anime aisle in your local Suncoast for proof of this.
As to why the last two episodes were incomprehensible and barely animated, Lea Hernandez was at a recent Anime Iowa and mentioned that Gainax gets stipulations from whoever requests the contract for the series they're creating. Toward the end of the series, the animators got tired of being screwed and threw the last episodes together, taking advantage of any contract loopholes and budget constraints. A very similar thing happened to Gunbuster, for those wondering why the end was in black and white with no animation.
It only does that if you don't set the option to score all steps. When that option is enabled, even when there are no arrows at all, it'll increment the "calories burned" total.
Of course, it can't take skill into account. Some songs, I could sleep through, and others turn me into a shuddering heap on the floor - yet I've burned the same amount of calories. The complexity of the routines and distance of leg movement can't really be gauged. But one thing is universal: if you want to see high calorie totals, play MaxX Unlimited in heavy mode.
Maybe I'm just not "with it", but could someone explain what Wikipedia is, and why I should care that they need $20k? Such vital information seems to be strangely missing from the article.
This has actually irked me about MySQL for a long time, even though we use it quite extensively.
The first time I noticed it, I actually sat befuddled as to what was going on. Oracle would have rejected the row, since I was trying to insert a NULL value into a NOT NULL column. When I finally figured out what was going on, I adapted our application to the behavior, but that doesn't mean I like it.
To this day, the only reason I don't advocate postgresql at our company right now, is that vacuum doesn't recover index space. We have tables with 90% daily turnover, and without daily reindexes, those indexes reach gigs if we don't catch them. Regardless of any improvements, I will continue to suggest against Postgresql until that little problem is fixed.
Data integrity is nice and all, but retrieving said data in a timely fashion is a tad problematic if indexes are essentially polluted with old data.
We also use RT, and also believe it is crap. Indexing? Shouldn't the program authors have all of that set up in the first place? Have you even seen some of the queries it executes? By God, they're nasty. We don't have half a million rows, but searches are abysmally slow, and even pulling up a known ticket is glacial. We're looking to replace it, or write our own if we have to. Stay away!
Don't forget the cost of a second phone line if you don't want to tie up your main line. That's $20 - $30 more. Doesn't seem much cheaper now, does it? Especially for those who have cell phones and want to get rid of their land lines and save $20 - $30 not having a main line at all.
So, I can either keep my land line and pay $35 - $50 for a worthless modem, or I can just pay $35 - $50 for DSL or Cable. Gee, I wonder which one I'll do.
See, now that's good news. Thank you very much. I actually contributed the current reindex script that's included with postgresql 7.2.3 and above, so I know how annoying this is. The guy above says you only have to reindex every few months, but he's wrong; our turnover was so high, we had to do it every day.
I'm all for maintanence scripts, but this is something central to the database itself. The daemon is a great idea, and I'd say a much bigger step forward than even the replication.
I'll wait and see, but this is good news.
No shit, not that it could even compare in features... The day Postgres replaces Oracle as the defacto standard, I'll start looking at the temperature in hell. I've used both, administered both, and I'm sorry but Postgres comes nowhere near even Oracle 7.3, never mind 8, 8i or 9i.
One thing I like to point out is that if you have high turnover data, not only do you need frequent vacuums to get good performance, but you also have to *reindex your database* because vacuum doesn't reclaim freed index space. This means if you don't reindex, you could possibly run out of *disk space*. The postgres developers like to reference their laudable MVCC Multi Version Concurrency Control system, but that very row reuse is the cause of the problem in the first place.
I mean, I like Postgres and all, but until they get rid of reindex and vacuum and add a whole lot of extra functionality, there's no way in hell it will replace Oracle.
No. You see, ridiculous comes from the Latin "ridiculus" and means something is laughable, or "to laugh". What he really meant was that the article was red-iculous, or "to red". As we all know, people become red when they're angry, and so this person was illustrating that this article made them angry using a little-known derivation of the humble word: ridiculous.
And here you are, insulting the poor irate troll for using said word. Shame!
Holy shit, man... I couldn't have said it better. Mac OSX puts every linux GUI to shame, and makes development easier with a common API. But I guess that's just a crazy idea we should never impliment, because Linux is "better than that".
This is *not* about desktops. We have the LSB, why not some kind of standard base for GUI design? I don't care if you write your fucking GUI in visual basic, so long as you follow common concepts of usability and design. How about a standard specifying the minimum set of features and integration all Linux GUI applications must have? Why do we have POSIX, LSB, and a whole bunch of other standards, but *absolutely nothing* uniting all GUI development?
Why that particular inconsistancy?
While I love the middle-click system, I've had multiple instances where I highlight something two or three times before it will paste. The problem above shows that I can't highlight something, and paste over another selection. Why? Why can't I paste from one selection to another? Because the very act of selecting something fills the buffer. And try cutting and pasting between your system and something running in Wine. I can get text from wine, but i can't paste back into it. Yeah, that's useful.
He is right. There is no consistant way to cut and paste between applications in any of the current GUIs, and that's just a shame.
Pico? Gross. Use nano. Pico actually tries to buffer the whole file in memory, so if you accidently or purposefully open a large (5MB+) file, it will be reeeeeeeaaaaallllly sllooooooowwwwww, as it has to fetch all of those blocks from disk, and possibly even swap depending on how much memory you have.
Of course, since the Linux 2.4 VM system assumes a user will never make a request for large amounts of memory, opening a 5MB file *will* result in swapping, since everything else is tied up in buffers and cache.
Yeah, because cost of living is the same across the world. What kind of crack are you smoking, again? It costs drastically less to live in India, hence Indian programmers can get paid less simply because of that fact. Why do Americans want 4x more salary? Possibly because rent, food, and everything else costs 4x as much.
Economics of scale? Bah.
But here's the funny part. As soon as Indian programmers start spending money in their economy and drive prices, standard of living, and various other things up, corporations will move to yet another country with lower costs. Then it will be the Indians bitching about no jobs.
And the cycle will continue, ad infinitum. That's just the way it works.
Yes!
Someone who understands! Secondly, DDR is excessively addictive. I've been playing for hours a day, and am on 7-foot songs now. Trust me on this, too... you feel a lot better.
Many ISP's also portscan their customers to make sure nobody is running evil services, partly to increase security. With this large of an increase in IP space, it's much easier to hide in the vastness of that space. Hence it'll be much much easier for a black hat to hide, hop addresses, and so on - all within one subnet.
So, while this may get rid of script kiddies as they have no boxes to hack anymore, the really dangerous people will essentially be untrackable. Ouch. Then again, they already are, this just makes it easier for them. Heh.
Forget Katz. I give a hearty "Fuck You" to the nauseating ass-hat "livegoats" for that bullshit introduction. How in the hell does an opinionated smarmy diatribe quallify as a book review?
DPI = Dots Per Inch.
You are welcome. ^_^
Seriously... This is like the fifth or sixth story from this month's Wired that's been posted to Slashdot. I got it in the mail and read all of these articles weeks ago, and yet they're still slowly rolling in. At this rate, Slashdot will have summarized each Wired article in the current issue individually over the course of the month.
Can't people just go to Wired and read the articles that interest them?
Throw an exception and catch it whereever. Eg:
Dude... that's disgusting, not to mention raping the exception system. Exceptions are meant to handle errors. PHP fixes the break/continue problem by giving those operators a parameter. So if you want to continue 2 loops up, you say "continue 2;".
Gah. Now I know why I don't use Python.
Doesn't scale... yeah right. That's why we serve over 1000 newspaper websites that make use of our news engine and multiple other applications all written in a PHP class architecture. Go ahead and try to Slashdot any of the sites we host.
This isn't an article about Ruby, so stop whoring out your favorite language and let it wait its turn. Don't slam PHP unless you know what the hell it can do if used properly. I mean, seriously...
It's not just that this isn't merely a season finale in place of a series finale. They could have spent five minutes editing the end to make this a real series finale.
As it stands, this episode has, continues to, and will seriously piss off every fan the show has ever had, should they decide to watch it. It was a cruel way to end the series, and I've actually blocked Sci-Fi on my own TV as a result. It's not just that they canceled the series... that I could handle. But what they did tonight was prove just how evil they truly are.
I hate them now. There is no string of obscenities long or colorful enough to describe just how much they pissed me off with the final few minutes of tonight's episode. If you want some fun, check out their farscape message board... They thought the deluge of mail they got for canceling was bad? I shudder to be anywhere near the Sci-Fi offices right now.
No... it's "TO BE CONTINUED..." here too. Those worthless, evil, disgusting wastes of oxygen didn't have the decency to chop off the last couple minutes of the episode to end the series on a positive note.
If I could cut extended basic and just get comedy central and cartoon network from now on, I would. This was just a straight slap in the face to any and all fans of the series.
Vacuum and reindex, that's why. To run a production system, and avoid filling your disks, you'll need to cron these to run at least daily on all of your databases. In some cases, even a full periodic import/export may be necessary to clean up the slow bloat postgres has problems with. So it's really an issue of missing features vs. maintenence nightmare. Personally, I'll do without the features.