totalperspectiv

Has there been any announced timeline on Go2?

Zipapp doesn't support c extensions though? And that is a large chunk of libraries that I use.

I think that at this point all the ceremony around setting up and deploying a python project outweighs it's 'easy to read and use' aspects. Unless there is a library you can't live without or rewrite, it seems like a language with better tooling and real benefits of a type system is a better choice.

If you're mainstream: Go or Java. If you're edgy: Nim, Scala, or Crystal

All of those have much more sane type, build, and packaging systems.

@perl-people, was this a solved problem when Perl was big? Or is python walking the same roads?

Someone has a PR merged already for Go. The benchmark numbers need updating

Speaking as an Nof1, if you were to do an early access release like Manning does with their MEAP books, I would go for that.

Will the ebook be released before the physical version? This is EXACTLY the book on Scala I've wanted and am so excited to see this coming!

As one of those new people boosting recent numbers, Scala is great! I use vscode with Metals and had no jvm experience before. sbt is annoying, Mill seems super promising, and graalvm native images basically mean that if I was going to do it in python, I might as well use scala now.

Very excited to see gc:arc make it into stable.

Hitchhikers Guide to the Galaxy - Adams Discworld series - Pratchett Foundation - Asimov American Gods - Gaiman Snow Crash - Stephenson Next - Crichton 1984 - Orwell

The premise of the article is about incorrectness in a language. So while I agree that most bugs are likely caused by the developer and not the language they are using, I think my comment makes sense in reference to the main post.

> And so if what you're craving is absolute precision and maximal avoidance of errors or incorrect behavior

If you are being paid to develop software, doing anything other than aiming for absolute correctness seems negligent, at best.

I think this is part of what leads to obsession with Rust. We build so many things on a daily basis with a long long list of 'it depends'. But Rust aims to make you write something as correctly as possible, and provides a really solid base for you to do this. So that list of 'it depends' shrinks drastically and you feel superhuman for building something so solid.

My main takeaway is the quote from scottlamb:

> ... these sorts of statements contribute to my belief that Go is an opinionated language that I should hesitate to choose for anything that the language's authors haven't specifically considered in depth.

Very nice write up. I liked the point that Result and Option types would fit nicely into Go and totally agree. Now that I've used rust, languages without Result / Option / match expressions feel weak and dangerous.

Perl5. Some version of perl5 is available by default on just about everything and can be counted on in a similar manner as counting on awk to be there for you.

I'm not going to defend Perl's readability, there are many opus's online in both directions. Suffice it to say that Perl is still a really good tool for certain $jobs.

For learning Perl, I used this: https://qntm.org/perl_en followed by some trial and error, followed by the book Modern Perl, then Higher Order Perl. glhf! Perl hacking is a blast

Yes. And No. I don't think recruiters look at github. Hiring managers might though, once your resume lands on their desk. So a project like this may not make you more discoverable, but it may make you more hireable once you've been discovered. Given that you have 20 years of experience though, it likely won't add a whole lot. And any questions that they ask you would likely be better answered by talking about real work experience rather than a toy project.

But it won't hurt :)

A thing that might be more productive would be to see what some of the core tech some jobs you are looking at use, and then re-implement that from scratch. You learn a lot, you can post that kind of stuff here and elsewhere and maybe be discoverable, and you can talk about it during an interview in a way that promotes you as an expert on something.

TinyGo recently became an official project and seems extremely successful.

This describes my process as well. I'd add that one of the huge benefits of the 1st pass is that it is low pressure. You just have to get through the material.

For example, I put off SICP for a very long time due to not wanting to put in the time for the exercises. Eventually I just decided to take a first pass, and made I through in a month. Second pass did the exercises.

I've always found Julia a little lacking for bioinformatics, but I'm not doing ML. I have very high hopes for Nim, which I think has better performance potential than Julia across domains and can produce binaries.

I'm very excited for this to go live.

Yeah, this is basically the boat I'm in. Python dominates. You either write it in Python, or maybe get away with writing it in something else and then wrapping it in Python.

I don't mind Python, but now that I've gotten a taste of ADT's and non-nullable types, writing Python feels like a kludge.

Check out this: https://github.com/frol/completely-unscientific-benchmarks

At this point I would not be sad if I was forced to use C# for some reason.

I hadn't seen Beef before. Is it 'as fast as C'? The docs look nice.

I'm curious how this differentiates from Nim other than the builtin types for bfx stuff. Still cool either way and great to see something else joining this space.

I wonder if there is a measurable difference between software written in a very basic text editor vs an IDE. Differences like naming conventions, name length, number of files etc. I've always thought that an IDE, while wildly useful in some scenarios, pushes/allows for unnecessarily complex design choices.

Or maybe I'm just trying to justify why I use vim...

1) yes: https://docs.scala-lang.org/overviews/repl/overview.html 2) yes: https://almond.sh/, there are other options as well 3) The compile times don't bother me. I just set up sbt to watch for files saves and run tests. I'd say the dev cycle is faster than python due to compile time type checking.

It's not the same as Python or R, you are right. There is complexity, but it's rewarding once you get past the initial curve. I felt similarity regarding the JVM, but again, it's not that bad. Plus with GraalVM you can compile binaries, which I love for so many reasons.

And Scala. The poster child of oop + functional

It's not on the same level as the R Python ecosystem, but you should check out Scala. It has the power and flexibility, but also a fairly solid backbone of data science libs.

As a torrent newb, what's the tldr on on why webtorrent over BitTorrent?

Is there a reason C libraries generally prefix with 'lib'? Or is it just historic?