Full self driving?

I think the GP has a point, the article switches from metrical to imperial units all the time. I don't know what is the imperial unit for a nm though

Just like blue thunder!

[citation needed]

Really interested not trolling.

I guess there is something unholy on that trinity of four :)

They do the same with SSH. The other day I mispelled homelinux.org (that's a dyndns domain) and ended up in some server asking my password. They listen to SSH for all domains *.mispelled-homelinux.org (I don't remember the exact name) and harvest logins and passowrds. Luckily I only allow public keys in my home router so I could notice.

Yes, they do. From the article you mention

"If you really need your results to add up exactly, especially when you work with money: use a special decimal datatype"

Is is true that the GP mentions small numbers and fp is in fact more precise with small numbers, but when the numbers get larger the difference between two representable fp numbers gets bigger also.

Yes, like Germany for example

Most mormons aren't creationists in the usual sense of the word. There isn't actually any official doctrine on the subject (most quotes that you find probably aren't official doctrine), and as far as mormon beliefs go, it doesn't matter. They believe what they feel comfortable with. Most will tell you that God works in natural ways, meaning that maybe he guides things a little, but he lets nature do stuff for him. In mormon doctrine, there is plenty of room for both science and religion. We're all about education and learning about how the world works. I don't believe in "magic," but science that we don't yet understand. Surely it's possible that God uses quantum mechanics, > 3 dimensional physics, and other things that we are only beginning to grasp.

I think the respondent's point is that many error messages are nonsensical and thus hard to remember. Often, I read an error message only to forget it 5 seconds after I've clicked Ok. Sure, a puppy dog or a baby would help with this (personally I like the colour and number system). What would also help is if the error was informative (and not written in binary).

Great advice, but for my family's safety, I'd want a professional survey and a report with a PE signature on it, not an amateur survey.

The other question is what portability really means.

Many people think that portability means "your code will run on multiple platforms".

With Java, I feel it is more a case of "your code will run on the Java platform".

The distinction is that, in the latter case, a lot of the facilities that have been implemented for existing platforms have to be re-implemented for the new platform. I feel a lot of effort has gone into creating things for Java that already existed outside it.

By contrast, many other programming languages attempt to fit in and play nice with whatever platform they end up being deployed on. Where Java has your programs run inside a virtual machine which is more or less the same across native platforms, other languages have you create programs that are just like the programs your native platform knows how to run. Where Java has people build functionality on the facilities provided by the virtual machine, other languages have you build functionality on the facilities provided by the native platform.

The approaches are different, and lead to a vastly different feel both during application development and when using an application developed using one approach or the other. Both approaches have their pros and cons.

Java's approach has the advantage that, absent deficiencies in the specification and bugs in the implementation, the Java platform is the same everywhere, regardless of native platform. The disadvantage is that you lose access to the native platform's facilities that are not also in the virtual platform. It also means that your software is almost certain to not really fit in with the native platform.

The other approach leaves you with access to the native platform's facilities, which is a double-edged sword. The disadvantage is that many of those will not be available on all platforms, and code that uses them will therefore be non-portable. The advantage is that you can make your software do anything that would normally be expected of an application on the native platform. Software developed using this approach will thus tend to integrate better with the native platform, and feel less foreign to users.

Doubled-plus. Sure, there are 40% efficient solar panels, if you have a satellite or space probe budget. Others are more like 20%, and when you're talking about super cheap panels, 10% is kind of a magic number. On the ground, 20%-ish for conventional or 10%-ish for super-cheap is already on-par, long-term, with other energy sources. If these really achieve 86% efficiency and don't cost a bloody fortune, this is revolutionary. Holy balls indeed!

Wait a minute... are you saying that that they're trying to save their data in a nonexistant location, or in a location that you don't personally agree with? I absolutely hate having a program tell me where to store the data. Unless I'm trying to store in in a read-only or system subdirectory, I'll put my files where I damned well please.

If you're talking about where the OS looks for the program, it sounds like the design of your installation program is at fault.