Hacker Newsnew | past | comments | ask | show | jobs | submit | mamcx's commentslogin

Yeah, this is how we survive.

I even dream of build tools for business to make apps (like Air table, but better) and even if you can do anything that do, perfectly, the software they need not means they want to babysit it all the time.

Is like the person that knows how cook, amazingly, yet hire a chef for take care of it most days.


Yeah, this is a hard problem, in special because Standard SQL databases only partially implement the relational model, have not good recurse for deal with relations-in-relations and lack of ways to (in user space) build your own storage (all stuff that I dream to tackle).

I think the possible answer is to try to "compress" columns with custom datatypes, it could require to touch part of the innards of sql (like in postgreSQL you need to solve it with c) but is a viable option in many cases where you noted that what you could express in json, for example, is in fact a custom type that could be stored efficiently if there is a way to translate it to more primitive types, then solved that the indexes will work.

The second option is to hide part of the join complexity with views.


I only need 1 million. 10 as much!


I work independently as consultor/solo dev (https://www.elmalabarista.com) for years now, so with that much money (even 1 million) I just be set for life!.

But I actually love my job (programming) and do it in my spare time (after program for work!) and like to join others to learn (as I have done for https://spacetimedb.com/).

Will probably dedicate the time for my dream of build a FoxPro-alternative, and pretty certain will love it for more than a decade, so if anyone wanna help get funds I all hears!


+1

`jj` is the only tool that make me use `rebase` personally. Before, I see as the punishment given by my team wishes :)


And if a major problem, `jj op log` + `jj op log restore` fix it. This is the major super power of jj: Before I need to nuke the git repo on bad rebases (not chance in hell I can find how undo the massive 20+ steps bad rebase)

I mean `git reflog` is right there! But jj is awesome, agreed

Poor.

My dream is to build such tool, I slowly doing in the side (https://tablam.org). Probably need to ask for funding too.

In concrete, what I want is a real alternative to Fox/Access that work, unrestricted, locally (including inside a phone/iPad). I don't mind have support for cloud stuff (that is what pay the bills mostly) but that is secondary IMHO.

Current computers, even mobile, have far much power than most need, and is a shame not much tools actually exploit it.


Super interesting, I hope I can dig into this at some point!

Senior Rust · Databases · compilers · business applications engineer

  Location: Medellín, Colombia
  Remote: Yes
  Willing to relocate: No
  Technologies: Rust, RDBMs (PostgreSQL · SQL Server · SQLite), Swift, Python
  Résumé/CV: https://github.com/mamcx
  Email: mamcx@elmalabarista.com
Senior software engineer with 30+ years building production systems and 3+ years working as core developer on database internals and high-performance RDBMs. Recent work includes building the internals of a production-ready real-time database used in a large multiplayer game.

Founder and principal engineer with end-to-end ownership from architecture to production.

Looking for senior / staff / principal roles in Rust, databases, or backend systems.


> I wonder, at which point it is worth it to make a language?

AT ANY POINT.

No exist, nothing, that could yield more improvements that a new language. Is the ONLY way to make a paradigm(shift) stick. Is the ONLY way to turn "discipline" into "normal work".

Example:

"Everyone knows that is hard to mutate things":

* Option 1: DISCIPLINE

* Option 2: you have "let" and you have "var" (or equivalent) and remove MILLIONS of times where somebody somewhere must think "this var mutates or not?".

"Manually manage memory is hard"

* Option 1: DISCIPLINE

* Option 2: Not need, for TRILLONS of objects across ALL the codebases with any form of automatic memory management, across ALL the developers and ALL their apps to very close to 100% to never worry about it

* Option 3: And now I can be sure about do this with more safety and across threads and such

---

Make actual progress with a language is hard, because there is a fractal of competing things that in sore need of improvement, and a big subset of users are anti-progress and prefer to suffer decades of C (example) than some gradual progress with something like pascal (where a "string" exist).

Plus, a language need to coordinate syntax (important) with std library (important) with how frameworks will end (important) with compile-time AND runtime outcomes (important) with tooling (important).

And miss dearly any of this and you blew it.

But, there is not other kind of project (apart from a OS, FileSystem, DBs) where the potential positive impact will extend to the future as much.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: