Can projects fitting with the #permacomputing concept be something else than low level?
9 comments
@raphael I think the answer really depends on how bleak your outlook for the future is. To some degree permacomputing is speculative computer science, so (in my opinion) really it's a question of what problems you see actually coming to pass that would require making changes to how you write software today to ensure that software is still useful in the future. @raphael for example, I think my own outlook is fairly optimistic in terms of availability of computing hardware and energy availability, but I'm pessimistic about the digital divide and expect we will have more prolonged major supply shortages here and there in the future, so in my own projects I put a great deal of thought into keeping minspecs as low as possible, portability, and avoiding dependence on bleeding edge hardware features @raphael That's a good way to frame the question. "Low-level" is relative of course but I think you can easily do stuff using higher level abstractions - using languages like LISP, BASIC, C, C++ or Lua, etc. You can also do stuff with simpler CLI or GUI tools. I think where things become less "perma" is when the stack underneath the abstractions starts to look hyper-complex and dependent on specific high-end configurations. @raphael yeah, the technical permacomputing work has less to do with writing software, and more to do with finding ways to do without. :permacomputing: |
@raphael .. it's a matter of aesthetic!