Créer un compteSe connecter

Recherches récentes

Aucune recherche récente

Options de recherche

Disponible uniquement lorsque vous êtes connecté.
mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

639
comptes actifs

mastouille.fr: À proposAnnuaire des profilsPolitique de confidentialité

Mastodon: À proposTélécharger l’applicationRaccourcis clavierVoir le code sourcev4.3.4

#softwarearchitecture

2 messages2 participants1 message aujourd’hui
Suite du fil
Public
screwlisp

Looks like I dodged a bullet when I decided /not/ to randomly add a class slot to one of the main metaclasses. In chapter 2:
"
Don't be fooled by this: metaobject protocols are not designed or implemented by arbitrarily exporting the internal structure of existing implementations. As we go along, we will give explicit attention to the design principles underlying our evolving metaobject protocol.
"
#softwareEngineering #AMOP #lisp #softwareArchitecture
@simoninireland

Public
Yuna

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

Compiled Languages vs NodeJs picture
#NodeJS#BackendSecurity#SecureCoding
Suite du fil
Public
screwlisp

I'm only going to very lightly touch the general theme of #BDI agent #softwareArchitecture. I will argue that Sandewall's #CAISOR paradigm is a slight generalization Sacha's style of life-long emacs useage to create #AI .

Today basic interactive creation and expantion of new knowledgebases including expected-to-be-complex new types and adding lisp / CEL-logic as regular entities.

telnet lambda.moo.mud.org 8888
co guest

@kentpitman @prahou @pesco @dougmerritt @mdhughes @nosrednayduj @sacha

ExplorerFlux en direct
À propos