HackerLangs
トップ新着トレンドコメント過去質問紹介求人

jitl

12,814 カルマ登録 14 年前
Jake Teton-Landis

https://jake.tl

https://twitter.com/@jitl

https://github.com/justjake

Making https://notion.so/product since 2019.

投稿

Claude Fable 5 available globally tomorrow

twitter.com
46 ポイント·投稿者 jitl·10 日前·3 コメント

Show HN: JavaScript port of SQLite's parser, 2x-200x faster than others

github.com
2 ポイント·投稿者 jitl·2 か月前·0 コメント

Lisette – Rust syntax, Go runtime

lisette.run
12 ポイント·投稿者 jitl·3 か月前·1 コメント

Honda cancels the two electric vehicles it was developing with Sony

arstechnica.com
2 ポイント·投稿者 jitl·4 か月前·0 コメント

Consistent Hashing: Algorithmic Tradeoffs (2018)

dgryski.medium.com
1 ポイント·投稿者 jitl·5 か月前·0 コメント

Scaling Beyond Memory: How Materialize Uses Swap for Larger Workloads

materialize.com
2 ポイント·投稿者 jitl·10 か月前·0 コメント

In defence of swap: common misconceptions (2018)

chrisdown.name
116 ポイント·投稿者 jitl·10 か月前·150 コメント

コメント

jitl
·12 時間前·議論
that is a specific brevity instruction!
jitl
·一昨日·議論
yeah but, the existing code was also full of bugs, so isn’t it all a wash in the end?
jitl
·一昨日·議論
bun has never been fit for production, at least not for load bearing business apps. it’s been haunted by segfault bug reports since the early days, and i personally hit at least one a week when im doing lots of bun stuff. im excited for bun with less segfaults
jitl
·8 日前·議論
rust to c supports infinite platforms that already have a c compiler by implementing a single rust to c program

on the other hand, porting llvm to an infinite number of platforms requires an infinite amount of work

so, it is less work this way
jitl
·8 日前·議論
Works for me:

    $ git clone https://code.haverbeke.berlin/wordgard/wordgard.git
    Cloning into 'wordgard'...
    remote: Enumerating objects: 8274, done.
    remote: Counting objects: 100% (8274/8274), done.
    remote: Compressing objects: 100% (4747/4747), done.
    remote: Total 8274 (delta 6049), reused 5002 (delta 3464), pack-reused 0 (from 0)
    Receiving objects: 100% (8274/8274), 1.61 MiB | 2.93 MiB/s, done.
    Resolving deltas: 100% (6049/6049), done.
jitl
·8 日前·議論
so like… any website
jitl
·8 日前·議論
why would they swap. add
jitl
·8 日前·議論
android isn't linux-y enough to be able to use android auto on a more typical linux kernel?
jitl
·8 日前·議論
I have a boring Mercedes mid-size SUV. Carplay works. I can skip/repeat tracks using the standard control on the steering wheel; the instrument cluster shows the current track the same way it's done with connected phones forever. On the center console screen, we use the Carplay view with 3 splits - one for Spotify, two for navigation (map & next direction). Google Maps and Apple Maps are both reliable where I drive (Miami).

Tesla is a great car below the from the headlights down, I love driving my dad's Y performance to the grocery store when I'm visiting home. But no way I'm going to get a car where I can't point the vent at my armpit without using a touch screen. No way I'm going to get a car where I can't talk to whatever agent I want while stuck in traffic. I much rather have a boring car that doesn't tick me off.

If Tesla (or Rivian) add Carplay, they'll really move up the my list (still want physical vent control tho). Would you stop driving your Tesla if an update added Carplay tomorrow?
jitl
·9 日前·議論
we’ve got the benchmark graphs from the announcement, and i hear tepid opinions from people with gpt 5.6 access. fable is far ahead of gpt 5.5 (my prev daily driver) also. much less passive aggressive / overly defensive.
jitl
·10 日前·議論
it’s the industrial revolution for thinking, seems important
jitl
·10 日前·議論
people like me who want to use the best ai on the planet to get stuff done right
jitl
·10 日前·議論
the plan is to make money by charging a premium for the best product on the market instead of giving it away for free.
jitl
·10 日前·議論
> even Japan dropping a credible model

if fugu/fugu ultra was good, why aren’t we hearing about how good it is? seems super slow and expensive, and everyone i’ve talked to who tried it gave up
jitl
·10 日前·議論
it’s still significantly far ahead of openai. gpt 5.6 looks like “better 5.5”. fable does not feel like better opus 4.8.
jitl
·10 日前·議論
if you are in competition heavy space where in product LLM productivity provides value, dinosaur thinking like this will get you left behind
jitl
·10 日前·議論
if you’re building on LLMs you gotta have an eval and prompt iteration pipeline, and you ought to be evaling every model release — your competitors will do this, and your users will want the latest and greatest (for frontier tasks) and the cheapest/fastest. So you should already be paying this cost anyways. i guess it depends on your team size and scale but not building this muscle seems like not having continuous delivery for regular code or even like not having tests and ci to merge to main.
jitl
·10 日前·議論
i don’t think 5.6 will be as good as fable. their benchmark graphs say so, maybe they’ll take some limiters off next week or something now that being Fable tier isn’t scary anymore.
jitl
·10 日前·議論
fixing minor bugs takes one slack message for us now. bugs go down, goodness go up.

fixing more serious regression also easier. connect honeycomb mcp, ask agent to debug while i walk to coffee and get some pistachio rose dates. by time im back with my oat latte ive got a full report on what happened and can send the next slack message to fix.

life is good
jitl
·10 日前·議論
better point than i made by getting down into the analogy mud, well put