Slashdot Mirror
Domain: uni-muenchen.de
Stories and comments across the archive that link to uni-muenchen.de.
Stories · 3
-
Why String Theory Is Not Science (forbes.com)
StartsWithABang writes: Earlier this month, a conference was held devoted to the question of whether untestable scientific ideas like string theory and the multiverse are actually science or not. While many opinions were stated and no one changed their mind, the answer is apparent: unless you're willing to change the definition of science to include "this thing that isn't science," then no, string theory is not science. It's a theory in the sense of a mathematical theory — like set theory, group theory or number theory — but it isn't yet a scientific theory. Of course, it could become science, but that would require that it actually do the things a scientific theory does: make testable predictions that can be validated or falsified. -
Physicists (String Theorists) and Philosophers Debate the Scientific Method
StartsWithABang writes: One of the most damning, albeit accurate, condemnations of String Theory that has been leveled at it is that it's untestable, non-empirical, and offers no concrete predictions or methods of falsification. Yet some have attempted to address this failing not by coming up with concrete predictions or falsifiable tests, but by redefining what is meant by theory confirmation. Many physicists and philosophers have jumped into this debate, and a recently completed workshop has produced no agreements, but lots of interesting perspectives being live blogged by a physicist. Also weighing in is a philosopher in three separate parts. -
Is Code Verification Finally Good Enough?
Jonathan asks: "As someone who has been following the development of software verification technology, a recent trend has intrigued me. It seems that the formal method people have finally come down off their high horse and are offering code verification as just another tool. This approach shows up in recent Java and C# based code verification tools that aren't aimed at 'proving correctness' so much as finding potential errors. Now it seems that such an approach is beginning to find its way into XP methods[pdf] as another verification tool to supplement unit tests. Given the current speed and effectiveness of tools like the Spec# verifier, is code verification via automated theorem proving finally going to make its way into the mainstream?"