No-Code vs. Pro-Code: A New Hope

Re:No-Code vs. Pro-Code: A New Hope by nkingsy on Wednesday September 09, 2020 @12:23PM (#24422643)

I’m currently in the process of converting a no code product to “pro code“ per their definition, and I agree with their intentions here.

Many of these efforts in the past (including the team I’m on) lump opinionated libraries in with what I call secondary programming languages.

Opinionated libraries can save everyone a lot of time, as long as they are programmable and allow easy access to levels below, as well as further abstraction upwards. Throwing a new programming language into the mix interferes with abstraction traversal and stack traces in a devastating way.

[ Parent | on HN ]

Re:No-Code vs. Pro-Code: A New Hope by matharmin on Wednesday September 09, 2020 @12:37PM (#24422804)

There is a huge advantage to using an existing language (JavaScript/TypeScript) like this, compared to creating new DSLs. There is simply such a big ecosystem to leverage in terms of development tooling (auto-complete etc), existing libraries and existing libraries.

[ Parent | on HN ]

Re:No-Code vs. Pro-Code: A New Hope by RandoHolmes on Wednesday September 09, 2020 @12:37PM (#24422802)

I'm of the opinion that all great abstractions have explicit methods to allow you to pierce them when needed.

[ Parent | on HN ]