That tsts project looks very interesting. I suppose there are various practical reasons for doing this. For me I'm just glad to see an easy way to run the newest TypeScript compiler (and I guess type checker?) in the browser. There's an unofficial Wasm build of tsgo/ts7, if I recall was about 12Mb. Another advantage of tsts I imagine is the ease of diving into the compiler internals as it's running (interpreted) instead of a binary distribution, another language (though I like Go), or having to recompile it on every change. Good luck with the project, I'll be keeping an eye on its progress with interest.
Why did I have to see this mysterious and intriguing code in the morning, now my brain won't rest until I learn what every symbol means and how it works. Thanks for sharing!
Closed source (and vibe-coded) software, especially for a language runtime, is a non-starter for many people including myself. But proprietary license is actually common in the APL and K family of languages. They are fascinating though, and plenty of free/open implemenations exist, for example: https://ktye.github.io/
Before you get downvoted to oblivion, please enlighten us on what you mean by "agent of regime". Which regime do you mean, and is there evidence he (c)overtly worked with them?
I recently learned about that too, how Lean provides ways to create new language syntax and DSLs, which is (on the surface) similar to Lisps like Racket. It's like operator overloading but way more flexible and general purpose. I'm wary of such language features, convenient for specific purposes (like working with vectors or matrices) but I'm afraid it's too powerful for normal usage, if everyone starts building their own DSLs and syntaxes, it would likely make the typical codebase difficult to read and understand. For example, the C++ template metaprogramming madness, it can be used responsibly but in my opinion it was detrimental to the language ecosystem.
It reminds me of people who built businesses on top of APIs provided by Facebook, Reddit, etc. One day the company decides to rug pull the public interface, either to replace it with their own competing product or nothing at all. The anti-competitive pratice makes sense but what I don't understand is the latter case, which is common, where the company is just removing possibilities of how users can participate in their ecosystem and platform. Not only destroying third-party opportunities for profit, but not even providing their own alternative.
> Without dramatically upending our understanding of quantum field theory, there is no room for any new influences that could bear on the problem of consciousness.
This kind of intellectual arrogance and blindness is exactly how people believed that the earth is the center of the universe, and that only human beings have souls. There is nothing new to be learned from their dogmatic opinions.
Perceiving plant gods and spirits is closer to experimental science, attempts to describe and make sense of your actual lived experience. Dismissing them without any evidence or experience, just because they don't fit in the worldview you grew up in, is closer to religion.
That makes sense, how larger projects benefit from static typing not only for the project itself but the build process. And how it helps with reliability and predictability during the compilation step, instead of finding out during run time.
Your other projects look interesting too, they seem friendly for new learners to pick up. And the fact that you've been using your own build system, frameworks, etc., for some years already is a great signal that they're practical and useful. Thanks for sharing, I'm looking forward to exploring more.