Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
davexunit
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
91.
▲
by
davexunit
2y ago
Hope my post didn't come across as complaining because I agree! Wasm is great right now for lots of things, just wanted to highlight a use case that isn't great yet.
92.
▲
by
davexunit
2y ago
In Scheme what you want to do is allocate a big bytevector and use it over and over. This is what I already do outside of Wasm. I don't want or need linear memory involved, I just want access to my (array i8) from JS.
93.
▲
by
davexunit
2y ago
Thanks for bringing a reasonable perspective to this discussion.
94.
▲
by
davexunit
2y ago
Yes, I know there's more overhead on the web than native, but that is missing the point of my post. I'm talking about issues with Wasm GC relative to other ways of rendering with Wasm. I've played many browser games with go
95.
▲
by
davexunit
2y ago
Perhaps I should've said this in the post to ward off comments from the anti-GC crowd but I do realtime graphics in managed memory languages just fine outside of the Wasm context. This is a Wasm problem.
96.
▲
by
davexunit
2y ago
This was a quickie post for me. Just a tale of what my experience has been. No in-depth, apples to apples comparison so I don't know the magnitude of the performance differential.
97.
▲
by
davexunit
2y ago
Yes, that's right. I'm hoping there will be a way to do this in a future revision of Wasm GC.
98.
▲
by
davexunit
2y ago
Sorry but it's just a different choice not a mistake. I do realtime graphics just fine in non-web managed memory languages.
99.
▲
by
davexunit
2y ago
Slower, single threaded, greatly increases binary size, separate heap from JS so bad interop with extern refs. Wasm GC is a great thing.
100.
▲
by
davexunit
2y ago
As mentioned, that works quite well already but it's not the topic of this post.
101.
▲
by
davexunit
2y ago
Gmail.
102.
▲
by
davexunit
2y ago
Stack switching in wasm would be great (as long as they aren't nerfed which they might be!) but note that Hoot has fibers right now : https://gitlab.com/spritely/guile-hoot/-/tree/main/lib&#x
103.
▲
by
davexunit
2y ago
Since everything would be speaking OCapN you could use the browser interface as a convenient command center. This idea is becoming quite appealing to me actually... would be cool to have a little dashboard showing the health of my servers a
104.
▲
by
davexunit
2y ago
okay
105.
▲
by
davexunit
2y ago
> I wonder how hard this would be to port to Hoot It would be interesting, though I don't know if it would make sense. In any case, the way to do it would be to extract all the code that does POSIX things into an abstraction layer.
106.
▲
by
davexunit
2y ago
Actor systems can handle unpredictable errors and if you watch a recent talk by Douglas Crockford about actors/Misty there are Erlang-like "let it crash" examples.
107.
▲
by
davexunit
2y ago
There are many layers of capabilities. Unguessable process IDs would be necessary for network capabilities. A sandboxing environment would be necessary for system or process level capabilities. It's still worth having the network se
108.
▲
by
davexunit
2y ago
Right, they would need to be unguessable to be used as capabilities.
109.
▲
by
davexunit
2y ago
I tell ya, it was sometimes difficult to be a lisp guy doing devops full-time.
110.
▲
by
davexunit
2y ago
Shepherd is a wonderful little service manager. The project has been integrating the good features of systemd (socket activation, timers, etc.) while retaining the hackability of using a fully featured programming language for configuration
111.
▲
by
davexunit
2y ago
I should clarify that when he calls it vaporware he means that he is interested in propagating the actor model concept rather than any specific language or implementation.
112.
▲
by
davexunit
2y ago
Douglas Crockford has described Misty as vaporware (hence the name), whereas at Spritely we are building and shipping things that can be used. Rather than build an entirely standalone domain specific language, our research and development b
113.
▲
by
davexunit
2y ago
Erlang actors are not privately addressable, so they cannot be used for capability security. The actors described here are.
114.
▲
An annoying failure mode of copying nurseries
(wingolog.org)
3 points
by
davexunit
2y ago
|
0 comments
115.
▲
by
davexunit
2y ago
Wrapping file i/o in actors is exactly what we do in the Goblins distributed programming system. It ensures that only one operation is happening against the file descriptor at any given time while allowing other actors to use it asynch
116.
▲
by
davexunit
2y ago
What line of cymbals? A? K? Something else? Zildjian make quality stuff but maybe you'd prefer either a different line of theirs or another brand entirely like Meinl or Sabian. You never break as many sticks and cymbals than when you&#
117.
▲
by
davexunit
2y ago
Yeah, electronic cymbals just don't feel right at all. The price to pay for being able to practice somewhat quietly, I suppose.
118.
▲
by
davexunit
2y ago
I'm a long time fan of Sabian cymbals but good lord their new logo is so awful. The old one was way better and it's especially bad when compared to Zildjian's iconic logo.
119.
▲
by
davexunit
2y ago
Maybe, but I haven't pushed very hard for it as I don't use OOP very often. I did buy Art of the Metaobject Protocol in case I wanted to try to make some of the improvements myself, but haven't gotten around to it.
120.
▲
by
davexunit
2y ago
Strange to see this show up on the front page now when I wrote this back in 2022. For context, this is a light critique of Guile's CLOS-like OOP system which overall I think is a pretty great approximation of CLOS. I just wanted to wri
More ›