commit 3b51766e9842f2e890b6c3096fe52aaf62216754
parent ed3149c14940d5cfadc460afef6b05463a59bc35
Author: Anders Damsgaard <anders@adamsgaard.dk>
Date: Thu, 30 Apr 2026 20:49:28 +0200
content: add post about Simulink the UNIX way
Diffstat:
3 files changed, 40 insertions(+), 0 deletions(-)
diff --git a/pages/017-unix-simulink.cfg b/pages/017-unix-simulink.cfg
@@ -0,0 +1,8 @@
+filename=unix-simulink.html
+title=Simulink the UNIX way
+description=Miguel Arpa Perozo applies the UNIX philosophy to reimagine Mathworks Simulink, using software leverage, modularity, and pipes.
+id=glacier-laptop
+tags=unix, programming, simulation
+created=2025-01-10
+updated=2025-01-10
+#index=0
diff --git a/pages/017-unix-simulink.html b/pages/017-unix-simulink.html
@@ -0,0 +1,14 @@
+<p>The UNIX software engineering principles from the 1970s are as
+relevant as ever. Miguel Arpa Perozo applies the UNIX philosophy to
+reimagine MathWorks Simulink, using software leverage, modularity, and
+pipes. In his blog post, "Simulink the Unix Way", he describes creating
+a simplified version of Simulink where each block in a simulation is an
+independent executable, communicating through Unix pipes. This design
+enhances flexibility, integrates seamlessly with tools like gnuplot,
+and supports reproducibility with version control systems such as
+git. While the approach introduces challenges, like managing feedback
+loops and reduced user-friendliness compared to traditional Simulink,
+it demonstrates the enduring power of UNIX principles in modern software
+design.</p>
+
+<p>Check out his post here: <a href="https://mig-ap.com/posts/suw/">https://mig-ap.com/posts/suw/</a>.</p>
diff --git a/pages/017-unix-simulink.txt b/pages/017-unix-simulink.txt
@@ -0,0 +1,18 @@
+The UNIX software engineering principles from the 1970s are as relevant as
+ever. Miguel Arpa Perozo applies the UNIX philosophy to reimagine MathWorks
+Simulink, using software leverage, modularity, and pipes. In his blog post,
+"Simulink the Unix Way", he describes creating a simplified version of Simulink
+where each block in a simulation is an independent executable, communicating
+through Unix pipes. This design enhances flexibility, integrates seamlessly
+with tools like gnuplot, and supports reproducibility with version control
+systems such as git. While the approach introduces challenges, like managing
+feedback loops and reduced user-friendliness compared to traditional Simulink,
+it demonstrates the enduring power of UNIX principles in modern software
+design.
+
+Check out his post here: [1]https://mig-ap.com/posts/suw/.
+
+
+References:
+
+[1] https://mig-ap.com/posts/suw/
