Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
emmanueloga_
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
emmanueloga_
1y ago
That sounds great!
32.
▲
by
emmanueloga_
1y ago
The article suggests running Kuzu in a FastAPI frontend for network access. A caveat: production Python servers like Uvicorn [1] typically spawn multiple worker processes. A simple workaround is serving HTTP through a single process languag
33.
▲
by
emmanueloga_
1y ago
From my perspective, the article seems primarily focused on promoting React Server Components, so you could mention that at the very top. If that’s not the case, then a clearer outline of the article’s objectives would help. In technical wr
34.
▲
by
emmanueloga_
1y ago
Hey, thanks for sharing your thoughts! I appreciate you putting this out there. One bit of hopefully constructive feedback: your previous post ran about 60 printed pages, this one's closer to 40 (just using that as a rough proxy for ti
35.
▲
by
emmanueloga_
2y ago
I looked into eBPF-based observability tools for k8s some time ago and found at least four tools that look incredibly similar: Pixie, Parca, Coroot, and Odigos. There are probably others I missed too. Do you have any thoughts about this? Fr
36.
▲
by
emmanueloga_
2y ago
For those that have not implemented toposort or don't remember it: 1) only directed graphs without cycles can be topologically sorted (DAGs) 2) there can be more than one topological order and 2) reverse post order of depth first trave
37.
▲
by
emmanueloga_
2y ago
I'm surprised this was announced in a random tweet instead of a blog post with a release roadmap or something like that.
38.
▲
by
emmanueloga_
2y ago
Awesome thank you for the clarification!
39.
▲
by
emmanueloga_
2y ago
I spent way too long figuring this one out, so this is what I got: An improvement on [1], which I vaguely remember using with pen and paper to find minimums of differentiable functions. The original algorithm runs "on a loop" (ite
40.
▲
by
emmanueloga_
2y ago
...and it's a hunk of steel that must weigh a few tons and is built to withstand an extinction-level disaster. I mean, even for the '30s, it seemed a little bit excessive. I understand it had to be somewhat heavy for stability and
41.
▲
by
emmanueloga_
2y ago
I wonder about the angle of the article, starting with "B-Trees stand the test of time" ending with "everything else has seriously diminishing returns". I never ask myself why we still use hashmaps or heaps or whatnot, s
42.
▲
by
emmanueloga_
2y ago
That's cool, I don't know how popular canvas heavy apps are these days, what kind of apps are you working with? I used to work on a set top box app, and for some of the features, replacing the whole page with a single canvas was t
43.
▲
by
emmanueloga_
2y ago
This is why it pays out to turn on "Paint Flashing" [1] in the web console, even if just from time to time. -- 1: https://web.dev/articles/simplify-paint-complexity-and-reduc...
44.
▲
by
emmanueloga_
2y ago
Nice game! I found myself putting my finger directly into the paddle many times. Instead of the message "Push here to play" you could create a more obvious UI element where one should press (something like the grip part of a slide
45.
▲
by
emmanueloga_
2y ago
I think brew's author point holds even if you replace "invert binary tree" with any other LC problem. In terms of the problem itself, a binary tree can be expressed something like: type Node<T> = { value: T, left?
46.
▲
by
emmanueloga_
2y ago
Lecun's thesis: "if we generate outputs that are too long, the per-token error will compound to inevitable failure". > The finding that language models can get better by generating longer outputs directly contradicts Yann’
47.
▲
by
emmanueloga_
2y ago
I feel like people are being overly critical of this work. When used sparingly, scrolling effects can add charm to marketing pages and portfolios, and I've seen some great uses on so called "explorable explanations" and other
48.
▲
by
emmanueloga_
2y ago
I understand this position very well! Sometimes there’s room for trade offs, you lose some flexibility but gain something in return. Also replacing some of CF primitives with something else later can be viable, specially if you plan for it.
49.
▲
by
emmanueloga_
2y ago
Cloudflare is a nice option if you can adapt your system to run there [1]. You could also run just the frontend on CF and host any APIs elsewhere. Or check these sites [2] [3] with some good reviews and comparisons of hosting providers. Reg
50.
▲
by
emmanueloga_
2y ago
At some frequencies sounds like a more (or less) chip-crushed church organ.
51.
▲
by
emmanueloga_
2y ago
My attempt at nice looking TS version: function sum(f: (x: number) => number, upper = 500) { let sum = 0; for (let n = 0; n < upper; n++) sum += f(n); return sum; } const weierstrass = (x: number, a =
52.
▲
by
emmanueloga_
2y ago
+1, it the obvious thing missing in the article!
53.
▲
by
emmanueloga_
2y ago
> There were missteps along the way. A big example was the TV software that was originally an acquisition, SageTV [2]. Somebody decided it would be a good idea to completely rewrite this Java app into Web technologies on an embedded Chro
54.
▲
by
emmanueloga_
2y ago
Quick summary: ClojureScript + Babylon.JS on the frontend and Clojure for the backend, coordination via Websockets. The point about lack of tooling for Babylon.JS is interesting: a lot of times I see people wanting to release games but spen
55.
▲
by
emmanueloga_
2y ago
I feel like we are, overall, in agreement, although this may be a case of [1] :-). -- 1: https://youtu.be/XHO4Aby6fT8?t=11
56.
▲
by
emmanueloga_
2y ago
For this particular example, I feel like a combination of both human input + algo could work. Something like: * Have graphviz or some other solver output the [x;y] pairs for each vertex. * Use the initial positions to create, with a physic
57.
▲
by
emmanueloga_
2y ago
Kind of, with caveats. For one "extensions can interfere with each other and cause incorrect behavior" [1], and the practicallity of implementations varies. Say, Cypher queries using AGE can be order of magnitude slower than using
58.
▲
by
emmanueloga_
2y ago
I think it is a problem of incentives: programming languages with small, elegant specs are often created by academics, and academia and the software industry have fundamentally incompatible incentives.
59.
▲
by
emmanueloga_
2y ago
The whole incident report is interesting, but I feel like the most important part of the solution is buried here [0]: * "We're adding timeouts to prevent user requests from waiting excessively long to retrieve assets." When y
60.
▲
by
emmanueloga_
2y ago
Fun fact: pixi uses uv as a library to install pypi packages!
More ›