achille-roussel

9 ms·

31.
Show HN: Netjail – Go package to safely send requests to user-provided URLs(github.com)
6 points by achille-roussel 3y ago|0 comments
32.
Show HN: Go 1.22 range functions with database/sql(github.com)
4 points by achille-roussel 3y ago|0 comments
33.
Show HN: High-performance K-way merge in Go with experimental range functions(github.com)
3 points by achille-roussel 3y ago|0 comments
34.
by achille-roussel 3y ago
We tried that actually, and it can work well but you make a different set of trade offs. For example, you can’t get the granularity that durable coroutines give you, you’re bound to snapshot and restore the entire state of the application.
35.
by achille-roussel 3y ago
You’re correct that code migration is still a to do, we’ll be exploring how to do that in the future. As you can imagine there are a lot of challenges with it, but ideas are welcome!
36.
by achille-roussel 3y ago
Yes, we planned to update the coroc compiler to generate this value instead of having it hardcoded so it will be more future proof.
37.
by achille-roussel 3y ago
This is a good callout, although we probably won't be able to significantly improve the performance of Go compiled to WASM until WebAssembly evolves and introduces support for threads or stack switching so we can define goroutines base
38.
by achille-roussel 3y ago
My bad, I misread your initial comment as "it would cost a lot of money"! Memory might be the limiting resource to support time travel debugging in some use cases, but for the ones we are targetting, the problem space is a bit mor
39.
by achille-roussel 3y ago
Source-level debugging is what we have in mind; we have done a lot of work on Wazero and as part of https://github.com/stealthrocket/wzprof to enable it. It is still not a solved problem, and it requires support for ea
40.
by achille-roussel 3y ago
This is a very interesting project, thanks for pointing it out!
41.
by achille-roussel 3y ago
Thanks for the support! Note that timecraft runs programs compiled to WebAssembly, so the "guest" application that runs on it does not have to be written in Go! That being said if you're interested in contributing to the proj
42.
by achille-roussel 3y ago
Thanks for bringing up those questions! We did not make mention of the performance overhead because we don't have that data to share yet. Timecraft is a young project, and our initial focus is on exploring the use cases that the soluti
43.
by achille-roussel 3y ago
You're not wrong, software development is costly, and we have a team of bright and experienced engineers tackling this problem! There is a lot more to timecraft than improving the debugging experience, and we tried to put into perspect
44.
Show HN: WASI socket extensions for Go 1.21(github.com)
6 points by achille-roussel 3y ago|0 comments
45.
by achille-roussel 8y ago
Correct me if I’m wrong, but MQTT is just a network protocol, it doesn’t solve storage, retries, failure resilience, etc... it’s well suited for pub/sub operations over TCP, not so much for ensuring “exactly once” delivery of messages.
46.
by achille-roussel 8y ago
There are no issues with memory utilization of the MySQL databases other than once the working data set don’t fit in memory anymore it has to be fetched from disk on cache misses, which slows down fetches. Disk utilization of the Job databa
47.
by achille-roussel 8y ago
We do want to open source the code. In order to get to production we took some shortcuts which tightly integrated some components of this system with Segment’s infrastructure and would make it hard for anyone to deploy. We discussed open so
48.
by achille-roussel 8y ago
On your first point, you’re correct. Directors scan their databases on start to rebuild their cache and reschedule the jobs that need to get retried. The scan is usually quick for data that was recently inserted since they’re likely in cach
49.
by achille-roussel 8y ago
That’s correct, we were multiple months into the project and already using it in production when I came across (the other) centrifuge. We chose to just go with it because it wasn’t worth changing all the code and everyone’s habit of referri
50.
by achille-roussel 9y ago
go:noescape is meant to be used on functions that are implemented in assembly because escape analysis only works on Go code. As far as I know a etting this tag on a function that is implemented in Go has no effect.
51.
by achille-roussel 9y ago
I agree, there's area for improvement for the compiler here and hopefully in the future we won't have to worry about those issues. For now those are constraints we have to deal with to make our software more efficient unfortunatel
52.
by achille-roussel 9y ago
We've invested a lot in Go at Segment and introducing a new language isn't cost-free, building the expertise, tools, and processes to work with a new technology takes time and energy. It's way more time efficient for us to le
53.
by achille-roussel 9y ago
I used them and was very pleased with the experience. The recruiting process was both interesting and very fair, I got opportunities to present where my strengths were, and also got challenged out of my comfort zone. I think they were doing