It sounds like you said it is simultaneously far left and far right?

This is so weird. I haven't visited the site the early Afghan War, maybe early Iraq War era, but I remember it being rather US-jingoistic, pretty right wing? And the site tilt was pretty heavily "white American male" not a famously left-wing demographic.

Meh, I knew of Fark back when all that was at the site was a single photo of a squirrel with large genitals.

I used to play on the mud Three Kingdoms in the mid '90s, and Drew was a Wizard (admin) there (named "Cletus"). When Fark became a link aggregator, I used to visit for the Photoshop contests (then ended up drifting off to Worth1000 when that became a thing). I'm not surprised that he ended up launching a porn site, because, well, Drew, but they launched a TV service that ended up getting gobbled up by Adult Swim? Weird.

Crazy to see all of the stuff that's happened with the site since I left; it entirely dropped off my radar.

Here's some example code of a "wrong" program that is 100% valid:

// well-formed code; no compiler will flag an error
int sum_two_numbers(int a, int b)
{
        return a-b;
}

Is it faster? It sounds really tedious and error-prone to me. If someone were to suggest I quit writing code and instead spend the rest of my career supervising the intern as he writes code for me to review and correct, I'd feel the same way about that.

So what?

Do you honestly think that it is going to be faster to

- Call 911
- Get an EMS vehicle dispatched
- Send it to them .. then to just go directly to EMS?

If you do, I think you need to rethink that process. Or, you have never before called 911.

Also, FYI, despite what you may think, ambulances DO have to follow the speed limit.

This whole process seems very dumb and not thought through.

If someone is not responsive in the back of a vehicle when the ride ends. the vehicle should just BE DRIVEN TO THE NEAREST EMS LOCATION, either the fire department or hospital. Calling the city EMS and wasting their time is nonsensical when the person IS IN A VEHICLE THAT DRIVES ITSELF ALREADY.

Then, if they get to the EMS and it turns out the person is just asleep, then charge them a few hundred dollars and reimburse the city.

the vehicles start looking more like a wingless airplane than a car.

And what does the company's name mean? ;) (Hint: it's Greek)

It adds up to 40 miles per day, not 5. 5 would be a cloudy day.

I used to be anti-solar-panels-on-cars back when solar panels were expensive, and ones of reasonable efficiency were even more expensive - the argument was, "put it on your roof where it belongs". But that's just not the case any more. Adding solar is just not that much of a cost to the car. It adds some complexities, but mainly in the design / early manufacturing phase.

Also:

The average American drives 37 miles per day.

1) So if you're in a sunny climate, it covers all of said average-driver's driving. Otherwise, said average-driver has to plug in occasionally, but not nearly as often.

2) Most people drive less than the average (the average is skewed by a long-tail - small numbers of people who drive very far every year). What you actually should be meaning is the median US driver; the median drives 23 miles per day. Most Europeans, even less.

3) Even for said "average american", their daily average is skewed by long drives (e.g. road trips and similar). Wheren of course you're plugging in, you'd be plugging in even if the car was adding 80 miles a day. But when not on road trips, their daily average is lower.

4) Surely you can see the appeal of the tangential benefits, such as being unstrandable - where even if you run out in the middle of the desert 20 miles from the nearest town, you're still going to get there, just delayed (remember that EV ranges, if you drive very slowly, increase like 2x, so 40 miles a day becomes 80, so a 20 mile shortfall is only a ~4h delay on a sunny day).

5) Nobody is saying, "One car for everybody". Of course appeal varies by person and by location. Here in Iceland for example we have three problems. One, very little sun at all for a good chunk of the year. Two, even in the summer, when the days are long, the sun is mainly low and circles around you. Solar power just kinda sucks here in general. And three, the three-wheel config would mean that the centre wheel wouldn't align with tracks in the snow from other cars (although there is a slight advantage, in that it also wouldn't align with road ruts from studded tyres, which often fill with water in the rain and become hazardous).

But somewhere in the southern US, it's a great option.

I am deep in the AI space

And I can tell you, the number of companies that have deployed AI to production well, to any kind of degree, are very slim.

The problem isn't the technology. Its that most companies are staffed and run by incompetants, and are unable to change at the pace needed to get benefit from AI

The disruption caused by AI is going to be felt as existing Fortune 1000 companies all start being disrupted by other companies with half of the operating expenses.

A

For those who didn't follow it, it's not that it's a contact binary that is so neat in and of itself, it's that when they modeled it, they determined that, the collision that formed it was less than 5 meters per second (less than 11 mph / 18 kph). Like a parking lot fender bender, but with the cars being ~750 billion tonnes.

N/T

17 more years? I can't wait to see people in their 70's through 90's adventuring through the universe. Are stargates handicap-accessible?

Seriously though dude this is actually interesting science news vastly more important than some cheesy show.

I love scapegoating individual developers as much as the next guy, but if you take a look at the Win32 API, you'll find loads of fun "features" such as:

- Every single function that takes a string has two implementations: one that ends with the letter A (and takes its strings as ASCII) and one that ends with the letter W (and takes its strings as UCS-16). And then it has a preprocessor-define (with no suffix) that gets expanded to either one implementation or the other, based on your compiler settings.

- windows.h defines preprocessor-tokens for min() and max(), which means any C++ program that ever calls std::min() or std::max() will error out with a very strange compile-time error, if it included windows.h first; the work-around is to define NOMINMAX first to prevent windows.h from polluting the namespace.

- Modern windows is perfectly capable of arbitrary-length file-paths, but ships by default with a 260-character filepath limit anyway, "to preserve backwards compatibility with older software that expects that limitation to be enforced". To get correct behavior you have to hand-modify your registry; otherwise you find out about this limitation when you go to unzip a .zip file and the unzip mysteriously fails even though the .zip file is valid.

These are all defects that other OS's simply don't suffer from, either because the other OS's were designed correctly from the beginning, or because the people in charge of the other OS's long ago took the hit (in short-term breakage) and fixed the problems rather than letting them linger forever to preserve backwards compatibility.

All Windows developers (good and bad) have to deal with these issues, probably forever, and every line of code they add to work around these problems has to be supported and debugged and tested as well, hence the damage compounds.

Before Trump, it was a cultural norm that a President of the United States was expected to follow ethical and moral guidelines as well as laws; not only because anything less would be dishonorable and a disservice to his country, but also because otherwise he would pay a steep political price for his unethical behavior. Trump's most significant political innovation has taken the form of figuring out how to convince a plurality of the American public that the only real standard for Presidential behavior is "whatever you can get away with".