Developers spend most of their time figuring the system out

• enso

  83 7,286 9.9 Scala

  Hybrid visual and textual functional programming.

  

I’ve always been fascinated by the glamorous toolkit project. Their ambitions are fascinating and align closely with software I’ve daydreamed about on more than one occasion. I wish I was more comfortable with lisp, or that it was compatible with Svelte/Typescript/Deno/Tauri which account for 90% of the projects I work on. I hope projects like this and Enso[0] are early iterations of what IDEs will look like in the future. There is so much room for innovation regarding ways to extend and augment the text formats used to author and represent software systems.

[0]https://github.com/enso-org/enso

• forth

  3 89 0.0 Assembly

  Porting Richard Jones' FORTH to ARM

>You don't write README.md, ARCHITECTURE.md, JavaDocs, etc, at all?

Maybe? Not sure - haven't worked on enough big projects to declare answer

>A new developer is supposed to go through all the codebases and figure out for himself?

Yes to this bit - code should have very clear structure to it with appropriate comments attached, whether that's literate style as JonesForth<https://github.com/phf/forth/blob/master/x86/jonesforth.S> shows, small section header comment or whatever.

It should be very clear what section exploring does - tiny example but cat <http://9p.io/sources/plan9/sys/src/cmd/cat.c> from plan 9 very simple segmented code - deals with file opening in main loop and cat function just reads and prints text

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project