very nice article. :)
liability. this is a great analogy for opening the code… for how people see it today.
but opening up should always be seen, first, as a blessing: if you create any piece of software that people want to contribute with their time writing code “for free”, how can we look at it in…
you probably don’t care about this, jessica… but i’ll try it anyway.
if i write too much, you won’t find time to read. too little, won’t find will.
truth is i don’t know why i’m getting in touch. i like to think it’s one way i contribute to the grand scheme, with random iterations like this.
what a great story! loved the 10⁴⁵ number and how the rainbow that goes down to just 10⁹ (should be noted that even tetrachromats won’t see much farther from that since the 4th cone adds almost no more range and 10¹¹ is just actually bad math).
too sad it doesn’t paint the whole picture. nor is it comprehensive enough, imho…
i would argue the only downside to client-side rendering is complexity.
you just admitted that the SEO is not an issue if implemented correctly. also, we can easily add server-side rendering to client-side, not so much the other way around. this can easily fix any SEO issues and even offer an alternative method for loading…
let doesn’t allow for re-initialization anywhere within the same scope, while
var allows it. this can be especially troublesome for testing things on the console, for instance.
couldn’t agree more. for any kind of interview, for that matter (not just devs)! here’s an idea, though… how about telling them the following?