All of them are pretty well closed-up and lacking extensibility. But the boy's cheap Blu-Ray player grows new features from time to time despite this. (I assume that the manufacturer gets some manner of kickback for supporting the myriad of network streaming options that it does, as there's no other way for them to make money by continuing to support a device which is already sold and I simply don't believe in corporate goodwill at the razor-thin-margin area of consumer electronics.)
Perhaps more to the point: It works with Netflix and supports the TV rips that I download automagically, which is good enough for my needs...though I've also seen him digging through a bunch of other free content from who-knows-where.
And, well, that's it. It can't play Angry Birds, but if he wanted to play a cheesy game he's also got a perfectly adequate PC. *shrug*
1) Is it limited in ways that actually matter for most people?
2) So use the built-in thing, and then plug a box in later. *shrug* This isn't the 90s where having built-in whiz-bang functionality adds physical size to a display like a built-in VCR, where things had few (if any) external inputs.
This is 2012, and the whiz-bang functionality doesn't take up any perceptible space inside of a display. And it's generally included whether you want it or not. And if it gets tired as formats progress and march on, there are a multitude of available inputs to connect an external box to even on the lowliest modern LCD.
3) Most folks (and I'm specifically referring to anyone who doesn't have a compulsively-organized NAS full of their own rips) will want a Blu-Ray player, anyway. And the Blu-Ray machine will generally be able to do many of the same things as a Roku.
Right. So I shouldn't store a massive many-user maildir on NTFS, and I shouldn't keep huge single-file datasets there either. Got it.
But those are corner-cases, of which I'm sure there are some that ext2/3/4 falls down on as well: Ain't nothin' perfect.
For common use, where there often aren't more than a few hundred smallish files in a directory or any one file exceeding a few gigabytes: What's the problem?
And even then: If I push the envelope with NTFS and do those horrible, horrible things with it: What's the downside? Will performance simply be less than ideal, or will my cat spontaneously give birth to honest-to-god Gremlins who will incite the apocalypse?
So you get this super-nifty thing which can only be attached to the most super-nifty of the HDMI ports, which will only be equipped to begin with on devices which were already super-nifty.
So, I guess the choices are as thus (since keeping an old TV and buying a new Roku isn't an option):
1. Keep old TV, buy old Roku.
2. Buy new TV, keep old Roku.
3. Buy new super-nifty TV, don't bother with super-nifty Roku because the super-nifty is already built into the TV.
(4. Oh, yeah: At no point is there any functional merit to a new super-nifty Roku. Neat!)
I'm just one man, but I've tried hard over the past decade to find a real problem with NTFS (and I've been sternly bitten by ReiserFS and ext2/3 over that same period), and just haven't: It's worked on the many hundreds of computers I've fondled just fine, and even seems to survive mild hard disk failure with some amount of reasonableness.
What, in your opinion, makes NTFS a pain in your ass? (I ask because I'm curious and want to avoid any such scenario, not because I am predisposed to attack your observations.)
The black ones turn just as gross: Take one apart sometime and have a look inside.
The wife's WoW-playing machine slowly developed some issues with the W and 2 keys on her fancy Saitek keyboard. It was really pretty nasty in there. Some scrubbing bubbles for the external plastic bits, and a bit of Deoxit on the Mylar membrane switches, and she's got people asking her what she changed because her DPS went through the roof.
I take apart my favorite keyboard (an old, heavy, squishy white NMB that I really like the key-feel of, Model M be damned) once every year or two and give everything but the keyswitches a good wash in the dishwasher. It's been a good friend for nearly a decade, despite the occasional spill or cigarette ash or the constant bombardment of smoke residue, and I want to keep it around. (The keycaps were worn smooth long ago...)
So, yeah: I clean keyboards. Time is money, but money can't always buy a keyboard that I actually like. It's more of a functional thing than a spastic reaction to the obvious bacterial flora that obviously must be living on it, but whatever the case cleaning it helps me type in ways that keep me happy.
Windows may not be a filesystem, but it only ships with one sane choice of general-purpose filesystem, and that choice is NTFS. Therefore, Windows == NTFS for the purpose of a discussion in the context of filesystems. Not literally, but plainly for all intents and purposes.
(Counterarguments about Windows also shipping with crappy filesystem(s) needn't apply, since Linux/*BSD ships with those too. And HPFS, the only other then-viable choice from IBM/MSFT, and perhaps the only one that Linux and Windows and OS/2 all supported properly at the same time, got killed a long long time ago.)
(Disclaimer: This is does not represent my opinion on anything. It simply is a representation of how things are.)
The whole point of the Magnuson-Moss act is to eliminate such gotchas as "warranty is not given if you change X."
To use a car analogy, I can change the firmware in my car without affecting the warranty on the rest of the car. If something mechanical breaks, it is their duty to either fix it under the terms of the warranty (in compliance with the Magnuson-Moss Act) or prove that my modification caused the failure.
Saying "we won't fix it because you poked it funny, and we don't understand funny" isn't a legal option for them.
However, saying "we aren't going to fix your engine because your firmware removed the rev limiter, leaned the mixture and advanced the timing, causing the burnt rings and broken valves in your motor" is perfectly reasonable and valid -- as long as my firmware modification actually did those things. And even then, it's up to them to show that to be the case.
Naaah. Just occasionally: I'm only out of town for a week or so at a time once or twice per year, if that.
And if something happens during that "week or so," then it's whatever -- not cheating. The wife and I have discussed it in general concept many times over our 8 years: She's only potentially offended by an emotional relationship developing that does not involve her. Meanwhile, I'm not interested in a secondary emotional relationship, so that's not an issue for me to contend with.
(But am I interested in a temporary physical relationship? Sure. FFS, does the Earth have gravity? There's lots of cocks and lots of cunts, and most of them fit together pleasurably.)
So, such as it is: Sometimes, fucking is just fucking fucking. This does not mean that simple fucking is necessarily fucking cheating, though you and/or your SO may view things differently -- which is OK, too.
Your Handbrake benchmark is impressive. It makes me ponder whether I should investigate overclocking modern-ish CPUs more than I have been.
But meanwhile (again), I've really enjoyed stability: Plug it together, configure it to spec, and it just works. It's very nice in ways that weren't always common, when a random ISA card might be unhappy with the bus speed of a (stock) 10MHz XT, or when dealing with the various hairy tribulations of VLB.
As to your future report: Please do, in a year or so -- by all means. I'll be very interested in what you've found by that time (this/. article will be long closed by then, but my email address will be the same). We can continue the discussion when you've got something long(ish)-term to report..
If your benchmark for stability is "I overclocked a [random thing] a few days ago and it still seems to be happy," then I don't think we really have anything discuss right now.
Let me know in a year or three how it works out.
(I've overclocked my Q6600 SLACR and had it appear to be stable for a few days, but then the crashes came. Much tweaking and posturing later, I've found that I'm far happier with a slower system that does not crash than I am with a fast system that sometimes crashes: I want my systems to have planned uptimes of years, if possible -- not mere days or weeks. And at stock clocks, the Q6600 simply has not crashed. YMMV.)
Back in the old days overclocking a K6-2 from 300 to 350 required good cooling and some luck and increasing the bus speed overclocked all of the components on the mainboard. nowadays they make CPU's to be overclocked with the K and black series.
Meh. None of that: AMD K6-2 300's running at 350 for years and years with perfect stability, using whatever random cooler, with months or years between planned reboots, with nothing more than a change in clock speeds: From 100x3 to 100x3.5.
Maybe I was just lucky, but it is simply my experience. As I said, YMMV.
When I'm out and about on my own for business or whatever, my wife doesn't call me and seldom expects me to call her. I might be gone for a week and talk to her for four minutes, total, and normally not even that unless there is a particularly egregious drama at home.
Accordingly, hiding a 1k-mile-away "affair" has/would've been/is -easy- for me, and I expect no different from her.
We've both got cell phones, so this is completely optional behavior in this modern world.
What do we win?
(editor's note: syphilis and HIV are unacceptable as a reward. incidental offspring of personal trainers and/or pool boys may be interpreted with prejudice.)
As long as you stay reasonable (don't change voltages) you're getting a good performance gain for free. Why not get a 30% performance boost?
Because some of us would rather pay more to get a 30% performance boost without fiddling about trying to gauge system stability, and others of us are happy enough with the out-of-the-box stable systems that we have by default.
I've done my share of overclocking (having first overclocked a 386SX from 33MHz to 40MHz, a P100 to 120, and then some K6-2s from 300 to 350), but lately I'd rather just have a system that is both reliable and that doesn't need fucking-with.
The page as it is now is fine, but it needs one thing changed. The black bar with gray text is hard to read. Why are web designers so obsessed with making their pages so hard to read? A little more contrast please.
Seconded. I've had variously slow response from 4.2.2.x, but at least it/they always works.
Lately, I've been using Google's 8.8.8.8 with 4.2.2.1 as a secondary.
Allegedly, this can piss off some CDN systems, but meh: The other option is my ISP's DNS, which is consistently both broken and laggy to such an extent that I cannot imagine how they've managed to fuck up BIND so thoroughly.
I try to park up-hill, in a protected area (near a curb, if possible) away from common shopping cart trajectories. This generally puts me almost as far away from the building as possible.
The reasons are simple:
1. I'm lazy. And depending on the particular nature of my work, walking to/from the store might be the closest thing to actual exercise that I might experience that day.
2. I'm lazy. I'd rather spend a minute or two extra walking two/from the store, than possibly even more time fighting for a "good" space close to the building.
3. I'm lazy. I prefer to find an easy parking space where there are few pedestrians to dodge, and where I won't find myself needing to back up the car at all.
4. I'm lazy. Parking far away from others is cheap insurance against random accidental damage from carts and car doors. When/if I repaint my car, I want to have as few things to fix as possible.
No, I really have no idea what they teach in school.
That's just how it went down in my neck of the woods, based on my own research into local history and reading texts and periodicals from the period: Inter-urban passenger count went down to such an extent that it was no longer profitable. Various mergers between rail companies happened in an attempt to regain profitability (or just take advantage of fire-sale pricing, which is really the same thing), and ultimately things just plain failed.
Same as what happened to the local ferryboat which traveled up and down the river, between downtown and a park which was (then) at the edge of town: With the advent of affordable cars, people eventually stopped using the boat in sufficient numbers to make it worthwhile.
This may not be a valid generalization of the rest of the country, but it's what happened here.
But frankly, I don't care how much energy my neighbor uses. It's plain and obvious that good insulation pays for itself, but if someone chooses to do things differently then I've got no business telling them otherwise: It's their money, and they can burn it however they wish.
Meanwhile, there's lots of reasons that Germany's average per-capita efficiency is better, and insulation is just one small aspect of it.
At a glance:
Germans seem to be more willing to live closely together. This tends to allow things like food to be profitably sold closer to where people actually live, while also allowing greater access to public transportation. This leads to fewer big things (trucks, buses, trains) ferrying things and people about, instead of the US version which generally has everyone driving some distance to go about their daily business, buying in bulk because it's a pain to get to the store, and requiring a larger vehicle in order to move it around.
The US used to have functional passenger rail between neighboring cities, but we killed it by driving cars and have since built things in support of that habit.
I, and my neighbors, seem to like it this way: We could easily choose to live more closely together (by moving to a downtown apartment or a larger city or both) but we instead prefer to have big houses, big yards, and all of the detrimental effects that the resulting sparsity brings.
For instance: I enjoy having enough space that I can have a huge bonfire and a modest fireworks display without worrying about burning down the neighborhood, park my three cars and have room to work on more, have enough distance between myself and my neighbors to have a rock band perform in my front room without annoying others, and have multiple people sleep after a party without crowding or putting anyone on the floor..
Accordingly, I also have to drive several miles to get anything much more complicated than beer or a loaf of bread.
It's a tradeoff. It's expensive. I'm OK with that. If some other nation decides to do things differently, that's OK too. *shrug*
I live in a smallish (38k) town which does not have, and never has had, any manner of residential building code. At all. Folks can (and do!) run their own electrical and plumbing, or remodel whatever they want. Permits are required for new construction, but that's for reasons of zoning and flood zone restrictions -- not construction technique.
Somehow, houses aren't falling down. They seem to stand up to heavy snow and high wind just fine.
Sewage doesn't run through the streets, no home I've ever seen here has been wired with 20-guage speaker wire (unlike the Florida hotel I stayed at the other night), and etc.
Things here seem to work fine, though we accordingly don't have very many architects in town. (I consider this to be a good thing.)
Slashdot Mirror
All of them are pretty well closed-up and lacking extensibility. But the boy's cheap Blu-Ray player grows new features from time to time despite this. (I assume that the manufacturer gets some manner of kickback for supporting the myriad of network streaming options that it does, as there's no other way for them to make money by continuing to support a device which is already sold and I simply don't believe in corporate goodwill at the razor-thin-margin area of consumer electronics.)
Perhaps more to the point: It works with Netflix and supports the TV rips that I download automagically, which is good enough for my needs...though I've also seen him digging through a bunch of other free content from who-knows-where.
And, well, that's it. It can't play Angry Birds, but if he wanted to play a cheesy game he's also got a perfectly adequate PC. *shrug*
1) Is it limited in ways that actually matter for most people?
2) So use the built-in thing, and then plug a box in later. *shrug* This isn't the 90s where having built-in whiz-bang functionality adds physical size to a display like a built-in VCR, where things had few (if any) external inputs.
This is 2012, and the whiz-bang functionality doesn't take up any perceptible space inside of a display. And it's generally included whether you want it or not. And if it gets tired as formats progress and march on, there are a multitude of available inputs to connect an external box to even on the lowliest modern LCD.
3) Most folks (and I'm specifically referring to anyone who doesn't have a compulsively-organized NAS full of their own rips) will want a Blu-Ray player, anyway. And the Blu-Ray machine will generally be able to do many of the same things as a Roku.
Is that a problem with NTFS, or with NTFS-3g's implementation of it?
Right. So I shouldn't store a massive many-user maildir on NTFS, and I shouldn't keep huge single-file datasets there either. Got it.
But those are corner-cases, of which I'm sure there are some that ext2/3/4 falls down on as well: Ain't nothin' perfect.
For common use, where there often aren't more than a few hundred smallish files in a directory or any one file exceeding a few gigabytes: What's the problem?
And even then: If I push the envelope with NTFS and do those horrible, horrible things with it: What's the downside? Will performance simply be less than ideal, or will my cat spontaneously give birth to honest-to-god Gremlins who will incite the apocalypse?
So you get this super-nifty thing which can only be attached to the most super-nifty of the HDMI ports, which will only be equipped to begin with on devices which were already super-nifty.
So, I guess the choices are as thus (since keeping an old TV and buying a new Roku isn't an option):
1. Keep old TV, buy old Roku.
2. Buy new TV, keep old Roku.
3. Buy new super-nifty TV, don't bother with super-nifty Roku because the super-nifty is already built into the TV.
(4. Oh, yeah: At no point is there any functional merit to a new super-nifty Roku. Neat!)
Actually, AC: I think I know what I'm "probably thinking of," and FAT (in any incarnation) isn't it.
I'm just one man, but I've tried hard over the past decade to find a real problem with NTFS (and I've been sternly bitten by ReiserFS and ext2/3 over that same period), and just haven't: It's worked on the many hundreds of computers I've fondled just fine, and even seems to survive mild hard disk failure with some amount of reasonableness.
What, in your opinion, makes NTFS a pain in your ass? (I ask because I'm curious and want to avoid any such scenario, not because I am predisposed to attack your observations.)
The black ones turn just as gross: Take one apart sometime and have a look inside.
The wife's WoW-playing machine slowly developed some issues with the W and 2 keys on her fancy Saitek keyboard. It was really pretty nasty in there. Some scrubbing bubbles for the external plastic bits, and a bit of Deoxit on the Mylar membrane switches, and she's got people asking her what she changed because her DPS went through the roof.
I take apart my favorite keyboard (an old, heavy, squishy white NMB that I really like the key-feel of, Model M be damned) once every year or two and give everything but the keyswitches a good wash in the dishwasher. It's been a good friend for nearly a decade, despite the occasional spill or cigarette ash or the constant bombardment of smoke residue, and I want to keep it around. (The keycaps were worn smooth long ago...)
So, yeah: I clean keyboards. Time is money, but money can't always buy a keyboard that I actually like. It's more of a functional thing than a spastic reaction to the obvious bacterial flora that obviously must be living on it, but whatever the case cleaning it helps me type in ways that keep me happy.
Windows may not be a filesystem, but it only ships with one sane choice of general-purpose filesystem, and that choice is NTFS. Therefore, Windows == NTFS for the purpose of a discussion in the context of filesystems. Not literally, but plainly for all intents and purposes.
(Counterarguments about Windows also shipping with crappy filesystem(s) needn't apply, since Linux/*BSD ships with those too. And HPFS, the only other then-viable choice from IBM/MSFT, and perhaps the only one that Linux and Windows and OS/2 all supported properly at the same time, got killed a long long time ago.)
(Disclaimer: This is does not represent my opinion on anything. It simply is a representation of how things are.)
I will vote for me.
The whole point of the Magnuson-Moss act is to eliminate such gotchas as "warranty is not given if you change X."
To use a car analogy, I can change the firmware in my car without affecting the warranty on the rest of the car. If something mechanical breaks, it is their duty to either fix it under the terms of the warranty (in compliance with the Magnuson-Moss Act) or prove that my modification caused the failure.
Saying "we won't fix it because you poked it funny, and we don't understand funny" isn't a legal option for them.
However, saying "we aren't going to fix your engine because your firmware removed the rev limiter, leaned the mixture and advanced the timing, causing the burnt rings and broken valves in your motor" is perfectly reasonable and valid -- as long as my firmware modification actually did those things. And even then, it's up to them to show that to be the case.
So what do you call this behavior wherein you encourage people to write interesting things? "Anti-trolling" seems lacking in finesse, somehow.
Now, I'm curious:
How does me getting modded up benefit you?
Naaah. Just occasionally: I'm only out of town for a week or so at a time once or twice per year, if that.
And if something happens during that "week or so," then it's whatever -- not cheating. The wife and I have discussed it in general concept many times over our 8 years: She's only potentially offended by an emotional relationship developing that does not involve her. Meanwhile, I'm not interested in a secondary emotional relationship, so that's not an issue for me to contend with.
(But am I interested in a temporary physical relationship? Sure. FFS, does the Earth have gravity? There's lots of cocks and lots of cunts, and most of them fit together pleasurably.)
So, such as it is: Sometimes, fucking is just fucking fucking. This does not mean that simple fucking is necessarily fucking cheating, though you and/or your SO may view things differently -- which is OK, too.
Does that clear up your confusion?
Your Handbrake benchmark is impressive. It makes me ponder whether I should investigate overclocking modern-ish CPUs more than I have been.
But meanwhile (again), I've really enjoyed stability: Plug it together, configure it to spec, and it just works. It's very nice in ways that weren't always common, when a random ISA card might be unhappy with the bus speed of a (stock) 10MHz XT, or when dealing with the various hairy tribulations of VLB.
As to your future report: Please do, in a year or so -- by all means. I'll be very interested in what you've found by that time (this /. article will be long closed by then, but my email address will be the same). We can continue the discussion when you've got something long(ish)-term to report..
If your benchmark for stability is "I overclocked a [random thing] a few days ago and it still seems to be happy," then I don't think we really have anything discuss right now.
Let me know in a year or three how it works out.
(I've overclocked my Q6600 SLACR and had it appear to be stable for a few days, but then the crashes came. Much tweaking and posturing later, I've found that I'm far happier with a slower system that does not crash than I am with a fast system that sometimes crashes: I want my systems to have planned uptimes of years, if possible -- not mere days or weeks. And at stock clocks, the Q6600 simply has not crashed. YMMV.)
Meh. None of that: AMD K6-2 300's running at 350 for years and years with perfect stability, using whatever random cooler, with months or years between planned reboots, with nothing more than a change in clock speeds: From 100x3 to 100x3.5.
Maybe I was just lucky, but it is simply my experience. As I said, YMMV.
Oooh, ooh! *raises hand* Can I play?
When I'm out and about on my own for business or whatever, my wife doesn't call me and seldom expects me to call her. I might be gone for a week and talk to her for four minutes, total, and normally not even that unless there is a particularly egregious drama at home.
Accordingly, hiding a 1k-mile-away "affair" has/would've been/is -easy- for me, and I expect no different from her.
We've both got cell phones, so this is completely optional behavior in this modern world.
What do we win?
(editor's note: syphilis and HIV are unacceptable as a reward. incidental offspring of personal trainers and/or pool boys may be interpreted with prejudice.)
Because some of us would rather pay more to get a 30% performance boost without fiddling about trying to gauge system stability, and others of us are happy enough with the out-of-the-box stable systems that we have by default.
I've done my share of overclocking (having first overclocked a 386SX from 33MHz to 40MHz, a P100 to 120, and then some K6-2s from 300 to 350), but lately I'd rather just have a system that is both reliable and that doesn't need fucking-with.
YMMV.
Isn't this part of what CSS what supposed to do?
Seconded. I've had variously slow response from 4.2.2.x, but at least it/they always works.
Lately, I've been using Google's 8.8.8.8 with 4.2.2.1 as a secondary.
Allegedly, this can piss off some CDN systems, but meh: The other option is my ISP's DNS, which is consistently both broken and laggy to such an extent that I cannot imagine how they've managed to fuck up BIND so thoroughly.
5. Park far away, anyway, if able to.
I try to park up-hill, in a protected area (near a curb, if possible) away from common shopping cart trajectories. This generally puts me almost as far away from the building as possible.
The reasons are simple:
1. I'm lazy. And depending on the particular nature of my work, walking to/from the store might be the closest thing to actual exercise that I might experience that day.
2. I'm lazy. I'd rather spend a minute or two extra walking two/from the store, than possibly even more time fighting for a "good" space close to the building.
3. I'm lazy. I prefer to find an easy parking space where there are few pedestrians to dodge, and where I won't find myself needing to back up the car at all.
4. I'm lazy. Parking far away from others is cheap insurance against random accidental damage from carts and car doors. When/if I repaint my car, I want to have as few things to fix as possible.
No, I really have no idea what they teach in school.
That's just how it went down in my neck of the woods, based on my own research into local history and reading texts and periodicals from the period: Inter-urban passenger count went down to such an extent that it was no longer profitable. Various mergers between rail companies happened in an attempt to regain profitability (or just take advantage of fire-sale pricing, which is really the same thing), and ultimately things just plain failed.
Same as what happened to the local ferryboat which traveled up and down the river, between downtown and a park which was (then) at the edge of town: With the advent of affordable cars, people eventually stopped using the boat in sufficient numbers to make it worthwhile.
This may not be a valid generalization of the rest of the country, but it's what happened here.
Perhaps it's better.
But frankly, I don't care how much energy my neighbor uses. It's plain and obvious that good insulation pays for itself, but if someone chooses to do things differently then I've got no business telling them otherwise: It's their money, and they can burn it however they wish.
Meanwhile, there's lots of reasons that Germany's average per-capita efficiency is better, and insulation is just one small aspect of it.
At a glance:
Germans seem to be more willing to live closely together. This tends to allow things like food to be profitably sold closer to where people actually live, while also allowing greater access to public transportation. This leads to fewer big things (trucks, buses, trains) ferrying things and people about, instead of the US version which generally has everyone driving some distance to go about their daily business, buying in bulk because it's a pain to get to the store, and requiring a larger vehicle in order to move it around.
The US used to have functional passenger rail between neighboring cities, but we killed it by driving cars and have since built things in support of that habit.
I, and my neighbors, seem to like it this way: We could easily choose to live more closely together (by moving to a downtown apartment or a larger city or both) but we instead prefer to have big houses, big yards, and all of the detrimental effects that the resulting sparsity brings.
For instance: I enjoy having enough space that I can have a huge bonfire and a modest fireworks display without worrying about burning down the neighborhood, park my three cars and have room to work on more, have enough distance between myself and my neighbors to have a rock band perform in my front room without annoying others, and have multiple people sleep after a party without crowding or putting anyone on the floor..
Accordingly, I also have to drive several miles to get anything much more complicated than beer or a loaf of bread.
It's a tradeoff. It's expensive. I'm OK with that. If some other nation decides to do things differently, that's OK too. *shrug*
Hmm.
I live in a smallish (38k) town which does not have, and never has had, any manner of residential building code. At all. Folks can (and do!) run their own electrical and plumbing, or remodel whatever they want. Permits are required for new construction, but that's for reasons of zoning and flood zone restrictions -- not construction technique.
Somehow, houses aren't falling down. They seem to stand up to heavy snow and high wind just fine.
Sewage doesn't run through the streets, no home I've ever seen here has been wired with 20-guage speaker wire (unlike the Florida hotel I stayed at the other night), and etc.
Things here seem to work fine, though we accordingly don't have very many architects in town. (I consider this to be a good thing.)