It's got to be tough spending a career working on ContentEditable. I don't know how these guys handle it.
Not only do you get to spend all day every day wading through the impossible pile of bugs, contradictions, mutually exclusive implementations and downright wackiness in the thing itself (did it seriously just allow the selection to include the opening DIV tag of the contenteditable itself???), but you get to have the same conversation every day with developers who haven't ever used ContentEditable and therefore consider it to be trivial.
"Why are you implementing the caret in javascript? Haven't you heard of ContentEditable?"
"Why is your simple WYSIWYG editor component seven megabytes of javascript? Wouldn't it be better to just use ContentEditable and be done with it?"
I only had to work with the technology for a few months. Years ago. And I'm still scarred today. Props to these guys for sticking it out!
The CKE people are some of the most hard working devs I've ever encountered in my life. I still find it funny how making little details like backspace/delete key behavior work is such a gargantuan task. And almost nobody gets it right.
I actually applied to CKE as my first job as, having made my own WYSIWYG editor [0] as a side project while I was at school, it seemed like something I had experience of. Never heard back from them: sounds like I dodged a bullet then!
Once again I'm sorry for the lack of reply. Back in I.2013 our team was much smaller and we were overloaded with post release stuff shortly after launching CKEditor 4.0.0. So lots of emails were left unattended :(
Tade0 (buongiorno!) was right that at that time we were not looking for junior developers, but ofc the lack of reply was a mistake on my side.
Yep, I'm working there ;) Please send us the details via contact form https://ckeditor.com/contact/ or feel free to PM me directly at ["w.walc", ["cksource", "com"].join(".")].join("@")
I'm curious, have you ever used TeXmacs? It is, in my non-expert oppinion, by far the best WYSIWYG editing experience (barring some minor implementation bugs). The visual bounding box cues, in particular, make formatting much easier.
I guess it was probably because(to my knowledge) only recently they started hiring junior developers.
Anyway it was a hard and thankless job, but during these almost two years I learned a lot about having an, um, work ethic and doing things to the best of my ability.
Also my current job looks really easy in comparison.
Having did a fair bit with ContentEditable ~13 years go it was downright crazy back then - biggest issue being the wildly different HTML produced by different browsers, which I did handle by server side processing. From what I recall it was nothing but a big bag of special cases.
Not only do you get to spend all day every day wading through the impossible pile of bugs, contradictions, mutually exclusive implementations and downright wackiness in the thing itself (did it seriously just allow the selection to include the opening DIV tag of the contenteditable itself???), but you get to have the same conversation every day with developers who haven't ever used ContentEditable and therefore consider it to be trivial.
"Why are you implementing the caret in javascript? Haven't you heard of ContentEditable?"
"Why is your simple WYSIWYG editor component seven megabytes of javascript? Wouldn't it be better to just use ContentEditable and be done with it?"
I only had to work with the technology for a few months. Years ago. And I'm still scarred today. Props to these guys for sticking it out!