The 2025 Annual Julia User & Developer Survey is now live. Please: 1) click here to complete the survey; 2) send the link (Julia Developer Survey 2025) to friends and colleagues who use Julia and ask them to complete the survey; 3) share and post wherever Julia users and developers may be found; 4) encourage other Julia users and developers to do all of the above. Your response is anonymous. We have removed some survey questions this year to make the survey a bit shorter, faster and easier to complete. Survey results will be presented at JuliaCon and available online after JuliaCon. This annual survey provides information to the Julia community and the public about who is using Julia, how Julia is being used, areas for improvement and how this is changing over time. Thank you!
I still find few things odd.. like the division of TECHNICAL vs NON-TECHNICAL aspects.. why “Open source - code is available and can be modified” is technical and “MIT license” is NON-TECHNICAL ??
No in-language or built-in support for mutable, fixed size arrays
Is this still relevant? Memory has been a thing since 1.11 now.
Do you accept comments? Q15: typo in Github Copilog
Thanks!
While we’re at it, can we find the results of the 2024 survey somewhere on the internet?
https://www.youtube.com/watch?v=qru5G5Yp77E The presentation of survey results starts around 3 hrs 14 mins.
I remember that they were presented at JuliaCon, but presumably the PDF with the slides exists? It is definitely a more practical format
I can’t upload pptx or pdf here. You can send me an email at andrew.claster@juliahub.com and I will send it to you.
Thank you! We will get this fixed.
Thank you! I will make a note of this and we can address it in next year’s survey.
Thank you! I will make a note so we can address this in next year’s survey.
I’m getting 403 errors for the survey link.
Does this work: Julia Developer Survey 2025
It is working for me.
No, I also get a page where it’s only written 403, literally
Could you please open a PR to add the PDF to www.julialang.org/_assets at main · JuliaLang/www.julialang.org · GitHub? I’m happy to open the PR for you if you email me the PDF, I think you already have my contact. I recently need to refer to the results of the survey but had to refer to the 2023 one because the 2024 one was nowhere to be found.
The 2024 results are now uploaded.
I am linking the original post for people who did not see it yet.
I think that entry is too vague because while Memory fits the bill in Julia and other contexts, “mutable” has different meanings elsewhere that could suggest something like a stack-allocated C array. We have SVectors and Accessors to sort of do that, but those aren’t builtin.