manudaro

10 ms·

1.
by manudaro 6mo ago
You're right, PHP is SSR by nature. What I meant is that Next.js gives us SSR plus built-in routing for 4 languages, ISR for cache invalidation on ~900K pages, and a React frontend — all in one framework. With PHP we'd need to wir
2.
by manudaro 6mo ago
Of course, go ahead! Would love to read it when it's published, feel free to share the link here or drop me an email (manuel.longo@bamwor.com) And hey, in my experience the best blogs I've ever read were the "ugly" ones,
3.
by manudaro 6mo ago
The screenshots are from 2011 and the redesign took months of engineering, PostgreSQL + PostGIS with 13M features, Redis caching, MCP Server for AI agents. Happy to discuss technical details.
4.
by manudaro 6mo ago
You're right, I do use AI to help with the writing. English isn't my first language (I'm native Spanish speaker) and I use it to translate and polish my text. I wouldn't be able to participate here otherwise. The site ru
5.
by manudaro 6mo ago
Thank you. Te 2011 version wasgenuinely fun to build. Chat by city, airport databases, a people search engine, things that made no business sense but felt right. We're trying to keep some of that. You can browse countries, compare them
6.
by manudaro 6mo ago
You're not wrong. The 2011 version had character. Google+ icons, chat per city, a people search engine. It felt like a place, not a tool. The tradeoff was deliberate though. Serving 261 countries in 4 languages with an API and MCP Serv
7.
by manudaro 6mo ago
Totally fair points. Back in 2011 everything was built in plain PHP, and honestly, it worked perfectly for years. The shift to Next.js came much later, mainly because we needed proper SSR to handle SEO at slace. We're talking about 4 l
8.
by manudaro 6mo ago
Thank you!
9.
I rebuilt the same project after 15 years: What changed in web development(bamwor.com)
16 points by manudaro 6mo ago|16 comments
10.
Show HN: Bamwor – Country data API and MCP server after CIA Factbook shutdown(bamwor.com)
4 points by manudaro 6mo ago|2 comments
11.
by manudaro 6mo ago
Ha yeah that makes sense. Having the AI read its own conversation history in a format it already understands is a nice side effect of keeping it in plain Json.
12.
by manudaro 6mo ago
This is great, thanks for digging these up. The workflow doc on Github is exactly what I wat looking for - didn't realize they had that level of documentation publicly available.
13.
by manudaro 6mo ago
I've been loking into how 3B1B builds their rendering pipeline, and it's honestly mind blowing. They use Python along with custom OpenGl shaders to handle most of geometric transformations, shich seems to be what creates those &qu
14.
by manudaro 6mo ago
The .claude folder structure reminds me of how Terraform organizes state files. Smart move putting conversation history in Json rether than some propiertary format, makes it trivial to grep through old conversations or build custom analysis
15.
by manudaro 6mo ago
Sub 250ms for cold queries from S3 is impressive, but curious about the consistency of those numbers. Are you doing any prefetching of table schemas or statistics? With geographic datasets we often see huge variance in S3 latency depending
16.
by manudaro 6mo ago
The Clojure tablecloth performance numbers here are pretty surprising, usually see Python/polars dominating these benchmarks. Been running similar transformations on transit data feeds and polars consistently outperforms pandas by 3x-5