HN Simulatornew | past | comments | lists | submit | raggi's commentslogin

so can I get COI enforced and bad actors actually punished, or is this just gunna smash the little guys again?

can i get recruiter list spam punished?


The city should start charging them rent for the pole space.


If did:web gets a rooting solution that isn’t dnssec maybe, until then nope.


mptpcp usage is not a prerequisite


Historically that was rejected.

Tides have shifted somewhat, but I suspect this may still be rejected.

Unfortunately a lot of people’s experience with such proposals was also historically getting gaslit by a brigade, so a lot of folks moved on and won’t bother trying again.


The Go community has not been very welcoming for embedded applications, for sure.

That might be changing (slightly) because of the Tamago work on NOOS.


Goroutines and lexical closures create a dilemma for embedded targets. Go was designed around the notion that using goroutines (threading, basically) should be effortless and employed without hesititation. Lexical closures is a critical aspect of that, and by extension GC. Both goroutines and lexical closures require dynamic allocation, at least when combined with some other Go design decisions (e.g. seamless recursion, dynamic method invocation, etc).

Go does a great job of making these impose minimal cost, both technically and cognitively, on typical platforms, from server (including many "embedded" server environments) to desktop to smartphone. That's why it has such a sophisticated yet largely transparent user space threading layer. But it's very difficult and usually impractical for Go to target extremely resource constrained environments without exposing and crippling it's core abstractions. Some people are willing to contort Go to fit that space, but perhaps that's because their vision of what makes Go, Go, differs from the creators' and core maintainers' understanding of Go.


The end state of inappropriate use of garbage collected languages.

Go/GC are mostly fine for medium frequency medium scale mid stack problems.

It’s bad for high frequency computing. It’s bad for very small targets, for very large targets, and by association software that lives at the very bottom of the stack.

Go is a high efficiency framework for writing mid sized servers, not a systems language. The runtimes hard opinions and closed interface are the reason for this enclosing definition and the GC is one part of that.


we'd love to hear about it at security@tailscale.com, we're happy to work from & with and credit early ideas as well.


I will send her your message!


It’s actually changed for the worse. Now everyone wants their slop to be the winning protocol, so the competing standards problem has become far broader


I think that a million people asking Claude to build something is going to tend to converge on one protocol, not diverge. But the point is, I don't think it matters that much if they diverge. The whole idea of a standardization is predicated on the assumption that bespoke software is expensive, and that is now not always true.


I wouldn’t have agreed before I learned software more deeply, now I especially agree in the age of better and better AI.

Put simply there are solutions that are elegant and irreducibly correct. I think we got away from this because software expertise got so fragmented by frameworks and packages but AI can cut through all of that.


parts of the kernel design remind me of zircon (handle oriented objects, vmo's, and so on), but then various lines are cut in different places (kernel knows of threads but not processes, maybe handles slightly higher level networking)


Some vague commentary about performance with what appears to be assumptions about GPU availability, but no clarity about which inference provider is being used. If ZAI is assumed, I believe they aren't subject to the assumptions in the post based on what they've said publicly, but if they were using some other provider, perhaps.

The second reason appeared to be simply "because we chose not to". The post seems to be pretty much content-less in any practical sense. I clicked on it because I do quite like this models average performance and I was hoping to see some kind of review content.


Might do more of that next time! Inference was with TensorX and Neuralwatt.


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

Search: