Mir: 미르: 개발자를 위한 새로운 AI 기반 프로그래밍 언어

### 미르의 부상: 새로운 AI 중심 프로그래밍 언어
* 💻 2025년에 가까워지면서 개발자들은 다양한 방식으로 'C'와 유사한 새로운 프로그래밍 언어를 계속 개발하고 있지만, 이제는 **AI 애플리케이션을 위해 특별히 설계된 Mir라는 고유한 언어**가 등장하고 있습니다.
* 🤖 Mir는 **JavaScript를 생성하는 AI 기반 함수형 프로그래밍 환경**을 제공하여 개발자가 기존 코딩을 우회하는 동시에 **테스트 중심 개발(TDD)의 문제**를 해결할 수 있도록 지원합니다.
* 📝 이 언어의 문법에는 시그니처와 예제가 포함되어 있어 **TDD의 블랙박스 버전**과 비슷하지만, 사양이 복잡하고 다소 혼란스러워 보여 구현하는 데 어려움을 겪을 수 있습니다.
* 🔍 2시간 동안 Mir를 실험해 본 결과, 필자는 **잘못된 사전과 예상치 못한 구문 등 수많은 문제**를 발견했고, 이는 마치 약속을 제대로 이행하지 못하는 브랜드 외 제품처럼 느껴졌습니다.
* ⚙ 축 정렬 바운딩 박스 충돌 감지를 위한 간단한 함수를 만들려고 시도했지만, **생성된 코드가 올바르지 않아 AI를 효과적으로 유도하는 데 어려움**이 있었습니다.
* 🧠 저자는 AI 도구에 지나치게 의존하면 개인의 성장과 문제 해결 능력을 저해할 수 있다고 주장하며 **독립적으로 코딩하는 법을 배우는 것**의 중요성을 강조합니다.
* 💡 궁극적으로 미르는 구문 분석기와 프로그래밍 개념을 이해하는 학습 도구로 사용될 수 있지만, AI 기술이 발전함에 따라 **코딩 기술을 개발하는 것이 여전히 중요**합니다.
* 🚀 AI의 기능에 대한 논의는 **기업이 왜 이렇게 강력한 도구를 판매하는지에 대한 의문**을 제기하며, 점점 더 자동화되는 미래에는 **기술력을 유지하는 것이 매우 중요**할 것임을 시사합니다.

Mir는 코딩 기술 습득의 중요성을 강조하는 혼란스러운 AI 기반 프로그래밍 경험을 제공합니다.

It's almost 2025, and if there's one thing that's consistent among developers, it's creating new languages that are kind of like 'C, but...'.  You know, 'C, but easy,' 'C, but modern,' or 'C, but for furries.'  But this time, we have a language

designed to be used with AI.  That's right, it's going to be 'C, but for AI and furries.' Obviously, AI is going to take all of our jobs the moment that product managers can accurately describe what they want, which means our jobs are effectively safe at infinitum.  But there is

room for us to be able to take advantage of the AI, you know, the classic AI experience that we all have where we tell the AI that it's a mother,  we're proud of it, we glaze it really hard, or threaten to commit seppuku if it doesn't give you

back JSON. And yes, that still is true when it comes to Anthropic.  Right now, I cannot get it to properly format a JSON.  Anyways, this new language is called Mir, and it's kind of unique, right? It has this basic grammar that proposes signatures, which is kind of what the

function name and shape should be, and then examples. So kind of like test-driven development, where you don't write tests, you just write like the blackbox version of it. That's right, that means it's an AI-powered functional programming experience in JavaScript, of course.

It produces JavaScript. I mean, what other language would it have produced? It only produces JavaScript. That means you get all the benefit of avoiding writing code plus you get all the agony of writing tests. It's late-stage TDD, really. That's what it is. We've officially hit

late stage AI powered test driven development and if a VC ends up seeing this video, pretty sure Mir's in store for about a $10 million funding because let's let's just be real here AI that's all you got to say that's actually all

