J.Random

We already did.

New trailer:

This thread needs this video.

Erm. What? I think this part needs an author's definition of "universe" and description of how, exactly, it's "generating energy".

You've been using it for a week. Give it some time to disappoint you. BTW, about these automatic updates. It's not the first one, either. The first one I've read about was an unstable NVidia driver update forced by Windows Update.

My first experience, updating notebook: 1. Download - install - reboot - no network. All devices are there, but no interfaces. Rollback. 2. Found out that's because Cisco VPN client was installed. Uninstall, repeat #1. 3. At least now there was network connection. Trying to install Cisco VPN - BZZZZ. Error. Tried installing DNE software, tried Dell client - nothing. At some point instead of error in the middle of install it has begun to drop the "Cisco VPN client is not compatible with this OS version" message without even starting the installer. Very informative. 4. Tracking. Tracking everywhere. Even when you disable tracking, your system will send data. Adding insult to injury, updates are automatic. My system will decide when it wants to reboot? More importantly, if some update breaks the OS completely, you won't be able to prevent it from installing. 5. Store apps. Undeletable vendorware. Like XBOX app. Why would I want this crap on my PC? It's ridiculous. 6. Then I saw a certain screenshot of someone talking to russian MS techsupport, asking if he will be able to reinstall Win10 a year later for free. The answer: you will have to buy a key in a year, even if you have used your right for a "free" update. It will be free only until you need to reinstall. MS Win10 FAQ states kinda otherwise, but it doesn't mention the time period. Looks like a classic bait and switch. 7. To hell with it. Rollback? BZZZZ. It seemes that at some point recovery partition was overwritten, even if it wasn't supposed to for at least a month. Now it's Win10 or nothing. Great. 8. Spent a couple of hours downloading different Win8/8.1 distributions with WUDT until one of them accepted the BIOS product key. 9. Back to Win8.1 on notebook, now dualboot with Debian, where I actually spend more time than in Windows. I don't think I will even try to update my main Win7 desktop at all. At least until I see some changes in Microsoft's attitude.

Nope. The issue is that there's no thermal shadow as you get lower than 500Mm or so. Your radiators simply won't radiate any heat, even if they're shadowed by heat shield. In fact, I think they start accumulating external heat at some point.

I know (see "application servers" in my previous post). I've had a pleasure to maintain and troubleshoot this kind of stuff. Not the best memories.

Wow. This thread really escalated from innocent joke into platform discussion. Never thought it would happen. My 2c. Java is awful. It's a perfect example of DLL hell, when different versions of runtime aren't compatible or interoperable and different apps ask you to upgrade and downgrade your JRE at the same time, and everyone else pulls its own jre along, or even installs it into the system. It even has its own freaking tzdata! GC is ridiculously bad, way too often I've seen recommendations to "just restart the container" if enterprise-class app is misbehaving. I've seen application servers where such restarts were scheduled daily. What's worst for me is that hardware manufacturers LOVE making management utils in Java. I've seen worse only once, when Hitachi storage management web app asked for Adobe flash. Java is BAD. PS Maybe there are good Java apps. I have never met one.

And that's exactly what I was taking about: in this case, it becomes a single point of failure, and if you want proper reliability, you have to redesign. Thank you for proving my point. Except those of us who use KJR.

If this washing machine is business-critical for me, I'll have at least three of them: active, standby and spare. Whenever one breaks, standby becomes active, spare is installed instead of broken machine, and the broken one is replaced by vendor through RMA, free of charge, and becomes new spare.

