Hacker News Reader

Comment by Tade0 | Hacker News Reader

The Selection API alone is such a minefield of divergent browser implementations that it's a massive PITA.

And that's just the start. Check what happens in different browsers when you hit backspace in a contenteditable containing a single space character.

Overall there are a lot of such changing, undocumented behaviours.

View on HN

I know. The APIs offered by browsers for editing text are less than ideal, and require a lot of work to make something robust. That being said, my point stands. If something is not easy it doesn't necessarily mean that is not worth doing. I have my opinions about how text editing should work in my software, and it is my job to design and develop a solution that fullfills my vision. I will take working around the browser APIs every day instead of fighting a library developed to fullfill a different vision, that adds layers of indirection on top of the same problematic browser APIs.

There's a name for what you're displaying here and it's "Not Invented Here Syndrome".

I strongly advise against this.

Now I am confused. Did you express the same strong advice against doing this to Dominic when they started working on lexical? In the end draft.js already existed. Why reinvent it? How much should we go back in time to find the point when things started to be so perfect to make everything coming after a worthless reinvention? What I think instead is that some developers have a phobia of writing code, and prefer to glue together various pieces to "get the job done". Others enjoy the process of creating something unique and potentially better, for some connotation of "better" that is not to be disputed. I think that there is nothing bad in doing so.

Don't listen to naysayers. If you think you need it, and you want to do it - do it; Always. Failures will make you learn, success is how we progress. Road not taken approach is individual.

Reply on news.ycombinator.com