Get this: malfunctioning. They should be able to avoid hitting the pedestrian in the first place. Also, there are the various situations in which the car or its inhabitants are doing something wrong and need to be stopped. Bottom line: cops must have the right to pull over vehicles. It's plain from Rule 2.
Suppose a vehicle hits a pedestrian or cyclist, and drags the corpse. A witnessing cop can either (1) pull the vehicle over, or (2) follow the vehicle at a polite distance while all identifying features of the victim are shed to the ground. I think pulling the vehicle over is the appropriate course of action here. If nothing else, to prevent the trauma to hundreds of witnesses.
If a vehicle is being operated recklessly, it should get pulled over. If there are outstanding tickets / warrants for its owner, it should be searched / impounded. I don't see why the presence of a driver should matter here.
That's how in vitro fertilization works. We collect a dozen or so eggs, and splash a few thousand sperm on 'em. Some get fertilized, some don't. We overcollect the eggs because the surgery is invasive and always carries risk, not all eggs are viable, etc. As a result, in vitro fertilization usually results in more fertilized embryos than the mother is willing to carry. If you want to take issue with in vitro fertilization, that's another fight for another day. We're just talking about what happens to the embryos which are not implanted.
Curious thing: religious people tend to support in vitro fertilization because they tend to want to reproduce more than secular folk do. An unintended consequence of in vitro fertilization is the destruction of viable, fertilized embryos. This is not a subject of dispute. Is this not "killing" in the eyes of the church? What makes it ok, when embryonic stem cell research is not?
"Drawing a line" is a bit of a straw man. We're talking about hours after conception, not weeks. At this point in time, the cells are indistinguishable from one another. A featureless blob of cells.
I, too, reject the notion that at some magical instant, the embryo becomes a fetus. It's a very gradual process, in the first few hours of which, you've definitely got a lump of undistinguished cells, and 9 months later, you've definitely got a living thing (assuming everything goes ok). There's a lot of grey area, and drawing a line is a vast oversimplification.
Fact of the matter is, we're talking about embryos that are slated for destruction. We're talking about preserving those to save / better future lives. We aren't going around harvesting fetuses.
Please, inform yourself. This sort of ignorance is embarrassing. "Harvesting fetuses" is not how we get embryonic stem cells.
Excess fertilized embryos are a byproduct of in vitro fertilization. These embryos (not fetuses) would be destroyed if not donated to science. The fertilized embryos are on the order of 50-150 undifferentiated cells -- not a fetus -- in a microscope, one appears to be a spherical blob. At this point, the stem cells are "cultured" -- fed, and allowed to multiply, just like we grow bacteria or other single-celled organisms.
Ah, how I love arguing with trolls. That was one example. I'd have better data if/.'s search didn't suck so hard.
But anyway, here's another example, from Sep 2001. The article, by the way, is on Bloomberg, a fairly mainstream publication. This isn't just slashdot. Google was already big news in 2001.
Do you mean, "back before Luddites knew what Google was"? Because a quick search of Slashdot shows (for example) 3 Google stories in the week of Dec 12-19 of 2002. Whoever modded parent as "informative" needs to learn how to do a little research.
Cool? Hell no. Unity is too 1989 for me. Also, way too buggy to be a no-questions-asked replacement UI in a stable release. I haven't used it since Natty, since it crashed so hard I had to hard-reboot the machine, less than 2 minutes after boot (just clicking around in the menus, looking for a way to configure the system). That experience really made me wonder: do ubuntu devs eat their own dogfood?
If you've got it, you could bring in a personal hotspot. But in my experience, if Ubuntu detects a wifi card, it works fine -- so even if you can't connect to anything nearby, just seeing the wifi utility operating is enough for me.
I won't bother telling you what make or model my laptop is. Last time I bought a laptop, I went in with an Ubuntu LiveCD. I'd pop it in a machine, wait for it to boot. I checked out 3 systems, and found one whose sound, video, wifi all worked after suspending and hibernating. The employees didn't bother me, but if they do, just explain that the cd won't harm the system, and you won't buy a laptop without verifying that everything works in your OS of choice. I'd walk out before purchasing another laptop that needs hours of fussing with drivers.
The success or failure of any currency is a matter of faith. Not enough people have bought into Bitcoin to be effective, so it's highly susceptible to "runs" -- everybody pulling out at once because of a perceived threat to its value, soon compounded by the value plunging due to everybody pulling out. In a very real sense, it's the people who predicted Bitcoin wasn't worth a shit that are at fault for its demise.
Yeah... that wasn't a good example. Look at Zimbabwe, or more historically, Brazil, for real-world examples of large economies (which BitCoin is not) tanking due to inflation.
I daresay, the Earth would be a better place to look for life. I mean, it's easy to get there. And you know that you'll find it, so no chance of disappointment. Crazy scientists.
Alternately, just ask for a raise to match / beat the amount offered by the other company. Don't tell them about the other offer. If you get the raise, cool, stick around another while. Otherwise, kick rocks.
Yeah, I'm an Apple-hater from the Linux camp. The world just lost one of its preeminent technological visionaries, and reading the article brought a tear to my eye. Fuck cancer, indeed.
Yeah, I'm dubious of their claims that they can conclusively prove that a certain structure is harder than everything else in a class with an evolutionary algorithm. Typically, evolutionary algorithms follow a "steepest ascent" pretty closely, and they're much better at finding local maxima than global. But then, I'm a mathematician, not a materials scientist, so what do I know?
Just sharing my personal experience. I tried to dive into a few small projects, and failed. I met William Stein, he helped me get started on Sage, (arguably a much smaller project back in '06... but still) and I've since watched lots of newbies get nurtured into productive developers.
I'd suggest the opposite. Most often, a small library is written and maintained by a single developer. There are relatively few bugs to be found, so you can only add features. The developer of the project might not be keen on the features you want to add (especially if you're an inexperienced developer).
Compare to a large project, like Sage. There are lots of bugs, lots of features on the todo list, and an active, thriving community. There's documentation and community support to help new developers get started on the project, and a "beginners" tag that gets used in the ticket system.
Those who do not believe in the future must not be aware of the past. Were you born yesterday?
Get this: malfunctioning. They should be able to avoid hitting the pedestrian in the first place. Also, there are the various situations in which the car or its inhabitants are doing something wrong and need to be stopped. Bottom line: cops must have the right to pull over vehicles. It's plain from Rule 2.
Take advantage of its collision-avoidance software. Surround it, and slow down.
Suppose a vehicle hits a pedestrian or cyclist, and drags the corpse. A witnessing cop can either (1) pull the vehicle over, or (2) follow the vehicle at a polite distance while all identifying features of the victim are shed to the ground. I think pulling the vehicle over is the appropriate course of action here. If nothing else, to prevent the trauma to hundreds of witnesses.
If a vehicle is being operated recklessly, it should get pulled over. If there are outstanding tickets / warrants for its owner, it should be searched / impounded. I don't see why the presence of a driver should matter here.
That's how in vitro fertilization works. We collect a dozen or so eggs, and splash a few thousand sperm on 'em. Some get fertilized, some don't. We overcollect the eggs because the surgery is invasive and always carries risk, not all eggs are viable, etc. As a result, in vitro fertilization usually results in more fertilized embryos than the mother is willing to carry. If you want to take issue with in vitro fertilization, that's another fight for another day. We're just talking about what happens to the embryos which are not implanted.
Curious thing: religious people tend to support in vitro fertilization because they tend to want to reproduce more than secular folk do. An unintended consequence of in vitro fertilization is the destruction of viable, fertilized embryos. This is not a subject of dispute. Is this not "killing" in the eyes of the church? What makes it ok, when embryonic stem cell research is not?
It's not a gradual process at all. It's nearly instantaneous.
Contradiction.
"Drawing a line" is a bit of a straw man. We're talking about hours after conception, not weeks. At this point in time, the cells are indistinguishable from one another. A featureless blob of cells.
I, too, reject the notion that at some magical instant, the embryo becomes a fetus. It's a very gradual process, in the first few hours of which, you've definitely got a lump of undistinguished cells, and 9 months later, you've definitely got a living thing (assuming everything goes ok). There's a lot of grey area, and drawing a line is a vast oversimplification.
Fact of the matter is, we're talking about embryos that are slated for destruction. We're talking about preserving those to save / better future lives. We aren't going around harvesting fetuses.
Please, inform yourself. This sort of ignorance is embarrassing. "Harvesting fetuses" is not how we get embryonic stem cells. Excess fertilized embryos are a byproduct of in vitro fertilization. These embryos (not fetuses) would be destroyed if not donated to science. The fertilized embryos are on the order of 50-150 undifferentiated cells -- not a fetus -- in a microscope, one appears to be a spherical blob. At this point, the stem cells are "cultured" -- fed, and allowed to multiply, just like we grow bacteria or other single-celled organisms.
A class-action lawsuit could change that.
That is NOT the reason I go to SFU. It's... one of a few reasons.
Ah, how I love arguing with trolls. That was one example. I'd have better data if /.'s search didn't suck so hard.
But anyway, here's another example, from Sep 2001. The article, by the way, is on Bloomberg, a fairly mainstream publication. This isn't just slashdot. Google was already big news in 2001.
Do you mean, "back before Luddites knew what Google was"? Because a quick search of Slashdot shows (for example) 3 Google stories in the week of Dec 12-19 of 2002. Whoever modded parent as "informative" needs to learn how to do a little research.
Cool? Hell no. Unity is too 1989 for me. Also, way too buggy to be a no-questions-asked replacement UI in a stable release. I haven't used it since Natty, since it crashed so hard I had to hard-reboot the machine, less than 2 minutes after boot (just clicking around in the menus, looking for a way to configure the system). That experience really made me wonder: do ubuntu devs eat their own dogfood?
If you've got it, you could bring in a personal hotspot. But in my experience, if Ubuntu detects a wifi card, it works fine -- so even if you can't connect to anything nearby, just seeing the wifi utility operating is enough for me.
I won't bother telling you what make or model my laptop is. Last time I bought a laptop, I went in with an Ubuntu LiveCD. I'd pop it in a machine, wait for it to boot. I checked out 3 systems, and found one whose sound, video, wifi all worked after suspending and hibernating. The employees didn't bother me, but if they do, just explain that the cd won't harm the system, and you won't buy a laptop without verifying that everything works in your OS of choice. I'd walk out before purchasing another laptop that needs hours of fussing with drivers.
The success or failure of any currency is a matter of faith. Not enough people have bought into Bitcoin to be effective, so it's highly susceptible to "runs" -- everybody pulling out at once because of a perceived threat to its value, soon compounded by the value plunging due to everybody pulling out. In a very real sense, it's the people who predicted Bitcoin wasn't worth a shit that are at fault for its demise.
Yeah... that wasn't a good example. Look at Zimbabwe, or more historically, Brazil, for real-world examples of large economies (which BitCoin is not) tanking due to inflation.
I daresay, the Earth would be a better place to look for life. I mean, it's easy to get there. And you know that you'll find it, so no chance of disappointment. Crazy scientists.
School... project? Are you sure that's a thing? Doesn't sound like it would help with standardized tests, so I'm pretty sure there's no budget for it.
Alternately, just ask for a raise to match / beat the amount offered by the other company. Don't tell them about the other offer. If you get the raise, cool, stick around another while. Otherwise, kick rocks.
Yeah, I'm an Apple-hater from the Linux camp. The world just lost one of its preeminent technological visionaries, and reading the article brought a tear to my eye. Fuck cancer, indeed.
Turns out, the iPad owners don't want to trade 'em in for printers. Strange, that.
Yeah, I'm dubious of their claims that they can conclusively prove that a certain structure is harder than everything else in a class with an evolutionary algorithm. Typically, evolutionary algorithms follow a "steepest ascent" pretty closely, and they're much better at finding local maxima than global. But then, I'm a mathematician, not a materials scientist, so what do I know?
Just sharing my personal experience. I tried to dive into a few small projects, and failed. I met William Stein, he helped me get started on Sage, (arguably a much smaller project back in '06... but still) and I've since watched lots of newbies get nurtured into productive developers.
I'd suggest the opposite. Most often, a small library is written and maintained by a single developer. There are relatively few bugs to be found, so you can only add features. The developer of the project might not be keen on the features you want to add (especially if you're an inexperienced developer).
Compare to a large project, like Sage. There are lots of bugs, lots of features on the todo list, and an active, thriving community. There's documentation and community support to help new developers get started on the project, and a "beginners" tag that gets used in the ticket system.