3 ms·

Thanks, I need all the luck I can get. Currently, I'm building a couple of products with my stack, and it's going well. For conditional processing that you and

Thanks, I need all the luck I can get. Currently, I'm building a couple of products with my stack, and it's going well. For conditional processing that you and your colleagues did, was it within the browser? I'm doing this as simple step such that I turn a giant "HTML forest" into lean javascript and DOM binding. It's working well for me, so I wonder what the gap is? Personally, my stack is underengineering since I'm combining the roles of web server, database, messaging stack, queues, caches, load balancer, workflow into one cohesive platform. My dry run video: https://www.youtube.com/watch?v=bWYgChA_aYA&feature=youtu.be https://www.youtube.com/watch?v=bWYgChA_aYA&feature=youtu.be goes into more details.

lelanthran 3y ago
> For conditional processing that you and your colleagues did, was it within the browser? Yes - it's the most common way to do it (the script language that comes with htmx runs in the browser too). > It's working well for me, so I wonder what the gap is? It usually turns out that it's less work simply using JS in the browser than remembering the new language. I'm not saying that your effort would have the same result, but it's the result I've seen in the past for this sort of thing. > Personally, my stack is underengineering since I'm combining the roles of web server, database, messaging stack, queues, caches, load balancer, workflow into one cohesive platform. That's what I meant by over-engineered - too much is included in the project, much of which won't be used by most intended users. I accept that maybe "over-engineered" is the wrong word. Tell me, what's the problem statement you had that prompted this development effort? What problem where you trying to solve when you started this?
- mathgladiator 3y ago
  Originally, it had to do with board games and running them in a web/cloud environment. Using websockets made building the game easier, but now there is exceptionally complex state within the process (await/async). Generally speaking, the cloud is unforgiving place to hold state within a process. I can speak deeply about streams at scale ( https://dl.acm.org/doi/10.1145/3477132.3483572 https://dl.acm.org/doi/10.1145/3477132.3483572 ). Adama emerged as a tool to help define a "transactional document schema" which I could use to emit deltas to a logger (like Kafka), and once I added a notion of "privacy polices with code"... the potential exploded. I believe I'm onto something with this platform, so I've decided to start hiring to build digital products that fit the thesis. I would say I'm over-engineering in that I'm making the service available to others rather than leveraging in a portfolio of products, but I'd rather keep it open rather than have secrets. (It's a good thing I'm retired because this is a large endeavor)

lelanthran 3y ago

> For conditional processing that you and your colleagues did, was it within the browser? Yes - it's the most common way to do it (the script language that comes with htmx runs in the browser too). > It's working well for me, so I wonder what the gap is? It usually turns out that it's less work simply using JS in the browser than remembering the new language. I'm not saying that your effort would have the same result, but it's the result I've seen in the past for this sort of thing. > Personally, my stack is underengineering since I'm combining the roles of web server, database, messaging stack, queues, caches, load balancer, workflow into one cohesive platform. That's what I meant by over-engineered - too much is included in the project, much of which won't be used by most intended users. I accept that maybe "over-engineered" is the wrong word. Tell me, what's the problem statement you had that prompted this development effort? What problem where you trying to solve when you started this?

mathgladiator 3y ago
Originally, it had to do with board games and running them in a web/cloud environment. Using websockets made building the game easier, but now there is exceptionally complex state within the process (await/async). Generally speaking, the cloud is unforgiving place to hold state within a process. I can speak deeply about streams at scale ( https://dl.acm.org/doi/10.1145/3477132.3483572 https://dl.acm.org/doi/10.1145/3477132.3483572 ). Adama emerged as a tool to help define a "transactional document schema" which I could use to emit deltas to a logger (like Kafka), and once I added a notion of "privacy polices with code"... the potential exploded. I believe I'm onto something with this platform, so I've decided to start hiring to build digital products that fit the thesis. I would say I'm over-engineering in that I'm making the service available to others rather than leveraging in a portfolio of products, but I'd rather keep it open rather than have secrets. (It's a good thing I'm retired because this is a large endeavor)