Show HN: Teal – a serverless VM and programming language
condense9.com
condense9.com
The current goal is to build data pipelines really fast and operate them really well, but I'm also interested to see how far the VM abstraction can be pushed. What would "soft infrastructure" look like?
A serverless language doesn't really explain what it is, I mean JS, Python, Java etc.. all run in serverless environments.
But after reading more it seems similar to Erlang, as each function can be deployed to other systems and invoked as if it were a local function... <- this is what you want to emphasise.
I would suggest adding a graphical flow chart on how this works (maybe like this https://i.imgur.com/fJHyJni.png). Perhaps a comparison of how regular programs invoke functions, compared to how Teal invokes functions (showing scalability and parallel computing).
> "Why should I learn a new language?... Because it'll give you a new way to think about cloud software."
This is not a good reason. If you want people to learn a random language, you need to demonstrate the reasons why it's better! At first glance it seems crazy to have no interoperability with another language/package manager.
Anyway, sorry if I sound critical, I think there's real potential in this idea and am excited to see more development for Teal!
- "serverless language". Fair point; I'm still working on how to describe it. I'm trying to get across the idea that it's a language for describing serverless applications (rather than a language that runs in a serverless env).
- flow charts: working on it
- new language: you're right, that section is pretty cringy
[1] https://lobste.rs/s/6bphbw/fennel_programming_language_ratio... [2] https://news.ycombinator.com/item?id=24285767
From a dev point of view, it's this: The ability to take business-logic "units" in Python, and quickly connect them into larger programs/workflows that run on Lambda.
So the language features aren't particularly interesting - it's not meant to replace Python. But it can do things that are hard/awkward using just Python.
Disclaimer: I'm tech lead of the project.
It doesn't even require await/async style programming. You can make a synchronous call which can take a few days to complete without any problems. And in case of any failures the state of all threads and local variables is automatically restored.
Just remove the second sentence, it is just fluff and reduces user trust. Your 'plans' don't mean anything to me as a user