Depends on the clause... When I was under one, breaking it meant paying back certain (non-salary) expenses, like cost of insurance, college courses, training, relocation expenses, etc. I know plenty of people that have had new companies cover non-compete expenses. Higher level executives are more problematic (I vaguely recall MS suing google over that).
how do you think they know if a domain is available? They ask other people. Lots of other people can and do see it.
Re:Good reporting there, submitter
on
LLVM 2.2 Released
·
· Score: 5, Informative
Exactly! From the clang readme. Half of these things are a nice feature for XCode/IDE integration.
III. Current advantages over GCC:
* Column numbers are fully tracked (no 256 col limit, no GCC-style pruning).
* All diagnostics have column numbers, includes 'caret diagnostics', and they
highlight regions of interesting code (e.g. the LHS and RHS of a binop).
* Full diagnostic customization by client (can format diagnostics however they
like, e.g. in an IDE or refactoring tool) through DiagnosticClient interface.
* Built as a framework, can be reused by multiple tools.
* All languages supported linked into same library (no cc1,cc1obj,...).
* mmap's code in read-only, does not dirty the pages like GCC (mem footprint).
* LLVM License, can be linked into non-GPL projects.
* Full diagnostic control, per diagnostic. Diagnostics are identified by ID.
* Significantly faster than GCC at semantic analysis, parsing, preprocessing
and lexing.
* Defers exposing platform-specific stuff to as late as possible, tracks use of
platform-specific features (e.g. #ifdef PPC) to allow 'portable bytecodes'.
* The lexer doesn't rely on the "lexer hack": it has no notion of scope and
does not categorize identifiers as types or variables -- this is up to the
parser to decide.
Potential Future Features:
* Fine grained diag control within the source (#pragma enable/disable warning).
* Better token tracking within macros? (Token came from this line, which is
a macro argument instantiated here, recursively instantiated here).
* Fast #import with a module system.
* Dependency tracking: change to header file doesn't recompile every function
that texually depends on it: recompile only those functions that need it.
This is aka 'incremental parsing'.
Re:Good reporting there, submitter
on
LLVM 2.2 Released
·
· Score: 1
The FSF requires all GCC contributions to be assigned to the FSF. Apple has contributed code to GCC. What if Apple (or any other contributor) supports the GPL v2, but not v3? The FSF has the legal right to update the license (to GPL v3 or closed source proprietary), but that code was contributed under the GPL v2 license.
Re:Good reporting there, submitter
on
LLVM 2.2 Released
·
· Score: 1
In the OS 8/9 days, Apple experimented with Linux. The result: mkLinux. That was 1995/1996, before Steve Jobs returned, but Apple was involved until 1998.
I've heard rumors (from a couple different sources) that Apple considered replacing the OpenStep/OS X BSD kernel with mklinux but considered it unsuitable for technical, not legal, reasons.
I check labels when I'm at the store and also search the internet beforehand. There are some sites with a list of American made products, but they have a tendency to be out of date. Manufacturer web sites sometimes mention if a product is US made.
I find it easier to buy American goods at Walmart than many other stores. I make an effort to buy American (or European) products even if it is more expensive. Imported third world shit has no value to me, so it's overpriced at any cost. Of course, I make enough money that paying a premium for premium quality is worth it to me.
There are hundreds of thousands, perhaps millions, of people with a local account and shell on a $5/month linux webhosting plan. Many of those people don't know what they're doing (the users and the admins), use guesable passwords, etc. Add in the phpbb, etc. exploits and every script kiddy in the world has shell access to a linux machine.
It's not compatible with GPL 2. It's not compatible with GPL 3. The googles of the world are already using GPL (2 or 3) software and won't be affected.
Is GNU a strong selling point for using *BSD? gcc, gdb, bison, bash, as, emacs, groff, make, and tar are the only OS X GNU command line tools I can find.
Microsoft offered $31/share for a stock that was trading at $18 (not $12, my bad)/share. With the recent layoffs, declining profit, being bought looks pretty good.
Slashdot Mirror
in the same vein, showing extended characters when holding the option key (on a Macintosh, not a Piece of Chit).
There's this wiki TeX Editor page. (I'm a happy TexShop user).
Depends on the clause... When I was under one, breaking it meant paying back certain (non-salary) expenses, like cost of insurance, college courses, training, relocation expenses, etc. I know plenty of people that have had new companies cover non-compete expenses. Higher level executives are more problematic (I vaguely recall MS suing google over that).
how do you think they know if a domain is available? They ask other people. Lots of other people can and do see it.
Exactly! From the clang readme. Half of these things are a nice feature for XCode/IDE integration.
...).
III. Current advantages over GCC:
* Column numbers are fully tracked (no 256 col limit, no GCC-style pruning).
* All diagnostics have column numbers, includes 'caret diagnostics', and they
highlight regions of interesting code (e.g. the LHS and RHS of a binop).
* Full diagnostic customization by client (can format diagnostics however they
like, e.g. in an IDE or refactoring tool) through DiagnosticClient interface.
* Built as a framework, can be reused by multiple tools.
* All languages supported linked into same library (no cc1,cc1obj,
* mmap's code in read-only, does not dirty the pages like GCC (mem footprint).
* LLVM License, can be linked into non-GPL projects.
* Full diagnostic control, per diagnostic. Diagnostics are identified by ID.
* Significantly faster than GCC at semantic analysis, parsing, preprocessing
and lexing.
* Defers exposing platform-specific stuff to as late as possible, tracks use of
platform-specific features (e.g. #ifdef PPC) to allow 'portable bytecodes'.
* The lexer doesn't rely on the "lexer hack": it has no notion of scope and
does not categorize identifiers as types or variables -- this is up to the
parser to decide.
Potential Future Features:
* Fine grained diag control within the source (#pragma enable/disable warning).
* Better token tracking within macros? (Token came from this line, which is
a macro argument instantiated here, recursively instantiated here).
* Fast #import with a module system.
* Dependency tracking: change to header file doesn't recompile every function
that texually depends on it: recompile only those functions that need it.
This is aka 'incremental parsing'.
The FSF requires all GCC contributions to be assigned to the FSF. Apple has contributed code to GCC. What if Apple (or any other contributor) supports the GPL v2, but not v3? The FSF has the legal right to update the license (to GPL v3 or closed source proprietary), but that code was contributed under the GPL v2 license.
In the OS 8/9 days, Apple experimented with Linux. The result: mkLinux. That was 1995/1996, before Steve Jobs returned, but Apple was involved until 1998.
I've heard rumors (from a couple different sources) that Apple considered replacing the OpenStep/OS X BSD kernel with mklinux but considered it unsuitable for technical, not legal, reasons.
I check labels when I'm at the store and also search the internet beforehand. There are some sites with a list of American made products, but they have a tendency to be out of date. Manufacturer web sites sometimes mention if a product is US made.
leopard betas supported AEBS/time machine usage.
I find it easier to buy American goods at Walmart than many other stores. I make an effort to buy American (or European) products even if it is more expensive. Imported third world shit has no value to me, so it's overpriced at any cost. Of course, I make enough money that paying a premium for premium quality is worth it to me.
nah... this is a nasty hole.
that's the drawback of a monolithic kernel. You need to recompile to add or remove offensive parts. And those offensive parts aren't sandboxed.
There are hundreds of thousands, perhaps millions, of people with a local account and shell on a $5/month linux webhosting plan. Many of those people don't know what they're doing (the users and the admins), use guesable passwords, etc. Add in the phpbb, etc. exploits and every script kiddy in the world has shell access to a linux machine.
Maybe they should use hello.jpg
It's not compatible with GPL 2. It's not compatible with GPL 3. The googles of the world are already using GPL (2 or 3) software and won't be affected.
Is GNU a strong selling point for using *BSD? gcc, gdb, bison, bash, as, emacs, groff, make, and tar are the only OS X GNU command line tools I can find.
and a few graduate students.
Of course, roff/nroff/troff were used for typesetting 10 years before that.
More of that $3 a gallon gasoline goes to state and federal gov't (via taxes) than to those evil oil companies (via profit).
Having talked to MySQL about licensing the proprietary version, all I can say is you're full of shit.
OpenStep property lists kick json's ass 7 ways to sunday.
Im thinking of MySQL. I'm thinking of the closed source version they sell.
They're losing employees. And by losing, I mean firing.
Microsoft offered $31/share for a stock that was trading at $18 (not $12, my bad)/share. With the recent layoffs, declining profit, being bought looks pretty good.
Last I checked, $31 is greater than $12.
here you go!