you have to say to a VC and you you get millions of dollars. I mean look at friend.com. Anyways, I played with Mir for about 2 hours in hopes of making something, really anything, just like can I even create the simplest function? But as I started playing with it, I realized

several things: one, it does appear that an AI has written this language because the specification is actually insane. Look at this: literals, literals is one literal and an optional zero or more literals. What syntax is that? I don't know, but you eventually kind of figure it out. You go

on over to literal and you look at the list type, you'll notice that it's in brackets: literal. Okay, so what does that mean? That means you can only produce a list of one item. It's just an inconvenient variable. Like oh my gosh,

what is this specification? And when of course when you look into the types, you'll see right here that you can produce a list with a type or a dict with a type. What, what, why, why are there malformed dicts? I never thought I would ever see a malformed

dict, but here I am, 2024, almost 2025, and I can't stop singing: what is a one-typed dict? What is a one-typed [Music] dict? Is that like supposed to be a set? That's not a dict, dog! What is, what is

that this specification is a lot like kind of buying off-brand cereal, you know it has all the proper shapes and everything, but the moment you actually try it out it's not the same, it hits differently, it does not feel good. So of course I did the only thing that I could

possibly do, a fix the list boom, also turns out you can only have positive integers, so fix the integers and look at that, what is that? Is that a red X? Yeah, that's right, there's a red X in a parser. How do you build the tokenizer

and then you're using a red, oh no, yo dog, I heard you like parsers so I put a parser in your parser. This project clearly has a lot of AI influence because the types and the setup is just, it just feels all crazy, but you know what? We got it fixed, I didn't

fix the dicks though, I don't think anything can fix that dick. That is one malformed dick, so I left that aside and I figured okay, let's solve a problem using lists as my data structure. I know convenience, developer experience, all wrapped up into one data structure, lists.

All right, so the problem I decided to do was AABB collision with a point. All I want is an axis-aligned bounding box and a point. Also, thank you for the sub, appreciate that. Hey Zippy, thanks for that offline sub, Zippy. All I want is an axis-aligned bounding

box and a point. I'm simply going to have something that takes in a list of height, width, and its X and Y position, and then it's something else that's just a list of XY position. And now I'm just going to have to specify a bunch of examples and

hope that it produces out the code that I wanted to produce so here right here is my first attempt and here's the code that it produces now just one quick look at it we'll see that it produced just exceptionally incorrect code and I know right now I can hear them I can hear

them charging all the way in starting to yell getting all frothy at the mouth the AI proed Max Melissa like well actually you didn't give you didn't give enough prompting okay that's the problem is you didn't give enough examples your examples

weren't good enough I don't think you actually know what you're doing see the thing is if you just understood prompting you'd be able to prompt better and clearly you don't understand prompting of course I don't it's brand new language that I had to fix

myself so I'm going to give more examples and obviously a second clear problem with this approach is that there's no like check boxes where I can say how much and by what extent I wish to either threaten self harm harm to the mother or glaze the AI so obviously

probably not going to get it correct and does it even tell the AI not to hallucinate another really valuable strategy I don't even think it does anyways gave a whole bunch more examples and got a new piece of code which in fact still does not work if you couldn't

understand why this code was wrong look at it input zero let's call that X and input one let's call that Y if input X is greater than any element within that element list and input two is less than or equal to the element adjacent to it

It's considered containing like that's crazy, like how did they get that? How did it get this answer at this point? I'm two hours into fixing bugs and producing absolutely nothing, so I just tried GPT. Gave it a quick little English sentence.

Gave it the structure of my code, boom, one shot of the answers right out. You know this project's kind of like cute, it's funny. Hey, it's a great way to learn how to write a parser, so if you, whoever wrote this, actually ended up writing out

the parser by hand and doing everything, it's a great experience really to learn and to become a better programmer. So hey, hats off to you, but at the end of the day, this always highlights the same thing for me, which is why do men avoid learning to code? What is this like, why

are you doing this? Just learn the code, just learn how to just test it, a points in a box, learn to write a return statement with a couple conditions. It's like not hard. You can go so much further if you don't have to rely on something

