TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

New horizons for Julia

217 点作者 leephillips3 个月前

11 条评论

affinepplan3 个月前
I know I know I know that this same refrain has probably been said nonstop since Julia&#x27;s first day after launch, but the language really is getting noticeably better every single release. Each of the releases I&#x27;ve been around for (so 1.8-1.11, and now on nightly, 1.12) is adding meaningful new features, performance improvements, and addressing many of the oldest and sharpest pain points<p>the `--trim` feature coming in 1.12 will still be considered experimental, and if I had to take a guess won&#x27;t be considered &quot;stable&quot; until 1.14 or so, but I&#x27;m really excited to see it picked up around the ecosystem!
评论 #43120176 未加载
评论 #43120066 未加载
catgary3 个月前
I’m kind of sad, because I think I have completed the journey from advocating for Julia at my first job to becoming a full-blown hater. I have complaints about the type system and the general failure of a good autograd library to emerge as the standard&#x2F;default.<p>But my main complaint about Julia is its general approach to memory management. You are encouraged to think about how memory is being allocated e.g. by using StaticArrays for smaller, immutable arrays, or pre-allocating the arrays and operating on them in-place. But you don’t actually have control over allocations, and it’s easy for some type instability to cause unnecessary allocations - even after you stick a bunch of type annotations which should give the compiler sufficient information to force type stability or at least crash&#x2F;fail to type check.<p>At this point I think people are better off investing their time&#x2F;efforts into Rust for computationally heavy workloads on the CPU (polars for data frame stuff, ndarray for numpy functionality, Enzyme for autodiff) and using torch&#x2F;jax for GPU-centric work (also, it’s significantly easier to write python bindings for rust libraries than C++ or Julia libs).
评论 #43122401 未加载
评论 #43124015 未加载
评论 #43121233 未加载
cardanome3 个月前
Small static binaries could be an killer-feature for Julia.<p>While I always had an eye on Julia and it is a lovely language, especially the multiply dispatch and general lispy-ness in spirit, I never really had a good use case for it.<p>Python always was the better choice due to the stronger ecosystem and faster launch time. Rarely did I need the extra performance Julia offered. But Python is annoying to deploy so Julia starts to seem tempting, at least for smaller projects where you don&#x27;t want to do a complex docker setup.<p>Julia is for sure prioritizing the right things.
评论 #43125007 未加载
currymj3 个月前
The article describes Julia as &quot;a general-purpose programming language aimed at science, engineering, and related arenas of technical computing&quot;.<p>I think this is about right. If you are going to solve differential equations or run some numerical weather codes or solve an integer program or simulate an electrical circuit, it would be a good idea to consider Julia rather than reaching for Fortran, C++, or MATLAB. It is a much nicer language and still very fast.<p>My experience is that people who want to use Julia for data science and especially for deep learning, usually find that you can get the job done, but often it&#x27;s easier to use PyTorch or Jax and just accept the limitations of Python.
评论 #43136153 未加载
jarbus3 个月前
Julia is still such an absolute joy to use. I have a dream that somehow, Torch.jl, which attempts to provide a julia interface to pytorch, will magically take off. Python is ok, but julia is just so fast, fun, and easy to scale.
评论 #43153029 未加载
systems3 个月前
Julia is not a scripting language, or in other word, Julia scoping rule are not scripting friendly<p>currently if in a file i have<p><pre><code> local s = 0 for i = 1:10 t = s + i s = t println(&quot;$s&quot;) end println(&quot;$s&quot;) </code></pre> and I execute this file, I will get an error<p><pre><code> ERROR: LoadError: UndefVarError: s not defined</code></pre>
评论 #43120355 未加载
评论 #43120420 未加载
评论 #43124425 未加载
blindseer3 个月前
I&#x27;m happy to see static compilation in the works! If static compilation takes off, and people are able to build Python packages that are secretly just compiled Julia code, I can see a world where more people opt to using Julia over C or C++. Though writing Rust libraries that work as Python packages is a joy and Julia would still have competition.<p>Julia biggest problem at the moment is growth. Julia has suffered from not having exponential growth, and has either maintained a small linear growth or has fallen in popularity. Search online on YouTube for tutorials, on Twitch for WatchPeopleCode, or on GitHub for benchmarks; and Julia is not even in the room where the conversation is happening - there just isn&#x27;t any mindshare.<p>And for good reason. There are so many ergonomic challenges when using Julia in a large codebase and in a large team. Julia has no formal interfaces, LSP suggestions that are often just wrong, and no option types. This just makes writing Julia code a drag. And it makes it quite difficult to advocate to developers experienced with languages that offer these features.<p>Additionally, the core conceit pushed by Julia advocates is that the language is fast. This is true in controlled benchmarks but in real-world scenarios and in practice it is a real pain to write and maintain code that is fast for high velocity teams because it requires a lot of discipline and a strong understanding of memory allocation and assumptions the Julia can and cannot make. You can write code that is blazingly fast, and then you make a change somewhere else in your program and suddenly your code crawls to a halt. We&#x27;ve had test code that goes from taking 10 minutes to run to over 2 hours because of type instability in a single line of code. Finding this was non-trivial. For reference, if this were uncaught our production version would have gone from 8 hours to 4 days.<p>The lack of growth really hurts the language. Search for pretty much any topic under the sun and you&#x27;ll find a Python package and possibly even a Rust crate. In Julia you are usually writing one from scratch. Packages are essential to data processing are contributor strained. If you have a somewhat unpopular open source code code you rely on that doesn&#x27;t work quite work the way you want it to, you might think I&#x27;ll just submit a PR but it can languish for months to a year.<p>The Julia community needs to look at what programming languages are offering that Julia developers want and will benefit from. The software world changing very quickly and Julia needs to change too to keep up.
评论 #43122676 未加载
评论 #43125465 未加载
dleather3 个月前
I prefer to code in Julia almost always. It really is such a wonderful experience. Now if only I could land an industry job with my Julia skills...
jshen3 个月前
I really like the direction of Julia and its managing of trade-offs. I hope it gains more traction.
LeroyRaz3 个月前
How does Julia compare to Python with Jax?<p>I just love pythons ease of use, and the few times I&#x27;ve tried Julia it has felt clanky in comparison, and then Jax just makes everything so amazingly fast.
评论 #43120890 未加载
评论 #43121831 未加载
评论 #43121119 未加载
acmj3 个月前
&gt; <i>The next major Julia release, 1.12, is likely to appear in mid-2025. It will finally include the ability to generate static binaries of a reasonable size, appropriate for distribution.</i><p>I would be thrilled if Julia had this in early days, but now it is a little too late. I have jumped the boat.
评论 #43124671 未加载
评论 #43121523 未加载