totalperspectiv

This is super cool ... are there any more detailed docs on it? It sounds like it's borrowing a bit from Rust's ownership model?

Replace the word fan with supporter, which is more in line what what I was thinking, and is certainly needed in programming.

I feel like it might, if it replaced pip and gets full endorsement from the python org. It's a fantastic project, but untill it has complete backing it's just a technical risk to include in a project.

Huge fan of poetry. I highly recommend people try it out. It feels like cargo, but for python.

'Great Thoughts Friday' from Richard Hamming

https://youtu.be/a1zDuOPkMSw

Did you make a username 'smug forgetting smug' just to make this comment? For your next throwaway can I recommend: smgfgttgs 'smug forgetting thugs'?

Coming from other languages I always thought of Errors as something 'other' that just kind of magically work within their own little exceptions code path. So in Rust I was expecting errors to be similarly complex and 'other'.

I had a major aha moment recently when reading something that described errors as just types. When put that way it suddenly made so much more sense to me.

I've been using it as a way to learn some of the fundamentals of my field and write packages from other languages in Rust as a learning exercise. Then once those reach some level of usability / goodness, I've started building small CLI's for $work.

I have a feeling that inside of 5 years Rust will be blowing up on the job market. It's just so good and so practical that once you pick it up, anything less well designed will feel like a kludge and hack that might blow up on you at any point.

Here is a link to the discussion on Reddit a while back: https://www.reddit.com/r/perl/comments/dq1lzy/the_perl_maste...

It's worth reading. What I think it is is a power / money grab by a small group inside Perl. It's not reflective of the goals or desires of the wider Perl community. Or at least those goals and desires would not be presented in this way.

That's a fantastic SO answer.

What exactly is it about Fortran that makes it better for an HPC env and numeric computing than c++? Or is it more just an available libs/history question?

Not directly related to the article, but given a green field, what project qualities would lead one to choose Fortran as a tool to solve the problem over anything else?

Kind of cheating because Kernighan literally labels it as beautiful. It's Rob Pike's implementation of Ken Thomson's regex matcher.

https://www.cs.princeton.edu/courses/archive/spr09/cos333/be...

Excellent maps, thanks for sharing, commenting so I can find this again.

While not always considered a hobby, I think social groups are forming around group exercise more often now. It's healthy, you get a little shared suffering in, and you meet a whole cross section of your community you may not meet otherwise.

Is his name L Bob Rife?

I'm hoping someone with more experience will chime in, but what about rpython / pypy?

As an aside, what is Mike Pall working on these days?

This is super cool. I would like to seem some performance benchmarks to see if it still holds the speed of LuaJit.

Were they okay with it once you explained what was so funny?

What I can't reconcile with myself is, if I'm going to add type hinting in Python, why not use a language where my efforts of adding type hints result in performance gains? I get why it's nice for a team, but it seems like a lot of work for half the potential benefit of a typed language.

I totally agree on this. Having read papers and tried to implement, or even re-implement the same algorithm, even when their source code is available, it's hard to get results that match.

I'm not a hard core TDD guy, but sometimes a few tests go a long way to making your code reproducible...or even just working correctly.

I would love to see a newer version of Julia in there to see if they've fixed some of the problem areas.

That's exactly how I found it as well. Brent has some really high quality bioinformatics libraries written in Nim, and supports them well.

I can confirm, the book is excellent and worth a read-through.

Isn't this just a version of a cache oblivious algorithm, using van emde boas ordering to make maximal usage of bytes per pull into the cache? Or is there more to it that I'm not seeing?

Good link to a similar discussion: An Introduction to Cache-Oblivious Data Structures - https://news.ycombinator.com/item?id=16317613

The trick meaning to be non-industry specific?

That book also totally changed how I read for the better.

I tend to have two books going at a time. One I read seriously, usually in the morning and take notes etc. The other is purely entertainment band is usually an evening or weekend mornings book.

To answer both my own questions. Rust does not seem to have this same problem: https://godbolt.org/z/JpwcRN

But iterating over the loop with .iter_mut is different than iterating over 0..v.len(), which is interesting.

rustc also doesn't vectorize it?