Preaching to the choir, but this is what happens when the powers that be think it's a great idea to remove divisions or subsidiaries from the email address.
I agree. I think part of the problem is the lack of exposition for the sake of inspiring the public. Most of the current expositions are marketing fairs that only show off products that investors hope will have mass appeal and not necessarily ground breaking inventions. Since truly ground breaking or inspirational inventions may not do well at your local electronic retailer, this means most of the public's attention is focused solely on consumer items.
The world's fair use to played a role during the beginning of the industrial age. When its focus changed to being a cultural exchange around 1939, it has devolved into a traveling Disney Epcot theme park.
I'm sure there's a protocol for three people joining where the second and third share a middle initial, but I haven't seen it come up and we're not a small place.
I have and the conflict is solved by reverting back to first_name.last_name format with a number appended at the end for the second (and later) full name with same middle initial or for all names without a middle initial.
Don't forget "Mindless Obama Worshipers". In this case, the ad hominem rebuttal was retaliation for an ad hominem attack. Neither side added any intelligent thought to the discussion.
The subject was Lamacchia Loophole not Lamacchia. The wire fraud charges against Lamacchia didn't stick because it was misapplied. The wire fraud charges against Swartz would apply because unlike Lamacchia he was not authorized to be on MIT campus and gained fraudulent access to their internal network via a wiring closet which allowed him to gain access to JSTOR. The Lamacchia Loophole wouldn't apply since, in this particular case, the prosecution isn't using wire fraud charges as a means to prosecute copyright infringement. The copyright law has been strengthen to the point where they no longer need to try to make a related charge. Of course, I am not a lawyer so this is pure speculation.
WIRE FRAUD?? Really? Intentional deception of others to personally gain from them? Where? How? Who? did that happen.
At the risk of condoning prosecutor's reach, I believe the wire fraud charge resulted from the trespass, wiretap, and using MIT's credentials to gain access to JSTOR.
I do agree that the term "gaymer" seems to segregate rather than integrate the gay gamers from the rest of us. However I believe the term in the article refers to a forum where they all congregated. I think it's a neat play on words and a cool name for a forum that they use share their experiences and thoughts with fellow gay gamers ( I assume that it what the forum is for ). I think the person who trademarked the term is a douche bag and I wish them luck in their legal battle.
We fantasize about doing that all the time. Unfortunately we have to work in the real world.
Here's how it happens most of the time. You need a device that has a very niche market (i.e. not many competitors to choose from). Out of the very few devices available, you pick one from a vendor who advertises it supports linux. You purchase the device only to find out that the driver is for a very old 2.6 kernel which doesn't work well with the other devices that are directly supported by the current kernel version. You have two options:
(1) You use their blessed linux distribution which is little more than a very old snapshot of Slackware or LFS and attempt to back port all the other device drivers.
(2) You use LXR to make the necessary changes in their driver code to get it to work with the current kernel. Since your modified code is not part of the official kernel tree and you don't have money budgeted to maintain the code outside of the project, you are committed to always update this driver when a new project comes along and we have to use this one device with the new system.
#2 is our only real option and having LTSI back port the important stuff to their 2-year kernel makes our job much easier.
I think you may be confusing the userland ABI offered by glibc with the kernel API which is more relevant to the article.
The stable kernel API is where the real work savings is at. Now that the embedded market is gaining momentum, the big players formed the LTSI to stabilize the kernel API long enough to be of use. I'm on the LTSI bandwagon since the time I save from not having to use LXR to modify driver code WHICH DOESN'T BELONG TO MY ORGANIZATION the more time I have to spend working on my own code.
Excuse the emphasis. I always get a "release the code to the kernel" response despite the fact that it's not my code to release. The LTSI is the industry's mitigation to the "fuck you" response from the kernel devs every time a more stable API is requested. Unfortunately more often than not, the response is a direct quote.
I don't know why you are surprised by the news mentioned in the article. This is very old news. It was common for the big tech players to agree to not poach each other back in the late 90's and early 00's. Probably hidden better these days. It was "shocking" when this story broke a decade ago.
These agreements are not exclusive to tech industry either. A lot of niche service industries have similar "gentleman's agreement" amongst themselves.
I guess nothing like calling Steve Jobs a dick to win some free mod points.
Hush. I remember the original Apple ][. Imagine how I feel.
I remember playing with the Lisa (perhaps Lisa 2 it was '84) in a computer showroom. Later when the Macintosh came out, I was surprised by how much smaller it was.
I didn't say it was unjustified just unfair. In fact, depending how Oracle responds, it may actually make Java more secure than other options/languages.
What I am suspicious of is the lack of coverage for the other exploits. Which unfairly diminishes Java's image while elevating the status of similar products that may have the similar vulnerabilities.
Smear campaign. I always wondered why a "mega" exploit package was reportedly offered up for sell yet only the Java exploit contained in the package was the one getting the media attention.
Preaching to the choir, but this is what happens when the powers that be think it's a great idea to remove divisions or subsidiaries from the email address.
I agree. I think part of the problem is the lack of exposition for the sake of inspiring the public. Most of the current expositions are marketing fairs that only show off products that investors hope will have mass appeal and not necessarily ground breaking inventions. Since truly ground breaking or inspirational inventions may not do well at your local electronic retailer, this means most of the public's attention is focused solely on consumer items.
The world's fair use to played a role during the beginning of the industrial age. When its focus changed to being a cultural exchange around 1939, it has devolved into a traveling Disney Epcot theme park.
I have and the conflict is solved by reverting back to first_name.last_name format with a number appended at the end for the second (and later) full name with same middle initial or for all names without a middle initial.
Don't blame the Fugees. That's a Justin Bieber song.
Don't forget "Mindless Obama Worshipers". In this case, the ad hominem rebuttal was retaliation for an ad hominem attack. Neither side added any intelligent thought to the discussion.
The subject was Lamacchia Loophole not Lamacchia. The wire fraud charges against Lamacchia didn't stick because it was misapplied. The wire fraud charges against Swartz would apply because unlike Lamacchia he was not authorized to be on MIT campus and gained fraudulent access to their internal network via a wiring closet which allowed him to gain access to JSTOR. The Lamacchia Loophole wouldn't apply since, in this particular case, the prosecution isn't using wire fraud charges as a means to prosecute copyright infringement. The copyright law has been strengthen to the point where they no longer need to try to make a related charge. Of course, I am not a lawyer so this is pure speculation.
I'm curious. How is Alan Shepard related to the civl rights act?
At the risk of condoning prosecutor's reach, I believe the wire fraud charge resulted from the trespass, wiretap, and using MIT's credentials to gain access to JSTOR.
From the details given by most of the articles detailing the events leading up to his arrest, I would have to disagree with your assertion.
I think the more apt term is "alleged criminal" and playing semantics doesn't invalidate the OP's opinion. You are entitled to disagree.
Yea he was fortunate up until the time he got assassinated...
I think history pretty much invalidates you assertion.
You touch my stuff... I'll ...
Very bad since the entire 5650-5925 MHz amateur radio allocation is included in the WiFi announcement.
Bad for experiment and hobbyist that uses the band. Bad for the industry because the proposal will meet opposition.
Also there is a lot of hand waving on the "Dynamic Frequency Selection" channels and how they will enforce minimal interference to weather radar.
I do agree that the term "gaymer" seems to segregate rather than integrate the gay gamers from the rest of us. However I believe the term in the article refers to a forum where they all congregated. I think it's a neat play on words and a cool name for a forum that they use share their experiences and thoughts with fellow gay gamers ( I assume that it what the forum is for ). I think the person who trademarked the term is a douche bag and I wish them luck in their legal battle.
We fantasize about doing that all the time. Unfortunately we have to work in the real world.
Here's how it happens most of the time. You need a device that has a very niche market (i.e. not many competitors to choose from). Out of the very few devices available, you pick one from a vendor who advertises it supports linux. You purchase the device only to find out that the driver is for a very old 2.6 kernel which doesn't work well with the other devices that are directly supported by the current kernel version. You have two options:
(1) You use their blessed linux distribution which is little more than a very old snapshot of Slackware or LFS and attempt to back port all the other device drivers.
(2) You use LXR to make the necessary changes in their driver code to get it to work with the current kernel. Since your modified code is not part of the official kernel tree and you don't have money budgeted to maintain the code outside of the project, you are committed to always update this driver when a new project comes along and we have to use this one device with the new system.
#2 is our only real option and having LTSI back port the important stuff to their 2-year kernel makes our job much easier.
I think you may be confusing the userland ABI offered by glibc with the kernel API which is more relevant to the article.
The stable kernel API is where the real work savings is at. Now that the embedded market is gaining momentum, the big players formed the LTSI to stabilize the kernel API long enough to be of use. I'm on the LTSI bandwagon since the time I save from not having to use LXR to modify driver code WHICH DOESN'T BELONG TO MY ORGANIZATION the more time I have to spend working on my own code.
Excuse the emphasis. I always get a "release the code to the kernel" response despite the fact that it's not my code to release. The LTSI is the industry's mitigation to the "fuck you" response from the kernel devs every time a more stable API is requested. Unfortunately more often than not, the response is a direct quote.
At least at the moment.
I'm hoping the new Google X phone will have a replaceable battery, but I doubt it.
Actually the same can be said of the iPhone. But we all know we really want the easily replaceable one.
I don't know why you are surprised by the news mentioned in the article. This is very old news. It was common for the big tech players to agree to not poach each other back in the late 90's and early 00's. Probably hidden better these days. It was "shocking" when this story broke a decade ago.
These agreements are not exclusive to tech industry either. A lot of niche service industries have similar "gentleman's agreement" amongst themselves.
I guess nothing like calling Steve Jobs a dick to win some free mod points.
Or Google products? The Nexus 4 has a non-user replaceable battery.
Maybe "an OS whose primary application space is based on HTML5" is a better description.
I agree the summary seems inaccurate.
Hush. I remember the original Apple ][. Imagine how I feel.
I remember playing with the Lisa (perhaps Lisa 2 it was '84) in a computer showroom. Later when the Macintosh came out, I was surprised by how much smaller it was.
I didn't say it was unjustified just unfair. In fact, depending how Oracle responds, it may actually make Java more secure than other options/languages.
What I am suspicious of is the lack of coverage for the other exploits. Which unfairly diminishes Java's image while elevating the status of similar products that may have the similar vulnerabilities.
Please cite some evidence that the above is true.
Smear campaign. I always wondered why a "mega" exploit package was reportedly offered up for sell yet only the Java exploit contained in the package was the one getting the media attention.