Functional Programmers need to take a look at Zig.

Scripty

Scripty는 매우 단순하고 제한적인 스크립팅 언어로, 문자열이나 호스트 문서 내에서 임베딩되어 사용될 수 있다. 변수 할당, 반복문, 조건문 없이 단일 표현식만을 지원하며, 주로 쿼리 언어 프레임워크로 설계되었다. Zig 언어로 구현된 스택 기반 VM을 통해 빠른 평가가 가능하며, 향후 정적 분석, 자동완성, 네이티브 코드 컴파일 기능이 추가될 예정이다. Scripty는 다양한 호스트 환경에 맞게 평가 컨텍스트를 정의할 수 있어 HTML 템플릿(SuperHTML)이나 마크다운(SuperMD) 등에서 유연하게 활용된다.

https://kristoff.it/blog/scripty/

#scriptinglanguage #zig #staticanalysis #templating #vm

Scripty

The perfect scripting sidekick! (or so I like to think)

RE: https://hachyderm.io/@kristoff/116488267530388091

This was so refreshing to read, and it made me love Zig even more as a learner. From my reading, I think the essential distinction is whether the contributors actually think about and acknowledge the changes (and the design of those changes) they're making.

In light of that, the AI ban itself isn't the "perfect" borderline, I think. It's because there are a lot of developers who can utilize AI as a tool, driven by their own thinking, decisions, and understanding (using AI for searching parts of code, online documentation, and less hallucination-prone code generation with good human review would be good examples). So I understand Zig's policy as having a clear boundary on that, even if it's not perfect as intended. But at the same time, I can think of two things for software development in general (not directly to Zig's) with great respect and love for the current Zig's AI policy.

One is that it might be okay to allow the core development team to use AI since they're trusted not to misuse it. Second, it's more intrinsic if there were a good metric to deterministically check contributors' understanding. Not perfectly aligned with the second point, but letting them write the PR comment in their own words could be a more mitigated solution than a strong AI ban, if I allow AI use while upholding the philosophy I felt was behind that.

I'd be glad if anyone could share their thoughts on this.

#ai #vibe_coding #zig #oss

Sent my first PR on Zig. 🥳

Had an issue with the elf loader failing for some object files, and decided to actually get to the bottom of it.

#zig

Cursor удалил прод за 9 секунд, а Zig и JVM запретили AI-коммиты

Двенадцатый выпуск еженедельных IT-новостей от OpenIDE! На этой неделе прошёл JPoint 2026, вышел Amplicode 2026.1 со Spring Agent Toolkit, а Anthropic впервые обогнала OpenAI по оценке на вторичном рынке. Плюс история о том, как AI-агент удалил продакшн-базу данных за 9 секунд.

https://habr.com/ru/companies/haulmont/articles/1032174/

#Amplicode #Spring_Agent_Toolkit #Cursor #Claude_Opus #GitHub_Copilot #Anthropic #Ghostty #Zig #AI_инфраструктура

Cursor удалил прод за 9 секунд, а Zig и JVM запретили AI-коммиты

На этой неделе прошёл JPoint 2026, вышел Amplicode 2026.1 со Spring Agent Toolkit, а Anthropic впервые обогнала OpenAI по оценке на вторичном рынке. Плюс история о том, как AI-агент удалил...

Хабр

GPU-accelerated terminal environment in Zig
Attyx는 Zig 언어로 작성된 GPU 가속 터미널 환경으로, 세션, 분할, 탭, 팝업, 상태 표시줄, 명령 팔레트 등 tmux와 유사한 기능을 기본 제공한다. macOS에서는 Metal, Linux에서는 OpenGL을 사용하며, 5MB 미만의 경량 크기를 자랑한다. 개발자는 터미널 작동 원리를 이해하고 Zig를 배우기 위해 직접 개발했으며, 현재 실무에 사용할 만큼 안정적이다. 기존 GPU 터미널인 Ghostty나 Kitty와는 별개로 독자적으로 구현되었다.

https://github.com/semos-labs/attyx

#gpu #terminal #zig #programming #opensource

@gmc Claude vibe coded me a perfect DVUI interface but it's not ready for production yet. In the end I decided for dartlang multiplatform UI on top of flutter https://docs.flutter.dev/
#zig #dart
Flutter documentation

Get started with Flutter. Widgets, examples, updates, and API docs to help you write your first Flutter app.

Claude and zig, thanks to its simplicity, are the best combination for vibe coding beginners like me. I don't mind that zig doesn't accept AI contributions to its core, I mind that Anthropic will stop teaching Claude new zig versions and my code will have no future.
#zig #claud
@nelson When #Zig was a simple language, it had an async feature that wasn’t good enough, and iterating on that led here. For my part, I love knowing that only the parts of my code where I made my std.Io available are going to do IO!
I know there are systems where a hundred pointers costs too much but they’re working on it and I bet the “restricted pointers” angle (or something similar) will let them move those costs to comptime for the usual case where there’s only one IO type being compiled.