Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
drob518
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
61.
▲
by
drob518
2mo ago
I’ve been using v4 Flash 0731 a lot lately and you can’t beat the price performance. That said, it sometimes takes my prompts as more of a suggestion than a directive. I’ve found that introducing a reviewer subagent (even with the same mode
62.
▲
by
drob518
2mo ago
There is some special sauce that they have. It’s not just a simple quant of another release. Or so they imply. I don’t have any insight into how it works or what the Bonsai special sauce is.
63.
▲
by
drob518
2mo ago
It’s still going to chew up context quickly. Surely, some of the added tokens are helping the model, but does it require as many as it generates? What happens on long, multi step tasks as it pushes old tokens out of context? I’m not sure we
64.
▲
by
drob518
2mo ago
You’re basically proving my point. As I said, it’s similar but incompatible, requiring a recompile or reassemble. The point being that the 32-bit instructions are not a distinct subset of all the instructions with the 64-bit instructions ad
65.
▲
by
drob518
2mo ago
And I suspect it’s accelerating quickly. This whole space is hyper cost-competitive and pennies matter, so being able to design whatever you want without having to talk to lawyers or pay anyone anything is a huge win and matters far more th
66.
▲
by
drob518
2mo ago
Yes, but x86 had a goal of running every old piece of code on the new thing. That’s not true with RISC-V. Whereas x86 accreted more and more features, RISC-V solves this with profiles that are not guaranteed to be compatible with each other
67.
▲
by
drob518
2mo ago
Definitely. I’m a weird software guy that got a hardware degree in college so that I could understand all the low level stuff. I remember there was a joint project with the hardware (ECE) and software (CS) students to build a simple compute
68.
▲
by
drob518
2mo ago
The Clojure community is definitely less macro-crazy than other Lisp communities. But it’s also very programmer-specific. I’ve worked on OSS Clojure code where the original programmer loved macros. In general, I found it more annoying becau
69.
▲
by
drob518
2mo ago
https://typedclojure.org/
70.
▲
by
drob518
2mo ago
Macros returning macros happens in every Lisp, including Clojure. It’s no biggie. Hygiene has nothing to do with it and there are ways of properly managing unique symbols in all Lisps, even if some dialects are more manual than in Scheme&#x
71.
▲
by
drob518
2mo ago
My own personal rule is that every Lisp programmer should understand macros and very rarely reach for them. They are a super-power, but easy to misuse. I think Paul Graham is partly responsible for the “Lisp = macros” thinking and the gener
72.
▲
by
drob518
2mo ago
I agree. Thus far, we seem to just be training an absurd number of parameters, and that’s all.
73.
▲
by
drob518
2mo ago
I’ve been struggling with this. I use Clojure and clj-paren-repair has been helpful ( https://github.com/bhauman/clojure-mcp-light/blob/main/src/c... ), but it would be even better if the model could
74.
▲
by
drob518
2mo ago
If you write a harness in Lisp, you can easily access the running Lisp environment via tools, one of which can be a repl tool. This allows the model to do whatever it wants within that environment. Obviously, this is “dangerous” and should
75.
▲
by
drob518
2mo ago
Sign of humility.
76.
▲
by
drob518
2mo ago
I self-identify as a Smug Lisp Weenie.
77.
▲
by
drob518
2mo ago
As far as Lisp programmers go, Joe is quite elite, though I suspect he’s got a twinkle in his eye when he says this, applying a bit of sarcasm. He’s been a Lisp programmer longer than most programmers have been alive.
78.
▲
by
drob518
2mo ago
The models generate Clojure just fine, with the exception of mismatching parens/brackets/braces pretty frequently. There is a tool which can correct that after every edit.
79.
▲
by
drob518
2mo ago
Unfortunately, I missed the Lisp machine era by a whisker. AI winter was just hitting as I graduated college (1989), and I got hired working on RISC systems, which were pretty much the opposite of Lisp machines at the hardware level. I have
80.
▲
by
drob518
2mo ago
Yea, this seems to be a consistent issue. The models don’t know when to think strategically and often make local edits that keep growing individual functions with more and more conditional logic.
81.
▲
by
drob518
2mo ago
In the Clojure world, there is a small utility that is pretty popular called clj_paren_repair (part of clojure-mcp-light: https://github.com/bhauman/clojure-mcp-light/blob/main/src/c... ) that uses p
82.
▲
by
drob518
2mo ago
There is a herd of companies all running a race. The technology is known. They all have roughly the same resources. It’s not unexpected that they have similar cycle times for model development and that those models will be of roughly the sa
83.
▲
by
drob518
2mo ago
Given local AI requirements, I expect minimum configurations for higher end machines to accelerate quickly. Yes, an entry level MacBook Air might be at 32 GB, but the entry MacBook Pro should quickly have 128 GB as a baseline. All this assu
84.
▲
by
drob518
2mo ago
It’s scary the number of security tokens that end up being ingested by these models.
85.
▲
by
drob518
2mo ago
Indeed. Sigh.
86.
▲
by
drob518
2mo ago
Cool
87.
▲
by
drob518
2mo ago
That dynamic was exactly why I moved from Scheme to CL many years ago (full disclosure, Clojure is my daily driver, now). I loved the minimalism of the RxRS documents, but they really only covered the small core of the language, and then al
88.
▲
by
drob518
2mo ago
I think you’re spot on here. OpenAI and Anthropic are burning cash at a phenomenal rate (clearly unsustainable in the long run), but it isn’t clear what the exit ramp is for them. If they stop training and just focus on inference (which the
89.
▲
by
drob518
2mo ago
Thanks. Yea, I’m sure there are corp strategies at play here. Zuckerberg didn’t just roll out of bed and decide to do this one day. Ever since the Llama 4 fiasco, I’m sure they’ve been trying to restart everything, but for whatever reason t
90.
▲
by
drob518
2mo ago
Of course it is. I never said differently.
More ›