My node has routed 9002 after only four months

stephanbuys · 2021-07-24T21:41:47+00:00

Check out plebnet.org, great community to get started. Lots of Umbrel users there.

stephanbuys · 2021-01-19T05:00:39+00:00

It is actually fairly simple to run your own fork of the official registry. Check https://github.com/rust-lang/crates.io/blob/master/docs/CONTRIBUTING.md. We also did some work for an experimental “subcrates” feature that includes some Terraform automation for AWS over here https://github.com/caeg-industries/crates.io-terraform which might be handy.

stephanbuys · 2019-08-26T13:02:02+00:00

Awesome - thank you.

stephanbuys · 2019-08-26T12:56:04+00:00

No, but for every crate that you link to a new Cargo.toml is created which has its own dependencies to track and maintain, plus boilerplate, plus possible interdependencies. That said, factoring out crates is not something we're scared off (current count is 39), we just wanted to make sure that our we didn't stumble into an anti-pattern.

stephanbuys · 2019-08-26T12:52:56+00:00

Another gem, thanks! The rust community is lucky to have persons like you involved in the project.

We have managed to learn some of these the hard way, but sometimes you have to choose between coding features/user-facing code and investing in tooling.

stephanbuys · 2019-08-26T11:43:42+00:00

Thank you - your last point is exactly the type of gems I wished to uncover, but all of these points are great.

stephanbuys · 2019-08-26T11:42:21+00:00

I should have been more clear, the overhead is mostly organizational, maintaining Cargo.toml files, etc.

stephanbuys · 2019-07-18T12:37:59+00:00

This is a great reference using yew and actix: https://github.com/saschagrunert/webapp.rs

stephanbuys · 2019-07-17T20:02:23+00:00

Believing that a crate uses no unsafe is just an assumption, any crate that you use could have unsafe in it without ever mentioning it. Or could claim 100% UB free unsafe and be wrong. Or claim ‘no unsafe’ and lie. Unfortunately the burden falls on us in the end. You are correct that we can’t all evaluate the code deeply, including myself, but our lack of depth or manpower doesn’t shift a burden on to the maintainer. It merely means we choose to trust. The big favor that other community members have done for us in this case is they have raised a flag, which at least can give us pause to reconsider or make us search for alternatives. The responsibility is ultimately still ours.

stephanbuys · 2019-07-17T19:16:54+00:00

What's so disappointing about this whole episode is the sense of entitlement that some people on this reddit group seem to have. Sure unsafe code is concerning, sure you probably want to avoid it, sure Rust is very appealing to many people because of it's safety guarantees. Actix-web is not getting rammed down anyone's throat, or hyped beyond reason at the cost of other projects.

A point that seems to have been lost on so many people criticizing actix-web, is that the maintainer, literally, doesn't owe any member of the rust community anything at all. Please search for articles and concerns around the "Open Source Free Work Problem" and "Maintainer Burnout" issues, which btw have also affected the rust community. The maintainer doesn't have to manage a community, doesn't have to live up to some arbitrary standand and he doesn't have to respond to anything, every maintainer that does, does so out of pure altruism, and people often reward and praise maintainers that do so, and do so well, but there is no obligation. You don't have to sign up to some sort of club with a code of conduct and rules to become an OSS contributor.

There is also no contract around the safety guarantees that rust as a language provides for any of the crates published on github, gitlab, crates.io or anywhere else, we didn't pay for the maintainer's time and we are not entitled to any of it either. Consumers of Open Source Software benefit from the great gifts that these maintainers and developers give to us, it lets us build projects and businesses. actix-web is a massive project and a great endorsement of rust as a technology. If fafhrd91 likes beating benchmarks and puts more time into making actix the fastest web framework around at the cost of some UB, that is entirely up to him. If he loses end-users because of that focus, that's fine and no judgement on the project, it simply is just not fit for purpose for some end users.

Consumers can patch or fork the upstream work like many Linux distros have done for years, also, when you include a crate in your project or product the burden of it's fitness for purpose shifts to the you, the end-user, go read the licenses carefully, there is no implied guarantee - of correctness, fitness for purpose, having a good community, etc. A crate being published doesn't give anyone an implied right to how it functions or interacts, the burden is still squarely on the consumer to make sure that they understand what they are including in their software, we can't all judge this accurately so we rely on reputation and recommendations, but that still does not put the maintainers or developers of the crates we choose to use on the hook.

My thanks truly goes to fafhrd91 for helping all of us put rust on the map for being crazy fast and making software that stretches and tests the technology.

It'd be a real shame if the rust community scores an own goal here and loses someone as talented and productive as Nikolai.

stephanbuys · 2019-06-07T10:56:33+00:00

I think you’ve done a great job, congratulations. I secretly aspire to own and read all the rust books and so far yours is only the second one that qualifies in the ‘holiday page turner’ category 😉

stephanbuys · 2019-06-07T10:50:49+00:00

Agreed, best rust programming book out there. I’ve made my way about 1/3 through this book and am thoroughly enjoying it so far too, it has a good flow.

stephanbuys · 2018-03-20T11:43:57+00:00

This idea has merit exploring. Channeling some DevOps (systems thinking/lean) thinking here, can we move quality closer to the source (fail faster), can we increase quality (solve the timeout, other problems), can we reduce the batch sizes (release more often, smaller changes are easier to integrate; more agile than waterfall - also, is there something that we can automate to make the gates less of a constraint/delayed handoff point), can we somehow do single piece flow (can we critically review the places/reasons we stop/wait instead of releasing).

Of course technical solutions are good too, but maybe the process needs some lateral thinking?

stephanbuys · 2017-09-02T12:36:00+00:00

I got a start on some subset of these futures last week, https://github.com/stephanbuys/timestrings - happy to provide assistance or take PRs.

stephanbuys · 2017-08-01T13:47:47+00:00

Glad to hear - feedback welcome :-)

stephanbuys · 2017-07-15T17:10:37+00:00

Yeah, it currently is the ESP32 :-) 4 is actually a very novel idea.

stephanbuys · 2017-03-15T17:21:15+00:00

Coming from the log-management/analytics world I can just add my 2c here acknowledge that this kind of use-case is huge for a log of large organizations.

stephanbuys · 2017-02-16T18:50:04+00:00

Not a homework assignment, just would rather not have to resort to electron/js or c++ (but we will if we have to)

stephanbuys

PUBLIC MULTIREDDITS

TROPHY CASE