alpaylan

Hi, author here! Please let me know if I could pitch in to the discussion in any way.

I agree. It’s especially weird moving across related domains because suddenly something you think you know has changed meaning. For instance eBPF is “verified”, but the verification is almost completely unrelated from the usual connotations.

Doesn't all optimizations need to be valid translations first? That was my reasoning when writing it.

You cannot escape from the human verifying the properties you want verified mechanically. This only gives you leverage in specific scenarios where specification is much simpler than the implementation.

I think the point I wanted to make was that even if it was deterministic (which you can technically make it to be I guess?) you still shouldn’t live in a world where you’re guided by the “guesses” that the model makes when solidifying your intent into concrete code. Discounting hallucinations (I know this a is a big preconception, I’m trying to make the argument from a disadvantaged point again), I think you need a stronger argument than determinism in the discussion against someone who claims they can write in English, no reason for code anymore; which is what I tried to make here. I get your point that I might be taking the discussion to seriously though.

The Maryland one (that would be me, although I haven’t really done anything except the WASM bindings, this is really all Joomy’s work, kudos to him) is vacationing in Izmir right now, why would that even be important though?

I'll add some links for the original VGD paper and related articles, that should help in short term. Thank you! I'll look into writing something on VGD itself in the next few weeks.

Ahahah, it unfortunately was not, but that would’ve been a good twist I agree

Thanks a lot!

Hi everyone, I'm the author of the package. This is something I had in mind for a while, and the results of the prototype is promising, so I'll keep working on it. My hope is to merge the analysis I do into upstream jq once I'm able to work on a large enough subset, and maybe keep a jq fork with type-hints at some point. I wanted to keep the README brief, so there are more details in the docs.md if you're interested. I'm also happy and excited to answer any questions!

Hi, the current version is just a prototype, but it's definitely not a one-off demo, it's an analysis focused on a very small subset, and it works on that subset and produces the better error message I mention. The roadmap is in docs.md for now, I'll add more details to the readme once I figure out a nice and brief way to do it.

Just added the license, thanks for reminding me of it.

Thanks a lot! Hopefully it'll be more usable at some point. Lots of novelty leads to lots of very badly experimented UI

I wrote a static site generator for adding interactive elements to my blog and I want to keep extending it. The link is a short introductory article showcasing a few features I added. I would be happy to hear any thoughts or comments!

I just wrote a new programming puzzle! It's a cryptic visual language that represents some English written text. If anyone wants to take a crack at it, please check https://puzzle.alperenkeles.com!

Ah, sorry for misleading.

I had a similar thought, actually started an open source project by myself at https://github.com/alpaylan/cvdl

My view is to have it similar to html/css paradigm of web. I started working with TOML based schemas for defining CV's, actually wrote my CV in the schema.

If you wanna go forward, I would love to be a contributor, also I would love to get your opinions.