Hacker Newsnew | past | comments | ask | show | jobs | submit | rvcdbn's commentslogin

maybe of interest: https://github.com/cloudflare/vinext

(haven't tried it myself)


It's not a good piece of software. Breaks in many places


that makes sense, it's not 1.0 yet


"Read the announcement: How we rebuilt Next.js with AI in one week".


It's not hidden at all, Claude pushes it even tho it poisons the context after every edit with false positives because it's always out of date. This feature should be hidden given how half baked it is.


couldn't opencode just switch to agent sdk?


I'm not 100% sure but I think OpenCode wants to control the harness and persistence, tool call flows etc. If they just used the Claude SDK then it would diverge architecturally from all the other providers, persist jsonl to ~/.claude, etc.


deno does support per-host network permissions https://docs.deno.com/runtime/fundamentals/security/#network...


I'm sure there's a reason but I would expect a system like this to use leader leases for local reads


rqlite creator here -- it's on my list to examine, not clear to me if it would add much beyond what is offered today. But it might.


IMO there really needs to be a way to mark all variables non-null by default at package or at least a file level. Otherwise there will be a strong safety argument for always using T! syntax on almost every variable and this will just be a lot of noise.


Under "other possible future enhancements":

> Providing a mechanism in the language to assert that all types in a certain context are implicitly null-restricted, without requiring the programmer to use explicit ! symbols.


i don’t think it will be that bad. we have a standard in our projects today that all java variables in code we own are not null. if you would like to have a nullable variable, you must annotate it with @Null

this is only an issue at the boundaries of our code where we interact with libraries. i imagine that will be the case with this new syntax as well


If I understand you, then you're not getting any compiler check support for misuses, correct?


I have to assume they have a lint rule for that.

With good tooling compiler error vs lint error is a distinction that matters about as much in practice as parse error vs type error—your editor and CI pipelines will yell at you either way.


I suppose an aggressive linter could assume unmarked should be treated as non-null and at least demand nullability markup where needed.


Anyone who knowingly developed this should be tried held personally responsible.


[flagged]


Locked in a cell, to think about all the innocents their shitty code ended up murdering.


"software is a force multiplier" well maybe that's the point. I am a superstitious b*tch but maybe the Universe doesn't want our force to be multiplied any more!!!!


I've been trading for 4 years on the side mostly on intuition. I like to think one can emotionally program the powerful computer that is the unconscious mind to serve the distributed monster of global finance for profit. Sometimes I even do tarot. Seems to kinda work LoL what could possibly go wrong????


true but as engineers we should sometimes sacrifice and live in the future a bit to maximize opportunity and in the future hardware will adapt to software as it always has


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: