LogicUpgrade

I'm using React in a very barbaric way. No (React) classes, no hooks, no custom (JSX) components, no nothing.

I use precisely two features:

1. I return JSX (via TypeScript) for HTML standard tags from methods (no custom components at the JSX level).
2. Those objects call each other, to composite a JSX tree, which eventually gets rendered at a host node with ReactDOM.render()

Everything else is a very basic hierarchical MVC architecture that's React-agnostic, so I can mix it with any framework, use native DOM manipulation, or even let someone animate a thing or two with jQuery.

Question is, is anyone else doing that, what's your experience?

And if not... why not?

Получавате ли това което очаквахте от присъствието на партията в парламента?

Доволни ли сте?

Ще гласувате ли пак за тях?

As we know the convention for records is that the generated getter methods match the property name without a prefix "get". The look is clean and intuitive and since they're immutable, that's fine.

However when mixed with objects that represent the same information we'd name the methods "getThing()" and not "thing()". Sometimes the objects would have setters, but sometimes they won't.

I'm just wondering how throwing records and their naming convention in the mix has affected the naming conventions for the rest of your objects. Do you still prefix "get" or do you skip it? Do you still use "set" for setters, or something else?

In a way the show is very predictable and has become formulaic over time. The script is sparse, and the budget doesn't permit them to do something too unexpected or original.

But I just love it anyway.

This thread is an attempt at an informal survey of opinions of DI containers and whether they're still considered a good practice in the industry. Note that I'm not questioning the idea of Dependency Injection itself, which is the simple concept of configuring the composition of an object through constructor and method parameters. But specifically practices like autowiring, or using XML configuration for injection, instead of using plain Java code in a designated composition root class (or classes).

At one point DICs have become unavoidable in projects, through frameworks like Spring and the like. I've often noticed they result in pseudo-singleton dynamics within the architecture, where eve