HNHacker News
TopNewBestAskShowJobs

mamcx

3,329 karma · joined June 18, 2012

http://www.elmalabarista.com.

Rust, F#, Swift, Python.

Experience building database engines and ERP software.

Open for work and custom development!

submissionscomments
mamcx··on Time to Move On: Querying Without Nulls and Bags
It has good points, but has 2 major problems, IMHO, that we observed when I was part of a team building a RDBMS:

* It again ignore the best solution for nulls: Algebraic types. Once you have this much get solved for free

* The argument against bags:

The best idea of the paper is that a RDBMS in fact internally do different data structure and temporal representations that are not of concern to the user. Correct.

THEN it jumps to the conclusion that bags should not be presented to the user, despite the fact acknowledge it need to display them.

This is wrong, and the major reason that is always overlooked is that assume that 2 identical values are wrong to exist.

I can have "Jhon, Jhon", be 2 separate persons, not know at this time more to disambiguating, adding a Id do nothing to help me, and yet, this data is correct as is.

The language MUST allow me to deal with this. It will absurd to claim an array language, procedural, functional, imperative, declarative, etc can and a relational can't.

It say the lang is intentionally limited for purity, that true, is ideal in some cases, but that purity is what the engine/compiler should track, but not distort MY DATA for this.

And the part where the perf of having bags dismissed is easy to debunk: implement a dbms and profile.

P.D: Is true that set unlocks lots of benefits, and in some cases are ideal. But very fast once you hit the real world you see that need both, similar how btrees alone is not enough, and then there is hash-based indexes and many others.

it sucks, but reality is unfriendly to pure pure languages

P.D.2: And to clear misunderstanding, I agree with the points in the same way Rust say the borrow checker is ON by default, but I argue we CANT make a strict rule, in special because data is not ideological pure

mamcx··on Time to Move On: Querying Without Nulls and Bags
The only good reason is that SQL is the only main interface for most of the main DBs.

There is NOT other *good reason*.

P.D: But, why? Well, at first SQL was truly small. Then the cost of "just adding" something look easier than redo another lang.

TODAY, SQL is insanely bad and complex.

To the point that you can, literally, learn Rust faster than SQL.

Seriously! look for example how many reserved words you need to be aware of:

https://en.wikipedia.org/wiki/List_of_SQL_reserved_words

P.D: I implement parts of the SQL support for a RDBMS. I think the teams expect >5 years to fully do it.

I bet is possible to implement Rust way faster than that (ie: I mean here for both: Parsing and correctly executing, not all optimization and other concerns)

mamcx··on Parametron: 50s Japanese computer that uses neither transistors nor vacuum tubes
As seen in Dr. Stone!
mamcx··on Parsers don't have to be complicated
And harder than that? Report the error, in a way that make some sense.

This is compounded by the fact that you need the semantics involved, the environment (ie: everything on scope), the source (that means you need to keep carrying big strings around).

And what is efficient means to be destructive, but you need instead the opposite for semantics, error messages, optimizations and the like.

mamcx··on Ask HN: Who wants to be hired? (August 2026)
Senior Rust / Database Engineer

Also open to do custom software development!

Location: Medellín, Colombia Remote: Yes! Willing to relocate: No

Technologies: * System engineer: Rust · query engines · programming languages · VMs · transactions · storage · performance optimization · data modeling · ERPs · Business Apps

* Databases: RDBMs · PostgreSQL · SQL Server · SQLite · SpacetimeDB

* Backend: Business logic · APIs creation · integration · orchestration · ETLs

* Additional: Python, F#, Swift, Web assembly, Git, Jujutsu, macOS, Linux (NixOS, Debian), Windows

* ERP/eCommerce building from scratch

Résumé/CV: https://www.linkedin.com/in/mario-alejandro-montoya-cortés-6... Email: mamcx@elmalabarista.com https://www.elmalabarista.com

Software engineer with 30+ years building production-ready business applications and 3+ years as a core database engineer building high-performance RDBMs.

Founder and principal engineer of small ISV with a long track record of owning complex systems end-to-end, from low-level design to production reliability.

Driven to learn new domains quickly and choose the simplest effective architecture, tools and paradigms for each problem.

mamcx··on Andy Pavlo joins ClickHouse to establish ClickHouse Labs
Maybe only an OS can be close to how MUCH deep you can go with a DB engine.

And I bet DB engines can go far than normal OS.

You don't know how much is still waiting for somebody to try, and how much is not applied. And how many of that DBs are not even doing, because all are constrained be being "apps" with so poor interface (sql).

