🦞🌯 Lobster Roll

Thread

Non-Recursive Make Considered Harmful (research.microsoft.com)
Abstract: Most build systems start small and simple, but over time grow into hairy monsters that few dare to touch. As we demonstrate in this paper, there are a few issues that cause build systems major scalability challenges, and many pervasively used build systems (e.g. Make) do not scale well....

Stories related to "Non-Recursive Make Considered Harmful" across the full archive.

Non-Recursive Make Considered Harmful (research.microsoft.com)
Abstract: Most build systems start small and simple, but over time grow into hairy monsters that few dare to touch. As we demonstrate in this paper, there are a few issues that cause build systems major scalability challenges, and many pervasively used build systems (e.g. Make) do not scale well....
Counting in Regexes Considered Harmful: Exposing ReDoS Vulnerability of Nonbacktracking Matchers (usenix.org)
Build systems at scale: Non-recursive Make Considered Harmful (2016) [pdf] (microsoft.com)
A non-recursive sorting algorithm (haskellexists.blogspot.com)
Learning Haskell as a Nonprogrammer (superginbaby.wordpress.com)
QuickChecking non-Haskell Code (brianmckenna.org)
State considered harmful - A proposal for a stateless laptop (blog.invisiblethings.org)
Intel x86 Considered Harmful (blog.invisiblethings.org)
Stack Overflow Considered Harmful? The Impact of Copy&Paste on Android Application Security (aisec.fraunhofer.de)
Traditional Assignment Considered Harmful (web.cse.ohio-state.edu)
Exploration of the complete design space for data-movement primitives supports the following conclu- sions: (1) traditional assignment is fundamentally flawed, and (2) any other data-movement primitive would be better. Pike, S., Heym, W.D., Adcock, B., Bronish, D., Kirschenbaum, J., and Weide,...
“Cloning considered harmful” considered harmful (plg.uwaterloo.ca)
50th Anniversary of "Go-to statement considered harmful" (cs.utexas.edu)
Fresnel Equations Considered Harmful (renderwonk.com)
Dead Store Elimination (Still) Considered Harmful (usenix.org)
Abstract: "Dead store elimination is a widely used compiler optimization that reduces code size and improves performance. However, it can also remove seemingly useless memory writes that the programmer intended to clear sensitive data after its last use. Security-savvy developers have long been aw...
A non-symmetric divide-and-conquer recursive formula for the convolution of polynomials and power series (arxiv.org)
Examples of Incorrect Abstractions in Non-Haskell Languages (reddit.com)
#ifdef Considered Harmful, or Portability Experience with C News (1992) (literateprogramming.com)
large-anon: Practical scalable anonymous records for Haskell (well-typed.com)
Smooth, non-invasive Haskell Stack and Nix shell integration (tweag.io)
``Rewrite it in Rust'' Considered Harmful? (goto.ucsd.edu)
Non-lazy futures considered harmful in Rust (swatinem.de)
"GOTO Considered Harmful” Considered Harmful (1987) (web.archive.org)
Non-Obvious Haskell Idiom: Guard-Sequence (entropicthoughts.com)
Non-Obvious Haskell Idiom: Conditional For (entropicthoughts.com)
Recursive Make Considered Harmful [1998,2006] (accu.org)
Alan Kay: Normal Considered Harmful (youtube.com)
Haskell prelude using GHC's new data kind promotion (blog.atnnn.com)
tmpfs considered harmful (rwmj.wordpress.com)
The Architecture of Open Source Applications (Volume 2): The Glasgow Haskell Compiler (aosabook.org)
Big O analysis considered harmful (t-a-w.blogspot.co.uk)