Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>You either believe that transformers models are "it", or you haven't actually removed the problem of specifying requirements formally. Which, you know, is actually much harder to do in English than it is to do in C++

This is actually something that makes me happy about the new AI revolution. When my professor said that I thought he was an idiot, because no-code tools always make it harder to specify what you want when you have specific wants the developer didn't think about.

We give kids books with pictures because pictures are easier, but when we want to teach about more complex topics we usually use language, formulas, and maybe a few illustrations.

I still think no-code was always doomed due to the fact that any attempt at it lacked the interface to describe anything you want, like language does.

AI is finally putting an end to this notion that no-code should be clicky high-maintenance GUIs. Instead it's doing what Google did for search. Instead of searching by rigid categories we can use language to interact with the internet.

Now the language interaction is getting better. We haven't regressed to McDonald's menus for coding.



I’ve used no code tools since the 90s and it just has a fatal flaw. For simple demo use cases it looks simple and cool. Then when you go to the real world and start getting pivots and edge cases you have to fix in the interface then it becomes a 4D nightmare and essentially a very bad programming language


I’ve spent a fair bit of time working on interactive chat systems that use a form of visual programming. It’s not good. Once you get past the toy stage (which is good and ergonomic), it’s just the same as programming except the tooling is far worse, you have to invent all your change management stuff from scratch, and it’s like going back 30 years.


What about coding in two languages, one textual and one visual?

Or a single language that has both visual and textual components

Or a single language where each component can be viewed in textual or visual form (and edited in the form that makes most sense)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: