Agree. Another way to look at it is: having both Julia 1.x and 2.x out there in the world has a cost. People need to spend more time dealing with the existence of incompatible versions. (I don’t want to dwell on it, but of course the python 2/3 split is the canonical example.) To pay that cost, there has to be some balancing benefit: Julia 2.0 has to be significantly better than 1.0 to make it worthwhile. While this scope change is highly desired by many people, I don’t think it meets that bar.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| New scope solution | 235 | 22403 | January 14, 2020 | |
| Global scope confusion again | 52 | 6968 | May 17, 2025 | |
| Local vs global scope again | 30 | 2483 | August 9, 2020 | |
| REPL and for loops (scope behavior change) | 42 | 15327 | September 16, 2020 | |
| Explain scoping confusion to a programming beginner | 26 | 3354 | August 11, 2020 |