Here's a funny idea: unless we know exactly how it was certified, what reliability margins QA has provided, how it was supposed to be used and how it was used, we wouldn't blame anyone. After testing THOUSANDS of struts, SpaceX has found several which didn't meet the specs. Were specs clear? What the test looked like? No idea. They've said something along the lines of "the material grain was different in flawed struts", which may suggest that the production process has something to do with it (as in, the first strut made every day tends to be flawed because the equipment didn't heat enough yet, or the blank isn't ready when it's out of storage, or there's a material impurity in some conditions - there may be dozens of other reasons) - which means that yes, there's a flaw which wasn't known until this failure. We simply don't know. What I know is that there's such concept as "redundancy" for these cases. Just think about it: Falcon can lose an engine and get to orbit, but just one strut snapped and what's left can't hold helium tank in place? It looks like some freak accident to me. Strut supplier may need to improve manufacturing and QA process. SpaceX may need to redesign the inner support structures for their rockets. Either way, we don't know the whole story. Even this conclusion they've made is preliminary. And there's certainly no point in blaming anyone.

And now everyone will probably blame the supplier because "OMG PART BROKE AT 20% CERTIFIED LOAD".

You cannot simply "use another launch site". Besides, as I understand, they're building another launch site because they want to "land-land" first stages instead of "barge-landing" them.

Don't know about french version, but "in russian" message isn't really in russian. It's an example of an awful unedited machine translation into something resembling russian.

If the air is denser at night then why did OP's night parachute landing was faster? #PinkElephantInTheRoom

Psst! Don't tell anyone, but this rule seems to not work when people share the asset file with modified sun_flare.

People think it will be a silver bullet for every issue they've ever had in KSP. I, personally, hope for dynamically-cast shadows (because U5 doesn't have "Pro" version and features like deferred lighting should be enabled anyway) and stable x86_64.

I didn't tweak anything, except commenting out the CityLights config. A couple of weird things: - the film grain effect on terrain. Not sure if intentional, looks kinda cool. - z-fighting? Sun high above, turned on the landing gear lights to see terrain better. Flickers. Was on OpenGL at the moment, not sure if important (performance impact is HUGE under OpenGL, btw). - wrong cloud shadow direction near the pole.

Guys. This site shows some 2500 objects and it's scary? It's actually close to 19000 man-made objects (2009 NASA report). If you include natural objects (which always were there and somehow didn't cause Kessler cascade), it's estimated as up to 300000 objects larger than 1cm (same report). Now, what would be a proper representation? Spatial density graphs and cumulative flux maps. They can also be scary if you look at the graphs themselves (OMG IT HAS DOUBLED IN THE LAST 10 YEARS), but then you look at numbers and they're all like 10^-8 objects per km^3, or 10^-6 objects per m^2 (yearly accumulated flux). ISS performed 5 PDAMs in 2014, 0 (zero) in 2013, 3 in 2012. That's the amount of tracked objects which passed through the 25km-wide "pizza box" and had a chance of hitting ISS higher than 1:100000. Most of the above was taken from http://orbitaldebris.jsc.nasa.gov/. At least it has numbers, not just pictures of extremely crowded near-Earth space.

Not my point. You say, ISS has to dodge debris all the time. I say, read on actual PDAM requirements. It's not like they dodge a bullet every time they move ISS. PDAM is executed when anything is predicted to come through the ISS security envelope (I'll leave it to you to google the "pizza box" dimensions) and has a 1:100000 chance of hitting ISS (some sources say that yellow danger level starts at 1:20000). It's not "OMG CLOUD OF DEBRIS WILL HIT ISS IN 90 MIN! WARP ONE MR SULU!" More like "Huh. This crap may get as close as 25km to ISS. Let's move it just to be sure." Debris is a problem, sure. It's getting more of a problem as we put more things in space. But it's getting blown out of proportion by graphical representations like the one linked in the OP. Measures have been taken already, with the requirement to deorbit satellites or put them into graveyard orbits. Space is HUGE.

You may need to read on when exactly DAM is executed.

I mean these objects' dimensions. If their icons/"blips" were sized proportionally to their real size and Earth, you'd see nothing except Earth.

Is disproportional graphical representation supposed to make it look worse than it is?

Minotaur (refurbished Minuteman)? And SpaceX wanted part of the market as well, what, they've canned Falcon-1 without replacement? Huh. I was under impression that the small LV market was oversaturated. Guess I was wrong, Rocket Lab may actually get customers.