Am I the only one? Am I a shit swe?
Edit - comments seem to suggest I was asking this question seriously. I was not, I was just (sort of) joking.
That being said, front end engineering is rapidly changing all the time, so the confidence I have in knowing I will always have work to do (read that to mean: a job) is satisfying.
If you find yourself struggling to articulate it, seriously and honestly consider whether you’re simply choosing to be stressed about it.
I’m speaking from experience here.
Then when I see it in the code, I'll know what it does or I'll be like "Oh wait, that new feature I read about, maybe that could be of use here".
I'm never going to remember everything and I'm okay with that :)
I mean they are adding features like static initialisation blocks when we only just got String.replaceAll(), and they somehow managed to fuck that API up despite it being explicitly a replacement for an existing bad API!
Where are all the containers? Sorted sets/maps? Why can't I even map an iterator?
That's W3C’s job, not ECMA’s.
> Where are all the containers?
?
> Sorted sets/maps?
Sets and Maps are sorted (by insertion order)
> Why can't I even map an iterator?
It's coming, but someone will likely be exhausted by that addition. https://github.com/tc39/proposal-iterator-helpers
That's not what a "sorted set" is. C++ and Rust provide sets (and maps) that sort based on an arbitrary comparison operator.
> ?
?
> but someone will likely be exhausted by that addition
I suppose. I guess it's one of those things that they really should have got right the first time. Like String.replaceAll(). I guess they will never add String.replaceAllSafe() - well just have to rely on linters to tell us that the API is terrible forever.
[1] https://docs.oracle.com/javase/7/docs/api/java/util/SortedSe...
My biggest learning while writing this was just how much is possible in JavaScript and TypeScript now, but I also realize that a lot of this I will not use myself or only use to understand some really specific code.