Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Is it really necessary to differentiate one from the other?
Didn't check the code yet but you may be fine using just a single js/ts lib and create different usage documentation for different frameworks/libs.
Or is that you mind to provide components directly instead? I'd need to check the details but usually a component is just a function so you should be fine here as well with a single lib to maintain.
Full Stack Developer, mainly working in .NET with web technologies and mobile (Xamarin).
WWDC14 Attendee, when Swift was presented, a bit rusty but can work in Swift too.
I preferred with prebuilt components so they're easier to use and the user has to read only few lines of code instead of the library usage code that could be more difficult to comprehend.
Every component is different from others because I try to use every feature that I know that library/framework has, for example in Angular there's a native check of SSR, in React I'm deep checking the options changes, and so on...
This gave me also some liberty on the components' code since I could improve their code without updating the documentation.
And last but not least, I prefer to have everything built in the same repository instead of having developer x or y that creates an "unofficial" component, so I can give support on everything I've made, otherwise I have to explain what was changed and why everything broke. I already tried that way and it was a mess, just because the unofficial component used some different default values.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Is it really necessary to differentiate one from the other?
Didn't check the code yet but you may be fine using just a single js/ts lib and create different usage documentation for different frameworks/libs.
Or is that you mind to provide components directly instead? I'd need to check the details but usually a component is just a function so you should be fine here as well with a single lib to maintain.
I preferred with prebuilt components so they're easier to use and the user has to read only few lines of code instead of the library usage code that could be more difficult to comprehend.
Every component is different from others because I try to use every feature that I know that library/framework has, for example in Angular there's a native check of SSR, in React I'm deep checking the options changes, and so on...
This gave me also some liberty on the components' code since I could improve their code without updating the documentation.
And last but not least, I prefer to have everything built in the same repository instead of having developer x or y that creates an "unofficial" component, so I can give support on everything I've made, otherwise I have to explain what was changed and why everything broke. I already tried that way and it was a mess, just because the unofficial component used some different default values.
Oh got it! 😁