The early prototype fast neutron reactors in the UK had issues with handling of the coolants, and are proving very expensive to decommission. Irradiated light metals coating the insides of pipes are difficult to deal with apparently. It's probably nothing that couldn't be solved with additional R&D, but how long before it actually pays off? The UK gave up on it before getting to a viable level.

but imho, cops should have cameras. And a fake off button.

Epic fail, routing protocols on 170+ POP routers all at the same time? Again, epic fail on design and implementation.

This works.

Dashcam video clears NJ man:

Ah, is it unstable or something from AT&T?

You don't watch TV? :P

Or worse, can't get DSL/fiber. Frak satellite (too slow and expensive).

I could as easily pick apart your arguments. I find it hard to imagine never using code that is shared with other projects for example. Why re-invent the wheel? Are you declaring code re-use dead? What about the system libraries? Do you hack those without notice too?

You could move the goalposts like that. I explicitly didn't respond because that is trying to derail the conversation.

But what the hell. You've stopped actually responding to the points I make.

So, I would contend that code reuse is helped, not hampered, by compiler-verified interfaces. I would contend that your "code reuse" is so stifling that it is literally inferior to copy-and-pasting... at least with copy-and-pasted code you can improve the module you copied without worrying that it breaks things.

And what happened to unit testing where you should easily enough shake out cases where people called a function they shouldn't have?

Why do you want to re-invent the wheel. Now, unit testing is good, but using unit testing to re implement (imperfectly) interfaces is, well, crazy.

I have argued that the programmer who just takes the IDE's word for it will eventually end up in deep trouble.

No, you've argued that programmers are perfect, that the comments will always be accurate, functions you call will never change, and the comments always need to be read for every getter and setter. And that's just to reject my examples.

And I categorically reject any of the above.

You seem to be arguing that duck typing is bad because shoddy practices rule.

Since the only example you have been able to give as to why duck-typing has any benefit, is as a patch to shoddy use of interfaces, this seems a remarkably dumb statement. I contend that duck-typing hurts the ability of the computer to detect errors, and your only response is that some people didn't properly use interfaces in legacy code. Not that interfaces are somehow a bad way to program. But a shoddy programmer may not have used them.

Well, fuck that. A paradigm that gives up useful features to paper-over shitty work, or allows code reuse between kinda existent modules via unspecified hack code that works 95% of the time is bad. Heck, any code that would need to be papered over like you suggest probably shouldn't be trusted. Duck typing is bad, it encourages bad practices and bad coding, and allows bad programmers to continue programming with silent errors as opposed to either fixing their shit or quitting their job and flipping burgers.

Cops have the authority and discretion to issue verbal or written warnings instead of citations for moving violations, so video recording won't change that.

And indeed, sometimes the requirement. For instance, in a state that shall remain nameless, the state patrol on drunk driving duty is supposed to pull over people who cannot stay between the lines. They don't bother citing the people who spilled soda in their lap, or were distracted, etc. It's not what their job is. But they do give a formal warning. That way, when their patrol is over, their sergeant can see they weren't asleep, or at a strip club.

I thought everyone knew this, or were able to google it especially if they are able to upload something like DDWRT to their router. Perhaps I had too much faith.

especially in AT&T if nobody he's ever spoken with about the issue knew enough to mention encapsulation. It doesn't sound like he's a dope, just possibly missed this factor. Somebody there could have simply asked him, "are you counting the overhead of PPPoE and ATM?" and then his post may have been entirely different, if it even existed at all.

With millions of home users and thousands of techs, the onus should not be on the customer base to understand how the vendor's product works internally.

Most places I've seen measure with encapsulation, because it's easier. The problem's not with the meter, it's with the small print

The problem actually is with the meter, if you're not allowed to see the meter.

"We're going to charge you based on this gas/electric/water/phone meter, but you have no way to verify the reading" is something the PUC wouldn't accept other than in the case of "the Internet".

the rules and licensing that happens on the State level should only be applicable to those roads.

Please explain the legal theory for the State being able to a-priori take away your right to free travel without due process of law and how that fits with, e.g. the 5/9/14th Amendments and the privileges and immunities clause. Remember, they seized most of these roads, however long ago.

Here's a more technical discussion from NHTSA. At page 74-75, the data elements of the Basic Safety Message I and II are listed. The BSM Part I message doesn't contain the vehicle ID, but it does contain latitude and longitude. The BSM Part II message has the vehicle's VIN. So this is explicitly not anonymous.

Back in the 1980s, when Caltrans was working on something similar, they used a random ID which was generated each time the ignition was switched on. That's all that's needed for safety purposes. This system has a totally unnecessary tracking feature.

Most of this stuff only works if all vehicles are equipped. It also relies heavily on very accurate GPS positions. However, there's no new sensing - no vehicle radar or LIDAR. The head of Google's autonomous car program is on record as being against V2V systems, because they don't provide reliable data for automatic driving and have the wrong sensors.

If something is going to be required, it should be "smart cruise" anti-collision radar. That's already on many high-end cars and has a good track record. It's really good at eliminating rear-end collisions, and starts braking earlier in other situations such as a car coming out of a cross street. Mercedes did a study once that showed that about half of all collisions are eliminated if braking starts 500ms earlier.

V2V communications should be an extension of vehicle radar. It's possible to send data from one radar to another. Identify-Friend-Foe systems do that, as does TCAS for aircraft. The useful data would be something like "Vehicle N to vehicle M. I see you at range 120m, closing rate 5m/sec, bearing 110 relative. No collision predicted". A reply would be "Vehicle M to vehicle N. I see you at range 120m, closing rate 5m/sec, bearing 205 relative. No collision predicted". That sort of info doesn't involve tracking; it's just what's needed to know what the other cars are doing. It's also independent of GPS. Useful additional info would be "This vehicle is a bus/delivery truck, is stopped, and will probably be moving in 5 seconds.", telling you that the big vehicle ahead is about to move and you don't need to change lanes to go around it.

Herp Derp there much?

you just called whatever the IDE autopopulated with, apparently without bothering to check what it was. Or at least that's what you said may happen.

Right, because you thought that the function was a different one because you misremembered the name. Or because you would assume a function like "getCurrentHealth()" would return the health of a character, and not, I don't know, concatenate two Strings randomly. Especially if that's what similar, or identically named, functions do throughout a library.

But, yeah, it may happen.

And oral lore is really "consulting with collegues" Which totally happens in real situations. If I ask someone, for example, how to get an arctan value outside the -pi/2 to pi/2 range, them explaining quickly how to use atan2f is more valuable than telling me a function name and "GTFO;RTFM".

Bottom line, I'm advocating for computers doing the work instead of comments (which may be unread, or out of date, or literally written after the code that referred to them). I posit many, many, reasons why having a computer check for errors instead of a human being. Your only response is that "Dude, but then I cannot hack two systems together using magic glue that happens to work, and enforces on everyone a requirement of never even optimizing their code, because any change could break my system. And could be avoided if I followed best practices."

When every advantage you suggest can be done in a superior way without using duck typing, I'm blown away. You have argued that perfect programmers don't need the fuckin' IDE, they can check their own work. Well, perfect programmers don't need the fuckin' comments either, they can read the entire code and know what happens.

I can only assume you're trolling, because while I've heard people defend duck-typing before, I've never heard such a malformed argument.