gnulinux
Joined 9 years ago
Karma
6,391
Submissions
2,423
Member since
Oct 22
Recent submissions
Comment · 6 days ago
Comment · 2 months ago
"1 nine" tends to mean "90% availability" i.e. 37 days of downtime per year.
9% availability would be an uptime of ~33 days a year, I think at that point, we're pushing the semantics of "available" if the service is down the entire year except one month on average.
Comment · 3 months ago
> run on postgresql with no overhead at all
Citation needed. I love postgres as much as the next person, but it does have more overhead than Sqlite which is in an in-process db linked through compiled C code, it doesn't run as a separate server. Very significant difference that when you use Sqlite db, there is typically no db process other than your application logic, unless you implement the server yourself. If you don't want your application to have multiple processes (say, as a toy example) then it totally makes sense to prefer Sqlite just for this reason. Sqlite and postgres are different tools, they serve different purposes.
Comment · 4 months ago
My 2 cents (I hope I don't offend anyone, and of course Emacs community is amazing). I've been using Emacs full-time since ~2010 but I must admit it's been more like part-time along with VSCode since ~2024.
> This is largely a discoverability problem
In my experience it's not a discoverability problem at all. Not even a little bit. My problem with emacs batteries has always been stability between different combinations of packages. I know how to use dired, I know how to install elisp packages, I know how to write emacs lisp myself. The issue with emacs is that it's difficult to create large packages with "batteries" because any additional package added can bork some random, seemingly unrelated package. E.g. back in the day (maybe around ~2020s or a bit before?) I've been using Spacemacs without vim keybinding, and although batteries were included and I was happy, this issue I mentioned above was even bigger. Because I constantly had to deal with installing a package and discovering that it broke some unrelated LSP, programming, or autocomplete package. It gets quite a bit frustrating at some point. Since this LLM madness started, I never really installed anything LLM related to Emacs, and have been using other text editor for LLM related stuff, Emacs for everything else (especially if there is a strong Emacs package, e.g. agda2-mode is incredibly good, almost flawless!)
Again, just my humble two cents. Obvious Emacs is amazing, and in many ways it's still my go-to, I just think that the biggest issue for me has always been randomly broken packages. Maybe I'm a terrible elisp programmer, that's possible! But I've been using emacs everyday for decades, so idk...
Comment · 4 months ago
To understand what's happening here, I'd recommend you to first understand Representation theory: https://en.wikipedia.org/wiki/Representation_theory
In representation theory we reduce problems of algebra to problems of linear algebra. E.g. the standard example is to find representations of groups, this way we can represent group operations as matrix operations. We do this because (1) linear algebra is mathematically very well-understood, (2) in terms of applications, linear algebra is computationally fast, faster than implementing the group with code manually (at least, in general).
In the OP post, author reduces quiver (which is a particular kind of algebra) to linear algebra. Once this is done, the intention is to solve problems of quivers in the language of linear algebra.
Comment · 4 months ago
Quiver (a directed graph with multiple edges) is a standard mathematical term:
https://en.wikipedia.org/wiki/Quiver_(mathematics)
https://ncatlab.org/nlab/show/quiver
A quiver is simply just the data of a category, i.e. a "category" without any of the laws, namely identity and composition.
They're not isomorphic to DAGs since Quivers can have multiple edges between the same set of vertices, directed multigraphs, if you will. There is also no requirement of acyclicity (DAGs are acyclic).
For example, in the category of Sets, vertices are sets and edges are functions between sets, so between e.g. N and N there will be infinitely many edges (all functions between natural numbers) with a particular distinguished identity edge that maps f(n) = n due to category laws. So if you turn the category of Sets to a quiver, you'll have infinitely many edges N -> N and one of them will happen to be the identity function `f(n) = n` but you "forgot" its "identity" relationship/law when you reduced the category to a quiver. This is not a graph, since within your data you need to express that there are other edges between N -> N for example `f(n) = 2*n` is another edge (we can call these multigraphs).
Comment · 4 months ago
Not only that, but they said "next time better model needed" as if that was their problem and not giving an AI agent a blank check... I mean AWS account access.
Comment · 5 months ago
Will you or someone else be able to explain why not?
Comment · 5 months ago
Thank you so much for this! I've been working on exactly this problem this week (which OpenRouter providers have the highest cache rate on average) because cache cost is sometimes half your cost: I'd much rather use a provider with more input caching with a more expensive/better LLM. Your results and lists seem more comprehensive than what I've done so far. Very helpful!
> The anti-AI.
but then it's an AI-generated picture of Nietzsche [1] and AI-generated README with AI-generated code (Claude being the co-author), and when I read sample transcript e.g. in (nietzschian-debugger/tests/fixtures/sample-sessions/sample-v1.json) it's clear the app also uses LLMs to generate output...
So what do they mean by "anti-AI"?
[1]: All issues with AI-generated images aside, AI-generating a person's likeness seems like the rudest way to do this... At least use an actual photo/drawing of his...