3 ms·
He's talking about AngularJS (v1). It is very different to modern frameworks like Angular (v2+), React, et.al. Frameworks from that era didn't involve setting u
by pjgalbraith 5y ago
He's talking about AngularJS (v1). It is very different to modern frameworks like Angular (v2+), React, et.al. Frameworks from that era didn't involve setting up any build process.
Have a look at https://angularjs.org/ https://angularjs.org/ or https://knockoutjs.com/ https://knockoutjs.com/
- sawka 5y agoYou still have to know a lot of JavaScript to get Angular working. The hope for Hibiki is for backend/devops engineers and data scientists who aren't JS experts (I've worked with many of these types in the past). Hibiki provides the glue to call to your backend processes. You can write "frontend" functionality in your backend code (Python, Go, Rust, Java, etc.) instead of having to write that in a language you're not familiar with.
- the__alchemist 5y agoThis implies the intent is to be usable by people who aren't proficient in JS. Yet, it requires proficiency in Hibiki's DSL.
- sawka 5y agoYa, kinda like how all template languages (go-template, handlebars, jade, TT, JSX, etc.) have their own DSL. With Hibiki you can get by with only understanding the basics and then calling backend AJAX handlers to do the rest of the work. If you want to go deeper and put more functionality on the frontend or create advanced generic components, then ya, you'll have to invest more into learning the framework. Most of the backend engineers I've worked with have no problem writing HTML, AJAX handlers, and using template languages. But they won't touch webpack/npm/babel with a 10-foot pole. Just trying to bridge the gap to get a little more pizzaz into their tools :)