DNF2

8 ms·

31.
by DNF2 3y ago
Why are you saying that? The Mojo code seems to have the same optimizations as the Julia code.
32.
by DNF2 3y ago
Are you sure the Mojo code hasn't been optimized? It seems to be hand-tuned with simd operations and multi-threading.
33.
by DNF2 3y ago
Please actually read the Mojo code. It is full of complex hand-optimized simd instructions. By comparison, the simd-optimized Julia code (especially the first version) is significantly more elegant and transparent. Impressively, the Complex
34.
by DNF2 3y ago
I'm curious about the "language instability". What kind of stability is that? Are talking about package instability, or the core language?
35.
by DNF2 3y ago
Compute power can directly influence developer hours. Developers/researchers spend a lot of time twiddling their thumbs waiting for a simulation/calculation to finish and plots to render. It directly costs time, and it also messes
36.
by DNF2 3y ago
The compiler is free and open source, not proprietary. It is built on LLVM, which is also FOSS. And Julia code is not Fortran/C/C++, not sure what you are asking.
37.
by DNF2 3y ago
I don't think this has anything to do with whether 1e-300 and 10.0^-300 is parsed differently (and perhaps that is a mistake). The poster seems to want to parse 1e-300 directly as a BigFloat in the call `BigFloat(1e-300)`, because of t
38.
by DNF2 3y ago
Yes, I got that argument, and that is exactly what I was arguing against. You cannot and should not parse the literal double `1e-300` differently dependent on which function it is later passed to. This is what `big"1e-300"` or `Bi
39.
by DNF2 3y ago
But Julia _does_ have namespaces, and you can import everything with the `import` statement, or you can retrieve only the functions you need. This is also what is generally done during package development, while dumping everything is for in
40.
by DNF2 3y ago
This is a problem for non-dispatch or singular dispatch languages, it's significantly different in the context of multiple dispatch. Namespaces are, well, not bad, but sometimes they are a solution to a problem that does not necessaril
41.
by DNF2 3y ago
The argument isn't silently treated as a double, it is explicitly and loudly treated as a double, because it is a literal double. And this is not an advantage to the designer exclusively, it is very much an advantage for the end user t
42.
by DNF2 3y ago
I actually find the string macro syntax even more convenient: `big"1e-300"`.
43.
by DNF2 3y ago
And now this comment is one of those, even though it's not actually based on trying out the new release.
44.
by DNF2 3y ago
How do you figure that, when the CFD software is already built and available, and the premise in the question is that that the asker is already in a position to start using it? It's pretty clear that the background of the asker is alig
45.
by DNF2 3y ago
Indeed there are no special operators, :. and ==: etc. They are just :, . and == And macro definition code looks quite different from 'regular' code since it works so much with expressions and symbols.
46.
by DNF2 3y ago
I would guess the majority of users never write a single line of macro definitions or expression evaluation.
47.
by DNF2 3y ago
Is building and testing an actual propeller going to be easier? I would have thought that setting up and running a simulation could be done in a moderate amount of hours, and could then be quickly iterated on. The only requirements are a la
48.
by DNF2 3y ago
After clicking trough to the repository, I found this part a bit perplexing: "running on a GPU requires initializing the Simulation memory on the GPU, and care needs to be taken to move the data back to the CPU for visualization."
49.
by DNF2 3y ago
> Also this is the first time I saw examples of Julia code and the syntax looks worse than C++. For someone who writes both Julia and C++, the above comment comes across as an obscene joke. Possibly, you object to the programming style i
50.
by DNF2 3y ago
So you gave up the language after someone gave you a flat out wrong answer to a single question? That's too bad.
51.
by DNF2 4y ago
Just to manage expectations: As far as I understand, v1.9 doesn't by itself solve TTFP/precompilation. The tweet seems slightly over-enthusiastic. But it puts tools to solve it in the hands of package developers. In that sense,
52.
by DNF2 4y ago
I know no one who uses Matlab for the uses you mention. Basically everyone is using it for algorithm development, that includes both students and companies. And the way I understand it, algorithm development/prototyping also its core a
53.
by DNF2 4y ago
> In that regard, Julia code reads like someone’s manuscript about the issue and not a program written by a programmer. To you, that’s desired. To me, that’s my actual worst nightmare That's a pretty dubious attribution of intention
54.
by DNF2 4y ago
> I don't stay plugged in beyond reading the changelog whenever a new version comes out ... > I've also noticed a distinct and crucial lack of long-term vision for Julia from the co-founders. Don't you find those two st
55.
by DNF2 4y ago
In Julia you can go low-level, but there is no requirement. You can write purely high-level, generic, untyped code, with good performance. So I'm a bit reluctant to accept the claim that it's lower level. What are the things whe
56.
by DNF2 4y ago
Maybe it's all floats in R, but in Julia, `return 500` means an Int is returned. But it's really hard to determine whether the Julia code is unstable based only on the R code.
57.
by DNF2 4y ago
The dispatch is based on the "runtime type", but that does not necessarily "happen at runtime", because the runtime/dynamic type can often be determined statically.
58.
by DNF2 4y ago
I'm not that good at reading R. But if the Julia code is similar, then this code is type unstable, sometimes returning an Int, sometimes a Float. That harms performance. Generally, it looks like a function where Julia could have a sign
59.
by DNF2 4y ago
Of course, this is piques one's curiosity. It might be, if the function is simple enough, that there is little advantage to Julia here. But if you are combining multiple operations on a vector, there could be opportunities for Julia, i
60.
by DNF2 4y ago
There's another issue. In addition to the open source license and what it promises, when you accept contributions from others it isn't just your work anymore. LightGraphs had 100 contributors, what about their efforts? Not to ment

More ›