...that by offering you new titles so early they are going to lose on all the overpriced cold drinks, and snacks they sell you at the theatre.
This is incorrect. Movie theaters make ZERO money on ticket sales for the first few weeks, then a small portion of the ticket sale, and then eventually a good portion. Pretty much ALL ticket money goes to the makers of the movie.
THE REASON why you have those overpriced drinks and such, is because it's the only source of income for the movie theater itself.
I'm 39, I've been programming since I was 6. I relate to this completely.
I observe, as Alan Kay has observed, that the industry is fad-driven and youth-focused. I remember when Node.js was exploding out, and asking myself, "What's the big deal here?" People were getting insanely excited about...
I think what happens is that young people get into programming, discover some idea, and then hype the fuck out of it. Other new programmers hear this idea, their brain explodes, and they start tapping the shoulders of all the other young programmers. Next thing you know, they all want to learn this programming language and it's the best thing in 4ever.
I have a very hard time getting excited about most "new" technologies; I have a very hard time getting excited about most "new" **ideas.** Reason being: I see very little that is new in them, a lot that is very old, and I see terrible implementations behind them most of the time.
I often find myself asking:
* "Why not just use TCP sockets, cron, and a couple hundred LOC, rather than importing this entire massive technology stack?"
* "I hate to be a jerk, but do you know it should only require about 12 bytes of data to store each entry here?"
* "Have you thought about using shared memory here?"
I see far more work going into sorting out and arguing for technology stack X vs. Y, rather than in what the problem actually is, and what would be the simplest and most direct way of solving it. Then our energy is lost in upgrade hell, attack vectors, and work-arounds for simple things that are very basic but didn't happen to be included in the stack.
I have seen more code written in work-arounds and patches and side-solutions and configuration systems, then it would take to simply just write our own solution -- with total control, all versatility required, easier flow, and far fewer places for bugs and attack vectors to arise.
So, I don't care about New Language X, or New Technology Y. I can learn the pieces of it as needed, but I just can't work up the exuberance for it.
It's hard to imagine the Bernie Sanders campaign growing like it did, without people posting on Facebook about him and his ideas.
#1 point of exposure for me -- was seeing things my friends posted on FB.
Vernor Vinge drew up some diagrams of what this would look like, whereabouts 2005: http://vrinimi.org/front9uns.j...
I'd be interested in seeing a paper that estimates the maximum lifetime of a technological civilization, on the basis that : (A) the estimates given are right about the number of stars, how many habitable planets are in the goldilocks zone, etc.,., (B) we are not atypical, and then (C) that we have not encountered signals from any radio emitting civilizations.
We might find that there would be so many technological civilizations, that technological civilizations should only exist for a few dozen years. Or we may find that they are so rare, that it's extremely uncommon that they overlap, and they may well last for several millennium.
The trouble with a lot of self-made men is that they worship their creator.