Skip to content

Latest commit

 

History

History
79 lines (56 loc) · 2.97 KB

README.md

File metadata and controls

79 lines (56 loc) · 2.97 KB

fullstack apps @ NIRV

  • standard application development @ nirv.ai
  • wouldnt trust anything in this repo while this line exists

update Q4 2023

  • dunno where i'm at with this, wouldnt trust anything except apps/hono

TLDR

  • HARD ADs: NIRV uses nimlang and Bun... for all application development
  • SOFT ADs:
    • preference for react and related ecosystem, but one-offs for things like svelte are accepted

why nim and bun

Any fool can write code that a computer can understand. Good programmers write code that humans can understand. Martin

  • nimlang and Bun (typescript) are the most usable and flexible languages on the planet
  • anything you can build, can be built and maintained competitively and economically
  • if you are:
    • searching for ultimate performance: start here
    • reasonable person building profitable and competitive applications: continue reading

When opinions clash

the hardest part in making a choice, is figuring out who to blame when things go wrong. Master Yuan-Ma, The Book of Programming

  • NIRV prefers openminded frameworks and libraries vs the opinionated toolset or kitchen sink
  • adhering to the unix philisophy
    • Make it easy to write, test, and run programs.
    • Write programs that do one thing and do it well.
    • Write programs to work together.
    • Self-supporting system: all software is built with nimlang and js

apis / backend apps

  • first choice should be nim
  • for non nim devs
    • edge compute: hono
    • everything else: elysia

bff: backends for frontends

  • any service/application specifically supporting an FE app should be in JS for interoperability (from a developer perspective)
  • same AD: hono for edge, elysia for heavy lifting

fe: frontends

  • react is still king. we took an initial look at svelte and it was deemed a lateral move vs a significant jump in performance or dev experience

MVAs

  • synchronizing the minimal viable architecture across services
BUN
NIM
  • dunno