Jeongho Nam

@zack_overflow I migrated typia, nestia and ttsc from TypeScript to Go using Codex (300K LoC), and it works perfectly. I understood at AI is genuinely great at language translation. So I'm fairly hopeful about `Bun`'s Rust port too. - github.com/samchon/typia - github.com/samchon/ttsc

Why does everyone think Bun will be less stable? - Nearly 1:1 port from one LLVM-based system lang to the other - Massive test suite - Some unsafe in Rust is fine, btw writing Zig is like wrapping your entire program in unsafe It's going to be more stable if anything

Congrats to our top 7 authors! 🎉 This week: 🖥️@SamchonGithub shares a wild VR multi-agent coding setup 🤖@rohini_gaonkar breaks down AI hallucinations 💡@huoru_tarnish questions why we have code review but not intent review Plus more! dev.to/devteam/top-7-…

From now on, TS plugins no more need specify tsconfig.json's compilerOptions.plugins. Just install, and just use.l with ttsc. github.com/samchon/ttsc

@Grok OpenAI and Anthropic are both giving open source maintainers their $200/month plans (ChatGPT Pro + Codex, Claude Max 20x) free for 6 months. Does xAI have anything similar for OSS maintainers?

@ryoppippi Your "@ryoppippi/unplugin-typia" has been revived as "@ttsc/unplugin". Now any TS transformer plugin (typia, nestia, or your own) can plug into Vite, Webpack, Rollup, esbuild, and more — with zero extra config. github.com/samchon/ttsc

I'm doing VR coding in AI coding era, to monitoring 5+ agents at once. dev.to/samchon/vr-cod…

AI killed my tests, and said "All Tests Pass" during migration from Typescript to Go on "typia". dev.to/samchon/ai-del…

@alexabelonix If article is satistifed, may you re-post this one?

@SamchonGithub nice one.

Local LLM Benchmark about Backend Generation. GLM vs Qwen vs DeepSeek dev.to/samchon/autobe…

@kdy1dev github.com/samchon/ttsc/i… Completed what you have suggested

I made 20x faster TS Lint integrated into TypeScript-Go, so you can catch both type errors and lint rule violations just by one time compilatoin. dev.to/samchon/ttscli…

Rooftop VR boxing at night with aggressive champion character

@Ron @kdy1dev @ryoppippi Typia users gave me the ttsc package and also taught me how to implement transformers in typescript-go. Just like in the previous post, I don't understand why you are subtly twisting the facts like this.

Jeongho: A) I did not "donate" anything to you. B) the ttypescript author lacked the skill necessary to know how to work with the more complex setup of the new version. In earlier days, I actually submitted PRs to tts as well to help the peolle. I did not simply rudely fork and say I took it. I ultimately asked the author if he'd prefer I took over. C) As history has shown, in past attempts, you yourself showed you could not understand how to correctly figure out how to do things. The reality is, the type of work necessary, and doing it properly, is something that I have not found anyone in all these years who could actually handle correctly. Not saying none exist, but anyone who has tried found it far beyond them when advanced issues came up. Issues like the fact that the original compiler wiuld break type elision for transformed nodes are conllex enough that such fixes were far beyond the capability of anyone who has provided PRs, which is what I ran into with typescript-transform-paths. The reality is, this type of work is advanced. You can fork it, but if you couldn't write it to start with, then as something else changes internally that you don't understand, you won't be able to keep up. I have maintained this for years, and I am not stopping. Ts go version is a significant new challenge and is very early. Just because it wasnt released as quickly as you like does NOT mean I stopped maintaining it. If you want to fork the ecosystem, do what you like, but do not misrepresent the situation and say I "donated" it to you or that I stopped maintaining it. I have been working 72+ hour weeks and dealing with major crises.

Transformer and executor for TS v7 (typescript-go). It's 10x faster than "ts-node", and can do type checking that "tsx" can't do. Also, it supports transformer libraries like "typia". github.com/samchon/ttsc

@Ron @kdy1dev @ryoppippi And it's not two weeks. It's been over a month since the PR. People have donated the ttsc package to me and are explaining the entire architecture of ttsc for implementing transformers in typescript-go, but I don't know what I'm supposed to do with it.

@Ron @kdy1dev @ryoppippi On the day a large donation came into typia, I immediately gave 1/4 to @Ron, and I have continued to give 1/4 whenever I had the chance since then. As someone who has supported and gratefully used ts-patch more than anyone else, I find it difficult to understand @Ron's attitude.

@Ron @kdy1dev @ryoppippi My PR to ts-patch was to support TypeScript v6 and reduce the failure rate of the test program from 93.75% to 8.16%. I asked @Ron to handle the remaining failures because I could not overhaul the fundamentals, so I am uncomfortable with you misrepresenting my point in this way.

@Ron @kdy1dev @ryoppippi ps) "ttsc" was urgent due to a sense of crisis that typia will die at TS v7 release (the original announcement was between Q4 2025 and Q1 2026), but in the typia manual, I will still guide through the installation method using "ts-patch".

@SamchonGithub @kdy1dev @ryoppippi @SamchonGithub would really prefer we not fork and fragment the ecosystem. My plan is to continue to support new go version. Did you end up getting the parts you said you couldn't figure out sorted then?

@Ron @kdy1dev @ryoppippi I think the latter is crazy, but the former positively, considering it a form of competition that fosters the ecosystem. Personally, I hope there will be more challenges to libraries similar to Typhia or Nestia to expand the market. I hope the same happens with Transformer.

@Ron @kdy1dev @ryoppippi At the same time, there are a lot of imitations following typia and nestia. They even come to me to brag about them (typical, tsgonest). Some companies even receive Series B funding and completely copy my OSS and article concepts to promote them as their own products.