A way to swap Caps Lock and Control is hardware issue because keyboards on the *books are actually adb keyboards and that have the limitation of the `caps lock' being in that spot.
first it is not Xwindows but X Window System. 2nd this is not a problem of LINUX but of the X Window System most LINUX distubutions are using, but they have not developed a way to do it.
No it is not but the problem is part of glibc because it is the part that runs the ld.linux.so so it is there where it needs to fix the speed problems.
In fact on ia64 you can use c++ code compiled with the Intel compiler and the HP compiler and GCC and it will be able to link which is a good thing and work (there are a few exceptions because the HP and Intel are know to have ABI bugs in them, they might get fixed soon though).
Windows NT/2000/XP is no where near UN*X as much as Linux and *BSD are. Mainly because of the idea of a kernel and what goes into it. The Windows server in Windows NT/2K/XP is part of the kernel while under UN*X, it is an userland program. And also Mac OS X, *BSD are based loosely around the UNIX source. Also Linux is inspired by MINIX which is inspired by UNIX.
Plan 9 is not UN*X but Mac OS X is and uses UTF-8 and UTF-16 for almost everything, and has a lot of fonts to support the different languages (Japanese, Chinese [Both traditional and Simplified], Korean, and other languages).
Also Don't use any of the M$ products for the Mac because they do not support Unicode at all.
Use OmniWeb for a Web Browser and Just use TextEditor for an word editor.
Also Terminal uses UTF8 for the default encoding, you can change this if you want.
There is already a high-level shading language, even LGPLed, the API is from Apple's QuickDraw3D, it is called Quesa, http://www.quesa.org/. It can sit above any other API, such as OpenGL or Direct3D. It is scene ordinated. It is a pretty cool api, it is a lot easier to use than Direct3D or OpenGL. The file format to save the scene is 3DMF binary or text (XML like); in fact the binary format was appointed to be the binary format for VMRL.
There is even a paper about the problems of integrating the UNIX and Mac OS Environments: http://www.mit.edu/people/wsanchez/ papers/USENIX_2 000/, it talks about more than just case sensitive but there were a few more problems than that going from UFS to HFS+. Also it takes about how to go from a single user system to a multiple user system and back.
One more option, they want to payed twice if the people who are buying the machine already have license for M$ software for all machines in their company/university, they want to get payed also for each new machine. Which is crap for the company/university because they have to pay twice for the software they already license.
UT has OS X support, it has been mentioned on macledge.com all the time.
For 1, the program is not potable to many UNIX's because most do not have /proc.
2) it cannot be ported to Linux on PPC any way.
3) like dlopen? there is a wrapper for it on Darwin.
4) well then you cannot use Linux PPC any ways.
INT 0D is reserved according to my asm book.
What about FireWire faster than fast ethernet and is peerless. Apple just released a reference driver.
A way to swap Caps Lock and Control is hardware issue because keyboards on the *books are actually adb keyboards and that have the limitation of the `caps lock' being in that spot.
Jordan Hubbard is not a former LINUX user, he is a former BSD developer of FreeBSD.
first it is not Xwindows but X Window System.
2nd this is not a problem of LINUX but of the X Window System most LINUX distubutions are using, but they have not developed a way to do it.
first it was the 90's but Jobs also did it at NeXT and it also almost killed NeXT.
http://trafac.chmcc.org
It is a bioinformatics web site for finding promoters in DNA sequences.
I did not design it, I work on it though (use and develop it).
M$ does not have any say into Apple because their shares are nonvoting ones.
I just noticed that, I cannot add.
There is one misprint:
256 + 652 is not 908 but 808.
ASS (AppleScript Studio) is Apple's replacement for HyperCard. It uses Cocoa to do must of its job.
If you look again, you will see that it was not focused on the left side but on the right, so the right side is not blurry.
3.4 likely, Apple will be submitting their precompiled headers (PFE) after 3.3 comes out.
gcc is not fully standards compliant when it comes to c++, this is being fixed via a new parser.
No it is not but the problem is part of glibc because it is the part that runs the ld.linux.so so it is there where it needs to fix the speed problems.
I though the problem had been fixed in the cvs version of glibc?
In fact on ia64 you can use c++ code compiled with the Intel compiler and the HP compiler and GCC and it will be able to link which is a good thing and work (there are a few exceptions because the HP and Intel are know to have ABI bugs in them, they might get fixed soon though).
Windows NT/2000/XP is no where near UN*X as much as Linux and *BSD are. Mainly because of the idea of a kernel and what goes into it.
The Windows server in Windows NT/2K/XP is part of the kernel while under UN*X, it is an userland program. And also Mac OS X, *BSD are based loosely around the UNIX source. Also Linux is inspired by MINIX which is inspired by UNIX.
Plan 9 is not UN*X but Mac OS X is and uses UTF-8 and UTF-16 for almost everything, and has a lot of fonts to support the different languages (Japanese, Chinese [Both traditional and Simplified], Korean, and other languages).
Also Don't use any of the M$ products for the Mac because they do not support Unicode at all.
Use OmniWeb for a Web Browser and Just use TextEditor for an word editor.
Also Terminal uses UTF8 for the default encoding, you can change this if you want.
That means Windows is out the window because it is not POSIX compliant and certified, so is Linux, *BSD, and Mac OS X.
It is one thing to follow the standards close but still have divergence from it for the good.
There is already a high-level shading language, even LGPLed, the API is from Apple's QuickDraw3D, it is called Quesa, http://www.quesa.org/. It can sit above any other API, such as OpenGL or Direct3D. It is scene ordinated. It is a pretty cool api, it is a lot easier to use than Direct3D or OpenGL. The file format to save the scene is 3DMF binary or text (XML like); in fact the binary format was appointed to be the binary format for VMRL.
There is even a paper about the problems of integrating the UNIX and Mac OS Environments:/ papers/USENIX_2 000/, it talks about more than just case sensitive but there were a few more problems than that going from UFS to HFS+. Also it takes about how to go from a single user system to a multiple user system and back.
http://www.mit.edu/people/wsanchez
One more option, they want to payed twice if the people who are buying the machine already have license for M$ software for all machines in their company/university, they want to get payed also for each new machine. Which is crap for the company/university because they have to pay twice for the software they already license.