Reddit Programming – Telegram
Reddit Programming
211 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
EHTML — Extended HTML for Real Apps. Sharing it in case it helps someone.
https://www.reddit.com/r/programming/comments/1oyw9g3/ehtml_extended_html_for_real_apps_sharing_it_in/

<!-- SC_OFF -->Hi everyone! I’ve been working on a project called EHTML, an HTML-first approach to building dynamic pages using mostly HTML. It lets you handle things like templating, loops, conditions, data loading, reusable components, and nested forms — all without a build step or heavy JavaScript setup. I originally built it to simplify my own workflow for small apps and prototypes, but I figured others who prefer lightweight or no-build approaches might find it useful too. It runs entirely in the browser using native ES modules and custom elements, so there’s no bundler or complex tooling involved. If you enjoy working close to the browser or like experimenting with minimalistic web development, you might find it interesting. Just sharing in case it helps someone or sparks ideas. Cheers! Link: https://e-html.org/ <!-- SC_ON --> submitted by /u/gyen (https://www.reddit.com/user/gyen)
[link] (https://e-html.org/) [comments] (https://www.reddit.com/r/programming/comments/1oyw9g3/ehtml_extended_html_for_real_apps_sharing_it_in/)
Microservices: Microliths as a resonable alternative
https://www.reddit.com/r/programming/comments/1ozflg5/microservices_microliths_as_a_resonable/

<!-- SC_OFF -->There are many fallacies related to Microservices people used to believe in (some still): that they improve design (architecture) on their own, just by the mere fact of a usage that they are needed because otherwise we cannot scale that they lead to simpler solutions ...and so on, many more It does not mean that they do not have their place - sometimes they do, but in the vast majority of the cases, they are neither required because of the predicted scalability needs nor because we have so many teams (like 10+, not 3 or 4) that we absolutely must separate each other on the service (process) level. But to be honest, the last argument is probably the strongest one can voice for having a few separate (micro)services: it often is objectively easier to work in parallel for multiple teams, if they all have their own service. That is where Microlits come in. They are a special kind of a (micro)service: A microlith is basically a service that is designed using the independent module design principles which avoids calls between modules/services while processing an external request. This typically requires some status and data reconciliation mechanism between services to propagate changes that affect multiple microliths. The reconciliation mechanism must be temporally decoupled from the external request processing. Having separated the processing of the external request and the communication between Microliths, we can split our monolithic application in several smaller parts without being hit by most of the distributed systems Complexity. The tradeoff is that we have to pay the price of temporally decoupled reconciliation between the Microliths. On the other hand, we do not need to deal with the problems that arise if a call to another service fails while processing an external request. <!-- SC_ON --> submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://www.ufried.com/blog/microservices_fallacy_10_microliths/) [comments] (https://www.reddit.com/r/programming/comments/1ozflg5/microservices_microliths_as_a_resonable/)
The CMDB as an architecture source
https://www.reddit.com/r/programming/comments/1oziiwz/the_cmdb_as_an_architecture_source/

<!-- SC_OFF -->Many organizations assume their CMDB can double as an architectural source of truth because it contains applications, servers, owners, service lines, capabilities, and relationships. But the CMDB was built for IT service management workflows, not for architecture, and that mismatch creates problems the moment you look deeper. The main problems are the different definitions of the terms, a capability of business application can mean something very different. The lifespan of the data, Capabilities for example can come and go in CMDBS depending on the current needs. And the conceptual base, if you base your architecture on ITSM, your architecture will also be ITSM based. That might be an issue for EA. I use a data filter in my architecture to still use the data, but transform it to use in my architectural tool. The main conclusion is: a CMDB is essential for IT operations, but it is not an architecture repository. Using it as one leads to confusion, rework, and the wrong mental model of the organization. You definitely should still use the information in there, but don't carbon copy it. <!-- SC_ON --> submitted by /u/GeneralZiltoid (https://www.reddit.com/user/GeneralZiltoid)
[link] (https://frederickvanbrabant.com/blog/2025-11-15-the-cmdb-as-an-architecture-source/) [comments] (https://www.reddit.com/r/programming/comments/1oziiwz/the_cmdb_as_an_architecture_source/)