There is a tons of "modernized" TUI since Rust/Go, and even better terminal and shells.

Because is a kind of filesystem.

How a TEAM operate IS NOT.

And that is the point of Github.

There is no escape to the coordination problem!

(And if you say mails, patches, and other asynchronous ways: same thing, more complex)

The idea is to make things "relational" (with improvements) instead of fully "physical database tables" that is what tied you into a binary format.

With this, this binary format stop to begin opaque, and can be even be represented (tables and such) textually or by "standard" outputs like Msgpack.

So think that `data Customer` has decoupled the idioms, programatic interface to their specific storage. In rust terms, each `data` is `serde`, so you can change and move between how physically things are represented.

BTW this is how the relational idea was mean to be used.

I think the main gist: you work not as app developer but as db developer, is something that is missing in some partial attempt like access and such.

BTW: Wanna join me or help?

https://www.freepascal.org/docs-html/ref/refsu4.html

You see the same offer by the same company for months! with the same generic reject (seriously I think no even check the resume or whatever!).

Then, a lot of fake I-am-a-AI "companies and middleman and such things.

Ironically, I have been contacted more by somebody looking here in hn than in all the job boards!

*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

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.

The problem with this line of thinking is the same with "I so good as C developer, my code is so-safe!".

And we see what reality instead tell: Yes, exist people where this claims are true, not, is not even a decently sized minority.

However, I consider that there is still not a great UI for the core service, in special for a complex project.

In the other hand, I bet jujutsu has the best basic take, and is still missing a good forge.

Why I not allowed to do things directly? For the same reasons the tables are like that

One of the worst has field names like `ft_0001...N` and table names like `UNCC_00001...N`, all in `text` fields (even numbers!), zero FK, almost no indexes and what are views?

The other has this funny field that is a blob that need decoding using a specific FreePascal version. The field? Where is the price of the product.

Other has, in the same column, mix of how handling "," or "." for numbers and I need to check the digital places to deduce which.

FUN.

P.D: I normalize all this Erps into my own schema and has get praise for things like, my product table is called products.

Rust is an absolute improvement over C/C++ in major ways. Once there, for ALL THAT DECADES all the developers and all the code written will be spared the problems of "crappier languages.

In the short term there are adaptation issues? fine. But that will be erased (way faster than is possible with C) and suddenly, never again worry about things.

My dream is to build an "access + excel + Jupyter" alike combo, where you declare the full components of a RDBMS, ie: "create log, select * from index, create queue, etc".

I think what is missing is the ability to actual declare the major paradigms so is not "I create a job queue on top of a leaky table" but "I declare a job queue".

This is my idea with https://tablam.org

No, the real actual problem is with invisibility aka: the absence of readability:

In a "dynamic typing" program the interpreter knows what `a` is but YOU not.

In very strong sense. You can imagine that `a` is a `int` because, well, you write the program, right? But in fact, is only probabilistic assumption.

Some day, `a` will be a program that delete the files of your computer.

Getting free labour, lipstick of "freedom", and enable to put millions invested in what open source never can do: Scaling, infra, win big contracts, etc.

Open Source NEVER win the market game.

It only give consolation to few that can run things locally.