Hacker News new | past | comments | ask | show | jobs | submit login

Front-end (web?) is a more narrow domain than what I was speaking to. It sounds like you are pointing out specific issues that you encountered when working on a particular project.

How is SOLID responsible for these issues? The acronym represents guidelines.

What you are describing sounds awful. IoC can get nasty when developers are inexperienced and off-the-leash.

Keep in mind that everyone is ignorant. We all have different experiences with different technologies on different codebases.




> Front-end (web?) is a more narrow domain than what I was speaking to.

It's the domain where proper architecture matters the most, because it's hard to get it right.

> It sounds like you are pointing out specific issues that you encountered when working on a particular project.

If by 'particular project', you mean every single FE project that I've worked on, that made unopinionated use of dependency injection, sure.

> How is SOLID responsible for these issues?

'LI' doesn't do any value add for these problems (You don't use all that much inheritance, or define very many interfaces when working on front-ends), and 'D' is actively harmful, because it paves the road to dependency injection. I find posting events to a bus to be a lot easier to deal with, then dealing with a spaghetti of objects interacting with injected dependencies.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: