4 ms·
I used that example as it was easy, but I could also have said: "we should be able to say: when the user is logged in and clicks on submit, then create a new ap
by estraschnov 12y ago
I used that example as it was easy, but I could also have said: "we should be able to say: when the user is logged in and clicks on submit, then create a new apartment" (you'll have recognized airbnb...) My point being it could be much more complicated than turning button to red.
Most people try to solve the issue with AI. I think it's one of the reasons why we haven't solved that problem (making programming more approachable) yet. I'd argue the first step is to make that it's readable in plain english. If we have this, then we can start thinking about AI. Why don't you have a look at Bubble (bubble.is). That's our approach
- jordanpg 12y agoA domain-specific WYSIWYG editor is a long, long way away from a future that doesn't involve any coding. Unless by "coding" you mean HTML/CSS/JS in e-Commerce web apps. The point is that there are infinitely many interfaces (again, in the most generic sense) that haven't even been conceived of yet. All of those will require coding.
- rezistik 12y agoI think the point is that we should program a way to avoid programming.
- estraschnov 12y agoI dont know... We're pretty close to WYSIWG, as you can read workflows. It's just the beginning, but we have something that 's def more readable than code And for the new interfaces, there will prob be some coding required, but let's build tools so that we can reuse them, without code