How are web-enabled systems attacked? Of course there are many ways, but first and the most used one method of probing is through reverse engineering output of console.log.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
The console.log is for demonstration purposes, you can just do:
let myNewVar = last
and then return it or use it or whatever, the only bit that is of significance is:
const {length, [length-1]: last} = str
Which I am still processing as Jon always blows my mind with some weird syntax I haven't seen before (or more precisely have seen but don't use so have to then go and do a load of unpacking of his solution 🤣)!
OK. So imagine this:
How are web-enabled systems attacked? Of course there are many ways, but first and the most used one method of probing is through reverse engineering output of
console.log.The console.log is for demonstration purposes, you can just do:
let myNewVar = lastand then return it or use it or whatever, the only bit that is of significance is:
const {length, [length-1]: last} = strWhich I am still processing as Jon always blows my mind with some weird syntax I haven't seen before (or more precisely have seen but don't use so have to then go and do a load of unpacking of his solution 🤣)!
@labspl - I'm not disagreeing with you, but - again - this is entirely irrelevant to the post, or to my original comment
@inhuofficial I aim to please :)