SaaSHub helps you find the best software and product alternatives Learn more →
TablaM Alternatives
Similar projects and alternatives to TablaM
-
-
InfluxDB
InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
-
-
Nim
Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
-
-
oils
Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!
-
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
prql
PRQL is a modern language for transforming data — a simple, powerful, pipelined SQL replacement
-
-
-
-
-
-
-
-
quickjs-emscripten
Safely execute untrusted Javascript in your Javascript, and execute synchronous code that uses async functions
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better TablaM alternative or higher similarity.
TablaM discussion
TablaM reviews and mentions
Posts with mentions or reviews of TablaM.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-03-25.
-
It's Time to Stop Building KV Databases
And what it make this even better, is that you can also write `SQL` so you can have the best of both worlds.
BTW, I think this idea can be move even further and my take is at https://tablam.org
-
Some Programming Language Ideas
I love these ideas! I've been thinking about the "fully relational" language ever since I worked with some product folks and marketers at my start up 15 years ago who "couldn't code" but were wizards at cooking up SQL queries to answer questions about what was going on with our users and product.
There was a language written in rust, Tablam[0] that I followed for a while, which seemed to espouse those ideas, but it seems like it's not being owrked on anymore.
And Jamie from Scattered Thoughts[1] has posted some interesting articles in that direction as well. He used to work on the old YC-company/product LightTable or Eve or something, which was in the same space.
I've also always thought Joe Armstrong's (RIP) thought of "why do we need modules" is really interesting, too. There's a language I've seen posted on HN here a couple times that seems to go in that approach, with functions named by their normalized hash contents, and referred to anywhere by that, but I can't seem to remember what it's called right now. Something like "Universe" I think?
[0] https://github.com/Tablam/TablaM
-
Sensible SQLite Defaults
I have some work on this idea: https://tablam.org
BTW something closer was done with FoxPro and similar languages...
-
YC's Latest Request for Startups
> Very curious if anyone knows how to pull this off.
I work in this space (small/mid-size).
The good news is that there are several "obvious" ways to pull this off because an ERP is the culmination of everything a company needs and does. So almost anything you can imagine on the software is part of it.
The bad news, and the reason everyone wants a solution, is that is truly a big space, and then you need E.V.E.R.Y.T.H.I.N.G.
---
My take is to start from the bottom, and build a much better version of Access/FoxPro (https://tablam.org).
Any medium/big ERP end being a specialized computing platform that needs:
- A programming language
- A database engine
- An orchestration engine
- ELT engine
- Auth
- UI/Report builders
And to be clear: NONE of the "programming language", "database engine", etc are a good fit today.
NONE.
This is the big thing, This is the reason (from a tech POW only) that most attempts fail.
This is the secret of why Cobol rule(d): Is all of this! but is too old! (also, this is why SQL still is best: Is almost this).
---
So, to pull this off, you need a team that knows what is "missing" from our current tools, makes a well-integrated package, and adds a "user-friendly" interface in a way that is palatable for the kind of user that uses excel (powerfully).
Is not that impossible. FoxPro was the best example of this kind of integrated solution.
P.D: This is my life's dream, to make this truth!
-
Ask HN: Looking for a project to volunteer on? (February 2024)
SEEKING VOLUNTEERS: TablaM relational language (https://tablam.org)
TablaM is an in-progress programming language to provide a more ergonomic experience for building data-oriented applications.
This means that where most languages are focused on low-level details or engineering at large, TablaM is tailored with some small & big design decisions to make it enjoyable to write applications for e-commerce, finance, ERPs, and similar.
Cool things:
- TablaM marry the array + relational models. It means we should get very little need for manual loops and all the ops are vectorized.
-
What if an SQL Statement Returned a Database?
Yeah, I worked on https://tablam.org and https://spacetimedb.com.
It becomes pretty clear that `order` is a significant property to make useful (and performant!) programs. "Duplicates" is also required to make usefull programs.
One nonobvious reason for this: You wanna report that a `customer` has a duplicated key `1`. If you CAN'T model `[(customer.id = 1), (customer.id = 1)]` then you can't report errors! And `erroneous` data is VITAL to make useful programs because then the only possibility is "perfect" data, and that is not possible!
Another reason is that we want to `count` duplicates, to see `duplicates`, and other NON-obvious at first: "What is a duplicate?". Get fun with floats, Unicode, combining case and non-case sensitive input... and is obvious that for useful programs IS REQUIRED to support bags in an extended version of the relational model.
And yet...
IS very important to remember about `set semantics` and try to adhere to it when makes sense. Your query planner will like it. You "valid" constraints like it. And `unique index` like it. And so on...
-
If you were dictator of the world what would you force programmers to write in?
Finally, for app development, I will "suggest" everyone use my lang https://tablam.org!
-
There are no strings on me
This is moe interesting than it looks, probably because the best part (IMHO) is about the type system, that is what enables the other ideas.
> In Julia, types are first-class and every value has a type
This is what I do from the start in https://tablam.org and only later found that is not common! Is so intuitive this way and simpler to check, by a lot. In fact, I waste so much time adapting type inference algorithms that are hard to translate because for some reason graphs are imposed on trees, types are second-class and live at a distance (and erased) and all is a mess this way.
The relational model already makes this so simple: `project / rename / extend` relational operators cover you.
From this other facilities become possible. Note how in `SQL` you don't have functions as first-class per se, but now try to imagine that a function is a table and suddenly, is much better!
-
Ask HN: Show me your half baked project
My relational lang (https://tablam.org) that I wish to be a Excel + Access replacement is still half-backed.
I move it slowly in my personal computer but not much in public. Maybe adding another person will help me on that!
-
Ask HN: Why did Visual Basic die?
> what is a good alternative to Access (or Fox, I add)
Nothing.
Access is(was) in fact a worse alternative to Fox:
- Much worse DB engine, and that is saying a lot (FoxPro db can and get corrupted. A typical functionality that was added to any fox codebase was a utility to fix it)
- MUCH MUCH worse programming language (VB) that is neither good as-is, much less as a data-programing language.
Fox/dbase is the only data-oriented language that was relatively popular and fit for the use-case.
This is by a mile the main point: Is a desert looking for languages that are made for business app/data oriented programing (and much harder looking for something not weird).
The main options: Fox/dBase/Informix(? not remember), kdb+, Cobol, SQL(when extended as store procedure lang with loops and that)
--
This point is big. Having a good form builder (that is already rare) is not enough to be a real contender for this space. You need a language where making queries is truly nice.
In short, you need a language that is `LINQ/Relational` as first-class end-to-end.
- If this lang needs an ORM: FAIL.
- If this lang needs to compose strings to make a query: FAIL.
- If exist "impedance mismatch" between data manipulation/queries and the rest of the lang: FAIL.
- It should also support super-advanced types like date, decimal, currency and ideally dimensional units. Ideally algebraic types as today.
- It should have a version of Rust `serve, Into/From` for easy conversion between data + formats.
- It should look "normal" like python/swift with `LINQ` queries.
This is the lang I trying to build: https://tablam.org
-
A note from our sponsor - SaaSHub
www.saashub.com | 30 Apr 2025
Stats
Basic TablaM repo stats
155
196
0.0
over 2 years ago
Tablam/TablaM is an open source project licensed under Mozilla Public License 2.0 which is an OSI approved license.
The primary programming language of TablaM is Rust.
Sponsored
InfluxDB high-performance time series database
Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
influxdata.com