Discussion
Loading...

Post

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
d@nny disc@ mc²
d@nny disc@ mc²
@hipsterelectron@circumstances.run  ·  activity timestamp 3 weeks ago

this makes arguments on both sides of mine https://kyo.iroiro.party/en/posts/100-percent-lisp/ the reason i think an explicitly multi-layered abstraction like C->lisp works is because it can be used to set strict bootstrapping requirements. you can do bootstrapping very well without it (see gcc) but whereas C is often derided as an unsafe base layer, it also happens to be the most portable one—and this tends to remain the case when using modern C with #embed and _Generic and defer

  • Copy link
  • Flag this post
  • Block
d@nny disc@ mc²
d@nny disc@ mc²
@hipsterelectron@circumstances.run replied  ·  activity timestamp 3 weeks ago

portability has some implications for safety—if you need to implement support for a platform by hand, you necessarily can't rely upon a well-tested impl (which is half the reason rust can claim memory safety), and often you can't rely upon the safety guarantees of e.g. rust (if you have to generate your own assembly)

  • Copy link
  • Flag this comment
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.1 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct