smasher164

15 ms·

91.
by smasher164 4y ago
I said in a sibling comment that scheduler activations may have been a flawed idea, but I don’t think the space of user-space scheduling APIs is fully explored. Google’s ghOSt work is an example of that. If io-uring is proof of anything, it
92.
by smasher164 4y ago
Project Loom experimentally proved that the benefit of virtual lies not in its fast context switches, but in the throughput afforded by having so many threads executed at once. I am aware of GC-aware green threads. They allow you to combine
93.
by smasher164 4y ago
Yeah, scheduler activations were one approach, albeit one that wasn't deemed effective. I think FreeBSD ended up removing the feature. A more recent attempt that's interesting is ghOSt from Google: https://storage.googl
94.
by smasher164 4y ago
> still lock the go VM with an infinite loop This is no longer an issue now with Go's async preemption. Also, this is less a "language-level concern" and more a consequence of a poor implementation of preemptive scheduling
95.
by smasher164 4y ago
Preemptive threads with growable stacks. There was some discussion around getting segmented stacks into the kernel, but I'm not sure that's the best approach. There might have to be some novel work done in making contiguous stacks
96.
by smasher164 4y ago
Not really tbh. The Go runtime has a work-stealing scheduler and does a lot of work to provide the same abstractions that pthreads have, but for goroutines.
97.
by smasher164 4y ago
> If that's the sense that's meant Yeah that's what I meant, a lightweight threading mechanism provided by the OS. > there's probably not much reason to add them when user space lightweight concurrency mechanisms a
98.
by smasher164 4y ago
After all the hoopla surrounding concurrency models, it seems that languages are conceding that green threads are more ergonomic to work with. Go and Java have it, and now .NET is even experimenting with it. How long until OS vendors introd
99.
by smasher164 4y ago
This is cool, but a 5 hour battery life is kind of a dealbreaker for a device I would be very mobile with. The 11 inch macbook air used to get over 11 hours, and netbooks used to get like at least 4 hours.
100.
by smasher164 4y ago
As long as you don't hardcode "expected paths" (like in the FHS) in the filesystem, and expose the expectations you have via some configuration (environment variables and flags are fine), then packaging your software for Nix
101.
by smasher164 4y ago
Yeah I just wanted to do a client-server app on a UDP-like socket, but WebRTC had so much complexity that it put me off. It's gotten better now, but WebTransport is the solution we've needed for a while.
102.
How to peacefully grow your service(rakyll.medium.com)
1 points by smasher164 4y ago|0 comments
103.
by smasher164 4y ago
I can't wait to try this out. Thanks for building this!
104.
by smasher164 4y ago
Oh that page isn't mine, I just found it as a good explainer for nix templates.
105.
by smasher164 4y ago
Nowadays, every one of my projects starts with a flake.nix file. I even have templates ( https://peppe.rs/posts/novice_nix:_flake_templates/ ) fo archetypes of projects, like a Go, Rust, GTK project, etc... I love t
106.
by smasher164 4y ago
Not to stretch the analogy too far, but isn’t this true of any non-trivial dynamical system? They are highly sensitive to initial conditions.
107.
by smasher164 4y ago
Not sure about the characteristics of your workload, but here's a talk where a group wrote device drivers in several high-level languages, and measured their performance: https://media.ccc.de/v/35c3-9670-safe_and_s
108.
by smasher164 4y ago
For how strongly worded this article is, you'd think the author would provide some substance in their reasoning. Reference counting, even atomic, is quite expensive. Not only because it can invalidate the cache line, but depending on t
109.
The Keyword Generics Initiative(blog.rust-lang.org)
5 points by smasher164 4y ago|0 comments
110.
by smasher164 4y ago
I wonder if you could apply e-graphs to situations where the union-find data structure would be used, i.e. if there are any additional benefits gotten from the congruence relation.
111.
by smasher164 4y ago
After reading through the Austral site, I have to say that the reasoning for its various features is very well articulated. This language ticks a lot of boxes. The only feedback I have to offer is to not skimp on the FFI, because the easier
112.
Spack – A flexible package manager that supports multiple versions(spack.readthedocs.io)
4 points by smasher164 4y ago|1 comments
113.
by smasher164 4y ago
wxPython is the only maintained alternative there. I think there’s an opportunity to create bindings to other languages with libClang nowadays. However, it’s gotta be done selectively, since there’s so much surface area in the API to fill i
114.
by smasher164 4y ago
This definitely matches my experience using Go at my previous organization. 1. Closures and concurrency really don't mix well. The loop variable capture in particular is very pernicious. There's an open issue to change this behavi
115.
by smasher164 4y ago
Go has asynchronous preemption now using signals. Tight loops are preemptible.
116.
Here We Go Again: Why Is It Difficult for Developers to Learn Another Language?(conf.researchr.org)
2 points by smasher164 4y ago|3 comments
117.
by smasher164 4y ago
Not a fan of articles that attempt to speak for me or say that I have stockholm syndrome. It’s super gaslighty and a pernicious form of contempt culture in the tech community. Instead of just saying how they feel about a language, they try
118.
by smasher164 4y ago
Yeah, his complaint about newtypes is just incorrect.
119.
by smasher164 4y ago
I think Project Loom support will open up green thread support for more Truffle-based languages. I could see Go, Haskell, Erlang, Scheme, and Concurrent ML -style languages taking advantage of that infrastructure. I'm also hoping for o
120.
by smasher164 4y ago
I think Spack[1] might address some of the problems surrounding Nix. It uses python to configure packages, and the upcoming release will have Windows support too. The "Getting Started" information is pretty helpful, but package-le

More ›