You have to do that in C++ too.
-
-
This Tweet is unavailable.
-
- 2 more replies
-
-
-
I guess the steeper learning curve (compared to less capable systems) may lead to some slowdown when starting out, although this is IMHO more than offset by the awesome error messages.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Once you internalize it, Rust is really easy to work with and is not a drag on productivity at all (unless you're doing stuff that really should use a GC). But it takes a long time to get there compared to many other languages.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It took me two years to feel productive with rust. I'm a slow learner, and the docs have improved, but ownership can feel weird. For me it was worth it, since I care about reliability and performance on greenfield projects. Others may not get the same ROI.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think types have an interesting productivity curve where they attenuate the initial exploratory process of programming.
-
This space of ideation realistically represents most of rusts hobbyist niche. I'll grant that types seem to scale very well asymptotically.
- 3 more replies
New conversation -
-
-
Grr lack of types dependent on values are a drag on my development speed (only slightly ironic)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Rust has an enormous learning curve, forces programmer to confront things that other languages let us defer…as bugs.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.