The interesting chip here is the i7-4770R
.. I expect it will be sold as motherboards with CPU soldered on for DIY builds, like the Atom boards.
I sure hope so. Maybe this is projection but I think such a mobo would be insanely popular for desktops.
Google's stance on a 60day turnaround of vulnerability fixes from discovery, and a 7-day turnaround of fixes for actively exploited unpatched vulnerabilities, is rather naive and devoid of commercial reality.
I think what you're saying, is that if someone is going around stabbing people in the heart, and if a doctor says these victims all need immediate medical attention (even the victims which are in isolated areas far from hospitals), then that doctor is being naive and devoid of medical reality.
I personally think you should quit blaming the doctor for the unfairness and horror that is inherent in the situation. Declaring the urgency of a problem being addressed, isn't "naive". It's not naive, even if addressing the problem is incredibly hard or even if it's effectively impossible.
If the doctor truly thinks the victims all really will get "immediate medical attention" then he'd be naive. But advising it isn't naive. Yelling at people "get that victim to the ER as fast as you can!" isn't naive. Telling people that heart stab wounds are very serious, isn't naive.
And the analogy with Google here, is that you just got stabbed in the heart, they're advising and hoping you get immediate medical attention, and 7 days from now, if your wife asks Google if they've seen you lately, they're going to tell your wife, "I heard he got stabbed in the heart last week. You took him to the hospital, right? If not, you better get on that, right now." You're concerned Google is going to scare your wife?! Be concerned that you're not at the hospital yet!
You think Google is being naive with unreasonably high expectations, but the need for those high expectations isn't their fault!
I will acknowledge that supply-side convenience can result in lower prices for customers, but I would still feel better of at least SOME of the GMO stories in the US talked about making the food better in some way other than cost.
Here you go. It's probably a hoax, though (been hearing about it for a long time yet I still don't see it in grocery stores).
Even then, if it is the same mechanism, you are still not infringing the patent.
Really? That sounds like copyright, where how you created something is what matters to whether or not it's a derived work. With patents, a completely independent implementation is still infringing, if in the end, it's the same mechanism. It doesn't matter how you got there. If you breed (rather than synthesize) Roundup Ready, it's still Roundup Ready. No?
...
The Roundup Ready patent has always struck a chord with me as a programmer, maybe because it parallels some things that happened to us. You could look at Roundup Ready as an interoperability requirement, something that is needed, in order to be functionally compatible with Glyphosate -- sort of like how you have to implement LZW to be able to read a GIF image.
(I'm not saying it's a perfect analogy. There are various differences. The big one up until 2000, was that lots of GIFs were in the wild and they could come from anywhere, whereas Roundup was single-source due to its own patent. So the "need" to be compatible with Roundup was more dubious than GIFs. But when the Roundup patents expired, the situations became much more similar, and Glyphosate could be argued to be almost a defacto standard.)
Since anyone is allowed to make or use Glyphosate, and it's pretty common and widely-deployed, its situation is a lot like a world where many users are sending you GIF images that you need to read, and the government is there, telling you that you're prohibited from doing so. I can sympathize with farmers a lot, when they say they ought to have the right to make plants which are compatible with a (now) non-proprietary weedkiller.
If that's the case then we don't know if it is safe for human consumption, do we?
Yep, to the same degree that we don't ever know if a new wild strain is safe for human consumption.
People, look at this as good news. This means that patented genes are in the wild, doing their own thing and the patent being infringed by mother nature herself. Confirmed by USDA, an authority courts can't merely blow off without looking silly.
The fact this happens, is a great reason why either gene patents ought to be abolished, or at least the patents in this particular genotype ought to be invalidated.
I'm really struggling to see how javascript is a moral issue.
When I go on about proprietary software being "unmaintainable and unauditable" do you think I'm talking about morality? If ever trade secret + legal monopoly software becomes as trustworthy as maintainable and auditable software, then we can pick morality nits.
Until then, let's stick to practical concerns. Practical concerns like "how can I be sure this foreign untrusted code isn't fucking me?" or "I figured out how this is fucking me, and I want to make it stop" or "I made it stop, but then I got a letter from a lawyer" or "I don't use that site anymore, because it was fucking me too much and their lawyers were assholes, saying I wasn't allowed to modify the code they were offering to my computer."
I know you're being funny with this. However, there are plenty of examples where change was not necessarily an improvement. There seems to be a mentality that the old way is always for dinosaurs, and that's simply an immature view.
Sample data point:
Years ago, we delivered systems to our customers with command line interfaces. Later, when GUIs became available, the thought was that all of those command lines should be removed, and replaced with icons and menus. As we learned the hard way, our customers could do their work much more efficiently with the command lines (once they were trained), but for new operators the GUI let them get the job done giving them time to learn the typed command structures.
Oh, of course: it's our own fault we were getting ripped off, since the government and the people are one and the same. Please, tell me another fairy tale.
It's not a fairy tale; it's a strategy. (Spock: "A lie?" Valeris: "A choice.")
This is another one of those RMS things which really does seem pretty nitpicky and impractical, at the time it's written but history shows that whenever you later look back, RMS is almost always right.
Javascript is so transient, so unimportant, and so close to the blurry line between code and content (though I'm surprised to be reading so many opinions here which are placing it on the "content" side). Our browsers are getting pretty decent at sandboxing these days, so the consequences of running unmaintainable and unauditable code within them, seem light. Who really needs maintainance for code that you only use for a few seconds and then throw away?
But it's creep. Unless I have my browser only run Javascript from whitelists, the "normal" operation is that it's doing something (running all kind of crazy proprietary stuff) that, outside the browser, just doesn't happen. My machines aren't are "pure" as RMS' machines but even so, there are really only so many places where I still have unmaintainable and unauditable code. The browser multiplies that by thousands.
It's funny; I normally don't go adding thousands of proprietary PPAs to my Ubuntu machine, and tend to be pretty conservative about what I allow to be installed. Yet my browser still isn't using a whitelist for Javascript. That's not entirely sane or consistent, is it? No matter where you stand on the Free vs proprietary spectrum, you get to call me a hypocrite. (Fortunately, I probably get to call you one right back -- unless you're as hardcore as RMS or as resigned as an iPhone user.)
They're individually inconsequential (I think!!), but I sure spend a lot of time in the browser. What's otherwise a fairly trustworthy machine, seems to be hanging by a thread: the browser's correct virtualization of the Javascript universe. If I'm really ok with that, then you'd think I'd also have some Windows or Mac OS X virtual machines around too, to further run more unmaintainable and unaudited code for my convenience. Why don't I? Maybe it's simply because doing that wouldn't really give me any more convenience. But maybe I'm inconsistent because I don't have my shit together, mentally.
I think there's a valid concern here, it's just hard to say it's important or what (if anything) to do about it. But I remember when "The Right to Read" pretty much got the same opinion from me.
As far as what to do about it, FSF's proposal seems pretty modest: don't have government actively making the creep deeper. We have enough to worry about without our own government putting us further at risk. Regulations.gov shouldn't be distributing a bunch of proprietary code to citizens; leave that sort of thing to commercial sites. Even if it's currently believed that the current version of that code is harmless (it wouldn't totally surprise me if some people have illegally(?) audited the Javscript), it's not a best practice, and outside of exceptional-because-we-don't-have-our-shit-together web it's something we normally wouldn't do or permit. If regulations.gov told you to download and execute regulations.exe or the iOS app as the only way for citizens to get some information from them, I'm sure plenty of people would be screaming. This is the same, but also different, by degrees. Whether it's two degrees or ten, though, I don't know...
Realized after submitting that I may have just misread your intended meaning.
That wasn't the dev pay, it's the referral bonus
And, who pays the taxes on the $30k?
When you whip out your camera and photograph my desk or back I am forewarned, and have time to rare back with the haymaker that will surely be your next experience. But there is no defense against people walking into your store, your office, your meeting wearing Google Glass.
This is what I totally don't get. Of course there's a defense against this stuff: the same defense you'd use if you saw a camera crew walk in with a giant WPIG news camera. If your cow-orker attented a meeting with a handheld camcorder always pointed at your face, you really wouldn't say anything?
What you don't have as good a defense against, is the in-the-wild-for-many-years miniature cameras with basically the same intrusion capabilities as Google Glass, except that they're less overtly displayed. Ten or fifteen years ago (actually much longer ago, but around turn-of-century is when it all got really cheap, I think) was the time to rage against this tech, not now.
But ok, rage on. Better late than never, if GG starts the debate which should have been. But flaming this particular product for something for which it's not even a real example of the problem (since GG is both relatively obtrusive (you see it) and relatively expensive ($1500)) seems kind of lame.
We should demand "recording" LEDs indicating when cell phone cameras are on, and the same for Google Glass.
The funny thing is that you might actually get something like that for the next revision of GG. But you're never going to get it in general; you'll never be able to feel like it's something you can rely on. Cameras are going to be recording you, without the slightest visual or audible signal. It's probably already happening.
Take it from a guy who often wears a hat when he's outside. I don't have gear in there but you'd be crazy to take my word for it. I could have some gear in there, and you'd never know. There are people out there with backbacks, purses, shirt pockets, bulky coats
Wait, what??? You mean size matters??? I'm so screwed.
Disclaimer: I'm all for research, this included.
It's a matter of priorities. Have you seen the debt lately? Have you seen unemployment lately? Have you seen the crumbling infrastructure lately?
I'm not in favor of funding science projects when we can't afford to fund basic human needs such as healthcare.
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?
