MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programming/comments/8ue8st/python_370_released/e1fotjb/?context=3
r/programming • u/sply • Jun 27 '18
383 comments sorted by
View all comments
Show parent comments
2
If you use a language interactively - and it's a common enough use case for python - static typing is a fairly big friction point.
10 u/[deleted] Jun 28 '18 static typing is a fairly big friction point.Why? Statically typed languages work perfectly with REPLs. 1 u/the_evergrowing_fool Jun 28 '18 Like a Slime environment? 0 u/[deleted] Jun 28 '18 That's different - Common Lisp is image-based. It's a viable alternative to types, of course (same thing with Smalltalk), but for the separately compiled languages you cannot have this level of quality of code navigation without types.
10
static typing is a fairly big friction point.
Why? Statically typed languages work perfectly with REPLs.
1 u/the_evergrowing_fool Jun 28 '18 Like a Slime environment? 0 u/[deleted] Jun 28 '18 That's different - Common Lisp is image-based. It's a viable alternative to types, of course (same thing with Smalltalk), but for the separately compiled languages you cannot have this level of quality of code navigation without types.
1
Like a Slime environment?
0 u/[deleted] Jun 28 '18 That's different - Common Lisp is image-based. It's a viable alternative to types, of course (same thing with Smalltalk), but for the separately compiled languages you cannot have this level of quality of code navigation without types.
0
That's different - Common Lisp is image-based. It's a viable alternative to types, of course (same thing with Smalltalk), but for the separately compiled languages you cannot have this level of quality of code navigation without types.
2
u/JanneJM Jun 28 '18
If you use a language interactively - and it's a common enough use case for python - static typing is a fairly big friction point.