matias stanghelini

[matias stanghelini @M_Stanghelini]

@mariagorskikh Hi, I've been following your work—it's fantastic. Have you tried using Treg? Maybe it'll help you reduce the number of tokens. https://t.co/M6mKcGnyQb

[matias stanghelini @M_Stanghelini]

@santtiagom_ El reverse proxy debería ser el único punto de entrada público (80/443). El backend (3000), DB y Redis deben quedar en una red privada, sin exponer sus puertos a Internet. Menor superficie de ataque y servicios aislados.

[matias stanghelini @M_Stanghelini]

@briannvalente @lautidev_ Coincido, en Oracle tenes un free tier muy generoso, en caso de incurrir en costos Los shapes de oracle usan shields enterprise qué te protegen a bajo nivel https://t.co/nojHBSjXbK

[matias stanghelini @M_Stanghelini]

@fedesturze Hola Fede, te comparto un proyecto que estoy trabajando, son aún algunos prototipos pero sería grandíoso diseñarlo en conjunto con el gobierno y entidades privadas, saludos.

https://t.co/C3BIzZgiq2

[matias stanghelini @M_Stanghelini]

@canal26noticias La vieja está tan dura que parece hecho con ai

[matias stanghelini @M_Stanghelini]

@tebayoso Que consejo de mierda, la gente tiene side projects mas que nunca.

[Miguel Ángel Durán @midudev]

¡He creado una biblioteca para usar IA en tu navegador!
Modelos de pesos abiertos y especializados.

✓ Gratis y Open Source
✓ Sin APIs ni servidores ni pago por tokens
✓ Tus datos nunca salen de tu dispositivo

Se llama runonweb:
→ https://t.co/ra79gy7TUS

[matias stanghelini @M_Stanghelini]

@Siumauricio @martincoll_dev La versión actual de dokploy se ve y se siente mucho más fluida y comprensible

[matias stanghelini @M_Stanghelini]

@https_memi Decile que se ponga un parripollo es la mejor inversión

[matias stanghelini @M_Stanghelini]

@payloadcms Does it make any sense to maintain a CMS in an era when agents write code on their own?

[matias stanghelini @M_Stanghelini]

@5eniorDeveloper @santtiagom_ Esto es meter miedo, si alguien comenta esto es porque no mira su propio código, el código es una responsabilidad por lo tanto el producto que creas te vuelve tanto o más responsable, entonces pienso los productos de level son una mierda?

[matias stanghelini @M_Stanghelini]

@ProfAviLoeb Hola Profesor, admiro su brillante trabajo, no sé rinda, potencialmente puede suceder que un medio de comunicación tenga información fresca o es una jugada de marketing o es una mentira extremadamente grande.

[matias stanghelini @M_Stanghelini]

@tebayoso Tremendo proyecto, te puedo armar telemetría dé paquetería adaptada al tipo de producto que se comercializa para ver por dónde va cualquier producto, te pongo a disposición mi empresa https://t.co/HUiG316Slu

[matias stanghelini @M_Stanghelini]

@MathiasChu Hola podrías probar usando wallsync @wallsyncfinance

[matias stanghelini @M_Stanghelini]

@rauchg The Dark Side of Vercel

[matias stanghelini @M_Stanghelini]

@nayibbukele ¡Gran iniciativa! Si necesitan apoyo para desarrollar aplicaciones potenciadas por IA para el sector educativo, cuenten con mi ayuda ad honorem. Estoy convencido de que nos espera un futuro brillante.

[Miguel Ángel Durán @midudev]

¡El compilador de React en Rust ya se puede usar fácilmente en Vite!

Con: react({ compiler: true })

✓ 10-17× más rápido que el de Babel
✓ En un repo de +1000 archivos: 14,3s → 0,81s

Olvídate de useMemo y useCallback:
https://t.co/Uas7in6qEB

[Justin Schroeder @jpschroeder]

All code should be rewritten in Rust.

Rust was such a horrible language for humans to write, and that's precisely what makes it incredible for agents. If you're not steeped in languages like I am (was), here's why this matters...

All languages fall into one of two camps: dynamic memory allocation and manual memory allocation. Sometimes languages allow for both, but programmers either needed to manage carving out chunks of memory for their program themselves or to delegate that responsibility to the machine.

The tradeoff between the two is roughly performance vs. pain and safety. Manual allocation is generally faster, but sucks to program and, if not done carefully, can leave security vulnerabilities (C, C++, Zig…). Languages that manage your memory are, generally, much more delightful to write but a bit slower (JavaScript, Python, Ruby, OCaml).

Rust tried to solve the security concerns through, essentially, the most complex language constructs known to man. It was fast. It was safe, and broadly it was the wrong decision for most projects because it was too hard to learn, too hard to change, and hard to hire for.

Not anymore. Programmers no longer program. They don't write syntax, they don't read code, and frankly most don't know a thing about security. Vibe-coded projects written in Rust are faster, safer, and more likely to work the first time (due to an insanely complex compiler).

It's the perfect tool for the moment. Only the Rust Foundation could miss this layup.

**I will leave one small caveat here: TypeScript is the inevitable language for agent development, deployment, and distribution, but thats deserves a separate post.

[matias stanghelini @M_Stanghelini]

@martin_tito_99 @FacundoMarino1 @julianpineiro bot spoiler

[Guillermo Rauch @rauchg]

If you’re not reading the code, whether explicitly or through agentic inquiry, one or more of these is true:

○ You’re a beginner
○ Software is throwaway
○ You’re prototyping
○ You have no users / revenue
○ You’re taking on debt & risk
○ Your problems are basic

And btw. All of this is fine. But the reality is that models are still not at the “full autonomy” stage yet.

They make rookie mistakes, they go down bad architectural paths. I just had the best model in the world add a nonsensical 700ms delay to “settle” something and it told me “you’re right, I was cargo-culting” 🤨

I am on the camp that this need will diminish more and more. Most code is indeed going to be assembly-like. But we also have the global internet and software infrastructure riding on these models and narrative, and we have to respect that.