When I was leaving a previous job, I watched my replacement put in a bloated as fuck .svg file embedded directly into the HTML… within that, was multiple base64 encoded uncompressed .png images. All to do a spinny animation you can whip up in 1 second with CSS transform transition. When I said that, they were confused because they didn’t even know what CSS is, they just use tailwind. Apparently writing your own CSS is firmly old school nowadays.
There is zero cares about performance anymore, nobody gives a fuck. Phones are powerful, internet is fast. Yeah sure let’s dump in this 80mb bloated nesting doll abomination above the fold directly in the HTML so it’s never cached and downloaded every time and bloat the images by 33% because base64 does that. When I raised my concerns I was dismissed because it looked good. That attitude was part of the reason I was leaving. Most websites are awful div soup nowadays with 10 frameworks up their asses. The first thing I do when I help people with their code is delete 60% of it.
Sorry, I still am upset by the direction the web dev industry was going.
Nothing is wrong with that, but it will give you different output. I tend to like using capture groups just out of habit, it makes it more flexible and useful in future. Most of my co-workers hated Regex so I tried to make it easy for them.
I also wanted the letters to be as close together as possible. In this example it doesn’t matter, but in other texts it might. Yours will find the first y, then the furthest possible e, then the furthest possible s. So you might get output where there’s a y on line 1 and the e s at the very end of the text. Nothing wrong with that, it’s just not what I was envisioning.
Also it’s funnier in this context to have a complicated regex.