Oliver Geer

Some things like plugins may be backported to v2 where possible, and security vulnerability fixes will be, but where it's too difficult ordinary features or bug fixes won't be.

In the past I haven't used SemVer well; to be honest v2.0 and v2.1 should be treated as part of major version 1, because they contain all the functionality of...

Another core architectural shift that is likely to be in major version 3 is using the `textarea` as the main target on which JavaScript code acts (but still using a...

In the find and replace plugin, debouncing is already implemented, as is limiting of the number of displayed matches (`const CODE_INPUT_FIND_AND_REPLACE_MATCH_BLOCK_SIZE`). There are two further actions that can be taken:...

The match-displaying algorithm will also be a good foundation for the selective-highlighting performance improvements.

Thank you so much! Improving performance should definitely be focused on more here in `code-input` than it has been in the past. Thank you again for all your time and...

Another aspect to improve performance in: > The reason why CodeMirror, Ace, Monaco, and the like can work faster even though they have bigger source code is because they work...

I've started simplifying the codebase using requestAnimationFrame and have moved the scrolling synchronisation to be CSS' responsibility, and it appears to be working well.

Using bounding boxes, editing elements inside the result element directly, and only highlighting some of the top-level tokens chosen by what is visible rather than all of them on every...

@andrelsm the main concept will definitely remain the same - additionally I believe that in Prism.js at least the top-level tokens are free of context so can be highlighted like...