# lhe/Biofast benchmark | FASTQ parsing \[Julia,Nim,Crystal,Python,...\]

**URL:** <https://discourse.julialang.org/t/lhe-biofast-benchmark-fastq-parsing-julia-nim-crystal-python/39747>\
**Category:** Biology, Health, and Medicine\
**Tags:** performance, benchmark, community, biology\
**Created:** [May 19, 2020, 11:16am UTC](https://discourse.julialang.org/t/lhe-biofast-benchmark-fastq-parsing-julia-nim-crystal-python/39747 "2020-05-19T11:16:23Z")\
**Posts on this page:** 1\
**Showing post:** 56

<div class="post-metadata">

**Author:** ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)\
**Post date:** [May 25, 2020, 8:17pm UTC](https://discourse.julialang.org/t/lhe-biofast-benchmark-fastq-parsing-julia-nim-crystal-python/39747/56 "2020-05-25T20:17:43Z")

</div>

Okay, here is one of @StefanKarpinski’s good comments on the matter. If you search the Julia Discourse, you can also find many other good comments by Stefan on this matter.

> [@1.0 adoption path?](https://discourse.julialang.org/t/1-0-adoption-path/7922/39):
>
> The big issue was upgrade deadlock. Instead of making it possible for packages to support both Python 2 and 3 at the same time, the Python devs provided the [2to3 tool](https://docs.python.org/3/library/2to3.html), hoping that the entire ecosystem would upgrade from Python 2 to 3 all at once. But upgrade effort turned out not to be what stymied the transition. Packages still needed to support Python 2 because most of their users were still using it. And since most packages stayed on Python 2, users did as well – if anything they depended on…

---

_[View the full topic](https://discourse.julialang.org/t/lhe-biofast-benchmark-fastq-parsing-julia-nim-crystal-python/39747)._