Talk:Lava flow (programming)

This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles 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.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science

Low

This article has been rated as Low-importance on the project's importance scale.

Things you can help WikiProject Computer science with:

Here are some tasks awaiting attention:

Article requests :
- Requested articles/Applied arts and sciences/Computer science, computing, and Internet
Cleanup :
- Computer science articles needing attention
- Computer science articles needing expert attention
Copyedit :
- Computing
Expand :
- Computer science
Infobox :
- Computer science articles without infoboxes
Maintain :
- Timeline of computing 2020–present
Photo :
- Find pictures for the biographies of computer scientists (see List of computer scientists)
- Computing articles needing images
Stubs :
- Computer science stubs
Unreferenced :
- WikiProject Computer science/Unreferenced BLPs
Project-related :
- Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

Comments on Cleanup Tag

Some reasons why I think this article could use some improvement.

No sources or references are sited and after a quick search I could not find any. Other than pages that copy Wikipedia minus the volcano related articles.
The second paragraph sites NSAPI as an example of this behavior without explaining why it is a good example (if it is).
- since there is no explanation for the relationship between lava flow and nsapi, I am going to remove it Quickie (talk) 11:39, 6 October 2008 (UTC)[reply]
The third paragraph reads like it was written by a disgruntled computer programmer.

Ryan Roos 01:31, 15 November 2006 (UTC)[reply]

Link: http://www.antipatterns.com/lavaflow.htm http://www.icmgworld.com/corp/news/Articles/RS/jan_0202.asp http://www.ddj.com/dept/cpp/184403518 I haven't read through these, but I think we can say that it does exist. Shinobu 08:16, 15 November 2006 (UTC)[reply]

I am working on a lava flow right now. --207.135.146.176 (talk) 16:11, 30 May 2008 (UTC)[reply]

Original URLS for Archive.org links

Do we preserve the original URLs if we are providing an archived version of a page AND the original URL domain is now a porn site?

Untitled section

"Lava flow" is where the goal is resurfacing, but unintended solid landfill happens over time.

Unlike big ball of mud, "Lava flow" is stable, allowing "Lava flow" to happen over larger timespans. Unlike cancer or a bubble, the pieces of a "Lava flow" do not (fail to) propagate, but are buried frozen solid beneath new lava flows. Unlike the wheel reinvented, "Lava flow" cannot be dug out without the risk of catastrophic cave-ins. Instead of ruining a car one risks ruining a city. Unlike hoarding, the affection with "Lava flow" is low. Older flows are merely tolerated or purposely ignored.

"suboptimal conditions" is rather generalised. Eruption appears to be optimal given the chances, the moment and the setting when it happens, again and again. During an eruption spirits and chances are high, followed by burnout and abandonment. In case of "Lava flow" the lack of team continuity and architecture does not trigger failure. Instead, "Lava flow" develops nooks, holes and tunnels.

The issue with Lava flow is insecurity. Burnout of team and individuals happens again and again. Over time the holes and tunnels allow for unsolicited spelunking. — Preceding unsigned comment added by 77.173.226.152 (talk) 12:58, 11 February 2021 (UTC)[reply]