4 ms·

Non-constructive reply: Developers have been burned too many times by snake oil vendors and "solutions" that only work for toy examples. Also, I've never seen b

by moring 9mo ago

Non-constructive reply: Developers have been burned too many times by snake oil vendors and "solutions" that only work for toy examples. Also, I've never seen being slow to be encouraged anywhere. Most consider it an acceptable tradeoff though. Constructive reply: What would be an approach to writing a large web frontend (large as in, many pages and controls) without using a large framework? I'm asking this because I know how to do it in React but also how to do it "the old jQuery way" (or equivalently, using today's standardized builtins). Productivity is easily 100x larger with React. edit: Ideally, together with a link to an example open-source application that does it that way, to understand how it works and feels at (code) scale.

seszett 9mo ago
> link to an example open-source application that does it that way My experience is with this: https://github.com/Dolibarr/dolibarr https://github.com/Dolibarr/dolibarr (what I currently work on is quite similar, but it's not open source). It works fine. Clients don't complain about the interface. The project has been going on for 20 years or so now, and doesn't need big refactors every time a dependency gets updated because it avoids dependencies.
- moring 9mo ago
  Thanks for your reply. This seems like it builds the UI almost completely in server code, which I usually avoid these days because in my experience, it causes other problems. I should have mentioned that in my question.
austin-cheney 9mo ago
> without using a large framework? I have explained this countless times. It rarely sinks in and quite often is met with hostility, so I don't bother any more. The problem is simple: its where people stake their career. Do they build their career upon writing original applications or upon using a tool? This difference is rather extreme. By the way, without React shouldn't default to jQuery. If that is your perspective of reality you are already at the maxim of your potential.
- moring 9mo ago
  > By the way, without React shouldn't default to jQuery I never claimed it does. I stated my experience to give context for my question for other solutions than React. > The problem is simple: its where people stake their career I meant my question to be about building a large frontend without a large framework, purely in technical terms. This has nothing to do with career choices.

by moring 9mo ago

seszett 9mo ago

> link to an example open-source application that does it that way My experience is with this: https://github.com/Dolibarr/dolibarr https://github.com/Dolibarr/dolibarr (what I currently work on is quite similar, but it's not open source). It works fine. Clients don't complain about the interface. The project has been going on for 20 years or so now, and doesn't need big refactors every time a dependency gets updated because it avoids dependencies.

moring 9mo ago
Thanks for your reply. This seems like it builds the UI almost completely in server code, which I usually avoid these days because in my experience, it causes other problems. I should have mentioned that in my question.

austin-cheney 9mo ago

> without using a large framework? I have explained this countless times. It rarely sinks in and quite often is met with hostility, so I don't bother any more. The problem is simple: its where people stake their career. Do they build their career upon writing original applications or upon using a tool? This difference is rather extreme. By the way, without React shouldn't default to jQuery. If that is your perspective of reality you are already at the maxim of your potential.

moring 9mo ago
> By the way, without React shouldn't default to jQuery I never claimed it does. I stated my experience to give context for my question for other solutions than React. > The problem is simple: its where people stake their career I meant my question to be about building a large frontend without a large framework, purely in technical terms. This has nothing to do with career choices.