4 ms·
I'm not very experienced but the part about (non-)shared front-ends doesn't sound convincing to me at all. Why are some methods to combine front-end code bad (a
by xg15 10y ago
I'm not very experienced but the part about (non-)shared front-ends doesn't sound convincing to me at all. Why are some methods to combine front-end code bad (angular) but others are good (ESI tags, allegro)? If there is no coordination between front-ends, how do you get a unified user experience and a consistent design?
- z3t4 10y agoyou can have a design document with examples and inspiration.
- xg15 10y agoYes, but why? This seems to me the same principle as "no libraries, instead keep a spec and re-implement the domain logic in each service" discussed elsewhere in this thread. You still have a common dependency of all services (the spec/design doc) and you'll still have to modify them all if the dependency changes. Except now you also have heaps of duplicate code.
- z3t4 10y agoIt's easy to duplicate code. But hard to delete shared code.