That's bullshit. I've tried that, and it makes no difference at all in the memory leaks I'm seeing. I use tabs a lot, and Firefox very frequently does not release all memory when I close the tabs.
Currently Firefox takes up about 1 GB with all caching turned off, and closing tabs makes minimal impact.
It's most likely memory related. Whenever Firefox leaks enough memory to start swapping on my machine (usually within a day of me starting it) choppy scrolling is always one of the first ways I notice.
The electoral college has hardly ever had any impact on an election - electors have with only a handful exceptions voted for the candidate they were told to as an outcome of the vote in their state. So why is it you think the Electoral College secures strong political representation for rural areas?
It sounds weird, and it might be some numbskull who just didn't think. However, a lot of the time people using stolen card numbers make smallish test transactions to check if they go through and go unnoticed before they start doing serious damage. It might not have been their own phone bill they paid. Or it might have been some idiot trying to frame someone.
The problem with that is that it ISN'T just the irresponsible merchants that get hurt. It's all merchant, AND their customers. Speaking as someone who handled card payments of $15 million a year at one point in a previous job, I can tell you that once we'd blocked the obvious problems (card transactions from Vietnam using US numbers for a service in Europe - yeah right), the vast majority of chargebacks were caused by seemingly authentic transactions (they had the card number, customers address, expiry date, security code, came from an IP in the right country and the card had not been blocked) that later turned out to have been carried out with stolen card details.
The chargeback fees added about 20% or so to our processing costs because of the high chargeback fees levied (chargebacks are mostly manually handled) from the less than 1% chargebacks we got.
One of my pet peeves, though, is that many card processing companies are setting their customers up for identity theft. When we received chargebacks, the documentation often included full copies of statements, sent daily in envelopes clearly labeled with the logo of one of the largest payment providers in the world. While the card numbers on those statements wouldn't be worth much, they did include full contact details, and often a cover letter from the customer with a signature and phone number as well as other details of their accounts, and the statements would often include things like account numbers for various services they'd paid for... More than enough to social engineer your way past some customer service people. And 99% of it was information we had no need for at all.
We restricted access to the chargeback documents to only staff who really needed it (i.e. the accountants), and destroyed them as soon as we could, but with a daily stream of envelopes it would only take a single bad apple somewhere (mailroom, postman, post office employee, random employee who happened to find out...) before a large number of people suddenly had a lot of personal information fall into the wrong hands.
For the company I worked at at the time that payment processor was a "legacy" one, and most of our business was via a provider that restricted access to the chargeback data to what pertained to us only, and only provided it electronically. It was still bad...
Advertisers on Google pay per click. They couldn't care less about whether you see their ads or not, or about anyone else who don't click their ads as long as their specific ad isn't annoying enough to make more people avoid them than they gain from clickthroughs.
Ask a random selection of people what "mega" and "giga" means, and I think you'd be shocked at how few people acually have any idea. Even "kilo"...
For all practical purposes the prefixes are technical words and mostly acquire their meaning to people in context. While consistency is good, insisting on the bi prefixes actually create less consistency until everyone agrees one way or the other. Given how little traction they've gotten in almost a decade, we're easily talking many more decades until it's resolved. It has already caused far more confusion than it has resolved.
The IEEE has around 360.000 members - it's a tiny fraction of the industry. They're not in a position to dictate usage. I doubt even most of their members use the bi prefixes.
English is defined by common use, not by edicts. The IEC and others can recommend or make standards, and people can choose to use them, but that doesn't mean that the traditional usage isn't equally valid.
I doubt most "ordinary people" even know the *bi prefixes. Much less would have any clue what the difference is.
I have at least 3TB worth of DVD's collected over the last 6-7 years, and that's only standard definition video. Once I start getting HD content that will grow far faster. It's also only a few TV series - it's mostly individual movies. Whenever I get around to setting up a proper MythTV setup with enough disk that might change quickly, and that will certainly eat away the terabytes fairly rapidly.
I've actually been spending some time lately looking at which RAID enclosure or network storage system to pick exactly to be able to store away all my DVD's and get Myth set up.
Are you really this clueless, or are you only pretending? He posted a link to DTD documentation for Microsofts old XML format that does specify how the data should be displayed. The exact same type of braindead requirements are still present in OOXML.
A word processor isn't a web browser - users expect their document layout to stay the same or they will consider a word processor broken. And when a document format spec state how a specific element should affect layout and rendering they can also validly consider it to not be compliant with the spec.
And that has absolutely no relevance. The markup there refers to marking up the raw data. How the data is meant to be interpreted is up to the specific application of XML. In this case, both OpenDocument and OOXML define a document format that use XML markup as parts of it's implementation, but then define specific rules about how the various constructs should be treated. In the case of OOXML some of those rules require an implementer to copy the behavior of a specific version of Word.
You're assuming that nothing else at all changed on the system to add to power consumption. Such as activity (both CPU and disk) when he shut down Beagle for example.
As for food in general, even SF is only 'ok' when you're used to London standards.
Food in London is only good when you avoid British food though (and of course the tourist traps)...
Also, people who like steak might want to consider avoiding ordering it in the UK. I've lived in London for 7 years now, and have yet to find anywhere that serve steaks that have been more than somewhat tolerable. People rave about the steaks in our local pub, so I tried it a few weeks ago and it took one bite to realize that I've never had steaks that bad anywhere outside the UK. Despite that, it was by far the best I've ever had IN the UK.
Generally steaks in British restaurants and steakhouses are overcooked (try getting staff in a British restaurant to understand the concept of rare steaks... I've had waiters stare at me incomprehensibly until I explained that I wanted it cooked at high temperature short enough to be heated through but stay red inside...), tough, poorly cut, covered in bland sauces (especially if you visit the evil that is Angus Steakhouse/Aberdeen Steakhous/Garfunkels/Brasserie Maxine's - in essence, avoid any "steakhouse" with mainly red interior...) as if they are afraid you might actually find the meat, often grilled so badly it tastes more of coal than meat.
Compare that with California (or anywhere else I've been in the US), where it's a rare occurrence to get steaks that are mediocre (which still will be far above the best steaks I've had in London...)
So it really depends - I've had many of my best steaks in the Bay Area, though for Chinese I definitively prefer London (assuming you go to a proper Chinese restaurant like New World or Royal China, not one of the take-away quality ones). And of course if you go to any of the Michelin guide restaurants in London the quality is fantastic and you have many of them to choose from..
Uh. No... Neither is right. The UK consists of Great Britain and Northern Ireland, and of course a lot of islands come under the jurisdiction of both of those two legal entities.
The island you refer to is the island of Great Britain, the largest of the British Isles.
You might think that is how it should be, but legally you don't have the right to deny people a job for any reason or choose to rent or sell for any reason you please - a long range of reasons are illegal discrimination whether you like it or not.
And if you were taken to court by a prospective tenant and you couldn't prove that you had a legal reason for picking another applicant, you might find yourself in deep shit.
Nonsense. I used to live in an apartment building where the family below us kept dumping food and oil down the drain. Every day. They did have to get plumbers out every few months, but it never took much work to clear things out, and over the years we lived there smell was never an issue except for right at the time when it clogged up if they didn't get a plumber out quick enough, but once the system was cleared it was fine.
Slashdot Mirror
So in other words you're one of the lucky ones that don't experience the memory leak. Doesn't help those of us who are.
Firefox at 1GB with one tab and the cache cleared here.
Currently Firefox takes up about 1 GB with all caching turned off, and closing tabs makes minimal impact.
It's most likely memory related. Whenever Firefox leaks enough memory to start swapping on my machine (usually within a day of me starting it) choppy scrolling is always one of the first ways I notice.
It sounds weird, and it might be some numbskull who just didn't think. However, a lot of the time people using stolen card numbers make smallish test transactions to check if they go through and go unnoticed before they start doing serious damage. It might not have been their own phone bill they paid. Or it might have been some idiot trying to frame someone.
The chargeback fees added about 20% or so to our processing costs because of the high chargeback fees levied (chargebacks are mostly manually handled) from the less than 1% chargebacks we got.
One of my pet peeves, though, is that many card processing companies are setting their customers up for identity theft. When we received chargebacks, the documentation often included full copies of statements, sent daily in envelopes clearly labeled with the logo of one of the largest payment providers in the world. While the card numbers on those statements wouldn't be worth much, they did include full contact details, and often a cover letter from the customer with a signature and phone number as well as other details of their accounts, and the statements would often include things like account numbers for various services they'd paid for... More than enough to social engineer your way past some customer service people. And 99% of it was information we had no need for at all.
We restricted access to the chargeback documents to only staff who really needed it (i.e. the accountants), and destroyed them as soon as we could, but with a daily stream of envelopes it would only take a single bad apple somewhere (mailroom, postman, post office employee, random employee who happened to find out...) before a large number of people suddenly had a lot of personal information fall into the wrong hands.
For the company I worked at at the time that payment processor was a "legacy" one, and most of our business was via a provider that restricted access to the chargeback data to what pertained to us only, and only provided it electronically. It was still bad...
Advertisers on Google pay per click. They couldn't care less about whether you see their ads or not, or about anyone else who don't click their ads as long as their specific ad isn't annoying enough to make more people avoid them than they gain from clickthroughs.
That depends on the ATM. Many ATM's will reject your card the moment you enter the wrong pin before you even get a chance to enter the amount.
For all practical purposes the prefixes are technical words and mostly acquire their meaning to people in context. While consistency is good, insisting on the bi prefixes actually create less consistency until everyone agrees one way or the other. Given how little traction they've gotten in almost a decade, we're easily talking many more decades until it's resolved. It has already caused far more confusion than it has resolved.
The IEEE has around 360.000 members - it's a tiny fraction of the industry. They're not in a position to dictate usage. I doubt even most of their members use the bi prefixes.
And I've yet not heard anyone except annoying geeks use the *bi prefixes.
I doubt most "ordinary people" even know the *bi prefixes. Much less would have any clue what the difference is.
I've actually been spending some time lately looking at which RAID enclosure or network storage system to pick exactly to be able to store away all my DVD's and get Myth set up.
Bytes isn't a SI unit.
A word processor isn't a web browser - users expect their document layout to stay the same or they will consider a word processor broken. And when a document format spec state how a specific element should affect layout and rendering they can also validly consider it to not be compliant with the spec.
What you say make no sense.
16 hex digits is 8 bytes. Good luck trying to post 2^64 16 byte sequences anywhere in your lifetime.
Food in London is only good when you avoid British food though (and of course the tourist traps)...
Also, people who like steak might want to consider avoiding ordering it in the UK. I've lived in London for 7 years now, and have yet to find anywhere that serve steaks that have been more than somewhat tolerable. People rave about the steaks in our local pub, so I tried it a few weeks ago and it took one bite to realize that I've never had steaks that bad anywhere outside the UK. Despite that, it was by far the best I've ever had IN the UK.
Generally steaks in British restaurants and steakhouses are overcooked (try getting staff in a British restaurant to understand the concept of rare steaks... I've had waiters stare at me incomprehensibly until I explained that I wanted it cooked at high temperature short enough to be heated through but stay red inside...), tough, poorly cut, covered in bland sauces (especially if you visit the evil that is Angus Steakhouse/Aberdeen Steakhous/Garfunkels/Brasserie Maxine's - in essence, avoid any "steakhouse" with mainly red interior...) as if they are afraid you might actually find the meat, often grilled so badly it tastes more of coal than meat.
Compare that with California (or anywhere else I've been in the US), where it's a rare occurrence to get steaks that are mediocre (which still will be far above the best steaks I've had in London...)
So it really depends - I've had many of my best steaks in the Bay Area, though for Chinese I definitively prefer London (assuming you go to a proper Chinese restaurant like New World or Royal China, not one of the take-away quality ones). And of course if you go to any of the Michelin guide restaurants in London the quality is fantastic and you have many of them to choose from..
Uh. No... Neither is right. The UK consists of Great Britain and Northern Ireland, and of course a lot of islands come under the jurisdiction of both of those two legal entities.
The island you refer to is the island of Great Britain, the largest of the British Isles.
You might think that is how it should be, but legally you don't have the right to deny people a job for any reason or choose to rent or sell for any reason you please - a long range of reasons are illegal discrimination whether you like it or not.
And if you were taken to court by a prospective tenant and you couldn't prove that you had a legal reason for picking another applicant, you might find yourself in deep shit.