Yeah, I self-replied much later with a correction, sorry. I meant SRS. I think in acronyms in car-land, too. Sometimes the wrong ones.

Spacers can dick with the airbag clockspring arrangement. If your car is old enough this ain't an issue. But ISTR it's illegal to defeat a working airbag.

In terms of overall volume it might be true, in terms of displacement it would probably be false. IIRC modern cruise ships have more vessel above the waterline than anything which floated before them.

Minivans are dying. They have turned out to be a fad. They are being replaced by CUVs. It turns out almost nobody actually wanted to carry cargo and a lot of passengers, and a minivan is half-assed at both. The only exception went out of production because buyers decided it was too old — the Chevy Astro. Only one engine but since 2000 it was awesome, and available in short or long versions and AWD or RWD. RWD with 3.23s gets up to 26 mpg on the freeway at speed, I wouldn't lie to you. We would have got rid of it already otherwise. This is on an engine rebuild and a trans rebuild and an axle rebuild and a brake rebuild, though, I'm not claiming it's great in all ways. But have you seen the kind of mileage minivans get? Mostly it's no better than that, and they don't behave like a truck when you want them to. The only one I ever wanted to drive was the mid-engined Previa S/C, and it gets like 22 on the freeway.

Nah, it depends on the state. You can improve the system in some places. Also, if you mount a 5-point to the 3-point mounts you're a fool, that's a waste of effort. You really need a cage.

If you make the A-pillar too deep, you'll have the same problem. You won't be able to see through it sideways. You can see this effect at work in the back of many cars, where it's often quite annoying. Hopefully advances in materials science (e.g. cheaper carbon fiber) will let us have skinny A-pillars again.

I'm with you on this. STEM is a term that's being pushed on us by political/media types for who-knows-what reasons. It reminds me of people talking about "ya". I saw that thrown around a lot as a genre of books, apparently meaning "Young Adult (literature)", and it took me a while to figure out what the hell people were talking about. It's not really even a genre, but a classification of the target audience. It's pretty dumb use of jargon.

Back to STEM. Science, technology, engineering, and math. As though those are the same things. As though astrophysicists and programmers and marine biologists are all doing the same thing, and their expertise is interchangeable. Whoever lumped all that stuff together either has an agenda, or has no idea what they're talking about. In the contexts I see it being used, I assume that the intention is either:

(a) Companies that rely on software developers complaining about the lack of people with "STEM degrees", in an attempt to justify more H-1B visas; or
(b) Dimwitted programmers who want to lump all kinds of people into a subculture of "science people" to make themselves feel important. Like, "I'm a STEM person, just like Einstein, Neil deGrasse Tyson, and Carl Sagan. I'm just like those guys, because we're all STEM, unlike the filthy common people who like reading fiction and looking at art."

I mean, I'm not sure what else I'm supposed to take away from the whole STEM thing. Nobody talked about it 10 years ago. Having a lot of biologists does not help with developing software. Having lots of people capable of making iPhone apps does not push particle physics forward. I really think we need to drop the whole classification of "STEM" as a thing.

And the whole "preferably within the space industry"... what space industry does this guy mean? Does he want to work for NASA designing probes, or Boeing trying to design a space plane? Or is there some other "space industry". It'd be great to know, because it would really help narrow down what he'd need to do to accomplish that goal. But doing something related to space would probably mean, yes, you need to go back to school and get a undergrad in that particular field. Go find out what schools have the best Aerospace Engineering departments, and work your ass off, because that's going to get competitive.

Right, if you have a spacer behind the steering wheel, that brings it closer. Unless, of course, it doesn't have tilt. My latest car has a telescoping column, so it's not a problem, I just adjusted the wheel back towards me.

I would say that it's not just the implementation, but choosing which thing to implement in the first place. A lot of these fads, whether it's "big data" or "cloud computing" or "agile development", have become popular because they're extremely useful in some cases. The mistake, sometimes, is in thinking that you've found a single solution to solve all problems, and applying it everywhere will fix everything.

