5 ms·

> Their namespacing and modularity is terrible, writing a complex gui, non-trivial web server, 3d renderer, or any sort of real time system is right out. And th

> Their namespacing and modularity is terrible, writing a complex gui, non-trivial web server, 3d renderer, or any sort of real time system is right out. And they seem dead set against changing that There are many dozens of open issues discussing namespacing, interfaces, levels of type abstraction and extensibility, garbage collector improvements, i/o latency problems, task-switching performance, and more. Prioritization of core effort in certain directions does not mean other issues are suppressed or even forgotten. Considerate proposals in other areas are welcome, and pull-requests implementing such proposals will be gratefully reviewed. They may not always be accepted -- immediately or sometimes ever. There is certainly some conservatism about adding features (such as interfaces), because features have costs and are near-impossible to remove once added. But other things just take time to get merged; for example, the generational GC took over a year, and there are other very large proposals that have been pending for longer than that because the implementation is lacking in some way or the implications are not fully worked-out to the point of consensus acceptance. That's ok, and IMHO healthy.

SolarNet 10y ago
Except their consensus making prevents real needed features from seeing any progress, sure they have thousands of open issues on the topic, but when did any of them last move. Oh and arguing too strongly on controversial issues (hex stringification! oh no!) gets you banned (that was a hilarious read). So how is anything supposed to move when there is a split in the community?
- tavert 10y ago
  You have an underinformed and incorrect understanding of what happened there. Leave it at that.
  - SolarNet 10y ago
    It looks like someone got banned for submitting a PR as a hypothetical solution which a core team member disagreed with, why would I ever contribute to a project like that. Other people seem to agree on that point: http://danluu.com/julialang/ http://danluu.com/julialang/
- ihnorton 10y ago
  I'm not aware of any pull-requests implementing an incremental GC with pinning support, or any alternative module/namespacing scheme. Those would certainly be welcome. As I said, the people actively working on the compiler have to prioritize because time and resources are finite. This is not the same as anyone being "dead set against changing", or a "ban people for making too much noise about it". > when did any of them last move. Here's a sampling of some improvements over the past 4 months. - Debugging, everyone's priority by astronomic margins, has seen massive work and a recent preview-release (I've been using it since the announcement: rough edges, but very solid core): https://github.com/Keno/Gallium.jl/commits/master https://github.com/Keno/Gallium.jl/commits/master https://github.com/Keno/ASTInterpreter.jl/commits/master https://github.com/Keno/ASTInterpreter.jl/commits/master https://github.com/JuliaLang/julia/pull/15859 https://github.com/JuliaLang/julia/pull/15859 https://github.com/JuliaLang/julia/pull/15444 https://github.com/JuliaLang/julia/pull/15444 - Revamp of closures to make anonymous functions as fast as any other: https://github.com/JuliaLang/julia/pull/13412 https://github.com/JuliaLang/julia/pull/13412 - Significant compiler performance improvements: https://github.com/JuliaLang/julia/pull/15300 https://github.com/JuliaLang/julia/pull/15300 https://github.com/JuliaLang/julia/pull/14543 https://github.com/JuliaLang/julia/pull/14543 https://github.com/JuliaLang/julia/pull/15609 https://github.com/JuliaLang/julia/pull/15609 - Work towards static compilation (a number of PRs): http://juliacomputing.com/blog/2016/02/09/static-julia.html http://juliacomputing.com/blog/2016/02/09/static-julia.html - Multithreading improvements: https://github.com/JuliaLang/julia/pull/15917 https://github.com/JuliaLang/julia/pull/15917 https://github.com/JuliaLang/julia/pull/15106 https://github.com/JuliaLang/julia/pull/15106 - Someone else pointed you to recent commits toward fixing the recompilation issue.

SolarNet 10y ago

Except their consensus making prevents real needed features from seeing any progress, sure they have thousands of open issues on the topic, but when did any of them last move. Oh and arguing too strongly on controversial issues (hex stringification! oh no!) gets you banned (that was a hilarious read). So how is anything supposed to move when there is a split in the community?

tavert 10y ago
You have an underinformed and incorrect understanding of what happened there. Leave it at that.
- SolarNet 10y ago
  It looks like someone got banned for submitting a PR as a hypothetical solution which a core team member disagreed with, why would I ever contribute to a project like that. Other people seem to agree on that point: http://danluu.com/julialang/ http://danluu.com/julialang/
ihnorton 10y ago
I'm not aware of any pull-requests implementing an incremental GC with pinning support, or any alternative module/namespacing scheme. Those would certainly be welcome. As I said, the people actively working on the compiler have to prioritize because time and resources are finite. This is not the same as anyone being "dead set against changing", or a "ban people for making too much noise about it". > when did any of them last move. Here's a sampling of some improvements over the past 4 months. - Debugging, everyone's priority by astronomic margins, has seen massive work and a recent preview-release (I've been using it since the announcement: rough edges, but very solid core): https://github.com/Keno/Gallium.jl/commits/master https://github.com/Keno/Gallium.jl/commits/master https://github.com/Keno/ASTInterpreter.jl/commits/master https://github.com/Keno/ASTInterpreter.jl/commits/master https://github.com/JuliaLang/julia/pull/15859 https://github.com/JuliaLang/julia/pull/15859 https://github.com/JuliaLang/julia/pull/15444 https://github.com/JuliaLang/julia/pull/15444 - Revamp of closures to make anonymous functions as fast as any other: https://github.com/JuliaLang/julia/pull/13412 https://github.com/JuliaLang/julia/pull/13412 - Significant compiler performance improvements: https://github.com/JuliaLang/julia/pull/15300 https://github.com/JuliaLang/julia/pull/15300 https://github.com/JuliaLang/julia/pull/14543 https://github.com/JuliaLang/julia/pull/14543 https://github.com/JuliaLang/julia/pull/15609 https://github.com/JuliaLang/julia/pull/15609 - Work towards static compilation (a number of PRs): http://juliacomputing.com/blog/2016/02/09/static-julia.html http://juliacomputing.com/blog/2016/02/09/static-julia.html - Multithreading improvements: https://github.com/JuliaLang/julia/pull/15917 https://github.com/JuliaLang/julia/pull/15917 https://github.com/JuliaLang/julia/pull/15106 https://github.com/JuliaLang/julia/pull/15106 - Someone else pointed you to recent commits toward fixing the recompilation issue.