Oh no I think is more the difference between makers and users. There were makers in my father's and grandfather's generation (I was born in 65) but there are so many toys available today that I just think kids are growing up as consumers. I rarely see anybody under 40 in my local electronics shop. Plenty of kids out buying phones and tablets though.
Also a lot of new tech these days is straight out of science fiction from the 1970s and 80s. People from older generations can just say oh yeah I read about this, while younger kids are more likely to be baffled by things which don't fit their worldview.
Its a 2D version if TCAS, where the vehicles have the option of coming to a complete halt if they face an impossible situation. TCAS uses communication between aircraft, so that they can negotiate a solution. So if you have two aircraft approaching head on one will tell its crew to pull up and the other to descend.
In your scenario communication between vehicles would definitely be required.
That bit only makes sense if the car had no idea how far away the truck way. As the car approached the truck the clearance should have increased and the car should have realized something was wrong if it didn't.
As far as I can see the truck driver was at fault, so why is such a big deal being made about this? Of course automation is going to make drivers lose concentration. Thats been understood for decades.
The language, the runtime libraries and the browsers were all changing rapidly at the time. It got us to where we are now. Javascript got a head start by ignoring some of the stuff which made java a pain for new programmers, like strong typing and security.
My father in law died when chemotherapy for cancer killed his bone marrow, and thus, his immune system. Maybe it would be a good idea to take samples of marrow stem cells before doing something which could kill the marrow entirely, so that the marrow could be re-booted, so to speak in the case of disaster.
Its really hard to do. It takes a lot of force to clean some surfaces. That requires a heavy robot. Then it needs to dispose of debris it collects so it has to be able to dump that somewhere appropriate. It needs to take care not to damage delicate things as well.
One issue I found working with very formal waterfall-like processes is that a typical project might generate several thousand problem change requests (PCRs). Each PCR is given to a developer to fix and that person makes whatever change which will make the problem go away. Do that a couple of thousand times and there is nothing left of your original clean architecture. Its just a mess.
But also Earth has shellfish which turn carbon dioxide into limestone. Venus does not.
Oh no I think is more the difference between makers and users. There were makers in my father's and grandfather's generation (I was born in 65) but there are so many toys available today that I just think kids are growing up as consumers. I rarely see anybody under 40 in my local electronics shop. Plenty of kids out buying phones and tablets though.
Also a lot of new tech these days is straight out of science fiction from the 1970s and 80s. People from older generations can just say oh yeah I read about this, while younger kids are more likely to be baffled by things which don't fit their worldview.
Ah no I didn't mean to imply that Linus is a steaming pile of dogshit masquerading as a wannabe politician.
I totally agree.
Back in the day, on newsgroups, if you did that you'd get absolutely SCREAMED at for "TOP POSTING", because it was WRONG..
This is the problem: Torvalds has never had an actual, paying job with a boss to answer to.
I like his preferred style too but I am not going to waste my life arguing about it.
Yeah but police who don't actually expect get shot by members of the public, during every shift they work.
Its a 2D version if TCAS, where the vehicles have the option of coming to a complete halt if they face an impossible situation. TCAS uses communication between aircraft, so that they can negotiate a solution. So if you have two aircraft approaching head on one will tell its crew to pull up and the other to descend.
In your scenario communication between vehicles would definitely be required.
That bit only makes sense if the car had no idea how far away the truck way. As the car approached the truck the clearance should have increased and the car should have realized something was wrong if it didn't.
Police lidars work at a hundred metres or so. Thats enough for avoiding conflicts like this.
Or not at all.
As far as I can see the truck driver was at fault, so why is such a big deal being made about this? Of course automation is going to make drivers lose concentration. Thats been understood for decades.
Its like they are not even trying. Python 3.5 is perfectly okay.
What about first or reverse?
Minification is a nasty hack for languages without a binary format. Python compiles to .pyc
Here you go
The language, the runtime libraries and the browsers were all changing rapidly at the time. It got us to where we are now. Javascript got a head start by ignoring some of the stuff which made java a pain for new programmers, like strong typing and security.
Java ran in the browser before javascript. It was a little slow at the time but what wasn't?
Thank God for unit tests
Handy when static analysis is all but impossible.
I don't see how locking between threads can work when their entire namespace is so mutable.
My father in law died when chemotherapy for cancer killed his bone marrow, and thus, his immune system. Maybe it would be a good idea to take samples of marrow stem cells before doing something which could kill the marrow entirely, so that the marrow could be re-booted, so to speak in the case of disaster.
No doubt both sides are spending big dollars on SEO to feed data into google's databases.
Its really hard to do. It takes a lot of force to clean some surfaces. That requires a heavy robot. Then it needs to dispose of debris it collects so it has to be able to dump that somewhere appropriate. It needs to take care not to damage delicate things as well.
Given the number of old people who eventually die by falling asleep while smoking, an intelligent smoke detector might be a good idea.
One issue I found working with very formal waterfall-like processes is that a typical project might generate several thousand problem change requests (PCRs). Each PCR is given to a developer to fix and that person makes whatever change which will make the problem go away. Do that a couple of thousand times and there is nothing left of your original clean architecture. Its just a mess.