I agree completely, particularly the part about getting all claims to trademarks away from the other top-level domains. As for the.TM already occupied, what about.TRM? However, there's still the problem about trademarks not being 'unique', take for example 'Apple' which is a valid trademark for a certain computer company as well as for The Beatles' record company (still alive and well as far as I know), and others too. How to resolve that? You would need a whole jungle of next-level domains to sort it out. www.apple.music.trm, www.apple.comp.trm,... This is, of course, a problem exisisting already and not caused by your proposal, but not solved by it either.
There's nothing stopping you from going faster than light speed in non-vacuum (by that I mean faster than 38 miles/second in this case). It happens all the time in physics experiments. It's a bit like going faster than the speed of sound, it will be a light "boom" which is visible as a blue corona. I'm not 100% sure but I believe the blue color of the water in nuclear reactors are caused by this. In any event I have seen many photos of the effect.
The maximum speed of information is the speed of light in vacuum. If information went faster you would be messing up the sequence of cause and effect. The light speed in non-vacuum hasn't got anything to do with this though. (and note that if it's not information it *can* go faster than light, but it's useful for nothing anyway so..)
"I disagree, specifying a preprocessor symbol should not _remove" "features, it should add them when necessary" No. When you define _POSIX_SOURCE this will limit the features to the POSIX subset. This is according to POSIX and it makes sense. How could you you write portable code if you couldn't define an exact environment? If the "default" feature set is bigger than any feature set implied by a particular symbol (e.g. _POSIX_SOURCE) then defining the symbol must remove features. Think about it.
Whatever happened to Fred van Kempen's code?
on
Alan Cox Interview
·
· Score: 1
The interview was just a little bit inaccurate about the details.. If I remember correctly Fred did release something that actually went in (replacing Ross' code), however he then continued to work on new releases without showing anybody the new code (very much Cathedral with himself as the only one in there). Alan fixed and maintained the already released code, and in the end everybody got fed up of waiting for the new stuff to come out of the Cathedral and Alan's version stayed in for good. You can find Fred's copyrights in the code.
"Programs as large as the Linux kernel don't receive comprehensive source reviews often enough" Well I must admit that I don't read the full kernel source when there's a new version, but at least I read every single patch file and I've read all of them since early '92. Lately I've stopped reading most of the new m68k stuff etc., concentrating instead on the platforms I use. So at least it isn't so easy to place any trojan in the patches. I know that many many other people also read all the patches, and there sure are a lot of people looking everywhere in the kernel whenever there' a new version.
- m68k sync - various minor driver fixes (irda, net drivers, scsi, video, isdn) - SGI Visual Workstation support --- THIS LINE WAS THERE WHEN *I* GOT Linus' POSTING - adjtimex update to the latest standards - vfat silly buglet fix - semaphores work on alpha again - drop the inline strstr() that gcc got wrong whatever we did - kswapd needed to be a bit more aggressive - minor TCP retransmission and delack fixes
"Hello, Professor Warwick," his PC announced when Warwick crossed the threshold of his office"
Arrgh.. the talking doors of Sirius Cybernetics in the Hitchhikers Guide To The Galaxy.. why do I feel like Marvin all of a sudden? (but I _would_ like to get a two-way implant for improving my memory!)
>Finally, someone who understands that programming in a GUI IDE is a >lot more powerful than a few xterms running vi and gdb. Who on earth is doing that still? I don't know anybody doing development with xterm/vi/gdb. Everybody here is using XEmacs+ddd (or whatever graphical debugger working well on the particular platform), and that integrated environment is as good as they get (I *did* use the MS and Borland IDEs back when I touched those systems).
I agree completely, particularly the part about getting all claims to trademarks away from the other top-level domains. .TM already occupied, what about .TRM?
As for the
However, there's still the problem about trademarks not being 'unique', take for example 'Apple' which is a valid trademark for
a certain computer company as well as for The Beatles' record company (still alive and well as far as I know), and others too.
How to resolve that? You would need a whole jungle of next-level domains to sort it out.
www.apple.music.trm, www.apple.comp.trm,...
This is, of course, a problem exisisting already and not caused by your proposal, but not solved by it either.
There's nothing stopping you from going faster than
light speed in non-vacuum (by that I mean faster than
38 miles/second in this case). It happens all the time in
physics experiments. It's a bit like going faster than the
speed of sound, it will be a light "boom" which is visible as a blue
corona. I'm not 100% sure but I believe the blue color
of the water in nuclear reactors are caused by this.
In any event I have seen many photos of the effect.
The maximum speed of information is the speed of
light in vacuum. If information went faster you
would be messing up the sequence of cause and effect.
The light speed in non-vacuum hasn't got anything
to do with this though.
(and note that if it's not information it *can* go
faster than light, but it's useful for nothing anyway so..)
"I disagree, specifying a preprocessor symbol should not _remove"
"features, it should add them when necessary"
No. When you define _POSIX_SOURCE this will
limit the features to the POSIX subset. This is
according to POSIX and it makes sense. How could you
you write portable code if you couldn't define an exact
environment? If the "default" feature set is bigger
than any feature set implied by a particular symbol
(e.g. _POSIX_SOURCE) then defining the symbol must
remove features. Think about it.
The interview was just a little bit inaccurate about the details..
If I remember correctly Fred did release something
that actually went in (replacing Ross' code), however
he then continued to work on new releases without
showing anybody the new code (very much Cathedral with
himself as the only one in there). Alan fixed and maintained
the already released code, and in the end everybody got
fed up of waiting for the new stuff to come out of
the Cathedral and Alan's version stayed in for good.
You can find Fred's copyrights in the code.
"Programs as large as the Linux kernel don't receive
comprehensive source reviews often enough"
Well I must admit that I don't read the full kernel source when
there's a new version, but at least I read every single patch file
and I've read all of them since early '92. Lately I've stopped
reading most of the new m68k stuff etc., concentrating instead
on the platforms I use. So at least it isn't so easy to place any trojan in the patches.
I know that many many other people also read all the patches, and there sure are
a lot of people looking everywhere in the kernel whenever there' a new version.
- m68k sync
- various minor driver fixes (irda, net drivers, scsi, video, isdn)
- SGI Visual Workstation support --- THIS LINE WAS THERE WHEN *I* GOT Linus' POSTING
- adjtimex update to the latest standards
- vfat silly buglet fix
- semaphores work on alpha again
- drop the inline strstr() that gcc got wrong whatever we did
- kswapd needed to be a bit more aggressive
- minor TCP retransmission and delack fixes
"Hello, Professor Warwick," his PC announced when Warwick
crossed the threshold of his office"
Arrgh.. the talking doors of Sirius Cybernetics
in the Hitchhikers Guide To The Galaxy.. why do I feel
like Marvin all of a sudden?
(but I _would_ like to get a two-way implant for improving my memory!)
>Finally, someone who understands that programming in a GUI IDE is a
>lot more powerful than a few xterms running vi and gdb.
Who on earth is doing that still? I don't know
anybody doing development with xterm/vi/gdb.
Everybody here is using XEmacs+ddd (or whatever
graphical debugger working well on the particular
platform), and that integrated environment is as
good as they get (I *did* use the MS and Borland
IDEs back when I touched those systems).