Live data from Hacker News

Rust and the limits of swarm design

esr.ibiblio.org

41–50 of 55 posts

Re: Rust and the limits of swarm design

#41
post #19

> This isn’t a question that comes up so often with respect to (say) Python because Python has an effective form of curation – blessing things into the standard library, at which point their alternatives generally disappear. In effect, Python modules are quality-filtered on the taste of the BDFL and the devteam. I love Python but this statement is absolutely coming from someone who does not write Python on a regular…

The libraries you mentioned augment the stdlib rather than replacing it.

Re: Rust and the limits of swarm design

#43
> Which brings me directly to what bothers me about the crate system and the sociology behind it – I don’t see any pruning. Worse, I don’t see much understanding of the need for it. A lot of Rustaceans don’t seem to grasp why, when the question is “where do I get feature X?” the answer “oh, there are 23 crates for that” is objectively terrifying.

Actually, I think the community does recognize that this is a problem they are running into as they scale up. Previously there was the discussion of the Rust Platform [1] as a pseudo-stdlib which was received with a lot of mixed since the Python approach isn't actually all rainbows and sunshine. More recently, there has been effort to try to improve the discoverability of relevant crates [2].

[1] https://aturon.github.io/blog/2016/07/27/rust-platform/

[2] https://github.com/rust-lang/rfcs/pull/1824

Re: Rust and the limits of swarm design

#44
Maybe we could have something like what Debian has to manage channels? Differents stages (experimental, testing, stable) and a group of official maintainers? I know that's not easy to create that kind of communities and that you née a lot of ressources (benevolent people). But that works great for Linux distributions.

Re: Rust and the limits of swarm design

#45
post #19

> This isn’t a question that comes up so often with respect to (say) Python because Python has an effective form of curation – blessing things into the standard library, at which point their alternatives generally disappear. In effect, Python modules are quality-filtered on the taste of the BDFL and the devteam. I love Python but this statement is absolutely coming from someone who does not write Python on a regular…

requests was indeed asked to join the stdlib. However, the schedule required for distribution would have made it more difficult for them to innovate in their current way. [0]

[0] https://github.com/kennethreitz/requests/issues/2424

Re: Rust and the limits of swarm design

#46
post #39

Earlier quoted context omitted.

Libraries tend towards standardisation regardless of whether they're being curated by the language designers. Python is actually a good example of this. Look at the library ecosystem built up around scientific computing. None of that is in the standard library, yet there is a common set of packages being used.

Scientific libraries are a complex problem, writing yet another web framework isn't. Furthermore most sci/num libs are heavily linked to C/C++ and FORTRAN code, where most of the work is done.

Web frameworks are rarely part of standard libraries. The closest I can think of is ASP.NET for C#.

Re: Rust and the limits of swarm design

#47
post #39

Earlier quoted context omitted.

Scientific libraries are a complex problem, writing yet another web framework isn't. Furthermore most sci/num libs are heavily linked to C/C++ and FORTRAN code, where most of the work is done.

Web frameworks are rarely part of standard libraries. The closest I can think of is ASP.NET for C#.

Go has a http server, so does python and javascript.

Re: Rust and the limits of swarm design

#48
post #27
post #19

> This isn’t a question that comes up so often with respect to (say) Python because Python has an effective form of curation – blessing things into the standard library, at which point their alternatives generally disappear. In effect, Python modules are quality-filtered on the taste of the BDFL and the devteam. I love Python but this statement is absolutely coming from someone who does not write Python on a regular…

Sure, but even then, I think his point is still applicable. It's urllib2 and requests, not urllib2 and requests and 20 other libraries. The fact that an inferior library is being kept alive by being in the stdlib is maybe unfortunate, but there's still only a small number of choices overall. That makes it much easier to do research and see within the first few search results that the majority of the community recomme…

His point is absolutely not applicable. Rust is a _very_ new language. The community will eventually converge on specific crates for specific purposes in time.

Re: Rust and the limits of swarm design

#49
post #47

Earlier quoted context omitted.

Web frameworks are rarely part of standard libraries. The closest I can think of is ASP.NET for C#.

Go has a http server, so does python and javascript.

So a http server is a web framework now? Okay, let's go along with this.

Node.js is popular, but it's not 'standard'. It's not part of any ECMAScript standard libraries, which would be the requirement if it was to be standard.

I don't know the situation with Go that well, so if it has a http library in the standard I'll take your word for it, but there do seem to be some popular non-standard http servers like Caddy.

As for Python, this is probably an example of where the impact of standards is not that great. How often is the standard http server used compared to popular third party alternatives? Are there any web apps you know of that are using the standard http server in production?

Re: Rust and the limits of swarm design

#50
post #33
post #8

Actually, the kind of features ESR asks for are covered by github, IMO. It's easy to review code quality from there, the number of stars and forks reflect project popularity, the list of committers (how many they are and who they are) can help having an idea about long term maintenance expectations, etc. The cool thing is that it works for almost any language : github is "social coding", thus it's also social validat…

10 years is "that long", now?

How many libraries you use today that you already used ten years ago? Is there more than a handful?
Post reply on HN