DNF2

22 ms·

121.
by DNF2 5y ago
But this is what most languages do, except they have _singular_ dispatch. Every OOP language has different behaviour for different input types, except it only works for the _first_ input argument. Julia simply extends this to every argument
122.
by DNF2 5y ago
In mathematically oriented code, long variable names make code less readable, not more . Mathematical expressions become long and difficult to parse, and the variables often have no intrinsic meaning, so trying to make up 'meaningfu
123.
by DNF2 5y ago
It think that the discussions on HN tend to be quite combative, and members of the Julia community (including myself) can get a bit worked up over negative claims that we find overly sweeping. That could lead to some dismissiveness. I do ge
124.
by DNF2 5y ago
I wonder where you got the impression that latency and precompilation performance are not valid concerns. This has been the _main_ focus area for the devs for a long time. It's pretty much all anyone has been talking about for over a y
125.
by DNF2 5y ago
Perhaps. It is possible that a community just cannot handle an extremely high level of social and communication skills. It becomes too much for them. The same thing can happen to politicians too; some of them are just so gifted, well-inform
126.
by DNF2 5y ago
The two-language problem is not concerned with calling out to or wrapping pre-existing libraries in a second language. It means having to write parts of your code in a second language, due to, for example, performance reasons.
127.
by DNF2 5y ago
So then that 'weakness' in python is not an issue to you personally, because you fluently drop down to a fast language anytime you need to, with no particular loss in productivity? Keep in mind though, that this could be a hurdle
128.
by DNF2 5y ago
I beg your pardon? Knowing that Python is slow is a strength of Python? Then, if Python suddenly became fast, it would be a negative? Did I misunderstand something? Presumably, all fast languages are at a disadvantage, then.
129.
by DNF2 6y ago
Not just floats, and I'm not sure they have to be that small. All sorts of structs containing bitstypes/value types can be stack allocated. In fact, even some structs with pointers to heap-allocated memory can be stack-allocated (
130.
by DNF2 6y ago
This is a Windows issue, I'm pretty sure. My solution is easy, install Julia under WSL. In fact, after moving from MacOS to Windows, this is my goto solution: install as much as I can under WSL. Problem disappeared.
131.
by DNF2 6y ago
This depends on what you mean by '(un)optimized code'. Because there's a difference between unoptimized and naive code. 'Unoptimized' code should still observe most of the performance tips in the manual (such as avo
132.
by DNF2 6y ago
I don't have a strong opinion on this, one way or the other. It's less verbose (which I like), and more familiar to those used to dynamic languages like python, matlab, etc. But this isn't my decision, I'm ok with either
133.
by DNF2 6y ago
I have no particular opinion on the teaching materials, I just use the manual and the discussion fora, so I don't know. But if a third party offers teaching materials, it's not so strange if it resides on their third party website
134.
by DNF2 6y ago
I simply do not understand how some people are able to form so strong opinions in such a short time, and spew out disdain and negativity on the most flimsy basis. It's a matter of temperament, I guess. Julia performance should be on pa
135.
by DNF2 6y ago
This is just a disagreement over basic design: should variable declarations be explicit or not. It is a choice, and something that reasonable people can disagree on. Framing this as a case of irrational and illogical behaviour is unnecessar
136.
by DNF2 6y ago
When do you run into this kind of problem? Is it possible that you are over-typing your function signatures? The generally recommended style is to write generic code with loose type restrictions, or even none at all.
137.
by DNF2 6y ago
No, this is incorrect, you are confusing backwards and forwards compatibility. Running your new code on old Julia versions could break immediately , just like in every programming language. Backwards and forwards compatibility have very di
138.
by DNF2 6y ago
Well, a lot of resources have been put into reducing compilation times, and large improvements have been achieved. It's not just perennially 'around the corner', the improvements are tangible and happening right now .
139.
by DNF2 6y ago
But this is really the worst conceivable use case for Julia. Why are you interested in making this change, when Julia offers no advantage in this scenario?
140.
by DNF2 6y ago
If it were 20 seconds for every plot, this would be a major problem for me, as I tend to make lots of plots. But it's only the first plot where this is an issue. Surely you're not in 'the zone' that soon? Seems to
141.
by DNF2 6y ago
I cannot fathom how ttfp is important. It's time to first plot, not to every plot. After it's down to ~10 seconds, why on earth does anyone care?
142.
by DNF2 6y ago
No one interested in interfaces? My impression is that interfaces is very commonly discussed, and is one of the most anticipated features in the language, though it may not come until v2.0.
143.
by DNF2 6y ago
I submitted an issue that gives a further >4x speedup with just simple straightforward code (no simd, fastmath or threads). It's important to make everything a view, and to remember the dots in the right places, otherwise this is qu
144.
by DNF2 6y ago
Yes it does. There are still issues with benchmarking in global scope, though, which is why it is better to use BenchmarkTools.jl
145.
by DNF2 6y ago
I had the impression that the inputs were one 2D and one 3D array. Are they both complex? Also it seems like they did not have the same sizes, as well as dimensionalities.
146.
by DNF2 6y ago
I commented on this, right next to your question: "Well, view could speed up code, but it also had some overhead, so creating lots of views came with a cost that would sometimes outweigh the benefit." So yes, there was indeed per
147.
by DNF2 6y ago
Well, view could speed up code, but it also had some overhead, so creating lots of views came with a cost that would sometimes outweigh the benefit. But, yeah, version info would be interesting.
148.
by DNF2 6y ago
That's good. I still cannot see the repository, though. I may be looking in the wrong place. It's no problem being new to a language, I just found the conclusions as bit too 'conclusive', so to speak, in that case. Views
149.
by DNF2 6y ago
That Julia benchmark is really quite unfortunate: 1. It treats all arrays as row-major, while Julia arrays are column major. That is pretty unfair. 2. It creates lots of unnecessary copies, as slices in Julia does not return views (but you
150.
by DNF2 6y ago
All right! I got the impression you were contrasting that particular post with the rest of this discussion, but apparently not. Still slightly confused here. Oh well, carry on.

More ›