If you're going to be a nitpicky law student, read more carefully. "OSX window manager functionality" -- there was no direct article before OSX. Contrast the statement with "THE OSX Window Manager functionality" -- as I read the statement, it meant the *available* functionality on OSX was a superset of linux -- meaning you have Aqua (the OS X window Manager) in addition to the world of available WMs.
X11 and Aqua side by side
Native Aqua and X11 applications run side by side on the Mac OS X desktop. You can cut and paste between X11 and Aqua windows. You can minimize X11 windows to the Dock -- even with the "Genie Effect." You use the Aqua window controls to close, minimize and zoom X11 windows. And of course, each X11 window comes with its own carefully rendered drop shadow.
Experts may choose to replace the native Aqua window manager with their own familiar, standard X Window Manager. [Emphasis Added]
So in short, OP was correct.:)
Btw, where are you a law student? I start my 1L year either fall 05 or 06 and wouldn't mind some feedback -- my degree is a masters/bachelors in CS...
-b
The problem is that random access memory has gone full circle. We once started with tape -- so all of your sorting algorithms had to be sensitive to the fact that you only had sequential reads. The problem with random access memory is that when it is over the network, the latency becomes HUGE in comparison to the rest of the memory heirarchy. The algorithm works just fine on a local SCSI or IDE hard drive, but begins sucking hard over ethernet. (ESPECIALLY w/collisions) To fix it, they'd need to stop using stock B tree algorithms and go back to "old" technology -- that is, algorithms that take into account that random disk accesses cost you time. That way, they can queue a whole bunch of data from over the network, and then treat it (in local cache) like a segment of a tape. This problem is quite common in large datasets.
> I've got a reasonable idea what a balanced tree is but no idea how you'd write one... never needed to.
*cringe*
This works just fine until something doesn't work *perfectly*, and then all hell breaks loose. I will give you a real world example. I'm currently working at a law firm (I'm starting law school in either fall 05 or 06) that uses a common "indstry standard" database tool -- it is a flat-file DB that uses B+ trees. [B trees are like binary trees, but they have many children instead of two, and B+ trees store information only in the leaves.] The idea between B+ trees is that because of the high degree of branching of the tree, you should never have to take more than 2-3 "slow memory" accesses to find your page. (i.e. the entire first node lives in memory. assuming a branching factor of 256, 16777216 records can be accessed within 3 accesses.) Building these trees is also a time-intensive process since there are a lot of writes that happen to parent nodes, and it is very likely that pages get flushed from virtual memory. The problem is that no one has a CS background and so no one understands the memory heirarchy, virtual memory, caching, write-on-update, LRU/MRU page replacement, et cetera, so when Concordance is *slow as all hell* -- no one knows why. [The answer is: When indexing a large database, the programmers seem to have been sloppy and the main node spills over onto a second memory page. Once other nodes begin to spill over, you get a case of "thrashing" in which every time your computer pulls a node back into the "working set" of what lives in physical memory, it kicks what you need out of virtual memory. Google for "thrashing" and the "row-major" and "column-major" order problem.]
*My* firm took a huge risk and hired someone with a CS degree (masters) rather than a paralegal, and they did some experimenting. I've gotten under-the-hood of many of their apps, and the things I've discovered have been shocking. (And these are industry "standard" solutions.) They've reaped the benefits of having someone that actually understands the underlying technology. Here is the archetypical example:
class foo has many pieces of data stored -- lets assume it stores names. class foo doesn't expose any of its methods, and the vendor doesn't give you anything other than the interface, which is: foo.getXelement(x,sort) -- returns the xth element of the array in the sorted order you select, and foo.getAllelements() -- returns the entire array in no specific order. [foo provides other functions not listed here] Now, lets assume you want to get the array, sort it, and print it out. You can a) call foo.getAllelements() and sort/print results b) for (int i =0; i < foo.getmaxElements(); i++) { print foo.getXelement(i, "ASC");} [call getXelement for every element in ascending order...]
BUT: I am giving you a secret peek at the innards of foo!
foo stores data as a linked list (so it can add easily) when you call foo.maxElements, it scrolls through the WHOLE LIST to find the size. furthermore, when you call "getXelement(x,sort)" -- it must go through the WHOLE list, then sort it, and return it to you. [approx n^2logn time] Lets say instead of getXelement(x,sort) it was just getXelement(x) -- which gave you the UNSORTED xth element of the array -- because it is a linked list, it would still need to go through x-1 nodes, resulting in a case of making an nlogn algorithm [comparison based sorting should be nlogn] an n^2 algorithm.
Very long story short: at some level, there must be someone technical so when things "go wrong" (like why many people accessing a shared harddrive over ethernet for disk intensive operations is a bad idea due to the nature of a bus architecture...) all hell doesn't break loose.
You joe-job your competitor from a comprimised relay in China. There is no money trail to follow. Punitive solutions will *not* work. (Far worse to punish one innocent small-business than it is to let 10 spammers go free...)
-b
I'm a product of the (high school) public education system as well. There is nothing wrong with public schooling in many parts of the country. The generalizations that "ALL public schools are x" or "they cannot produce students capable of y" are pure bull. Public school has taken me quite far in life. Let poor Horace Mann sleep in peace; just because *you* wasted your time in public school doesn't imply that the rest of us did.
However, bonus points for the honesty to admit you made a mistake. Perhaps that is one benefit of coming from a public school background? Many of the Adoverites and Exeterites I went to college with were incapable of doing so... (Public school got me into a wonderful university [check post history]...so don't knock it. )
GGP wrote "plunder" our inboxes. Clearly, no one is stealing anything from our inboxes. (They have no capacity to rapaciously steal everything in sight, leaving destruction in their wake.) Clearly, GGP meant "plague" our inboxes, as pointed out by GP's oh-so-witty "plague" Slashdot. (in ITALICS) However, GP is a douche that doesn't know what grammar really is, as GGP was grammatically correct, albeit with nonsensical diction.
One entry found for diction.
Main Entry: diction
Pronunciation: 'dik-sh&n
Function: noun
Etymology: Latin diction-, dictio speaking, style, from dicere to say; akin to Old English tEon to accuse, Latin dicare to proclaim, dedicate, Greek deiknynai to show, dikE judgment, right
1 obsolete : verbal description
2 : choice of words especially with regard to correctness, clearness, or effectiveness
Main Entry: grammar
Pronunciation: 'gra-m&r
Function: noun
Etymology: Middle English gramere, from Middle French gramaire, modification of Latin grammatica, from Greek grammatikE, from feminine of grammatikos of letters, from grammat-, gramma -- more at GRAM
1 a : the study of the classes of words, their inflections, and their functions and relations in the sentence b : a study of what is to be preferred and what avoided in inflection and syntax
2 a : the characteristic system of inflections and syntax of a language b : a system of rules that defines the grammatical structure of a language
3 a : a grammar textbook b : speech or writing evaluated according to its conformity to grammatical rules
4 : the principles or rules of an art, science, or technique a grammar of the theater
S/He had the right word class (transitive verb in the infintive form) -- but a poor word choice. Her/His grammar and syntax were correct. S/He was wrong in the semantics of his word choice. Grammar defines what classes of words are acceptable in what order. Clearly, the statement that someone is "... plunder[ing] slashdot" doesn't mean the same thing as someone "... harassing slashdot" -- yet in that context, plunder is not grammatically incorrect. It makes no sense, but it is by no means an improperly formed statement. [See also Chomsky and every compilers class EVER to implement LALR(1) for more on parsing/grammars/et cetera]
If you're going to be a "Language Nazi", be sure of your exact type....
Life at goldman really isnt so bad. Sollie is much more notorious for being a sweatshop.
My friend is an entry level at goldman and he's steady 7-6. Given salaries in the industry... I can't see how anyone would complain. The 100+ at sollie, however, can be crazy. [or so I've heard]
In many a large setting, a big concern is "does it play nice with XYZ." [Insert cliche about certain-hardware manufacturer that set the "random" retry ethernet window to minimum, rather than minimum+random, to achieve better performance for its cards, intentionally mucking with interframe spacing....] XYZ is going to be: Specific app or other (hardware) product. If the apps are internal (as some of ours are) then you can't help us -- but there are some fairly customizeable out-of-the-box apps that you could test against....
Basically, none of these purchases happen in a vacuum. The merits of the technology matter, but "playing nice" is a dealbreaker. If this causes ANYTHING to break, forget it for now. et cetera.
......Groklaw was slow because the slashdotting had already happened. Most of the people never leave the Slashdot homepage. They click the link from the story and never contribute to the discussion. The additional bump of lurkers probably slowed down groklaw.
100% Serious. Browsed to Groklaw. Slow as hell. Slashdot has a *LOT* more lurkers than you'd think. I didn't come to slashdot FIRST. I went to Groklaw, noticed it took longer than usual to load, and then went to check Slashdot for the cause of said slowness. Seeing the/. homepage, I decided to post. Didn't even notice I was FP until you pointed it out.... that was my first first post.:)
you have SONGS in your head?! LUXURY! I don't even have MUSIC. Hell, I don't even have EARS. In my day, we had to walk, but we didn't have schools, so we didn't know where we were walking or why, but it was up hill -- both ways, they hadn't even INVENTED down hill yet. And it was always snowing, but we didn't have sun yet. And forget not having shoes, we didn't even have FEET. We just had bloody stumps and we were glad. AND THEN they invented cosmic background radiation, and THAT was the "hip" thing the youngins were "listening" to after they invented "ears."
Kurose and Ross -- and Yang Richard Yang's class lecture notes from Yale's CS 339. Just google for (sans quotes) "yale yang richard notes". Also, check out ANTS.
Typing "Supreme Court" wouldn't be so bad. Typing "Supreme Court Of The United States" merits SCOTUS. [The rationale is "Supreme Court" can refer to many supreme courts....]
Slashdot Mirror
Clearly, you must word murder your children...
Actually faggy? Cute? Post an email next time, damnit.
Some of us troll slashdot looking for boyfriends....
Do you mean DHMO? That shit is *NASTY*.....
From apple's X11 page:
So in short, OP was correct.
Btw, where are you a law student? I start my 1L year either fall 05 or 06 and wouldn't mind some feedback -- my degree is a masters/bachelors in CS... -b
launch.yahoo.com
The problem is that random access memory has gone full circle. We once started with tape -- so all of your sorting algorithms had to be sensitive to the fact that you only had sequential reads. The problem with random access memory is that when it is over the network, the latency becomes HUGE in comparison to the rest of the memory heirarchy. The algorithm works just fine on a local SCSI or IDE hard drive, but begins sucking hard over ethernet. (ESPECIALLY w/collisions) To fix it, they'd need to stop using stock B tree algorithms and go back to "old" technology -- that is, algorithms that take into account that random disk accesses cost you time. That way, they can queue a whole bunch of data from over the network, and then treat it (in local cache) like a segment of a tape. This problem is quite common in large datasets.
[The program is called "Concordance"]
*cringe*
This works just fine until something doesn't work *perfectly*, and then all hell breaks loose. I will give you a real world example. I'm currently working at a law firm (I'm starting law school in either fall 05 or 06) that uses a common "indstry standard" database tool -- it is a flat-file DB that uses B+ trees. [B trees are like binary trees, but they have many children instead of two, and B+ trees store information only in the leaves.] The idea between B+ trees is that because of the high degree of branching of the tree, you should never have to take more than 2-3 "slow memory" accesses to find your page. (i.e. the entire first node lives in memory. assuming a branching factor of 256, 16777216 records can be accessed within 3 accesses.) Building these trees is also a time-intensive process since there are a lot of writes that happen to parent nodes, and it is very likely that pages get flushed from virtual memory. The problem is that no one has a CS background and so no one understands the memory heirarchy, virtual memory, caching, write-on-update, LRU/MRU page replacement, et cetera, so when Concordance is *slow as all hell* -- no one knows why. [The answer is: When indexing a large database, the programmers seem to have been sloppy and the main node spills over onto a second memory page. Once other nodes begin to spill over, you get a case of "thrashing" in which every time your computer pulls a node back into the "working set" of what lives in physical memory, it kicks what you need out of virtual memory. Google for "thrashing" and the "row-major" and "column-major" order problem.]
*My* firm took a huge risk and hired someone with a CS degree (masters) rather than a paralegal, and they did some experimenting. I've gotten under-the-hood of many of their apps, and the things I've discovered have been shocking. (And these are industry "standard" solutions.) They've reaped the benefits of having someone that actually understands the underlying technology. Here is the archetypical example:
BUT: I am giving you a secret peek at the innards of foo!
Very long story short: at some level, there must be someone technical so when things "go wrong" (like why many people accessing a shared harddrive over ethernet for disk intensive operations is a bad idea due to the nature of a bus architecture...) all hell doesn't break loose.
Who pays the cost of said investigations? So long as *No* expense is incurred on behalf of the joe-jobee, I have no problem with it.
You joe-job your competitor from a comprimised relay in China. There is no money trail to follow. Punitive solutions will *not* work. (Far worse to punish one innocent small-business than it is to let 10 spammers go free...)
-b
I'm a product of the (high school) public education system as well. There is nothing wrong with public schooling in many parts of the country. The generalizations that "ALL public schools are x" or "they cannot produce students capable of y" are pure bull. Public school has taken me quite far in life. Let poor Horace Mann sleep in peace; just because *you* wasted your time in public school doesn't imply that the rest of us did.
...so don't knock it. )
However, bonus points for the honesty to admit you made a mistake. Perhaps that is one benefit of coming from a public school background? Many of the Adoverites and Exeterites I went to college with were incapable of doing so... (Public school got me into a wonderful university [check post history]
-b
> For additional protection, hold the companies being advertised liable for the actions of the company doing the "promotion".
NATCH! It is great in theory...until Company A Joe-Jobs Company B. (google "joe job" or check it on wikipedia....)
GGP wrote "plunder" our inboxes. Clearly, no one is stealing anything from our inboxes. (They have no capacity to rapaciously steal everything in sight, leaving destruction in their wake.) Clearly, GGP meant "plague" our inboxes, as pointed out by GP's oh-so-witty "plague" Slashdot. (in ITALICS) However, GP is a douche that doesn't know what grammar really is, as GGP was grammatically correct, albeit with nonsensical diction.
One entry found for diction.
Main Entry: diction
Pronunciation: 'dik-sh&n
Function: noun
Etymology: Latin diction-, dictio speaking, style,
from dicere to say; akin to Old English tEon to
accuse, Latin dicare to proclaim, dedicate,
Greek deiknynai to show, dikE judgment, right
1 obsolete : verbal description
2 : choice of words especially with regard to
correctness, clearness, or effectiveness
Main Entry: grammar
Pronunciation: 'gra-m&r
Function: noun
Etymology: Middle English gramere, from Middle
French gramaire, modification of Latin grammatica, from Greek grammatikE, from feminine
of grammatikos of letters, from grammat-, gramma -- more at GRAM
1 a : the study of the classes of words, their
inflections, and their functions and relations in the sentence
b : a study of what is to be preferred and what avoided in
inflection and syntax
2 a : the characteristic system of inflections and
syntax of a language b : a system of rules
that defines the grammatical structure
of a language
3 a : a grammar textbook b : speech or writing
evaluated according to its conformity to
grammatical rules
4 : the principles or rules of an art, science, or
technique a grammar of the theater
S/He had the right word class (transitive verb in the infintive form) -- but a poor word choice.
Her/His grammar and syntax were correct. S/He was wrong in the semantics of his word choice. Grammar defines what classes of words are acceptable in what order. Clearly, the statement that someone is "... plunder[ing] slashdot" doesn't mean the same thing as someone "... harassing slashdot" -- yet in that context, plunder is not grammatically incorrect. It makes no sense, but it is by no means an improperly formed statement. [See also Chomsky and every compilers class EVER to implement LALR(1) for more on parsing/grammars/et cetera]
If you're going to be a "Language Nazi", be sure of your exact type....
*sigh*
You meant....
In Soviet Redmond, the problem is You!
-b
Life at goldman really isnt so bad. Sollie is much more notorious for being a sweatshop.
My friend is an entry level at goldman and he's steady 7-6. Given salaries in the industry... I can't see how anyone would complain. The 100+ at sollie, however, can be crazy. [or so I've heard]
....ix-nay
not ex-nay.
you insensitive od-clay!
In many a large setting, a big concern is "does it play nice with XYZ." [Insert cliche about certain-hardware manufacturer that set the "random" retry ethernet window to minimum, rather than minimum+random, to achieve better performance for its cards, intentionally mucking with interframe spacing....] XYZ is going to be: Specific app or other (hardware) product. If the apps are internal (as some of ours are) then you can't help us -- but there are some fairly customizeable out-of-the-box apps that you could test against....
Basically, none of these purchases happen in a vacuum. The merits of the technology matter, but "playing nice" is a dealbreaker. If this causes ANYTHING to break, forget it for now. et cetera.
......Groklaw was slow because the slashdotting had already happened. Most of the people never leave the Slashdot homepage. They click the link from the story and never contribute to the discussion. The additional bump of lurkers probably slowed down groklaw.
What do you want, my firefox history?
100% Serious. Browsed to Groklaw. Slow as hell. Slashdot has a *LOT* more lurkers than you'd think. I didn't come to slashdot FIRST. I went to Groklaw, noticed it took longer than usual to load, and then went to check Slashdot for the cause of said slowness. Seeing the /. homepage, I decided to post. Didn't even notice I was FP until you pointed it out.... that was my first first post. :)
Sigh. I only came here because Groklaw was all slow. I know why now. *grumble*
you have SONGS in your head?! LUXURY! I don't even have MUSIC. Hell, I don't even have EARS. In my day, we had to walk, but we didn't have schools, so we didn't know where we were walking or why, but it was up hill -- both ways, they hadn't even INVENTED down hill yet. And it was always snowing, but we didn't have sun yet. And forget not having shoes, we didn't even have FEET. We just had bloody stumps and we were glad. AND THEN they invented cosmic background radiation, and THAT was the "hip" thing the youngins were "listening" to after they invented "ears."
hooligans!
Kurose and Ross -- and Yang Richard Yang's class lecture notes from Yale's CS 339. Just google for (sans quotes) "yale yang richard notes". Also, check out ANTS.
-br
....so apple can sue real?
I guess KARMA is a bitch. (*Payback* for Harmony, anyone?)
Supreme Court Of The United States ==> SCOTUS.
Typing "Supreme Court" wouldn't be so bad. Typing "Supreme Court Of The United States" merits SCOTUS. [The rationale is "Supreme Court" can refer to many supreme courts....]
You mean we're being controlled? FIND THEM!!!! TO TRANTOR!!!!!! Or terminus.......or some random ringworld out in the edge of no where....