Fun fact: Not exist a viable true relational DBs implemented, neither exist one with a viable programming language AND apis that is for developers.

ZERO.

mamcx··on Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
The good reason for worry about it is the same for data grid, list, scrolls and any other UI component that loads arbitrary data.

All UI, honestly, is only meaningful in what the screen size and our vision permit. END.

UNFORTUNATELY, you can't avoid that a user is writing "a___" and the source data has millions of things that start with `a` and all the others are dozens.

So, you can end with a massive influx of data, and sure the user see that big mess and wanna dial in, but in the meantime is nice if the UI not die in the process.

mamcx··on So, you want to make a game engine (2023)
Reading the article show it talk about something else that build a "game engine" from scratch, what it says instead is *build a "engine"* to make the kind of games you will do over and over" that is more practical and attainable.

From developers this is how in-house frameworks work, that are mostly reusing other frameworks and libraries and create a sort of pseudo DSL.

mamcx··on EYG: A Programming Language for Humans
The Op identify well the problem and the idea of the solution but the implementation is typically dev oriented.

A good example of the actual tool is FoxPro and similar (even better than MS Access based on the ideals of the article) and I observed being actually used by occasional "developers" that need more than Access/Vb/Excel.

I'm on the hunt for it with https://tablam.org but the main major pain point is to bring the actual UI. You can go anywhere with syntax and such, is how you connect to the rest where the magic must prove is real.

mamcx··on Postgres LISTEN/NOTIFY actually scales
So this is not inside a trigger but on the app connected to pg?
mamcx··on Postgres LISTEN/NOTIFY actually scales
Is the optimization only possible using dbos? is not clear to me if this mean a way to tune normal PG
mamcx··on Everyone should know SIMD
Is interesting that this is how array langs work.

I bet will be easy to turn into a lib.

mamcx··on What I learned selling 2,500 MIDI recorders: Hardware is not so hard
AND shipping.
mamcx··on Topcoat: The full full-stack framework for Rust
This sound fantastic and Django is the main thing I miss from python.

htmx+ tailwindcss is the one combo that is right and I use it so seeing is the direction give me hope.

Some notes, I hope can be considered!:

- The main thing is the auto admin, then `auth`, is great that the `auth` is mean to have a one-to-one connection for your own extensions

- The main pain is that everything is tangled to the ORM and the auto-admin

What I have done informally is that with traits I have something like `ListQuery` and compose `Paginate(ListQuery)`.

Then pure descriptors of what the ui DO, but not what it looks like and not even html at all.

THEN, I inject the stucts/enums (all Ui is things like `Label{...}` with not logic at all in templating, all the server side is in charge of pre-render) into some templating and there is where the ui is alive, but replacing is 100% doable and expected.

What I miss is a way to introspect to auto-generate things more auto.

mamcx··on SQLite should have (Rust-style) editions
After read, it hit me that because sqlite is a DB, "editions" as-is not work.

Because it not tied to the data but to the code.

Instead, what I think should be is that the PRAGMAs become "data" that is always checked in full with "if manually set" and then on next "open" THEY GET APPLIED.

That is.

(and in the command line when open interactively they show up).

mamcx··on Tensor Is the Might
I read it as "tensors in programming*.

This also happens to "numbers", "integers" and such, because in the computer universe don't exist out math, only a subset(?) variation(?) of it

mamcx··on Distributed system is slower than a laptop
Well if the company have somebody like you it helps tons!

In the flip side:

> the problem with a single system is that mundane things cause unavailability

Is multiplied by each "system" you add. The basic failures are relative easy to deal and understand, the ones introduced by more complex system who knows?

Probably the most important step that I miss:

> How long would it take to procure a new server and restore from backup?

.. and applied to any complex extra you have.

For single system is viable (with something like nix) to go off for maybe half hour for what I see around, most of the time in procuring another machine (that what people do is to Bring any other machine it can not go to amazon and buy!) and restoring the backup.

Of course, I factoring that downtime is not "seconds or minutes" here, but neither I think many can do like that

P.D: all

mamcx··on Ask HN: What Are You Working On? (July 2026)
Rebuilding my long ERP-like project to become more like a "business engine" to become a proper ERP backend (so it can cover most business scenarios and is multi-company, branch, currency, etc).

Have now the core done and working on a MVP UI to validate it.

One of the things I always wish to do properly was to model currency and unit of measure in full as core types, plus truly trace everything related to the business transaction from production to beyond the sale.

Looking into a persistent workflow engine like `temporal` now...

P.D: I'm debating if open source or not, in light of the AI-pocalypse...

