3 ms·
I draw a different conclusion from the "stiff competition". Your conclusion is along the lines of "my god! they need to hurry up and finish it or they'll lose t
by sanderjd 13y ago
I draw a different conclusion from the "stiff competition". Your conclusion is along the lines of "my god! they need to hurry up and finish it or they'll lose the future!", whereas mine is more "what's the rush? there are good alternatives right now, and there will always be more code that needs writing in the future".
By the way, it is actually very possible to write real software in rust already - none of the changes in the last 6 months or so have really required all that much surgery to get up to date. Even this change sounds like it would have a fairly straightforward update path. The only big frustration for me is the lack of a mostly-implemented and "blessed" package manager. I'm watching progress on that front with much more interest than these language changes.
- sanxiyn 13y agoYeah, in some sense, these are all just endgames. To me, the last hard change was @-removal and interior mutability, which happened in October and November 2013. So your "last 6 months" comment is exactly correct.
- sanderjd 13y agoYeah, I guess a more recent biggish one was having to re-do a good deal of vector usage as those apis moved around and changed. But I would say my recent experience has been >90% crate moves and renames, which are really easy to deal with, especially with the right mindset of "I'm using pre-alpha software". I also agree with whoever it was (you?) who pointed out elsewhere that the only reason people are even able to gripe about this stuff is that the development has been way more collaboratively open than other languages. That openness has its pros and cons!