News for hackers. Stuff that matters.

henryluo

Re:Lambda 0.3 – a funcitonal lang with E2E doc pipeline on Thursday October 01, 2026 @12:08PM (#49923553)
Thanks for your prophecy :-)
Re:Lambda 0.3 – a funcitonal lang with E2E doc pipeline on Thursday October 01, 2026 @12:07PM (#49923540)
LambdaJS engine is quite complete on JS features, but performance wise, it is only about the same as Quick JS, much slower than Node/V8.
Re:Lambda 0.3 – a funcitonal lang with E2E doc pipeline on Thursday October 01, 2026 @11:08AM (#49922700)
Author of Lambda script here. Your feedback welcome!
Yes, I thought of this issue when I name it Lambda. But I like the name 'Lambda'. Once get over the initial stage, Lambda will be easy for people to remember.
Re:Executable Specs for Reliable Systems on Tuesday March 24, 2026 @11:56AM (#47504577)
Quint is an interesting lang, and the concept of 'executable spec' is definitely the direction to go in the age of AI vibe coding.

And the language, Lambda, that I designed and implemented has many similar characteristics: https://github.com/henry-luo/lambda

thanks.

As for the performance, I'm standing on the shoulder of great tools like MIR JIT compiler.

Lambda's PDF support is still very limited at moment. I do plan to enhance it in next release.
Glad to hear that. Note that the language is still being developed, and there're bugs here and there. So bear with those bugs. But it should be fun to try it out.
Hope it will change the way people work with data and documents.
While Lambda still has a pretty static GUI at the moment. My plan is to build it into a fully interactive, editable UI on all kinds of document data.

Show HN: Lambda 0.2 – a func language better than TypeScrip, jq and jQuery

https://github.com/henry-luo/lambda

What's your tool chain for data and document processing? - jq is great, but limited to JSON; and jQuery limited to HTML; templating systems get messy for non-trivial logic; TypeScript lacks pattern matching and schema support.So I built Lambda — an expressive functional language that combines the power of Lisp, TypeScript, and many DSLs like jq, jQuery, RelaxNG, etc.It has a lightweight 9 MB...

( Read More... | 17 comments | 7 points | on HN )
As for the '<' and '>' to open and close an element, there are two potential kinds of syntax design. Option 1 is to use some explicit delimiters. Mark 1.0 has settled on '<' and '>'. Mark 0.11 was using '{' and '}', which I felt confusing with map. So I changed to '<' and '>', to make it consistent with HTML/JSX and XML, which most developers are already used to. Option 2 is to use indentation to delimit the enclosed child content, like in Python and YAML.

Option 2 looks cleaner for configuration kind of usage. However, Mark is designed to be embedded in a scripting language, and used beyond just configuration files. Unless the scripting language uses indentation as delimiter, like Python, option 2 will not work.

Personally, I prefer C/Java/JS family of languages that has insignificant whitespace. So Mark is designed to use explicit delimiters '<' and '>' to enclose an element.

Hope that explains one of the most important syntax designs of Mark.

A new notation by itself won't be useful. It's the tool stack, the eco system around it that matters. That's why I'm building beyond that the format itself. I'm building the schema, the validator, the scripting and query language around it.
Here's the XKCD 927 post from last beta release: https://news.ycombinator.com/item?id=16308803
Yes, it's a must! Have that posted in the 0.11 beta release as well. :-)
Glad you like it. I have bigger plan for what's currently released. My next goal is to unify the schema of all those data formats, like JSON, XML, HTML, etc. And make the new Mark Schema able to validate all those data formats.
Glad to see your comment. Not sure I get you right. I also do not like many data notations and formats floating around. I hope there's one notation that can unify all the data that I'm concerned with. That's why I created Mark.

Show HN: Mark 1.0, a notation that unifies JSON, HTML, JSX, XML, YAML, and more

https://marknotation.org/

Author of Mark Notation here.Mark is a unified notation for both object and markup data, combining the best of JSON, HTML, and XML with a clean syntax and succinct data model.I'm glad to announce the 1.0 Release of Mark. This release is just the start of a long journey to make web a better platform to store and exchange data.Your feedback welcome!

( Read More... | 11 comments | 7 points | on HN )
Re:The Way of Code: The Timeless Art of Vibe Coding on Saturday May 24, 2025 @10:05AM (#44081212)
"When the way of code is abandoned, doctrines of ‘best practices’ and ‘standards’ appear. When intuition is dismissed, cleverness and pretense follow. When harmony is unnoticed, rules and processes multiply. When software fails, zealous testers arise."
Do you agree to Linus Torvalds that “Visual Basic did more for programming than Object-Oriented Languages did”?
Fake traffic, and spam everywhere. A constant war for all public content and services.
Re:Architecture Styles Worksheet [pdf] on Tuesday June 18, 2024 @12:51AM (#40714173)
Nice to see different architecture styles compared side-by-side in one concise table.
A lightweight 2D graphics library for rendering texts, geometries, and images with high-performance APIs that work across various platforms. Its main objective is to offer a compelling alternative to the Skia graphics library while maintaining a much smaller binary size.
Re:The dream of AI is the dream of free labor on Friday July 07, 2023 @08:47AM (#36630894)
It will work out to some extent at the beginning, but will encounter the Law of Diminishing Returns, and will saturate and flat out eventually.
Re:The dream of AI is the dream of free labor on Friday July 07, 2023 @08:18AM (#36630567)
The dream of AI is the same dream of free money, free content, free everything!

Older »