Steady Typing

Steady Typing

Lamdu’s UX for static types (written in Haskell)

I can provide an example on why I'm making /r/lamdu (with /u/Peaker). One of many reasons is that Lamdu introduced a novel UX for type errors which I believe can make static typing and type inference much more usable, for more details see link to this video Had our ideas been already implemented before then I'd just happily use that existing language and not work on a new one.

> A weak argument for a great idea. Thanks 🙂 You mean the idea of projectional editing, right? This video represents one facet and isn't at all the main argument for it. It is the third video in our series so far, each video showing a different aspect. The strongest of our arguments so far is in my opinion the "Steady Typing" video. > For related work, why don't you consider Unison? What do you mean? We'd really love to see our efforts converge. We also both use Haskell so it's not that impossible. Any work that can be re-used or shared we try to make available, such as momentu, our UI framework that we developed for Lamdu and the hypertypes AST manipulation and type-inference libra…

It's different to what you're talking about, but I found this very interesting anyway, "Lamdu"... * link to this video * link to this video One of the annoying things about visual/node based programming is that you can't work as quickly as you can with text-based code. Especially when it comes to: * copy and pasting multiple lines of code * ...including leaving the code in a broken/invalid state, temporarily while you shift things around (usually node-based stuff doesn't allow this flexibility, they typically enforce that everything is connected in a valid way at all times) * commenting/uncommenting things out So I think things like "Lamdu" where it's a kinda hybrid text + GUI interface are interesting. I…

I wonder if a language wanted to solve these issues of conflict, what would be some possible solutions? For syntax, I think protectional editing (r/nosyntax) could be used where the programmer could choose how they wanted their code to be formatted. (I.e. switching between braces vs whitespace, tabs vs spaces, etc.) If type systems are an issue, steady typing could be used so that types don't necessarily have to be correct for the program to be run. (Combined with projectional editing to remove type anotations could give a very pythonic experience) Naming conventions are a bit harder, but perhaps you could use machine learning to translate terse variable names into more detailed ones th…