kescobo

7 ms·

1.
by kescobo 3y ago
>To disagree, I'm a computational biologist and it's my firm belief 99% of the scientifically important stuff happens before the stats and plotting. I'm a microbiologist too, but the kind that uses mostly off-the-shelf too
2.
by kescobo 3y ago
>TL;DR: wrote a benchmark article without...running it? He benchmarks against the rust implementation, which, unless benchmarks have zero meaning, should be sufficient to get a general sense of the scale of the difference. The post is ob
3.
by kescobo 3y ago
Someone knowledgeable enough about movies can read a script and know of it's good or not without needing to see it actually produced. Here, it's possible to read the code and know what the program does sufficient to critique it fo
4.
by kescobo 3y ago
>However, in my opinion, this lack of validation (really, lack of parsing in any meaningful sense) means that the performance between this parser and Needletail is incomparable. So what exactly does it demonstrate? You get to claim your
5.
by kescobo 3y ago
Calling julia code from python or python code from julia is relatively straightforward. I haven't spent much time doing the former, but love the ergonomics of the later with PythonCall.jl and CondaPkg.jl to manage python dependencies.
6.
by kescobo 5y ago
It really depends on what you do - sometimes offsets are better, sometimes an index is better. If you really want 0-based indexing, you can have it! https://github.com/JuliaArrays/OffsetArrays.jl My own preference is r
7.
by kescobo 5y ago
>Julia does solve the two language issue, but not in all situations And not instantaneously. Developer time being finite, using what works from existing libraries while waiting for a pure-julia implementation seems like an excellent solu
8.
by kescobo 6y ago
Who am I to say what hills are worth dying on? But I don't want you to die at all - in case you're ever compelled to switch, I can't help you with end, but OffsetArrays.jl can help with your indexing woes, and I think there a
9.
by kescobo 6y ago
> If you take a functional approach, especially using pipes, dplyr and a split, apply, combine style, it is quite beautiful Sure, but what if you don't? Sometimes, this is the right way to do things, other times there are other appr
10.
by kescobo 6y ago
Out of curiosity, when was the last time you looked at DataFrames.jl? A huge amount has happened in the last year. Plus, if you want more tidy-like syntax, you can go with Query.jl, (or DataFramesMeta.jl, though that isn't quite finish
11.
by kescobo 6y ago
Style guide for the base language is to generally stick to ascii, and many of the big packages do that too. It's really nice in examples, analysis scripts and the like though.
12.
by kescobo 7y ago
% of the repos in the org on github? That number is lower than I'd like. % of the repos that are actively maintained? Much higher. One of the great things about julia is that it's really easy to throw together a package and regist
13.
by kescobo 8y ago
Depending on which plotting package you use. Plots.jl itself is pretty slow to get started still, though there are ideas on how to improve that. That said, once you're up and running, plots (and everything else) are super snappy. When