(Which is too bad, the ideas behind the project seem sound.)
(Which is too bad, the ideas behind the project seem sound.)
Do Rust projects have a tenancy of becoming abandoned maybe due to the complexity of the language since it's hard to contribute? I've seen enough cases on this that prompted me to ask this.
1. Rust projects become abandoned (observed fact)
2. Language complexity (?)
3. Hard to contribute (?)
I guess that’s why you were kind of defensive when you brought it up.
Rewrite-in-Rust is a thing. Not only for applications but also for foundational libraries (crypto, http, async, etc). The ecosystem is still young with lots of gaps and many devs are experimenting with new approaches to fill those gaps. More new projects -> more abandoned projects.
Other languages had similar teething problems, just ask anyone with applications in Zope, WebPy, Pylons, Merb, JS frameworks not named React, EJB, MFC, etc.
Python is an outlier though; it was mostly ignored until very suddenly it took off starting around the time Jupyter released.
Most (including I) think it took off due to how easy and accessible it was back then, syntax-wise. You could pick it up and be slightly productive in a day, be extremely productive in a week and essentially master it in a month.
Go is following a similar trajectory: productive contributor in a week, master in a month.
Rust is in the opposite direction: too many people simply give up on it, those that persevere report months before any reasonable productivity.
Reddit and Eve are interesting in being largely stuck with the now-dead platforms they built on too, in the form of web.py and Stackless Python. YouTube I presume the original Python application is gone in favour of a bunch of Go and Java microservices by now.
It's interesting as someone who was in the Python for web development camp as Python for scientific computing took off as the two camps were both oblivious to the existence of the other in many cases.
Wasn't PHP the king of dynamic laguages for Web?
I don't think Rails/Ruby was ever used more than PHP.
IIRC, PHP at its lowest popularity ever is still higher than Rails/Ruby at it's highest popularity ever.
The lowest I can recall PHP being at is +-6% (recently). The highest that Rails/Ruby ever got to was <3% (2004/2005/2006).
Major scientific libraries:
- SciPy: "Around 2001"
- ipython: 2001
- Matplotlib: 2003
- NumPy: 2006
- Pandas: 2008
Major web libraries:
- Zope: 1999
- Twisted Web: 2002
- WSGI: 2003
- Django: 2005
- Pylons: 2005
Applications mentioned:
- Eve Online: 2003
- YouTube: 2005
- Reddit: 2005
I don't think this justifies the claim that the web python community was around at the same time as the scientific community while the two were relatively unaware of each of other as "revisionist". It just makes it look like you were in the camp that was aware of the scientific stack and not the web stack.
I didn’t dispute this, please reread what I said again.
> It just makes it look like you were in the camp that was aware of the scientific stack and not the web stack.
No, actually I’m a web stack Python guy mainly, I just actually know my history.
But like, if you're trying to do something you'd otherwise do in C++? Audio/video processing, or something along those lines? Yeah, it's fine. The common libraries you choose today are likely to be maintained going into the future.
Other languages don't have as fun a type system, so I feel bogged down and lose motivation before I even start writing code.
I don't know how many others this applies to, but I have a lot of abandoned Rust projects because if it wasn't in Rust, I never would have even started writing them down before abandoning them.
https://twitter.com/bodil/status/1520404060138094592
The author of this crate enjoys advanced type systems, and can't wait for Rust to add what you'd call "more complexity" in the form of higher-kinded types, generic associated types, and specialization (some of these features are available in an unfinished/experimental form in the nightly compiler, but may not become part of the language anytime soon, if ever).