Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
stephen
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
Static Hermes: Statically Compiled JavaScript
(twitter.com)
3 points
by
stephen
3y ago
|
0 comments
62.
▲
by
stephen
3y ago
No. :-) That was certainly the promise/hype of Rust ~2-3 years ago, that it was going to become so ergonomic that even "boring line-of-business applications" (i.e. JS backends) could be written in Rust, by everyday programmer
63.
▲
by
stephen
3y ago
> Bun’s APIs try really hard to make the obvious & default way > also the fast way. Nice! That makes a lot of sense, and look forward to trying them. Fwiw I sometimes worry about the slippery slope to infra that exists on the JS s
64.
▲
by
stephen
3y ago
Hi! I saw your PR review of a community effort to add Bun to the Techempower benchmark. You had really great, exact feedback about "unnecessary allocation here", "unnecessary allocation there". It was eye-opening, in ter
65.
▲
by
stephen
3y ago
We've solved this ("any of these N related tables needs to update the search record") but building reactivity into our backend ORM: https://joist-orm.io/docs/advanced/full-text-search Granted, curre
66.
▲
by
stephen
3y ago
My caution with recording is that I've found re-recording to get progressively hard/more brittle as time progresses, b/c the test system inevitably drifts further and further from the state it was in when the test was first r
67.
▲
by
stephen
3y ago
Great article & visualizations of how systems have gotten more complex over time. Per his suggestion of "testing against a service stub / fake server" (instead of method-level mocking), my suggestion for large internal or
68.
▲
by
stephen
3y ago
Nice! The `t<X>` makes sense; we currently guess a tag name of "FooBarZaz" --> "fbz", but allow the user to override it, so you could hand-assign "t1", "t2", etc. as you added entities to the
69.
▲
by
stephen
3y ago
Neat! Love the "type-safe" prefix; we'd called them "tagged ids" in our ORM that auto-prefixes the otherwise-ints-in-the-db with similar per-entity tags: https://joist-orm.io/docs/advanced/
70.
▲
by
stephen
3y ago
I really like their acknowledgement that they expected to be used for game/edge caching/etc, but in reality everyone is using them as a new Heroku to deploy Rails+PG crud apps. Afaiu they're asserting their next goal is to ma
71.
▲
by
stephen
3y ago
Reading the article I didn't see it, but does FB have any innovation/papers/infra around "entity A changed, so cache keys x/y/z need invalidated"? Basically similar to Noria mentioned at the beginning of t
72.
▲
by
stephen
3y ago
Love it. I'd add a 3rd reason to her list, which is not a human bias like the two, but just that high-fidelity mocks lock ideation in the hands of UX. PMs & engs typically don't have Figma editor rights (I worked with a PM who
73.
▲
by
stephen
3y ago
Wow. Could someone do this for Typescript/JavaScript? Like the language is full interop with the existing JS ecosystem, but if I opt into certain restrictions (and run on some novel runtime), I get an insta-performance boost? Personall
74.
▲
by
stephen
4y ago
+1. The JS event loop auto-monad-izing Promises into Haxl [1]-esqe trees of implicitly-batched loads has been a big win for us building on JavaScript/TypeScript. If I had to move to another language, I'd really want to find a &quo
75.
▲
by
stephen
4y ago
We only use `position: sticky` for the first row of the table, but then stack everything else in a separate div, so something like: - parent div -- 1st child div, everything that is "stickied" to the top of the screen (really a tr
76.
▲
by
stephen
4y ago
I don't suppose this (or another forthcoming CSS property) would allow multiple `position: sticky` elements to stack after each other (instead of underneath)? That is one of our biggest layout PITAs, is the slippery slope of "stic
77.
▲
by
stephen
4y ago
> Array foreign keys Yes! We very occasionally use integer[] columns with ids, but hold off on using them widely b/c of the lack of integrity constraints. It'd be awesome to use more often.
78.
▲
by
stephen
4y ago
Hi jimmy! Yep, invariably the ask always ends up to be 2-way syncing. :-/ Fwiw realistically I think these things are generally best written as custom software anyway, b/c things like identity (of entities/mapping ids correct
79.
▲
by
stephen
4y ago
Interesting! Any plans for SalesForce support? We'd love to have a way to easily sync our internal system's data in/out of SFDC. ...and a source of GraphQL? :-) One of our engineers recently suggested syncing our PG database
80.
▲
by
stephen
4y ago
Amazing. Getting just AsyncLocalStorage and the rest of async_hooks later / or not all would be great, as that's currently blocking us from bun. Really appreciate the pragmatic approach! (Instead of being dogmatic like "we ju
81.
▲
by
stephen
4y ago
Awesome! I see the PRs you've linked to; sorry, I'd misinterpreted the post as experiments/"what if" exploration and not "there are patches landing soon". That's great!
82.
▲
by
stephen
4y ago
Little disappointing that he points out/measures a huge source of slowness, but unfortunately we can't really do anything about it (for valid reasons, he points out the tool fragmentation, etc). Originally, I was hoping that "
83.
▲
by
stephen
4y ago
You're not wrong re vim. :-) Definitely use whatever you like, but just like vim bindings, which look "omg wtf" to newbies but then become "cannot live without" once you learn them, once you learn the Tachyons-style
84.
▲
by
stephen
4y ago
Fwiw to the avoid 80%-in-TW / 20%-in-SCSS-or-something-else dichotomy/complexity, we built Truss which brings TW (Tachyons) style abbreviations to the existing "something else" tool chain (Emotion in our case). So then e
85.
▲
by
stephen
4y ago
If you dislike walls of class names, you could consider using Tachyon's style abbreviations like we do in Truss: https://github.com/homebound-team/truss
86.
▲
by
stephen
4y ago
My on-the-sidelines take is: Bun seems most promising to me, because it's chasing amazing performance _and_ widespread adoption. Like Just-JS has amazing performance [1], but the author is "just" (a very amazing/talented
87.
▲
by
stephen
4y ago
Great post/looking back at the core decisions/bets that worked out really well (from the post): * "Impose no runtime overhead on emitted programs." * "Align with current and future ECMAScript proposals." * &quo
88.
▲
by
stephen
4y ago
Ah yeah, you're right that Deno doesn't have a node_modules, but AFAIU it still downloads dependencies to "somewhere on disk" and then, every time your code runs, it re-evals all of them from scratch. So, admittedly I wa
89.
▲
by
stephen
4y ago
This is probably naive, but I'd love to see one of the Node.js competitors, i.e. Bun or Deno, innovate on the "it takes ~forever to load node_modules every time I run a test/script/etc" problem. I.e. Bun is improvin
90.
▲
by
stephen
4y ago
Naive question, but is that dictated in the spec? Probably? Just wondering that, since Deno is rewriting all of npm anyway, it would have been a great time to revisit some of these historical script-y design decisions, to make JavaScript&#x
More ›