Closed FlorianRappl closed 3 years ago
@FlorianRappl
Just my reasons for why I wrote it like this, Feel free to comment on this 😊
in your own articles, you seem to also mostly write it in two words; but I have seen the one word too
No. We always refer to it as "microfrontends" (see piral.io). If its spelled somewhere differently, then this is due to consistency for the respective platform (e.g., on bit dev they write it as two words).
Its just a single word (for the arguments above) - and ThoughtWorks did not coin the term. It was made popular beforehand (if TW brings something on their radar then has somehow been introduced somewhere).
Again you can choose whatever you want. But then you need to write "Micro Service", too. Its either arbitrary terms where you decide whatever or you bring in some consistency.
Just going with what is popular seems like the worst choice (this is why politics usually fails to provide good choices). Reasonable choices always have facts and arguments on their side. There are no arguments for using "micro frontends", there may be some for "micro-frontends", but there are more for "microfrontends".
As I agree with your original reasoning, I will change the spelling in the proposal. I just initially followed what seemed to be the "convention", but to some extent, I agree that this is arbitrary.
https://github.com/DanteDeRuwe/bachelor-thesis/blob/f281fa013250c6ffa5a3800051c4282ea25d5237/proposal/DeRuwe_Dante_BachelorThesisProposal.tex#L50
There are at least three variants out there:
Personally, I'll always go for the latter. The reason is simple: Its also "microservice" and not "micro-service" or "micro service". Having this analogy makes sense and I think having one dedicated name for it also is useful. Also since micro is a unit of measure its usually combined (its also "kilograms" and not "kilo grams". "petabyte" and not "peta byte").