That won't necessarily help much, actually -- libbluetooth is just the userspace component, the kernel drivers will probably still be initializing the hardware. You'd be better off disabling kernel support: blacklist the kernel modules for your hardware. Then you don't need to remove random packages, they just won't have anything to talk to in the kernel and will remain harmless and inert.
Alright then, how about... a compounding pharmacy that deals with narcotics? I mean really. They're selling medicine compounded into different forms, this isn't some kind of strange, unique new business they're in. I can get compounded codeine lollipops for my kids from a pharmacy. Pot brownies aren't all that different.
Except Anonymous didn't actually suggest putting the relay on Mercury, they suggested putting it in an orbit near Mercury's. I was hoping you had a reason for assuming the relay would be on Mercury besides failure of reading comprehension, but I guess not.
Why is putting a platform on or orbiting Mercury useful? It's not inhabited and it isn't always in the right place around the sun, sometimes it's going to be behind (or in front of) the sun at the same time as the thing you're trying to communicate with. You'd need a constellation of sun-orbiting satellites so there was always at least one in the right relative position.
Is it that you want the satellites near a magnetosphere? That kind of almost makes sense.
Why would there be temperature swings? The sun doesn't have a dark side and you wouldn't want a communications platform to turn very quickly anyway or be near anything else that could block line of sight to it. Just put a sunshade on one side of the platform that can withstand high temperatures -- 450C is no hotter than my soldering iron -- or am I missing something?
Is there any reason Amazon can't just sell the ebooks for 30% more in Apple's store than in its own?
Did you read the comment you're replying to: "...Force other eBook sellers to raise prices, and now Apple's own solution looks much more attractive...."?
Since the publisher is the one paying royalties to the authors, I hope the publisher's getting the lion's share of the money from distribution. I'm not optimistic about what the author gets after that either, but that's a separate complaint, isn't it?
Indeed. That's just how we use the language -- "engineer" has always meant a bunch of things besides just "professional engineer". In some places a "locomotive engineer" is the guy that drives a train! Now sometimes it means a software developer with no formal training. PEs deserve respect, but the word "engineer" just isn't used exclusively in association with professional engineering.
Maybe that's how it's used in some offices where lots of PEs work?
"Professional engineer", or the specific titles, "electrical engineer", "mechanical engineer", so on, I have no problem agreeing that those titles generally are and should be reserved. Sometimes you need to make the distinction, and this is how I see people use the titles.
Incidentally, if you refer to yourself professionally as a "welder" or "electrician" I expect you to be certified in your trade, especially before you do any work on safety-critical equipment. The trades example isn't as strong as all that.
I cannot for the life of me see what you're talking about. I found the area -- about halfway between the Channel Islands and Catalina Island, indicated by the news spot -- and it's flat black for the entire period. I see a lot of clouds that sort of look a little like contrails all over everywhere else.
Are you serious or is this just inane bitterness?
(a) We're talking about an SUV here, not a sports car. The design tradeoffs for the powertrain are going to be very different.
(b) Even if the Tesla Roadster really were that close to being the tzero, which is something I'm not convinced of, and the Model S were that close to the Roadster, Tesla's still the company with the integration and manufacturing experience.
(c) Tesla owns a manufacturing plant whose purpose is to produce powertrains for the Model S.
The electronics and control are the easy part. People who haven't thought about it don't really appreciate how much work goes into setting up a production run for machined metal parts: beyond the basic mechanical what-goes-where, there are tradeoffs in material choices, choices on which parts to source stock and which to manufacture custom, arranging manufacturing capacity and tooling up the plants where the production will be done, and QCing the finished product.
Of course they *could* do it, but Tesla has a powertrain that's pretty much exactly what they'd need already developed for the Model S, and they're presumably already gearing up for production of the components.
Tesla's proven they know what they're doing with the Roadster, so I can see why Toyota would want to spend $60M to adapt an almost-exactly-right design with a very low risk profile than spend probably more pulling together their existing R&D projects and tooling up, with all the entailing higher risk and extra development time.
The hybrid powertrains they've been developing are conceptually very similar to an all-electric powertrain, but there's a lot of mechanical re-engineering they'd have to do, and that takes time. Hell, maybe $60M is a loss, but they're doing this deal because all their best engineers are busy working on another project and they just don't have the staff to handle a big rush job right now. Staffing is a big deal!
Yeah, you have to read all the way through to the 3rd paragraph to find out about Halo Wars. Pretty obscure.
(Point taken, but come on, you have to be Indie Rock Pete to think Halo would have been better for being a bit player RTS rather than the phenomenon it is!)
In fact, if you really like developing games, you ought to take 8/5 corporate soul-crushing job (that will crush your soul much, much less) and just make games in your spare time (or at work during downtime) for fun.
Bad advice! If you do that you're working 80-hour weeks anyway, you might as well get one of those soul-crushing 80-hour-week games industry jobs and spend all your time doing what you want to and not just half of it. (Or did you think being a corporate programmer was fun and not soul-crushing...?)
Plus, if you're actually working in the industry, you will (a) get to work with other, more experienced game programmers and learn the game-specific parts of the trade 5x faster and (b) meet a lot of talented and motivated artists and game designers, so that when you do decide to break away and do some fun indie stuff, you don't have to do it alone. Unless you want to, in which case you can use those contacts for mentorship too.
And don't do Full Sail. People who care what school you went to will look down on you for it, people who don't care, well they don't care. Just be a great programmer, learn some assembler and the basics of working with vectors and matrices, and you'll be in demand.