It also ignores the fact that people mishear and misunderstand each other. All. The. Time. Those gaps we fill in? Often erroneous. People actually expect more from computers than from other people: nearly perfect listening AND comprehension.

NAT is still possible with IPv6. It would really just force people to "break" the internet if they tried something like that.

Why not just make it 640k bits? 640k ought to be enough for anybody.

Yep. A few years ago I got grilled by a (nice) guy in Israel about my certs, even though I had gotten all the answers right on their notary certification test. It was tougher than most "Green bar" certs are today. Which is how a competent CA works.

RIP old Startcomm.

If you can't keep a job, maybe it's because nobody wants to deal with a racist scumbag.

-jcr

fluency in [ mandarin | Chinese ] is a plus

Of course it's a plus. I'm likely to be hiring a group of Mechanical Engineers in the next six months, and I certainly want at least one of them to be fluent in Mandarin to make it easier to work with Chinese suppliers. It would be pretty handy if they speak Korean, Japanese or Hindi, too.

-jcr

That's not an unreasonable requirement, given the need to work with manufacturing operations in China.

-jcr

The department of labor found a statistical anomaly, and decided to try to nail Thiel for supporting Trump.

-jcr

Been there, done that. Basically had to go to the max dose of oxycontin just to take the edge off the pain.

This page you can see some pictures of the procedure and instruments people used on kidney stones in the 1600s. It seems unimaginable that anyone would subject themselves to that -- without anesthetic -- unless you've actually experienced it.

This company works with TLAs so they are obviously working hard to hire ppl that are NOT SPIES. Yet, we have 2 main types of Spies to be concerned about: Russian and Chinese. Chinese and Indian account for the vast majority of the Asian ppl. Obviously, the CHinese are going to be looked over hard. So, that leaves the Indians. And oddly, within India's military, they are VERY close to Russia. Much closer to Russia than to the west. As such, Indians are going to be looked at as well.

And dept. of Labor is saying that we must hire ppl of which a known quantity is going to be spies.

I have dealt with 1-2 spies already and both were Chinese. I would hate to have Dept. of Labor be able to control a company that deals with national security to this degree.

That said, we badly need a high speed rail network in the U.S

No, we don't. We have aircraft.

-jcr

Air travel should be one of those novelty things that the lucky few can justify

Fuck you. I'll buy what I can afford, and your approval is neither sought nor required.

-jcr

A properly designed system shouldn't be highly dependent upon any kind of persistence layer, although if you follow the provider's example programs you'll tend to spread dependencies through your code. But a smart designer hides that all away deep down in some kind of abstraction.

A demonstration of exactly how little you are dependent on a vendor is probably a very good thing, if you're a big customer. Oh, we'll run *this* part of our product on the other guy's cloud service and boom. It happens. Shows the vendors who's boss.

No, I'm the one pushing all the clean items. Solar, Wind, along with geothermal, hydro AND nuke. Without all of these, we can not solve the issue.

The developer of this thing has thoughtfully provided a "hello.c" file and cc. Oh, yes, and emacs. So go ahead and type:

cc -o hello hello.c

and marvel at the speed.

This environment is just like my first full-time, non-student programming job. There was no IDE, so we pretty much lived in emacs. I haven't used emacs in decades, but my fingers still remember the key bindings for the commands -- as long as I'm not trying to consciously remember them.

It was on a 68020 running at 16 MHz which delivered a grand total of 2 MIPS at 16 MHz. We shared all that computing power among four programmers, which was luxury because the system was supposed to support 16 users (32 max).

It seems almost inconceivable, but the funny thing is it was really just as fun programming back then as it is now with a supercomputer all to myself. Our office was next to a reservoir, and used to start a compile, wait five minutes for the parsing to catch any syntax error (about 75% of the time), then go for a walk on the 1.5 mile trail around the pond. Then I'd stop in at the convenience store to buy a cup of coffee, and head back to the office, and make would just be finishing up the linking. God forbid you got a link error though. That's why we had time to read the entire Unix manual (all eight sections) cover to cover. Many times.

This has fed my conviction that user perceptions of system speed are as strongly affected by consistency as it is by absolute speed. If you're used to a build taking fifteen seconds,a sudden change to 30 seconds seems unbearable.