What sets it apart is that it 1) stores content in TS / JS files 2) is a fully fledged CMs.
It is designed to be nice to work with from the start a project (and the structure of your app changes all the time) -> when everyone works on individual PRs -> to the end when the project is decommissioned.
It needs no cloud APIs, no DBs nor caching. No query language to learn. No sign up to get started.
It is fully TypeSafe and needs no type generation. You can rename and refactor content from you IDE.
It works amazingly with Cursor and friends (local content and schema + strong typesafty + validation)
Currently reqs are: Nextjs and GitHub.
APIs are pretty stable. UI is in the process of a revamp.
Will do a proper show hn some time in the near future.
> It's entirely possible that we do become obsolete for a wide variety of programming domains. That's simply a reality…
It is not a reality since it has not happen. In the real world it has not happened.
There is no reason to believe that the current rate of progress will continue. Intelligence is not like the weaving machines. A software engineer is not a human calculator.
To be fair he didn't say it is the reality now, he said the possibility is a reality. At least that's how I read his sentence.
And yeah, I do think it's a real possibility now.
I really liked this article. I think all of these points, in particular the conclusion of cost vs benefit could be the same whether you were talking about formal methods or web apps. This way of seeing things, with an engineering perspective, is the exact same we (at least I) see it but we mostly do web apps.
So cool. Have wanted to add an extra battery on my Yuba Spice Curry, but it is so expensive. Love the fact that it is possible to replace the individual cell. Been annoyed that ebikes are not as serviceable as normal bikes. Signed up now :)
I do that (via termux) with a onyx max boox 3. Works pretty well. I had some quality issues (got 2 dead lines on 2 devices so far) with the actual device but support has been very, very supportive so far so globally I'm very happy
This is correct. @tailrec will simply cause a compile failure if the compiler DOESN’T optimize the function, but the compiler does still optimize tail recursion without the annotation.
It’s a weird but helpful annotation. For example, Scala won’t optimize methods that can be overridden (non-final and public/protected), which is easy to forget. So the annotation is a nice check/confirmation that the compiler is doing what you expect.
GitHub: https://github.com/valbuild/val
Intro video: https://youtu.be/83bnYGIsm5g?si=5LN7dxnARrS4jNEx
What sets it apart is that it 1) stores content in TS / JS files 2) is a fully fledged CMs. It is designed to be nice to work with from the start a project (and the structure of your app changes all the time) -> when everyone works on individual PRs -> to the end when the project is decommissioned.
It needs no cloud APIs, no DBs nor caching. No query language to learn. No sign up to get started. It is fully TypeSafe and needs no type generation. You can rename and refactor content from you IDE. It works amazingly with Cursor and friends (local content and schema + strong typesafty + validation)
Currently reqs are: Nextjs and GitHub.
APIs are pretty stable. UI is in the process of a revamp. Will do a proper show hn some time in the near future.
reply