mamcx··on Why We Don't Trust the Database with Authentication
> When writing an API, it’s easy to unknowingly introduce a dangerous, implicit assumption: that the database is the ultimate source of truth. If a record is in the database, an application often treats it as authoritative. I want to explain in this post why that might be a very bad idea.

This premise is weird at best.

"the database is the ultimate source of truth" is not a "dangerous, implicit assumption", is the best rule you can get (and the rest of the post say so: all useful data comes from it!)

Instead the rest of the article is interesting on how to choose what to use for the hash, but not follow with this first paragraph :shrug:

mamcx··on Distributed system is slower than a laptop
I live in the ERP-adjacent world, and the vast majority don't have any of that, never have, and I pray most don't.

P.D: the business world is the one that needs AND tries everything, and most attempt to implement something is much worse than the simpler previous thing.

For most that I know and most I bet (even without knowing) add "high availability" or "warm standby" WILL CERTAINLY lead to worse availability.

In fact, the best setup for most people, and consider things from today (that you will see, not that different from mainframe days!):

- Single server on a *nix LTS/immutable distro with just the RDBMS + App backend, on decent hardware. Fast, lots of ram or whatever optional

- A true reliable backup system

- A decent network setup, ideally a VPN one for connect everybody, with good firewall, SSL and that is

More complex than this and is 90% certain is much worse, other 8% until the dude that do it and care leaves.

mamcx··on TypeScript 7
Yeah, I think was algebraic + pattern matching that break the ghetto. Suddenly types were far more useful without going crazy like Haskell!

P.D: Before, the exposure of types was from C++/Java, and special C++ is always a horrible exponent of anything except how make a overly complex language.

Once you see what good application of types look like, is far better sell!

mamcx··on Designing DB partitions you don't have to babysit
Sure, the point I try to make is that if you add things useful for OLAP to a OLTP system you could pessimist the OLTP system (that most often is the source of truth)
mamcx··on Do you need separate systems when you already have Postgres?
YES!

The problem of all the datastores is that are applications (like Wordpress) so you are too late to fix anything deep.

We need "frameworks" (so each sub-component can be used as-is or even swapped) and even wondering what a "system level" data engine could be.

mamcx··on Designing DB partitions you don't have to babysit
With the other comment about kdb+ and this show a misread of the article: The article AND ANY use of a columnar DB show the same issue: Point lookups are badly pessimized with both partitions on other columns and/or columnar.

That is why columnar DBs, not matter how impressive, are not used by OLTP workloads (and here this article point you can undo the advantages without pay attention at the consequences of partitions).

mamcx··on How working with a blind client revealed invisible accessibility gaps
In general you WANNA see any people using your app.

Read an "accessibility" spec or a requirement or a UX "good practice" is not a substitute for see how people use it!

One of my anecdotes from back in the day: The secretary of a school that use the app I help develop call about problems reading data, that comes in CD. We can't do much by phone so I travel to the town to try to debug on site (bring dev tools in the day where that means diskettes and cds, we were transitioning from FoxPro 2.6 DOS to Visual Fox Windows 95).

Eventually after some time the secretary put the coffee cup in the CD tray.

Go figure!

mamcx··on I don't maintain my homelab, it maintains itself
The same with NixOS and in production. Even less than 15 minutes month.
mamcx··on Show HN: WebBase-III – dBASE III rebuilt in the browser with its own interpreter
LOL!

Something I learn doing this stuff +25 years is that support and custom development eat you alive, and is not profitable for small ISV like mine.

Sadly, I can't use Fox now so I more constrained and unable to give the same. That is why I rebuilding the erp as an engine (fancy name: "headless erp") and working in make a lang and maybe a custom RDBMS. But then I need a GUI builder to get the same idea!

Just a minor inconvenience!

mamcx··on Show HN: WebBase-III – dBASE III rebuilt in the browser with its own interpreter
Cool!

I have this dream of revive this kind of spirit (https://tablam.org).

I started with Foxpro 2.6 and it was a blast.

One of the very cool things Fox allow us was to ship their ability to `CREATE FORM, CREATE REPORT, BROWSE, etc` so the users can customize the app with the same power as us. This is one of the most important advantages of ERPs and such made with Fox and is still unmatched.

mamcx··on Unlimited OCR: One-Shot Long-Horizon Parsing
Aside: what is the best to read receipts/bank statements/invoices?
mamcx··on Git is forever. I'm building Oak anyways
The other way is to make the tool UX do the semantic, ie:

`git split`

Something that I enjoy with jujutsu is that the semantics is the tool itself. ONCE you do that, the rest become easier!

← PreviousPage 2 of 34Next →