.TH SELF 7 .SH NAME just \- Just Don’t .SH AUTHOR Artyom Bologov .SH SYNOPSIS Just stop artificially restricting yourself to bad software. .SH TEXT .P So I wondered, why are we building arbitrary restrictions into our tech? It’s computers, they can bear anything. So why not .UR https://todepond.com/wikiblogarden/better-computing/just just .UE ... .TP .B Just don’t mandate types You don’t have to type everything. .UR https://wikipedia.org/wiki/Type_inference Just omit obvious types and the tech will catch up .UE . .UR https://wikipedia.org/wiki/Gradual_typing Only list necessary types or write your programs without them—it will catch up too .UE . .UR https://ericnormand.me/article/church-vs-curry-types And in case you do need types, you’d better use a decent enough type system .UE , not the useless bean-counting one. .TP .B Just don’t wait for compilation Just run the code. Just add more code to it and run it all together. Don’t wait while it compiles, just run and test it. .UR https://wikipedia.org/wiki/Just-in-time_compilation Compilation doesn’t have to be batched per files .UE . .UR https://wikipedia.org/wiki/Incremental_compiler It can be as granular as one function compiled into the program .UE . A running program too. .TP .B Just don’t throw errors \fBlost-compute (7)\fP You don’t have to throw errors and abort the computation. You can act on the erroring state and fix it. .UR https://lisp-journey.gitlab.io/blog/lisp-error-handling-how-handler-bind-does-not-unwind-the-stack And then proceed from where it stopped .UE . .TP .B Just don’t restrict objects .UR https://wikipedia.org/wiki/Multiple_inheritance Just inherit from multiple classes .UE . .UR https://metamodular.com/CLOS-MOP/ensure-class-using-class.html Just change which ones you inherit from if you want to .UE . .UR https://cl-community-spec.github.io/pages/update_002dinstance_002dfor_002dredefined_002dclass.html Just change the class definition whenever you like and patch its instances .UE . .UR https://realpython.com/python-metaclasses Just change how classes themselved (they are objects too, right?) behave .UE . .TP .B Just don’t tolerate the syntax No need to write all this every time. .UR https://wikipedia.org/wiki/Functional_programming Just wrap it into a function .UE . And function into a macro. .UR https://letoverlambda.com And a macro into a macro into a macro into a macro writing macro .UE . .UR https://wikipedia.org/wiki/Meta-circular_evaluator Just write your own language when programming .UE . Computer will handle any syntax. So don’t settle for inflexible syntax, just change it. .TP .B Just don’t shy away from gutting the compiler .UR https://stackoverflow.com/a/4257387 Just start the GC whenever you want .UE . .UR https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval#never_use_direct_eval! Just construct a new program inside the current one and run it .UE . .UR https://cl-community-spec.github.io/pages/compile.html Just compile a new function whenever you like .UE . Recompile the current one while it runs. .UR https://lispworks.com/documentation/HyperSpec/Body/f_wr_pr.htm Just modify how the runtime prints values .UE . .TP .B Just don’t program/“AI” it The world doesn’t need more software solutions. .UR https://malleable.systems It needs better, more humane, and more empowering tech .UE . We need social problems solved, not patched over with a new vibe-coded “AI” product. ================================================================================ .P .UR https://wikipedia.org/wiki/Common_Lisp Just use good programming tech .UE . .UR https://theguardian.com/technology/2023/jul/25/joseph-weizenbaum-inventor-eliza-chatbot-turned-against-artificial-intelligence-ai Just use this power for good .UE . Just be a decent person. .SH COPYRIGHT .UR https://creativecommons.org/licenses/by/4.0 CC-BY 4.0 .UE 2022-2026 by Artyom Bologov (aartaka,) .UR https://codeberg.org/aartaka/pages/commit/a91befa with one commit remixing Claude-generated code .UE . Any and all opinions listed here are my own and not representative of my employers; future, past and present.