Talk:Crash-only software

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

Ha ha. Is Windows XP intended to be crash-only software though?

As long as data isn't being written, and the user doesn't want to save any OS changes, Windows doesn't need to be 'shut down.' Otherwise, Windows is NOT intended to be crash-only. Hypothetically if it was, and settings are saved before shut-down, a person could save system-ruining settings without the OS waiting to make sure it survived. This will likely never be the case, as large non-volitile buffer hard drives will allow extremely fast Windows Vista shut down and start up times however, as they can quickly flash the data to the buffer and power down. 67.183.81.226 00:41, 28 January 2007 (UTC)[reply]

This article either needs more references or should be deleted. As far as I can research and understand this is not a common, well-know, lesser-known, practiced, or even discussed method of developing software. At the very best this article, which has been of poor quality since it's creation in 2005, is simply to validate some article posted by some random people at stanford that has since been taken down. The section on Erlang is completely unrelated and adds nothing to the understanding of "crash-only software".74.101.125.183 (talk) 17:34, 4 June 2019 (UTC)[reply]