After a month of #golang I would say it’s quite pleasant to work with, can’t say I love it (testing is painfully verbose) but I could see myself working with it for long periods for sure.
Today’s mission was rewriting some node.js to go and I managed to do it painlessly so that’s nice.
Next up convincing the team that #rustlang is better 😬
Dipping my toes into serverless stuff with #rustlang for $WORK, exciting!
Hey #rustlang fans I have an “architecture” question. I’m making a browser for the #gemini protocol. I’m trying to add #gopher support. The first step was to duplicate everything but then as you can guess that’s not great.
The starting point point is an URL and depending on the scheme I go one way or the other. The path is the same: get content, parse it, display it to the user.
What would be a great way to architecture this duplication?
Now that Asuka internals are kinda stabilizing I started adding some long overdue unit tests.
#rustlang unit testing is clean and easy, a pleasure to use!
I love that when fighting too much with #rustlang compiler it's just telling me that my design sucks and I'd better think again.
#rustlang folks any idea on what data structure I should use for a browsing history feature? Like being able to go back and forward. I’m thinking something indexable but also mutable. Any pointer appreciated :)
I’m in love with #rustlang. If you want to learn it read “The Rust Programming Language” seriously it’s really a great resource!
#rustlang cargo is much much faster at installing crates since the last time I used it!
I still believe in computers.
Port 70, 79 and 1965 enthusiast.
"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko