China
HN user
aaronblohowiak
Building an AS/RS for TCGs
Personal: aaron.blohowiak@gmail.com
while ClickHouse can scale down to compete with duckdb, I dont believe (but happy to be corrected) that duckdb can scale up like ClickHouse can.
most people dont have that scale problems, but when you do...
I can see their logic - instead of breaking people's builds, they are being the nice guys and letting you pay them back later. BUT, any time you break convention, you've dipped into your trust budget (even if you communicate it way more clearly than was apparently done here.)
Same price for regular and cheaper fast mode. Happy for these incremental improvements.
for LLMs as implemented today?
Put differently, 1/40 is not the same as 1x - 40x. I’d phrase as Reduced by 97.5% or 0.975x
How can you cut latency by more than 1x? I am no intending to be snarky, it just doesn’t fit my brain how you can reduce a measure time by more than the original starting time.
taalas!!!
Should according to your ethos, not should according to history, sadly.
Only penalties if you withdraw from 401k. Most 401k plans have some kind of moneymarket, bond fund, or similar
taalas is amazing. id gladly spend 5-15k on something that matched that performance with opus 4.6 quality
I disagree but the constraints required to get there are probably untenable for most practical applications, so in practice I agree.
how long they stay around after the cache miss is irrelevant if I am burning all the prior tokens again. also, how much context they have depends entirely on the task and your workflow. I you have a subagent implement a feature and use the compile + test loop to ensure it is implemented correctly before a supervisor agent reviews what was implemented vs asked then yes, subagents do have a lot of context.
So if I run a test suite or compile my rust program in a sub agent I’m going to get cache misses? Boo.
Kernel here is ambiguous.. I get what you mean, but parasolid is usually the thing described as the cad kernel.
External drive is workaround to apple’s pricing scheme, often purchased at same time as computer.
The fundamental tension between nouns and verbs and the attempts to unify them like events have made programming a long art form to study.
It's all use-case and priority-specific, and I think the more varied your experience and more tools you have in the tool belt, the better off you can be to bring the right solution to bear. Of course, then you think you have the right solution in mind (lets say using partitions in postgres for something) but you find the ORM your service is using doesn't support it, then what is "best" becomes not only problem-specific but also tool-specific. Finally, even if you have the best solution and your existing ecosystem supports it but the rest of the engineering staff you have is unfamiliar with it, it may again no longer be "best".
this ladder of problem-fit, ecosystem-fit, staffing-fit is something I have grappled with in my career.
LLMs are only so-so at any of the above (even when including the agent as "staff".)
It's really hard to get away from ssjs frameworks for front-end, so for my startup it's Axum + Seaorm for "the api" and a Svelte SSR "front end" / view layer.
I think rust programers are more likely to want flask/rack than Django/rails.
So this is a TUI WYSIWYG GUI ?
Safari can’t connect to your site
“Art project”
The last part of your post doesn’t necessarily follow or support your argument; the corollary is “It’s hard to outlaw rna”.
carcassonne!
Fewer unique video hours, YouTube pays residuals, vastly smaller library to personalize
you're in a bubble. probably urban, educated and wealthy.
best _former_ president of all time.
So if you are using multiple languages to have scripts that run off your pre-commit hook, this is like a package and language runtime management system for your pre-commit hook build system? Rather, I think this is a reimplementation of such a system in rust so it can be self contained and fast.
This is the kind of thing I see and I think to myself: is this solving a problem or is this solving a problem that the real problem created?
Why is your pre-commit so complicated that it needs all this? I wish I could say it could all be much simpler, but I’ve worked in big tech and the dynamics of large engineering workforces over time can make this sort of thing do more good than harm, but again I wonder if the real problem is very large engineering teams…
Guano
The hardest part is giving yourself permission to ship something you know is flawed.
I still feel like there's an unexplored space where you combine the benefits of both somehow though. Like a code-based CAD but it also has a GUI editor that stays in sync and avoids the need to type in coordinates by hand. That would be extremely difficult though.
I think you can do this if the data representation of operations and values is human readable. The simplest implementation would restrict the language/data format to operations representable in the gui.
Unlike trying to solve the "visual programming" problems, we don't need or desire Turing completeness.
Very interesting indeed!