Someone else here used the example of the language "Ruby" as a fad that was useless because Ruby is "awful". That doesn't seem right to me. In my experience, which is admittedly a bit limited (I'm not actually a programmer), it seems like different programming languages have their own strengths and weaknesses, so you may want to choose a specific language for a specific goal. However, realistically, in the projects that I've managed, it always made the more sense to take into account (a) the language any current code is written in; and (b) the languages my team is most comfortable working with. If you have a bunch of PHP programmers who only know PHP well, working to revise a web application written in PHP, then Ruby is probably a terrible choice. But then, Perl and C++ would also be terrible choices. Those aren't bad languages. They're just not the best choice for that particular project.

I don't want to start a shit-storm by talking about languages, since as I said, I'm not a programmer, but I think that example is simple enough. Similarly, "cloud storage" like Dropbox can be great for small teams working from different locations on small office documents. On the other hand, if you're a big company with tons of people working in a central office, editing video files that are multiple gigabytes each, then you're going to want some kind of internal storage. The issue isn't about implementing your Dropbox well, but making an appropriate choice for your needs.

I think it's the "The illegals are fleeing from a situation which we created with our War On Some Drugs For Profit" argument.

Because you're being belligerent, and frankly, kind of dumb. That's "the reason why you shouldn't put things in the cloud". If it were the reason, then it could be easily fixed by having cloud providers give assurances that your data will be stored in a specific jurisdiction, and then you would have absolutely no reason not to put things "in the cloud".

But really my post is meant to indicate that there are some things about digital storage and transmission that needs to be considered, and the law might need to be revised to address any unclear points. In my mind, it's a bit like having copyright laws saying that you can't make any copies of copyrighted materials, ignoring (a) the possible need to make backups; and (b) the fact that, technically, copies might be made in various caches whenever you transmit or playback the digital file.

And by that comparison, I mean to point out that some things don't simply translate between the digital world and the physical world, so the rules have to be considered carefully. There may be issues that need to be worked out and clarified, even if it's only a common-sense judgement.

If you asked me to give a simple "yes" or "no" answer, right this minute, as to whether Microsoft is on the right side of things here, I'd say "yes". I'm just pointing out that it might not be something that you can decide simply without any unintended legal ramifications. Is that so hard to understand?

Who told you that? That's hilarious. Every automaker has complained about having to raise that line to deal with legal requirements, not to make them better pass crash tests, but because they've been legally required to raise the rear impact zone. Raising the rear increases drag, on its own; when you kick it up over the rest of the lines of the car, you're ultimately just increasing area. Sometimes it's an intentional part of a design meant to increase downforce, but that's exceptionally rare.

I meant SRS, I don't know how ABS came out

They should issue the VR goggles to the cops an make white people look black.

Well, you can get a spacer for some vehicles, it can be a challenge to retain ABS but it is possible.

Honestly, I'm having a little bit of a hard time deciding what I think about this. On the one hand, I'm very much in favor of privacy, and it seems to me that the rules for searching a server in Ireland should be approximately the same as the rules for searching a storage locker in Ireland.

On the other hand, I feel that it's important to consider that, with the whole "cloud computing" thing, it doesn't necessarily matter where your data is stored. For example, I might throw a document in my Dropbox folder and it get synced to "the cloud", and I have no idea where that file is physically located. It could be in Ireland, for all I know. So even though I may not live in Ireland or access it from Ireland, I may not have intended to store it in Ireland, and I may not even know it's in Ireland, it happens to be stored in Ireland at this moment. It could be shuffled off to another physical location tomorrow.

So I guess that makes me wonder, in such a hypothetical circumstance, if declaring it absolutely within the jurisdiction of Ireland might be opening a bit of a can of worms. If I throw a file up in my Dropbox and it ends up cached in Russia, without my knowledge or permission, is it now subject to Russian copyright laws? Is it now subject to Russian decency laws? If the information is considered illegal in Russia, am I now guilty of smuggling?

I don't know. I'm not a lawyer, so maybe I'm wrong to think that there might be some weird repercussions.