Disagree. Tumbleweed moves, and anyone who gives it any notice while driving is putting others at risk. Any sane system ought to be able to recognize tumbleweed and give it the appropriate lack of attention.
I think massive improvements are made to safety when object collision is context aware. Heck, in my driving instruction manual they had an ordering of, "What to hit in an emergency situation," went something like "Animals, ditch, traffic on same flow pattern, structures (buildings, poles), pedestrians, oncoming traffic."
An even more obvious use of contexts: There are two objects, a bag and a baby. You have to hit one, which one do you run over? I think it is possible to build systems that make better decisions than chance in this kind of circumstance.
I would put it to you that at the speeds a motor vehicle travels
Such as 10km/h?
I would put it to you that situations where one would have to make a bag/baby decision one should not be travelling at highway speeds.
Even though a perfect decision can't be made in every situation, I contend one can do better than, "Fuck it, I'll probably hit it regardless," when operating a motor vehicle.
As someone who has successfully prevented collisions with cats, deer, and moose under differing circumstances (a moose in fog at night is about the most frightening thing I've ever come across), I think the ability to inform ones driving based upon the nature of a sudden unexpected obstacle is a critical part of driving well.
Bag: May involve gently changing direction, do not brake erratically, do not disturb flow of traffic. Baby: May involve driving into the ditch, other traffic, making full use brakes, honking horn, etc.
As someone who's done a fair bit of the reverse, and has recently needed to write C bindings for a few other languages (go, ruby), I thought this shouldn't be nearly so hard as you describe. Here's what I've come up with:
Example.cpp: Implements a class and C bindings for that class (The bindings could obviously be in a different file) #include "ExampleCBindings.h" #include class Example { public:
Example(int v) { value = v; std::cout << "New Example(" << v << ")\n"; }
~Example() { std::cout << "Deleting Example(" << value << ")\n"; }
int getValue() { return value; } private:
int value; };
ExampleCBindings.h: Public C bindings #ifdef __cplusplus extern "C" { #endif
typedef struct Example_t Example_class;// what I love most is that Example_t never exists;)
Example_class* newExample(int value);
void deleteExample(Example_class* example);
int ExampleGetValue(Example_class* example); #ifdef __cplusplus } #endif
main.c: Simple C driver program that uses the api #include "ExampleCBindings.h" int main() {
Example_class * ex1 = newExample(5);
Example_class * ex2 = newExample(ExampleGetValue(ex1) + 2);
deleteExample(ex1);
deleteExample(ex2);
return 0; }
Limitations include: * Does not support objects existing on the stack. You're in C, this is the norm for opaque data structures. * Need to individually wrap every function. Would need to create separate wrappers for overloaded functions, or write a variadic function that doesn't enforce types (Sigh, neither language supports reflection)
However, if you only wish to implement public functions, writing a script that autogenerates a wrapper like this would be fairly easy (I've done similar for a mocking framework for C code - now that's actually painful (not the script, inserting stubbed functions into a binary)). A little googling came up with a more formal attempt here.
And to prevent any of the command lines going into your command history, and thus exposing your passphrases, be sure to run (once on each account that will use the shell script):
"Our 32nm chip that won't be available for 8 months beats a chip that has been out for a year and made with a 40nm process"
Uhm... duh? By that definition, ARM is better than ARM. Hell, AMD is better than intel:P
Dominant reason is latency. Throwing around compressed video forces latency of at least 1 frame, in an industry where latency is measured in fractions of a scan line (single horizontal line in a frame)
Would need encode/decode hardware at every endpoint, this would add a lot of cost.
Compressing, uncompressing, recompressing video increases artifacts, can smooth/blur out the footage.
As well, not everybody viewing HD footage has a shitty provider, and giving providers the excuse "it comes that way" won't help anybody.
"Transcoding for iPod-like and USB Mass Storage devices that complements transcoding for Local Collection"
AKA when I use it to copy music to my android phone, it automatically transcodes everything to a preconfigured format. I consider that a small, but very handy feature (as I keep all my music in FLAC).
Regardless of what you think of the practicality, the ISS does exist. Therefore, it is feasible to have a space station (because we have one already). So your statement that, "None of [space stations, moonbases, interplanetary travel] are remotely feasible," is clearly false by counterexample.
Slashdot Mirror
Don't know what you mean by stating "Too bad the link is dead." It works for me.
Here's the link from Wikipedia's source:
http://www.bizjournals.com/pittsburgh/news/2012/05/29/spacex-success-brings-pittsburgh-space.html
According to http://en.wikipedia.org/wiki/List_of_Falcon_9_launches, someone has already contracted with them to deliver a payload to the moon (fifth from the bottom of the list).
Disagree. Tumbleweed moves, and anyone who gives it any notice while driving is putting others at risk. Any sane system ought to be able to recognize tumbleweed and give it the appropriate lack of attention.
I think massive improvements are made to safety when object collision is context aware. Heck, in my driving instruction manual they had an ordering of, "What to hit in an emergency situation," went something like "Animals, ditch, traffic on same flow pattern, structures (buildings, poles), pedestrians, oncoming traffic."
An even more obvious use of contexts: There are two objects, a bag and a baby. You have to hit one, which one do you run over? I think it is possible to build systems that make better decisions than chance in this kind of circumstance.
To alert other drivers that:
1. They should pay attention
2. I'm about to get all kinds of crazy
Ah, thanks. I didn't know why it worked, just found it incredibly convenient. And I think in my case it is set somewhere in /etc/profiles.d/.
Note to self: read through bash configuration documentation.
I would put it to you that at the speeds a motor vehicle travels
Such as 10km/h?
I would put it to you that situations where one would have to make a bag/baby decision one should not be travelling at highway speeds.
Even though a perfect decision can't be made in every situation, I contend one can do better than, "Fuck it, I'll probably hit it regardless," when operating a motor vehicle.
As someone who has successfully prevented collisions with cats, deer, and moose under differing circumstances (a moose in fog at night is about the most frightening thing I've ever come across), I think the ability to inform ones driving based upon the nature of a sudden unexpected obstacle is a critical part of driving well.
Bag: Should be avoided.
Baby: Should be avoided.
Bag: May involve gently changing direction, do not brake erratically, do not disturb flow of traffic.
Baby: May involve driving into the ditch, other traffic, making full use brakes, honking horn, etc.
You really think it doesn't matter?
As someone who's done a fair bit of the reverse, and has recently needed to write C bindings for a few other languages (go, ruby), I thought this shouldn't be nearly so hard as you describe. Here's what I've come up with:
Example.cpp: Implements a class and C bindings for that class (The bindings could obviously be in a different file)
#include "ExampleCBindings.h"
#include
class Example {
public:
Example(int v) { value = v; std::cout << "New Example(" << v << ")\n"; }
~Example() { std::cout << "Deleting Example(" << value << ")\n"; }
int getValue() { return value; }
private:
int value;
};
extern "C" {
Example_class* newExample(int value) { return (Example_class*) new Example(value); }
void deleteExample(Example_class* example) { delete (Example*) example; }
int ExampleGetValue(Example_class* example) { return ((Example*) example).getValue(); };
}
ExampleCBindings.h: Public C bindings // what I love most is that Example_t never exists ;)
#ifdef __cplusplus
extern "C" {
#endif
typedef struct Example_t Example_class;
Example_class* newExample(int value);
void deleteExample(Example_class* example);
int ExampleGetValue(Example_class* example);
#ifdef __cplusplus
}
#endif
main.c: Simple C driver program that uses the api
#include "ExampleCBindings.h"
int main() {
Example_class * ex1 = newExample(5);
Example_class * ex2 = newExample(ExampleGetValue(ex1) + 2);
deleteExample(ex1);
deleteExample(ex2);
return 0;
}
Limitations include:
* Does not support objects existing on the stack. You're in C, this is the norm for opaque data structures.
* Need to individually wrap every function. Would need to create separate wrappers for overloaded functions, or write a variadic function that doesn't enforce types (Sigh, neither language supports reflection)
However, if you only wish to implement public functions, writing a script that autogenerates a wrapper like this would be fairly easy (I've done similar for a mocking framework for C code - now that's actually painful (not the script, inserting stubbed functions into a binary)). A little googling came up with a more formal attempt here.
And to prevent any of the command lines going into your command history, and thus exposing your passphrases, be sure to run (once on each account that will use the shell script):
echo "export HISTIGNORE=\"safepassword*\"" >> ~/.profile
Or you could just put a space before the command you are running - this works for me in every bash shell I've encountered recently.
Seconded.
Actually, I run a modern version of the Linux Kernel on hardware slower than a 486 every day, though I admit I have access to a whopping 16 MB of RAM.
Seems snappy enough to me.
In the prairies? Damn near all of them.
No, the US knows full well they are violating Iranian law. They, like most, just don't care about Iranian law.
Desperate much?
"Our 32nm chip that won't be available for 8 months beats a chip that has been out for a year and made with a 40nm process" Uhm... duh? By that definition, ARM is better than ARM. Hell, AMD is better than intel :P
It's Microsoft. Do the words "Zune" and "Squirt" ring a bell?
Could have saved them a bundle with my competing technology, a sign that says "5:30am to 8:30pm: congested"
That is possibly the best review of a technical book I have ever read. Thank you!
As well, not everybody viewing HD footage has a shitty provider, and giving providers the excuse "it comes that way" won't help anybody.
"Transcoding for iPod-like and USB Mass Storage devices that complements transcoding for Local Collection"
AKA when I use it to copy music to my android phone, it automatically transcodes everything to a preconfigured format. I consider that a small, but very handy feature (as I keep all my music in FLAC).
...but of course absolute thinking is also a sure sign of a deranged mind.
Cognitive Dissonance. That is all.
what makes prefering same sex pairings more 'normal' than someone who prefers children?
I guess it's that most same sex pairings are between consenting adults, whereas children often are not allowed to give consent for such things.
FTFY
What is a "Nokia"?
A person, just like you and me :P
how can you sell 500000 times that amount of cobalt without dropping the price to the floor?
By doing something that increases demand 500000 times.
Regardless of what you think of the practicality, the ISS does exist. Therefore, it is feasible to have a space station (because we have one already). So your statement that, "None of [space stations, moonbases, interplanetary travel] are remotely feasible," is clearly false by counterexample.