i don't understand the point of this criticism - i swear people just post it because they don't know what the thing is and they feel they need to compulsively comment anyway.
no one stumbles on this repo by accident (jeremy didn't post it here). the only way you find it is you google "mlir tutorial" ie you know what MLIR is and you're actively explicitly looking for a tut. there is no situation where you're ambushed by this content.
like if i write a tutorial "integration by parts for beginners" but don't define integration are you gonna claim that it fails at being for beginners? does every title from now on need to explicitly have "... for beginners who know what this is and have already made the decision to start studying".
It's funny, I agree with both of you. Considering this repo was posted to this site and prompted thousands of people to stumble on it by accident, even a link in the README on the words "MLIR framework" would go a long way. I, as someone who is both super interested in applied FHE and subscribed to this guy's blog, almost skipped this post because I didn't realize it was about FHE, and I am probably in the target audience for it.
> Considering this repo was posted to this site and prompted thousands of people to stumble on it by accident
but the guy himself didn't post it. how are people so entitled that they're upset about a deficiency in a thing that they sought out. no one is making you go the repo (or asking you to go).
it's literally like complaining about free samples at costco - if you don't like what they have don't take one!
Taking the time out to post to complain that there's no info in a README is definitely not something I might choose to do, but if multiple people did it for my project, I might consider reflecting on the feedback and altering one line of README text to lower the friction of people checking out my project.
The Costco example is perfect because if I was the sample manager or whatever and I overheard people rudely complaining to each other that they didn't like not knowing what was in the sample products, I might consider putting the ingredients list up next to the sample station. The goal is, after all, to get as many people to come check out the product as possible, right?
> The goal is, after all, to get as many people to come check out the product as possible, right?
the goal of this repo is to do something nice for people, not attract attention. i know that 100% if this was the reaction to my public service, i would immediately take the repo private because ungrateful people don't deserve to have nice things.
The first paragraph of the first article in the series says this:
"As we announced recently, my team at Google has started a new effort to build production-worthy engineering tools for Fully Homomorphic Encryption (FHE). One focal point of this, and one which I’ll be focusing on as long as Google is willing to pay me to do so, is building out a compiler toolchain for FHE in the MLIR framework (Multi-Level Intermediate Representation). The project is called Homomorphic Encryption Intermediate Representation, or HEIR."
By the way, the author of the GitHub repo has updated the README to have a link to the MLIR framework now. ¯\_(ツ)_/¯. Can't wait to read about it.
I should have taken a moment to see that the HN poster here and the repo owner are not the same thing, and directed my comment to the owner rather than here - I leapt to the conclusion that they were the same person.
He added a single link on one line, and that's all it took. I appreciate people recognizing positive intent and not someone taking potshots.
