395 karma · joined December 1, 2013
I suppose it comes down to emergent phenomena: what's the lowest-level concept you HAVE to invoke to understand what's going on here? when you want to explain how taste buds work, you can talk about neural paths and chemical chains, and even though each of those things relies on quantum physics to exist, you don't have to invoke the concepts or objects of the quantum world to understand the phenomenon in question. but with this particular phenomenon, you do. you can't just explain how this works with higher level concepts, you have to get low down.
We are the future generation, and there is in fact prison slave labour now. It's directly on topic.
I was able to retrieve the full final content from the place where it was being uploaded to, but that didn't have any git-related files.
I got a new computer and when I was getting rid of my old one, it didn't occur to me to push all the commits or save the git repo. So, my next commit consisted of all the changes for that entire month.
Worse is that some writers seem to mix it up, use both periodically.
They mentioned pronunciation : 'S-Q-L' vs 'sequel'. I've always pronounced it S-Q-L. The lecturer implies there's no right answer, that 'sequel' is historical but 'S-Q-L' is preferred for international use.
The annoying thing, though, is that in writing a choice has to be made. If someone pronounces it 'S-Q-L' then to read 'a SQL query' is weird -- it should say 'an SQL query'. And vice versa for someone who pronounces it 'sequel'. 'an sequel query' isn't right.
So, in writing, what is correct? 'An sql query' or 'a sql query'?
Eg there's the 'parasitic instantiation' and then there's the 'Constructor pattern' and then there's the 'Parasitic Constructor', and there's like 3 other patterns that have their own permutations. Coming from Python and then Java, where classes just work...it's kind of annoying.
[edit] I was being a bit hyperbolic, the book discussed 6 ways of inheritance in JS, those being (1) Prototype Chaining (2) Constructor Stealing (3) Combination Inheritance <- most popular one according to the book (4) Prototypal Inheritance (5) Parasitic Inheritance (6) Parasitic Combination Inheritance <- pattern that is generally the best according to the book