HATEOAS, Data APIs, Java and How htmx Happened

Apple IIgs and HyperTalk, _hyperscript, starting with VBA then using Java, EJB 1.0 and J2EE, gosu, gscript, implementing Ruby on Rails, teaching at The Montana State University, Java got lots os stuff right, javalin and jobrunr, Java and Ruby on Rails, NodeJS became more appealing to Ruby on Rails developers, Yukihiro Matsumoto created Ruby, performance challenge with sorting rows in a table, JQuery get function, the intercooler.js library, intercooler is the competitor of turbolinks, WebComponents and CustomElements, BCE and the bce.design template, BCE follows the data API approach, htmx works with data attributes, the popularity of Angular, GWT was popular, htmx renders HTML directly, htmx follows HATEOAS, HATEAOS is stateless - the response already contains all possible actions, Roy Fielding coined the term REST, web was designed for coarse grained interactions, with hypermedia approach messages are self-descriptive - API versioning is easier to maintain, htmx encourages use of Java, JSPs with WebComponents (link to youtube ), the Quarkus Renarde web framework, implementation of authorization and authentication with htmx, GraphQL gives developers and users a lot of power - which can be a security issue, GraphQL requires the implementation of resolves, how to version a data API, Stefan Tilkov and resource oriented architectures ROAs, endless scrolling with htmx is easy to implement, htmx on discord

Carson Gross on twitter: @htmx_org, carson's company: Big Sky Software