trommlp

4 ms·

1. 1.▲
   by trommlp 3y ago

   You are of course right that developers have to learn to keep things simple and that skill comes from overengineering stuff. Maybe I have been overly negative on my original comment. As long as it's just a "phase" the long-te
2. 2.▲
   by trommlp 3y ago

   I don't know all the reasons individual developers would want a more complicated piece of software. Might be to show off, yes, or to learn about a new technology to the detriment of those developers that come after and the Ops people w
3. 3.▲
   by trommlp 3y ago

   I think you mention a very valid point that is worth reiterating: Even when you enter territory where HTMX gets cumbersome for some reason, you can still use custom JS or some other library to work around it. I admit that I initially starte
4. 4.▲
   by trommlp 3y ago

   I assume from what you are describing that OIDC is probably just the right tool for this job. In my problem domain (think internal apps that serve many different purposes with little overlap and a diverse set of users) logging in individual
5. 5.▲
   by trommlp 3y ago

   I wholeheartedly agree with your last sentence that is seems overengineered, but one has to assume that there are use cases that warrant such a complex auth scheme. I cannot speak to that as I have never implemented systems of massive scale
6. 6.▲
   by trommlp 3y ago

   I agree to some extent on it being a social problem. But I am not sure that developers are to blame outright. What seems to be unpreparedness or incompetence might just be the result of desperately trying to produce something from incomplet
7. 7.▲
   by trommlp 3y ago

   I really enjoy using a microframework and multiple small libraries to build a project instead of a huge, opinionated framework for the reasons you mentioned above. Glueing different interfaces together within my own "business logic&quo
8. 8.▲
   by trommlp 3y ago

   I think calling it the Hall of Fame/Shame is unjustified. I certainly agree when we talk about hardware products, because having very short support periods for those just seems wasteful. But it gets difficult when entering software, be
9. 9.▲
   by trommlp 3y ago

   In the case of commercial products it is especially frustrating if you need to log in to some customer portal in order to find such basic product information. And even if you create an account and log in it is not guaranteed to find this in
10. 10.▲
    by trommlp 3y ago

    Thank you for creating this. We keep track of EOL dates in our internal wiki with links to various websites. Would be nice to reduce the scatter and just link to this site! Would you accept Pull Requests that add server hardware EOS and EOL
11. 11.▲
    by trommlp 3y ago

    I agree. I use server-side rendering heavily in my projects at work and thus largely avoid custom Javascript (edit: the reason is laziness, not because I outright disliked Javascript). But if I want to enable some very basic user interactiv
12. 12.▲
    by trommlp 3y ago

    I would like to mention maud in this context: https://github.com/lambda-fairy/maud It is refreshingly different from other Rust templating libraries. It uses a proc-macro that compiles your HTML into Rust code. I also