In the US you can open a bank with about $500 worth of paperwork. As a result there are about 2-3 banks per person.
Are you seriously claiming that there are over 600 million banks in the US?
The banks dont talk to each other. They dont have a common banking network.
So explain to me why I can use my ATM card in any bank's ATM (albeit for a small fee), wire money between accounts of different banks, have my paycheck deposited directly in my account without my employer having to have arrangements with the specific bank I use, cash or deposit a check drawn on another bank, etc.
They often go belly up taking all of their customers money with them.
Accounts are insured by the federal government up to $100,000 in the event that that happens.
As we get a lot of US media, I am aware that VISA is pushing hard there "cheque card". In Canada you have been able to use your ATM card in retail outlets for a decade.
I got a "check card" (usable like any normal VISA) automatically when opening a U.S. account about 8 years ago. This isn't new here either.
Yes, you can run the OS in a state of partial
functionality (or replaced by other functionality,
if you prefer). I was referring to normal
use of the OS. Is Aqua also not a part of the OS,
because you can use X instead?
Hell, I could just boot Linux instead; even
the Darwin kernel must not count.:-)
Yeah, it's "just another app" that is installed
with the OS, starts at bootup, can't be shut
down (only restarted), and gets focus whenever
you click on an unused area of the screen. Oh,
and there's the minor issue of it being the primary
way the OS provides to let users interact with
their files.
Because, like spam, it is a behavioral problem, not purely a technical problem. System break-ins and e-mail worms can be prevented by technical means as well, but that doesn't mean it should be legal to carry them out.
It's rare, but it does happen. I once had a compilation fail claiming an unrecognized preprocessor directive #inclufe (or something similarly off by one bit). It was not that way in the file, and compiling it again succeeded.
It's kind of scary to think about what could have happened if it were a production build, and it had happened in a way that did not render the file uncompileable.
I'd imagine that, at least on a workstation/desktop, a lot of such errors go unnoticed, hitting unused RAM (such as cache that isn't used again, or the code/data for one of the fifty billion features of $BLOATED_APP that the user never uses...). Then again, given typical software quality, how many times would, upon seeing something crash or behave strangely, one think, "must have been a bit error!"?
So what if they let you take it back? You've already bought it at that point. It's yours. As long as you don't violate copyright (or other specific laws), what obligates you to accept their additional terms before using your software?
Re:VI is everywhere.
on
JOE Hits 3.0
·
· Score: 1, Insightful
If you can access the machine well enough to
use vi on it, you can probably get a copy of
joe onto it as well. Learn scp, ya bum.
Seriously, it's kind of silly to use a
particular editor just because of its ubiquity.
One can be familiar enough with vi to use it
(grudgingly) in an emergency, while still using
something more pleasant in non-emergencies.
That's why they phrase it as a "use tax". They're not taxing the purchase or importation, just your use of the item within that state's borders.
The use tax just happens to have a tax credit for sales tax paid on the same item.
If they charged higher tax on out-of-state goods,
or refused to credit for any sales tax paid to the other state (while still exempting things purchased in-state),
then you could argue that they're giving preference.
The original poster's "without
having to cough up $$$ for the expensive channels" comment
doesn't make it sound like he's talking about
timeshifting programming that he paid for...
HTTP runs over TCP, which means that to complete a "click", you'll need to be able to receive data at the spoofed IP address and respond based on it (specifically, you need to know the initial sequence number). Unless you can guess what that number is (which is not easy with good TCP code), you won't be able to get the server to listen to you. You might get lucky once in a while, but not enough for an attack that depends on a high rate of success.
As for MACs, they're for the local network only. As Google can't even see your MAC, spoofing it would have fairly little point.
To which I say, yes... you have lost something. You have lost the ability
to insure that the end user has access to the source code that you wrote.
No, you haven't. You're still perfectly capable
of putting all of your source code up on a website
and letting everyone who wants to download it. That they can't get it from specific other people doesn't change that, even if they happen to distribute binaries. Sure, it'd be nice if those who did would at least tell the users about your FTP site, but the terms of the GPL are neither necessary nor (IMO) worth it for that specific goal.
Insuring that users have access to code that
other people wrote, that happens to have
been combined with code that you wrote, is of course
another matter entirely.
Still, isn't the point of any mash to convert starches into sugars, so the yeast have something to ferment? Thus, there'll always be sugar at the end (unless the masher screwed up and no conversion occured). Of course, you probably meant added sugar, but you didn't say that.:-)
Plus, there's plenty of whiskey made from malted barley as well as (and instead of) the grains you mentioned.
Would that be the beginning of the mash, or the end of the mash? Technically, maltose is a sugar. And even if it's the beginning, I guess that means no beer with crystal malt in the mash?
Re:Because pseudo-compiled languages are better..
on
How C# Was Made
·
· Score: 1
So don't use char *. In D, you can pass the array itself by reference, which includes size information. Dynamically resizeable arrays are also available.
My point was that it has nothing to do with whether the code runs in a virtual machine or not.
Re:Because pseudo-compiled languages are better..
on
How C# Was Made
·
· Score: 2, Informative
You can get garbage collection and array bounds checking in fully compiled languages (such as D), too.
And you'd better still worry about such things to a certain extent, or else you'll be throwing exceptions on legitimate usage cases when your fixed-size buffer turned out to be too small, running out of memory because you didn't bother nuking references to old objects, etc.
I'm not talking about the patent clause. I'm
talking about section 2, clause b, which says
that any derived works have to be licensed
"at no charge to all third parties under the
terms of this license". Even if "at no charge" weren't there, since it has to be the same terms as the original,
Section 1 grants the right to royalty-free distribution
(and thus that right must be granted for derivative works as well). This goes way beyond source code availability.
Sure, you can try to charge copying fees, but
that's not the same thing, and anyone else can
easily undercut you, since they didn't have to expend the development effort.
108 days was just for one hard drive. I don't know exactly how many drives would constitute being full of them, but it'd only take two drives to exceed 6 months.
Which makes it even more of a shame that I have
to pay for that build quality for a mouse I'm
never going to use, just because it comes with
a system that I want.
Water goes down smoother than any beer; I'd expect it to still be the case if you added enough vodka to bring it up to a typical beer's strength. However, some of us want more than just alcohol, "goes down smooth", and cheapness from our beers.
Slashdot Mirror
In the US you can open a bank with about $500 worth of paperwork. As a result there are about 2-3 banks per person.
Are you seriously claiming that there are over 600 million banks in the US?
The banks dont talk to each other. They dont have a common banking network.
So explain to me why I can use my ATM card in any bank's ATM (albeit for a small fee), wire money between accounts of different banks, have my paycheck deposited directly in my account without my employer having to have arrangements with the specific bank I use, cash or deposit a check drawn on another bank, etc.
They often go belly up taking all of their customers money with them.
Accounts are insured by the federal government up to $100,000 in the event that that happens.
As we get a lot of US media, I am aware that VISA is pushing hard there "cheque card". In Canada you have been able to use your ATM card in retail outlets for a decade.
I got a "check card" (usable like any normal VISA) automatically when opening a U.S. account about 8 years ago. This isn't new here either.
Yes, you can run the OS in a state of partial functionality (or replaced by other functionality, if you prefer). I was referring to normal use of the OS. Is Aqua also not a part of the OS, because you can use X instead?
Hell, I could just boot Linux instead; even the Darwin kernel must not count. :-)
Yeah, it's "just another app" that is installed with the OS, starts at bootup, can't be shut down (only restarted), and gets focus whenever you click on an unused area of the screen. Oh, and there's the minor issue of it being the primary way the OS provides to let users interact with their files.
There's more to an OS than the kernel...
Because, like spam, it is a behavioral problem, not purely a technical problem. System break-ins and e-mail worms can be prevented by technical means as well, but that doesn't mean it should be legal to carry them out.
It's rare, but it does happen. I once had a compilation fail claiming an unrecognized preprocessor directive #inclufe (or something similarly off by one bit). It was not that way in the file, and compiling it again succeeded.
It's kind of scary to think about what could have happened if it were a production build, and it had happened in a way that did not render the file uncompileable.
I'd imagine that, at least on a workstation/desktop, a lot of such errors go unnoticed, hitting unused RAM (such as cache that isn't used again, or the code/data for one of the fifty billion features of $BLOATED_APP that the user never uses...). Then again, given typical software quality, how many times would, upon seeing something crash or behave strangely, one think, "must have been a bit error!"?
So what if they let you take it back? You've already bought it at that point. It's yours. As long as you don't violate copyright (or other specific laws), what obligates you to accept their additional terms before using your software?
If you can access the machine well enough to use vi on it, you can probably get a copy of joe onto it as well. Learn scp, ya bum.
Seriously, it's kind of silly to use a particular editor just because of its ubiquity. One can be familiar enough with vi to use it (grudgingly) in an emergency, while still using something more pleasant in non-emergencies.
That's why they phrase it as a "use tax". They're not taxing the purchase or importation, just your use of the item within that state's borders. The use tax just happens to have a tax credit for sales tax paid on the same item.
If they charged higher tax on out-of-state goods, or refused to credit for any sales tax paid to the other state (while still exempting things purchased in-state), then you could argue that they're giving preference.
The original poster's "without having to cough up $$$ for the expensive channels" comment doesn't make it sound like he's talking about timeshifting programming that he paid for...
HTTP runs over TCP, which means that to complete a "click", you'll need to be able to receive data at the spoofed IP address and respond based on it (specifically, you need to know the initial sequence number). Unless you can guess what that number is (which is not easy with good TCP code), you won't be able to get the server to listen to you. You might get lucky once in a while, but not enough for an attack that depends on a high rate of success.
As for MACs, they're for the local network only. As Google can't even see your MAC, spoofing it would have fairly little point.
To which I say, yes... you have lost something. You have lost the ability to insure that the end user has access to the source code that you wrote.
No, you haven't. You're still perfectly capable of putting all of your source code up on a website and letting everyone who wants to download it. That they can't get it from specific other people doesn't change that, even if they happen to distribute binaries. Sure, it'd be nice if those who did would at least tell the users about your FTP site, but the terms of the GPL are neither necessary nor (IMO) worth it for that specific goal.
Insuring that users have access to code that other people wrote, that happens to have been combined with code that you wrote, is of course another matter entirely.
Still, isn't the point of any mash to convert starches into sugars, so the yeast have something to ferment? Thus, there'll always be sugar at the end (unless the masher screwed up and no conversion occured). Of course, you probably meant added sugar, but you didn't say that. :-)
Plus, there's plenty of whiskey made from malted barley as well as (and instead of) the grains you mentioned.
Not to mention needing to develop eyes...
Would that be the beginning of the mash, or the end of the mash? Technically, maltose is a sugar. And even if it's the beginning, I guess that means no beer with crystal malt in the mash?
So don't use char *. In D, you can pass the array itself by reference, which includes size information. Dynamically resizeable arrays are also available.
My point was that it has nothing to do with whether the code runs in a virtual machine or not.
You can get garbage collection and array bounds checking in fully compiled languages (such as D), too.
And you'd better still worry about such things to a certain extent, or else you'll be throwing exceptions on legitimate usage cases when your fixed-size buffer turned out to be too small, running out of memory because you didn't bother nuking references to old objects, etc.
Sure, you can try to charge copying fees, but that's not the same thing, and anyone else can easily undercut you, since they didn't have to expend the development effort.
If that's the only goal, then what is that must-be-royalty-free stuff doing in there?
108 days was just for one hard drive. I don't know exactly how many drives would constitute being full of them, but it'd only take two drives to exceed 6 months.
How about spacecraft full of high-capacity hard drives? Just one 150GB drive would take over 108 days to transfer over a 128 kb/s link...
Which makes it even more of a shame that I have to pay for that build quality for a mouse I'm never going to use, just because it comes with a system that I want.
Wouldn't pressing very lightly on the brake accomplish the same thing?
And yes, I've had MGD before. I'll pass.
And since when are there around 1000 bits in a byte? 20996010 bits is approximately 2.5 MiB.
Except for things like leaving out ECC memory, of course..