4 ms·

I worked with early Polymer versions for about a year on a pilot project and loved the technology and implementation. Conceptually, I think its superior to lot

• krasicki 7y ago
  Shocker: https://micro-frontends.org/ https://micro-frontends.org/
  • ehnto 7y ago
    That article seems to confuse project management issues with architecture I think. Who in their sane mind would recommend using three different frontend frameworks living in one codebase? Who inevitably wraps it all together, Team Mop Bucket? What would the build pipeline look like and who maintains and fixes that? Monoliths still work if managed correctly. You can even organise code to get similar isolation as a microservice but still in the same codebase and tooling. If you find yourself looking into "micro services but it's frontend components" then I think you need to look at hiring a technical lead who can see a bigger picture architecture for everyone to work in. One of the benefits of consistent tooling and frameworks is knowledge sharing and mastering your tools as a company. If everyone is using different tools then you have created fragile knowledge silos throughout your company and you don't get that hive mind mastery of the tools, where there is always someone who knows what the right approach is.