else to think for you. I just don't understand it, and here, hear me out here. If these AIs were really that great, they're so great that they actually were AGI, they're able to learn, they're able to grow better as Sam Altman once said.

We're only a couple thousand days away from it. That's like 10 years, anyways. Also, that's a crazy way to say that. Who, who describes time windows in days like, 'Oh yeah, it's just, it's just like 3600 days away, 10 years.' You can

just say 10 years and no one's upset at you Samuel it's strange but anyways but even if these companies do produce something that actually can really produce good code you just got to understand something why would a company sell a product that can build anything why

wouldn't they just harbor those trade secrets and build everything right like why would you sell the infinite intelligence tool think about it for a couple it makes no sense like you would be able to compete with every product and start company after company after

company after company over and over again having super AI would be the most valuable thing in the universe so why ever would they just simply sell it they wouldn't because they'd be able to make everything at the speed of like light it'd be crazy let's just say that

the AI companies do fumble the bag and accidentally sell the greatest product ever that can produce anything in a snap of the fingers with just a basic few text prompts let's say that does happen you having hard skills is going to be absolutely incredible right like

learning how to be technical and talented and solve problems large on large scales will only help you it will only make you better it will only make you more valuable and when that inevitable day comes whether it's in 10 years or a thousand years that AI can

just do so much your technical skills will still be valuable stop making the trade it's not a trade you don't have to make the trade like you really don't you can just like learn and have fun and build stuff and become better at your craft the

Programming Is Cooked

This is a place for all the things that are awesome on stream. 

ThePrimeTime

AI 기반 프로그래밍 언어인 Mir 소개

Mir는 AI와 함께 사용하도록 설계된 새로운 프로그래밍 언어로, '인공지능과 털복숭이를 위한 C'라고 설명할 수 있습니다.

이 언어의 설계를 통해 개발자는 AI 기능을 활용할 수 있습니다.

Mir는 테스트 중심 개발과 유사하게 제안된 서명 및 예제와 함께 고유한 문법을 사용합니다.

자바스크립트를 생성하는 AI 기반 함수형 프로그래밍 환경입니다.

연사는 미르의 AI 역량을 바탕으로 미르의 잠재적 자금 조달에 대해 추측합니다.

연사는 Mir에서 간단한 함수를 만드는 데 두 시간을 보냈습니다.

이 언어의 사양은 혼란스러운 구문의 예와 함께 특이하고 복잡한 것으로 간주됩니다.

잘못된 사전을 포함하여 목록 및 사전 유형과 관련된 문제가 발견되었습니다.

화자는 사양을 타사 시리얼과 비교하여 불일치하는 부분을 강조합니다.

스피커가 목록 및 정수 관련 문제를 해결했지만 구문 분석기 오류가 발생했습니다.

미르를 사용하여 문제 해결 시도

화자가 데이터 구조로 목록을 사용하여 AABB 충돌 문제를 해결하려고 시도합니다.

처음 시도하면 잘못된 코드가 생성됩니다.

스피커가 더 많은 예제를 추가하지만 생성된 코드는 여전히 올바르지 않습니다.

추가 시도 후 화자는 GPT를 사용하여 문제를 쉽게 해결합니다.

미르 경험과 프로그래밍에서 AI의 역할에 대한 고찰

발표자는 Mir의 구문 분석기로 작업하면서 얻은 학습 경험을 되돌아봅니다.

연사는 AI 지원 프로그래밍의 필요성에 의문을 제기하며 직접 코딩을 배우는 것이 더 효율적이라고 제안합니다.

연사는 AI의 미래와 고용 시장에 미칠 잠재적 영향에 대해 추측합니다.

화자는 왜 인공지능 회사가 무엇이든 만들 수 있는 제품을 판매하는지 의문을 제기하며 내부에 보관하는 것이 더 유리하다고 제안합니다.

이 연사는 첨단 AI를 사용하더라도 기술력의 지속적인 가치를 강조합니다.