All Google has to do is ban scalping of the tickets. You buy a ticket, YOU get in, not the holder of the ticket.
How would one implement that while maintaining the ability for a business to decouple purchasing a ticket from the decision of which member of a development team gets to go?
That's why you need multiple layers in your transmission. The obvious signal should be a long, slow count of all of the prime numbers up to some arbitrary cut-off, like 9973. Then the transmission should repeat. This will give the aliens a strong clue that you're operating in base-10. Then, layered in your transmission - perhaps in a side channel, or by having different signals in amplitude modulation, frequency modulation, and polarization modulation, you can give multilayered information.
The next-most-obvious signal in your "palimpsest" should be a primer of some sort. This is where you can build basic mathematic, chemistry, etc. — ultimately building up to the detailed instructions for building a device the aliens can build that will transport one of them through a wormhole to talk to her dead father.
That would be true if we were to use this display for the uncreative purpose of displaying whatever threat-level the DHS is currently at.
I would pay for a display like this. Back in 2004 I had to resort to using the various colors of the dry-erase-marker rainbow to create a threat-level display on the whiteboard in my office. Back then my team's product had a memory leak somewhere in it, and nobody believed me. The servers would be up for a handful of days, and then just when everybody was lulled into a false sense of security we would get a flurry of random OutOfMemoryExceptions as the whole thing would sieze up and become unresponsive - pulling system administrators out of their scheduled meetings to conduct emergency rolls in a panic. And then, back to business as usual.
At first I was alone in suspecting a leak. Back then we didn't have any memory monitoring in place so it was all thruthiness from my gut. But worse than being alone in my suspicions was the sinking feeling that the leak was proportional to user load, which was on a steady incline with no sine of abating. So over the course of a few months - while everybody went about their business of making sure to only work on things that could be billed to client project numbers - the frequency of emergency rolls steadily increased, and I kept elevating my threat level in response.
"What's that on your whiteboard," some would ask. I would explain that a shitstorm was on the horizon and that we had better take some time to find and fix the memory leak even if it meant taking a hit to billable hours. "Leak? What leak?"
By doing this I got a partner onboard who put some hand-rolled memory monitoring in place using JFreeChart to plot the decline. "See...a memory leak!," we would insist. "No, no," said the best and brightest of our software engineers. "It'll pick up," he continued, suggesting that maybe I didn't really understand how the garbage collector worked and that maybe it merely needed to fall below some threshold before it kicked in.
And with that, I once again elevated the threat level, and kept elevating it until it hit the top. Eventually we got to the point where one out of four nodes in our cluster was always in the process of being rolled, with users spilling over to the remaining 3, and one of them would crumble just as the 4th node was coming back up.
We eventually discovered a dubious use of ThreadLocal in the old version of Xalan (the pre-xsltc version), and fixed the problem by upgrading the library. But without the threat-level indicator in my office, I might never have gotten attention to the problem before it was too late.
I'll pay $200 for one of these boards. And I want all of the colors, damn it.
How is it not the 4th model of the iPhone? There was the original, which spoke the 2.5G Edge protocol, then there was the 2nd one which spoke a 3G protocol, then there was the 3rd phone - the 3GS - which added a faster processor and video recording, and now there is the 4th phone, dubbed the iPhone 4.
...while the WebKit JavaScript VM is a bytecode interpreter.
The world has moved on since those days. Squirrelfish was a bytecode interpreter, yes...but Squirrelfish Extreme has been using JIT compilation since 2008. Note that Chrome also uses WebKit, and has been using a different Javascript VM called "V8", and it also compiles just-in-time. On the mozilla side of the fence, Tracemonkey also compiles just in time. The only laggard is IE.
I recon javascript will be used differently now that the runtimes are more capable. Your observation about how Javascript is used today only reflects the limited capabilities of yesterday's browsers. Flash can no longer be thought of as being uniquely optimized for long-running things. Those days are over.
Is there a point you wanted to make without a strawman? I didn't say that all phones had stupid restrictions. I would, however, go so far as to say that devices without stupid restrictions were not available by the carriers in my region at the time, and so you're free to rail against me for living in the "right place" back then...if you really must.
My point was to counter the notion that the industry was not already "turned back" before Apple entered the market. The grandparent is propagating a fiction that the industry was somehow open until the iPhone singlehandedly closed it.
Every cell phone I've ever had has been burdened with stupid restrictions, so Apple isn't really innovating in the Restrictions Department - they've just wrested some of the ability to restrict from the hands of the carriers. The last phone I had was a Motorola e815, which had the ability to do Bluetooth OBEX built into it, but Alltel decided to configure it off so that I couldn't load my own ringtones easily and had to buy theirs.
There was no Year 0 so the indices start from 1 in this case.
I'm always amazed how on a forum brimming with computer scientists, there's always an ample supply of pedants willing to insist that whatever calendar Gregory XIII pulled out of his ass in 1582 by papal fiat is somehow intrinsically less arbitrary than demarcating decades by years that end in zero.
I've checked since you last have, and your notion of when decades end is based upon the year 1 being the first calendar year...which is, of course, entirely arbitrary. So since we're already being arbitrary, why not be a computer scientist for once and just willingly accept the one time when everybody else is willing to start counting with zero like god intended?
Everybody take note here that the defense is not claiming that the garden has no walls, but is only claiming that they are made of a different material.
The slang term is far from being outdated, because it is still in use. Perhaps you have never heard it yourself, but I have.
I first encountered it through a hacker friend of mine in the early 90s in - of all places - Lincoln, Nebraska. He had spent some time out of the state working for the now-defunct maker of Sharebase. He returned to Nebraska after the demise of that company, and told me about the hacker culture and lexicon years before I graduated with my Comp Sci degree in 1993. I didn't know what to make of it at the time, but once the internet hit its inflection point I got online and found the Jargon File, of course.
I remember him using the word "chrome" to describe the GUI user-interface parts of a program (with a somewhat dismissive tone, because he considered to be uninteresting). This was in contrast to the non-chrome parts of programs, which he found more engaging. I have since witnessed it used in this way by several others.
In fact, I worked with a team of programmers on an internal system at a large market research firm who named major releases of a home-grown web templating system - because we thought dotted numbers were boring - after words out of the jargon file. We went through five major releases before this practice was retired: amiga, blob, chrome, dogcow, and eliza.
(Incidentally, one of my colleagues from that team went on to become a Program Manager for Google's browser project...although the browser already had the name before he joined.)
Now here's the kicker: think about what the word "chrome" signifies in Mozilla. It's a URL resource-type designator for referring to XUL markup, right? Well, what is XUL for? It's a markup language for the user-interface aspects of the mozilla browser...the browser's chrome. The hackers behind the mozilla project likely used this word because it was already in somewhat-common usage...and probably to amuse themselves. Perhaps this historical fact is inadequately documented, but to those of us who encountered this part of the lexicon in active use the truth is as plain as day.
Now consider Google's browser. Did they re-invent the rendering engine? No. The bulk of that browser's plumbing - with the notable exception of Lars Bak's javascript runtime and the multiprocess model - was something that they grabbed off the shelf, leaving the main contribution that differentiates the browser is the user-interface aspects of the program...the chrome. While Apple had already brought WebKit to the Windows world, they had utterly failed to make a UI that had any appeal to Windows users. Google created a browser whose chrome was more at-home, as it were. I would not be surprised if this was the genesis of the name.
I've heard people complain that they stole the word 'chrome' from mozilla before. I find that to be an absurd notion, however, given the word's history in hacker slang.
Slashdot Mirror
This is the first indication that the Manchurian Combover administration intends to have successors.
Rust. Because it's relatively new.
"First rule of leadership: everything is your fault." - Hopper, A Bug's Life
All Google has to do is ban scalping of the tickets. You buy a ticket, YOU get in, not the holder of the ticket.
How would one implement that while maintaining the ability for a business to decouple purchasing a ticket from the decision of which member of a development team gets to go?
Under which section(s) of the Sherman act?
For anyone wondering what postbigbang is referring to by "reduces yourself to their level":
http://en.wikipedia.org/wiki/Democrat_Party_(phrase) ...I, myself, prefer "Republiklan".
That's why you need multiple layers in your transmission. The obvious signal should be a long, slow count of all of the prime numbers up to some arbitrary cut-off, like 9973. Then the transmission should repeat. This will give the aliens a strong clue that you're operating in base-10. Then, layered in your transmission - perhaps in a side channel, or by having different signals in amplitude modulation, frequency modulation, and polarization modulation, you can give multilayered information.
The next-most-obvious signal in your "palimpsest" should be a primer of some sort. This is where you can build basic mathematic, chemistry, etc. — ultimately building up to the detailed instructions for building a device the aliens can build that will transport one of them through a wormhole to talk to her dead father.
That should do it.
...the absence of Flash.
That would be true if we were to use this display for the uncreative purpose of displaying whatever threat-level the DHS is currently at.
I would pay for a display like this. Back in 2004 I had to resort to using the various colors of the dry-erase-marker rainbow to create a threat-level display on the whiteboard in my office. Back then my team's product had a memory leak somewhere in it, and nobody believed me. The servers would be up for a handful of days, and then just when everybody was lulled into a false sense of security we would get a flurry of random OutOfMemoryExceptions as the whole thing would sieze up and become unresponsive - pulling system administrators out of their scheduled meetings to conduct emergency rolls in a panic. And then, back to business as usual.
At first I was alone in suspecting a leak. Back then we didn't have any memory monitoring in place so it was all thruthiness from my gut. But worse than being alone in my suspicions was the sinking feeling that the leak was proportional to user load, which was on a steady incline with no sine of abating. So over the course of a few months - while everybody went about their business of making sure to only work on things that could be billed to client project numbers - the frequency of emergency rolls steadily increased, and I kept elevating my threat level in response.
"What's that on your whiteboard," some would ask. I would explain that a shitstorm was on the horizon and that we had better take some time to find and fix the memory leak even if it meant taking a hit to billable hours. "Leak? What leak?"
By doing this I got a partner onboard who put some hand-rolled memory monitoring in place using JFreeChart to plot the decline. "See...a memory leak!," we would insist. "No, no," said the best and brightest of our software engineers. "It'll pick up," he continued, suggesting that maybe I didn't really understand how the garbage collector worked and that maybe it merely needed to fall below some threshold before it kicked in.
And with that, I once again elevated the threat level, and kept elevating it until it hit the top. Eventually we got to the point where one out of four nodes in our cluster was always in the process of being rolled, with users spilling over to the remaining 3, and one of them would crumble just as the 4th node was coming back up.
We eventually discovered a dubious use of ThreadLocal in the old version of Xalan (the pre-xsltc version), and fixed the problem by upgrading the library. But without the threat-level indicator in my office, I might never have gotten attention to the problem before it was too late.
I'll pay $200 for one of these boards. And I want all of the colors, damn it.
How is it not the 4th model of the iPhone? There was the original, which spoke the 2.5G Edge protocol, then there was the 2nd one which spoke a 3G protocol, then there was the 3rd phone - the 3GS - which added a faster processor and video recording, and now there is the 4th phone, dubbed the iPhone 4.
...half a billion priapic pop-ups in China.
So diamond is no longer the hardest [material] known to man?
It hasn't been for quite some time now, but the myth lives on. It was the hardest "naturally occurring" material until this discovery, apparently.
Reading sometimes helps.
There's an app for that.
The world has moved on since those days. Squirrelfish was a bytecode interpreter, yes...but Squirrelfish Extreme has been using JIT compilation since 2008. Note that Chrome also uses WebKit, and has been using a different Javascript VM called "V8", and it also compiles just-in-time. On the mozilla side of the fence, Tracemonkey also compiles just in time. The only laggard is IE.
I recon javascript will be used differently now that the runtimes are more capable. Your observation about how Javascript is used today only reflects the limited capabilities of yesterday's browsers. Flash can no longer be thought of as being uniquely optimized for long-running things. Those days are over.
Is there a point you wanted to make without a strawman? I didn't say that all phones had stupid restrictions. I would, however, go so far as to say that devices without stupid restrictions were not available by the carriers in my region at the time, and so you're free to rail against me for living in the "right place" back then...if you really must.
My point was to counter the notion that the industry was not already "turned back" before Apple entered the market. The grandparent is propagating a fiction that the industry was somehow open until the iPhone singlehandedly closed it.
Every cell phone I've ever had has been burdened with stupid restrictions, so Apple isn't really innovating in the Restrictions Department - they've just wrested some of the ability to restrict from the hands of the carriers. The last phone I had was a Motorola e815, which had the ability to do Bluetooth OBEX built into it, but Alltel decided to configure it off so that I couldn't load my own ringtones easily and had to buy theirs.
There was no Year 0 so the indices start from 1 in this case.
I'm always amazed how on a forum brimming with computer scientists, there's always an ample supply of pedants willing to insist that whatever calendar Gregory XIII pulled out of his ass in 1582 by papal fiat is somehow intrinsically less arbitrary than demarcating decades by years that end in zero.
I've checked since you last have, and your notion of when decades end is based upon the year 1 being the first calendar year...which is, of course, entirely arbitrary. So since we're already being arbitrary, why not be a computer scientist for once and just willingly accept the one time when everybody else is willing to start counting with zero like god intended?
Your post has forced me to either respond or not respond. Damn you and your restrictive discourse.
Everybody take note that the defense is not claiming that their garden has no walls, but is only claiming that they are not made of the same material.
Everybody take note here that the defense is not claiming that the garden has no walls, but is only claiming that they are made of a different material.
He's writing a user interface for his walled garden. He was complaining about somebody else's walled garden. That's totally different.
Our current energy policy is costing the lives of soldiers in the desert sands as we speak, and has been for quite a long time.
The slang term is far from being outdated, because it is still in use. Perhaps you have never heard it yourself, but I have.
I first encountered it through a hacker friend of mine in the early 90s in - of all places - Lincoln, Nebraska. He had spent some time out of the state working for the now-defunct maker of Sharebase. He returned to Nebraska after the demise of that company, and told me about the hacker culture and lexicon years before I graduated with my Comp Sci degree in 1993. I didn't know what to make of it at the time, but once the internet hit its inflection point I got online and found the Jargon File, of course.
I remember him using the word "chrome" to describe the GUI user-interface parts of a program (with a somewhat dismissive tone, because he considered to be uninteresting). This was in contrast to the non-chrome parts of programs, which he found more engaging. I have since witnessed it used in this way by several others.
In fact, I worked with a team of programmers on an internal system at a large market research firm who named major releases of a home-grown web templating system - because we thought dotted numbers were boring - after words out of the jargon file. We went through five major releases before this practice was retired: amiga, blob, chrome, dogcow, and eliza.
(Incidentally, one of my colleagues from that team went on to become a Program Manager for Google's browser project...although the browser already had the name before he joined.)
Now here's the kicker: think about what the word "chrome" signifies in Mozilla. It's a URL resource-type designator for referring to XUL markup, right? Well, what is XUL for? It's a markup language for the user-interface aspects of the mozilla browser...the browser's chrome. The hackers behind the mozilla project likely used this word because it was already in somewhat-common usage...and probably to amuse themselves. Perhaps this historical fact is inadequately documented, but to those of us who encountered this part of the lexicon in active use the truth is as plain as day.
Now consider Google's browser. Did they re-invent the rendering engine? No. The bulk of that browser's plumbing - with the notable exception of Lars Bak's javascript runtime and the multiprocess model - was something that they grabbed off the shelf, leaving the main contribution that differentiates the browser is the user-interface aspects of the program...the chrome. While Apple had already brought WebKit to the Windows world, they had utterly failed to make a UI that had any appeal to Windows users. Google created a browser whose chrome was more at-home, as it were. I would not be surprised if this was the genesis of the name.
I've heard people complain that they stole the word 'chrome' from mozilla before. I find that to be an absurd notion, however, given the word's history in hacker slang.