You are wrong. Most egregiously wrong for someone whose addy is in Finland.
Europe has allowed typography to be copyright, whereas the USA has not.
Designing a good font is hard. Many, many hours of work by a talented artist. Prior to computers, this was all manual, and resulted in a set of designs to be cut into cold type.
Without copyright, anyone could take a printed sample, recut it (and bear in mind that the original font was cut from a picture), rename it (to avoid trademark---say, call it Swiss rather than Helvetica) and sell the font as their own.
In fact, that is allowed in North America. It has generally not been allowed in Europe
Does your ISP filter spam for you? If so, I presume it does not count against your download cap. I also assume that the ISP has to archive all this spam that you never wanted, or read, or even received, but which was nevertheless sent to you.
So, every piece of spam to enter Argentina has to be archived for ten years?
Do they also archive every port scan, every ping, every Blaster and Sasser packet? Every ARP?
In 1793, failure to accept the French paper money was made punishable by death and the punishment was actually imposed as demonstrated by the lists of those condemned to the guillotine.
And yes, I was refering to a long time ago: about the 17th or 18th century I think
Back when paper money was first used in Britain, passing conterfeit money was a felony.
The punishment for a felony---any felony, was death.
Some people were not happy with taking paper money, rather than good, solid gold sovereigns. So, refusal to take the new paper money was made an offence---was made a felony!
sometimes I think the law is not tough enough because we do not yet know how to effectively identify and prosecute the offenders
The law is tough, and becoming tougher, because we do not yet know how to effectively identify and prosecute the offenders.
Spammers (as a generalisation), do it for financial reward. Negative reward is applied in the form of laws against spam. However, the chance of being caught is so low, that this is no real disincentive. Thus, in order to make it not worthwhile to spam, we have to either
Raise the probability of being caught and punished
Apply higher penalties
Eventually, a rational spammer will decide that penalty×prob_penalty_being_applied > profit, and will give up.
Since prob_penalty_being_applied is currently so low, the tempation is to make penalty very high.
But that has its own risks. Remember, you might as well be hung for a sheep as for a lamb. Draconian penalties usually result in offenders who 'shoot back'. A spammer facing 25 years as a guest of the authorities, might just be willing to take fairly extreme methods to avoid prosecution.
iCab allows this, and more. You can set JavaScript capabilities, filters, Cookie handling, identification string and other behaviours on a per site (per regexp URL actually).
One of the coolest things about iCab, if a little tricky to set up right.
DOCSIS 2.0 gives up to (roughly) 40Mbps down and 10Mbps up on really good cable plant. DOCSIS 1.0/1.1 manage uploads of 5Mbps maybe, 2Mbps more typically.
ADSL can get 8Mbps down, on a good day with a following wind. Any distance from the DSLAM and 2Mbps is far more likely to be the maximum. The ADSL forum says that 640kbps is the max upstream on ADSL. In fact, some kit can pull approaching 1Mbps, but that's it. Even ADSL2plus doesn't raise the upstream by very much.
Anyway, ADSL/Cable are inhernently asymmetric in speed, so a 4:1 down:up speed ratio is sensible and common.
Real speed requires something like fibre to the home, i.e. expending serious money in new infrastructure build rather than using the Technology Genie to wring slightly more performance out of sunk capital.
Hey, we have to find a use for all those IPv6 addresses somehow.
To some extent, it does not matter whether or not the razor is networked. The prospect of a universal power supply standard (that happens to provide networking) is interesting in its own right.
Which is a very interesting thought. Power has been essentially considered 'free', except for laptops. The concern has been much more with cooling. PoE though could provide a huge impetus for low power PCs. Eventually.
That ARM chip starts to look really interesting...
My understanding is that IOkit is quite different from Mach or FreeBSD---to the extent that drivers have to be pretty much rewritten from scratch. I also thought (though I'd be happy to be corrected) that the memory subsystem, and in particular the multiprocessor stuff, was mostly Mach. In fact, mostly 'Darwin' by now.
If the 'problematic' bits of FreeBSD 5.x are in the memory, threading and driver sections, then I would not expect those to have much relevance to Darwin, and hence would be no barrier to Darwin adopting the rest of FreeBSD 5.x as much a possible.
I appear, from the above link, to have a little dismissive of the contribution of FreeBSD as 'just' userland.
Re:Retrospect has done this for years
on
Tiger Early Start Kit
·
· Score: 2, Interesting
Does it MD5 them though? I thought it looked at the size, last mod date and a few other things, but did not run a digest over the whole file. I.e. it tries to be 'smart', or at least 'cheap', when calculating a signature. I've fairly sure that if you take a file and save it over itself without changing the contents that Retrospect will back up the whole file, because it thinks it has changed.
And also, Retrospect already does something like this and has for years. It's not particularly innovative. The interesting thing is detecting identical files. Having the operating system calculate MD5's for you seemed to me the interesting thing.
In a nutshell, every time a file is saved, it is examined for meta-data and content, which is then placed into an indexed database.
I wonder if Spotlight calculates (or could be made to calculate) an MD5 for the file. This would be useful for backup. If the backup program looks up a file's MD5 in its catalog and finds it already there, no need to back up again. This would survive arbitrary renaming or moving (the metadata would still need to be backed up for each file), and would make for major efficiencies when backing up multiple machines on a network (only one copy of Hei.dfont, Osaka.dfont, xxx.App, etc. in the backup set).
BTW MacOS X 10.4 (Tiger) is based on 5.x rather than 4.x technology so someone's trusting enough..
That's just the BSD subsystem---i.e. userland. Memory and I/O in particular have almost nothing in common with BSD and so FreeBSD UP vs MP performance etc. are not going to have any effect on Darwin.
I'd be interested to know long it will be before the ports tree has reasonably complete support for 5.3.
Slashdot Mirror
Europe has allowed typography to be copyright, whereas the USA has not.
Designing a good font is hard. Many, many hours of work by a talented artist. Prior to computers, this was all manual, and resulted in a set of designs to be cut into cold type.
Without copyright, anyone could take a printed sample, recut it (and bear in mind that the original font was cut from a picture), rename it (to avoid trademark---say, call it Swiss rather than Helvetica) and sell the font as their own.
In fact, that is allowed in North America. It has generally not been allowed in Europe
Does your ISP filter spam for you? If so, I presume it does not count against your download cap. I also assume that the ISP has to archive all this spam that you never wanted, or read, or even received, but which was nevertheless sent to you.
So, every piece of spam to enter Argentina has to be archived for ten years?
Do they also archive every port scan, every ping, every Blaster and Sasser packet? Every ARP?
And yes, I was refering to a long time ago: about the 17th or 18th century I think
Back when paper money was first used in Britain, passing conterfeit money was a felony.
The punishment for a felony---any felony, was death.
Some people were not happy with taking paper money, rather than good, solid gold sovereigns. So, refusal to take the new paper money was made an offence---was made a felony!
Still not good enough Superman. http://www.rawbw.com/~svw/superman.html
The law is tough, and becoming tougher, because we do not yet know how to effectively identify and prosecute the offenders.
Spammers (as a generalisation), do it for financial reward. Negative reward is applied in the form of laws against spam. However, the chance of being caught is so low, that this is no real disincentive. Thus, in order to make it not worthwhile to spam, we have to either
Eventually, a rational spammer will decide that penalty×prob_penalty_being_applied > profit, and will give up.
Since prob_penalty_being_applied is currently so low, the tempation is to make penalty very high.
But that has its own risks. Remember, you might as well be hung for a sheep as for a lamb. Draconian penalties usually result in offenders who 'shoot back'. A spammer facing 25 years as a guest of the authorities, might just be willing to take fairly extreme methods to avoid prosecution.
One of the coolest things about iCab, if a little tricky to set up right.
That sounds like an Exchange Server replacement. It doesn't sound like a free Exchange Server replacement.
So, doesn't this now start to sound more like a free Exchange Server replacement?
DOCSIS 2.0 gives up to (roughly) 40Mbps down and 10Mbps up on really good cable plant. DOCSIS 1.0/1.1 manage uploads of 5Mbps maybe, 2Mbps more typically.
ADSL can get 8Mbps down, on a good day with a following wind. Any distance from the DSLAM and 2Mbps is far more likely to be the maximum. The ADSL forum says that 640kbps is the max upstream on ADSL. In fact, some kit can pull approaching 1Mbps, but that's it. Even ADSL2plus doesn't raise the upstream by very much.
Anyway, ADSL/Cable are inhernently asymmetric in speed, so a 4:1 down:up speed ratio is sensible and common.
Real speed requires something like fibre to the home, i.e. expending serious money in new infrastructure build rather than using the Technology Genie to wring slightly more performance out of sunk capital.
Very good point.
To some extent, it does not matter whether or not the razor is networked. The prospect of a universal power supply standard (that happens to provide networking) is interesting in its own right.
Does your razor take AA cells? Or AAA, or C, or, ...
Now, imagine a universal, world-wide standard for low power devices. Would that be useful?
Which is a very interesting thought. Power has been essentially considered 'free', except for laptops. The concern has been much more with cooling. PoE though could provide a huge impetus for low power PCs. Eventually.
That ARM chip starts to look really interesting...
Aaargh! /me blushes.
Because the cable trailing along behind the plane is unsightly and tends to exceed the 100m limit quite rapidly.
I'd say that it's not just like robbing a bank, only worse.
That doesn't mean I think the sentence is unfair.
I hear the series is to be renamed "Grand Theft IP: ..."
My understanding is that IOkit is quite different from Mach or FreeBSD---to the extent that drivers have to be pretty much rewritten from scratch. I also thought (though I'd be happy to be corrected) that the memory subsystem, and in particular the multiprocessor stuff, was mostly Mach. In fact, mostly 'Darwin' by now.
If the 'problematic' bits of FreeBSD 5.x are in the memory, threading and driver sections, then I would not expect those to have much relevance to Darwin, and hence would be no barrier to Darwin adopting the rest of FreeBSD 5.x as much a possible.
I appear, from the above link, to have a little dismissive of the contribution of FreeBSD as 'just' userland.
Actually, no. Right mountain, wrong climber.
Does it MD5 them though? I thought it looked at the size, last mod date and a few other things, but did not run a digest over the whole file. I.e. it tries to be 'smart', or at least 'cheap', when calculating a signature. I've fairly sure that if you take a file and save it over itself without changing the contents that Retrospect will back up the whole file, because it thinks it has changed.
And also, Retrospect already does something like this and has for years. It's not particularly innovative. The interesting thing is detecting identical files. Having the operating system calculate MD5's for you seemed to me the interesting thing.
I wonder if Spotlight calculates (or could be made to calculate) an MD5 for the file. This would be useful for backup. If the backup program looks up a file's MD5 in its catalog and finds it already there, no need to back up again. This would survive arbitrary renaming or moving (the metadata would still need to be backed up for each file), and would make for major efficiencies when backing up multiple machines on a network (only one copy of Hei.dfont, Osaka.dfont, xxx.App, etc. in the backup set).
That's just the BSD subsystem---i.e. userland. Memory and I/O in particular have almost nothing in common with BSD and so FreeBSD UP vs MP performance etc. are not going to have any effect on Darwin.
I'd be interested to know long it will be before the ports tree has reasonably complete support for 5.3.