agbell

When the typical economist tells me about his latest research, my standard reaction is 'Eh, maybe.' Then I forget about it. When Robin Hanson tells me about his latest research, my standard reaction is 'No way! Impossible!' Then I think about it for years - Bryan Caplan

This. Also try contacting a lawyer who knows this area and asking to pay for a legal opinion brief so that you can post it online to be debated by legions of software developers.

Lawyers I know would politely decline that.

For those want to learn Elm, or to learn strongly typed functional programming in very well thought out order @rtfeldman's book "Elm In Action" is super good.

His experience working at a teaching company made his book very well structured for new comers.

This book was ahead of its time. Millionaires who live like college kids. Overworked and stressed out devs working for a faceless corporation. I read it a long time ago, but I recall it was super good.

Yeah, functions returning types based on computations in Zig can look a lot like Idris if you squint

I know very little Zig, but I agree with the post, that comptime seems simple, obvious and powerful.

It is interesting that it bears some surface level similarities to type constructors in languages with higher kinded types.

Thanks!

Thanks for reading. Interesting idea! I did have this thought myself at some point and went and checked on some other narrated podcasts and found they kept it all under one label, but I can see how that could be confusing. Maybe I'll try that for the next one.

Thanks for listening and thanks for supporting me!

Yeah, the further you go back into the back catalog the more you are listening to my learning-to-podcast phase. Hopefully they aren't too bad... I am a slow but persistent learner.

Podcast host here. Andrew Kelly, creator of Zig shares the back story behind the creation of Zig: Why he created it, how he created it, leaving his job to work on it full time and why he is confident he can build a language that is better and more popular than C. Let me know what you think of the episode.

Podcast host here. Andrew Kelly, creator of Zig shares the back story behind the creation of Zig: Why he created it, how he created it, leaving his job to work on it full time and why he is confident he can build a language that is better and more popular than C. Let me know what you think of the episode.

Oh, I've not seen ranger before. Looks pretty useful.

Are you a bot?

Hi, Interviewer here! Thanks for sharing!

Brian is super modest and claims to be a horrible programmer but he is comparing himself to Ken Thompson, who he thinks is just incredible.

One thing that was interesting to me about Unix at Bell Labs was the UNIX room. It was a shared room with the computer in it but also where the coffee machine was and where they would hang out. I'm not sure if we are missing something like this with our increasingly remote culture?

Very cool! I use zoxide as a alias for cd to do this. But it only really works if you have cded using the full path in the past. But usually I have.

Author here, thanks for reading. I totally agree that non-determinism is tricky. The big thing that got me to try McFly was the suggestions are path specific. I hear fish shell has this feature built in, but I havn't tried it out.

I may be unique in this regard but the types of actions I do in one path are very different from those I do in others: working on my blog is very different from the types of things I do when working on code and it was nice to have history aware of this.

I haven't actually used McFly a lot though, so I haven't quite seen if it going to become a permanent thing for me. The UI of using FZF for history is nicer, I just didn't like the suggested matches.

You are right though, I don't have my arrow keys setup like this. I'll try that out as well. Thanks for the tip!

Author here. Thanks for sharing!

Have you seen gron[1]? It can't do everything that jq can, but it is much more in the unix philosophy than jq. It simply flattens and unflattens json out into lines so you can use standard unix tools on it.

   ▶ gron 
   "https://api.github.com/repos/tomnomnom/gron/commits?per_page=1" | fgrep "commit.author"
   json[0].commit.author = {};
   json[0].commit.author.date = "2016-07-02T10:51:21Z";
   json[0].commit.author.email = "mail@tomnomnom.com";
   json[0].commit.author.name = "Tom Hudson";

    ▶ gron "https://api.github.com/repos/tomnomnom/gron/commits? 
   per_page=1" | fgrep "commit.author" | gron --ungron
    [
      {
        "commit": {
          "author": {
            "date": "2016-07-02T10:51:21Z",
            "email": "mail@tomnomnom.com",
            "name": "Tom Hudson"
          }
        }
      }
    ]

Thanks for reading the article. broot does more than just piping tree to less, it gives you a TUI version of tree that you can navigate along around it. The fuzzy finder in it works like FZF but it keeps everything in a nice compact tree view. It might be overkill but I like it.

That is great! I think there is a lot of room for innovation with dual use keys like this.

I'm sure the answer is you need to check, but would the cost of checking if you can gallop hurt performance in other cases.

I'm wondering if this removing the branch idea and the galloping idea can coexist.

Would this benefit from the galloping optimization Tim Peter's was talking about on Hn recently?

If one side is bigger than the other, try to find how many elements you can add from that side and advance that far.

I'd like to more about this. Can I use this?

I love this. One suggestion, instead of dedicated keys for ctrl, option and other modifier keys you can use 'permissive hold' in QMK to put modifier keys in your home row.

Hold down F or J for F Lock, D or K for Ctrl and so on. My fingers adjusted to it really fast. Your keys can act as modifiers when held, and normal keys when pressed and it is works super well.

https://beta.docs.qmk.fm/using-qmk/software-features/tap_hol...

Yeah, good point. I think you are right about it being incorrect. Updating...

You can check it, but I'm pretty sure the difference is negligible. But yeah, all benchmarks are using the code in perf and the pop code is just to demonstrate. It is not benched.

Edit: dropping the extra list() from the blog code examples.

TimSort is cool. In it's worst case it looks no better than merge sort, but give it some partially order data, or small amounts of data, where it uses insertion sort, and it really shines.

Here is a small monorepo example. We build a DAG of dependencies between parts of the monorepo and only rebuild what is needed.

This is different but similar to what Bazel does.

Cyber noir is subgenre that combines elements of noir and cyberpunk.

Isn't cyber punk supposed to be film noir set in a high tech future? So we just increasing the amount of film noir to get Cyber Noir?

So Jeff VanderMeer makes video games now?

This is very creepy.

Makes sense. Kafka is Apache, confluent platform is open core. So I agree the post is a bit confused about that. We can update it and link in the PR. No intention to misrepresent the facts on our parts, just a small team trying to build stuff.