Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mamcx
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
mamcx
15d ago
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 · tran
2.
▲
by
mamcx
18d ago
I also work on this area ( https://tablam.org ) and have used languages where this weird, poorly developed language SQL was not the main interface (FoxPro). Think on this: You imagine yourself writing a regular website with ONLy s
3.
▲
by
mamcx
29d ago
This make too much sense! In special when testing against a DB.
4.
▲
by
mamcx
1mo ago
There is not much material I can find out, maybe only https://elixir-lang.org/blog/2023/09/20/strong-arrows-gradua... that is kind of practical?
5.
▲
by
mamcx
1mo ago
P.D: By causality we have worked together? You can reach me at https://www.elmalabarista.com
6.
▲
by
mamcx
1mo ago
> btrees do not imply bags. Correct. > you insist that your data demands bags. No, I insist that real data needs both. You can bias the language/engine in one way or other. The underlying problem is that once you say: > if
7.
▲
by
mamcx
1mo ago
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 ag
8.
▲
by
mamcx
1mo ago
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
9.
▲
by
mamcx
1mo ago
As seen in Dr. Stone!
10.
▲
by
mamcx
1mo ago
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 st
11.
▲
by
mamcx
1mo ago
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 · transa
12.
▲
by
mamcx
1mo ago
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 th
13.
▲
by
mamcx
2mo ago
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
14.
▲
by
mamcx
2mo ago
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 practic
15.
▲
by
mamcx
2mo ago
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
16.
▲
by
mamcx
2mo ago
So this is not inside a trigger but on the app connected to pg?
17.
▲
by
mamcx
2mo ago
Is the optimization only possible using dbos? is not clear to me if this mean a way to tune normal PG
18.
▲
by
mamcx
2mo ago
Is interesting that this is how array langs work. I bet will be easy to turn into a lib.
19.
▲
by
mamcx
2mo ago
AND shipping.
20.
▲
by
mamcx
2mo ago
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 aut
21.
▲
by
mamcx
2mo ago
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
22.
▲
by
mamcx
2mo ago
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
23.
▲
by
mamcx
2mo ago
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 relativ
24.
▲
by
mamcx
2mo ago
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 o
25.
▲
by
mamcx
2mo ago
> 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 exp
26.
▲
by
mamcx
2mo ago
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
27.
▲
by
mamcx
2mo ago
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 expo
28.
▲
by
mamcx
2mo ago
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)
29.
▲
by
mamcx
2mo ago
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
30.
▲
by
mamcx
2mo ago
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 w
More ›