Monica Dinculescu (@notwaldorf on Twitter) works on the Polymer team in Google and is an expert in emoji and how to make them appear correctly in browsers – or not.
If you prefer to have an audio version, you can download it here (MP3, 30MB)
The interview was a whirlwind of information, but here are the questions we asked:
- You recently gave a talk where you criticise the INPUT element in almost painful detail. What’s the problem with it?
- HTML5 is 8 years old. Obviously a lot of what the spec promises in terms of form inputs is broken in implementation. How come we missed this?
- The promise of input is that it falls back to a text field in browsers that don’t support the “new” types, but that doesn’t seem to work, right?
- Whilst there are a lot of issues with “new” form elements, there were not many complaints to browser makers. Is the reason people using UI libraries instead?
- Web Components were the answer to a lot of these issues. But it seems that without libraries like Polymer, they are not usable, or are they?
- Originally the idea was to use the “is” attribute to extend existing HTML elements to become components. That’s a problem, right?
- Web Components excel in their modularity. This means, however that each of them have their own HTML,CSS and JS. Doesn’t that mean there is a lot of repetition and more code than needed?
- One of the criticisms of Web Components is that they are too powerful. People can hide a lot of functionality and code in a single element. Is that a problem?
- It is of course up to developers to chose the most performant and well-written component. But history showed us that people tend to prefer generic and pretty solutions. How can we prevent this?
- Are we building too many things with the premise to impress each other rather than building things that are really usable by others?
- Is the confusion about Web Components seeing the web as a collection of components rather than documents that link to each other? Should we reconsider what the web is? Do new developers think in components?
- Do we need more poster child applications that use Web Components in the wild? Who does?
- If you were to talk to a new developer who wants to start with the web, what are the things you have to know right now?
- How do we deal with legacy and backwards compatibility? Is this much less of an issue than we make it out to be?
- There seems to be a wrong perception that standards are a clean-cut and reliable thing, but even those have had a messy history, right?
- Has it become more complex to be a web developer? Does the idea of the extensible web manifesto make it harder to keep up?
If you are interested in seeing the talk we referenced here, you can check it out on Vimeo.