Citizen Kane
-
Did anyone mention Sling Blade? EDIT: You might enjoy the Bucket List
The world is a stage and most of us are desperately unrehearsed. —Sean O’Casey, Playwright
I call it a Kaiser Blade. Umm-hmmm.
BDF People don't mind being mean; but they never want to be ridiculous. -- Moliere
-
Nope. I dont like superhero movies either. I liked Eagle Eye, 1408, Amityville horror, pursuit of happiness among the movies I have seen recently. Damn I am watching too many movies and this does not includes Hindi films.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
d@nish wrote:
1408
The book is better. I found the film got boring quickly. (Well the book is actually a short story, it couldn't fill a full novel so not surprising it couldn't fill a full length film)
Simon
-
d@nish wrote:
1408
The book is better. I found the film got boring quickly. (Well the book is actually a short story, it couldn't fill a full novel so not surprising it couldn't fill a full length film)
Simon
Its something that always happens. You a read and then watch a movie based on it. The odds are that you will not like it. It happened to me in Da Vinci Code. The book is far far better than the film.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
-
Yesterday I asked for movie recommendation. (Here[^]). Most of the responses were in favour of Citizen Kane. I saw the movie. My opinion: Its BORRRRRIIIINGGGGG. Just an opinion.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
Old, not-so-old, and more recent movies in this list: M Usual Suspects Dial M For Murder The Sicilian Clan (although French, this movie has been shot in French, Italian and English) Psycho Strangers on a Train The Good, The Bad, and The Ugly Shallow Grave Lock Stok and Two Smoking Barrels Sexy Beast
-
d@nish wrote:
I will be watching Cloverfield
That's probably the worst film I've ever seen!!!
------------------------------------ "...great scott!" Aren't all meetings like this...
It's a stinker all right.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
Yesterday I asked for movie recommendation. (Here[^]). Most of the responses were in favour of Citizen Kane. I saw the movie. My opinion: Its BORRRRRIIIINGGGGG. Just an opinion.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
If you want to watch some decent films, try The Usual Suspects, Crash and American Beauty.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
Yesterday I asked for movie recommendation. (Here[^]). Most of the responses were in favour of Citizen Kane. I saw the movie. My opinion: Its BORRRRRIIIINGGGGG. Just an opinion.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
You all are spoiling me. With these many movies I will have to get better with programming. ;) :-D
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
-
Yesterday I asked for movie recommendation. (Here[^]). Most of the responses were in favour of Citizen Kane. I saw the movie. My opinion: Its BORRRRRIIIINGGGGG. Just an opinion.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
How about The Magnificent Seven which was a remake / interpretation of The Seven Samurai, a very good Japanese film.
"We may not be the smartest in the world, but we're the smartest you've got." -a co-worker, speaking to our manager
-
John Simmons / outlaw programmer wrote:
I watched The Dark Knight last night, and wasn't really that impressed
Ditto. The best bit of that film was the Keith Ledger as the joker, but even he was annoying in that he constantly licked his lips. Batmans bloody lisp was embarassing - when he first spoke in the film at the cinema I thought he was taking the piss, even my gilfriend started laughing. Overly long dull film - massively over-hyped piece of trash.
------------------------------------ "...great scott!" Aren't all meetings like this...
1.21 Gigawatts wrote:
over-hyped piece of trash.
Over-hyped, yes. Piece of trash, not at all. It simply didn't live up to the hype.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Its something that always happens. You a read and then watch a movie based on it. The odds are that you will not like it. It happened to me in Da Vinci Code. The book is far far better than the film.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
Yeah, it's true. I suppose really I should stop watching films based on books. :) (Although 'Atonement' is a good book and film. The film is probably enhanced by reading the book, but both are good in their own right)
Simon
-
Its something that always happens. You a read and then watch a movie based on it. The odds are that you will not like it. It happened to me in Da Vinci Code. The book is far far better than the film.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
Even if done well, a 2 hour movie script only contains about 100 pages of novel material. Making a good 2 hr movie out of a book more than about 500 pages is almost impossible because you have to start cutting into the main plot, not just dropping secondaries.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
Yesterday I asked for movie recommendation. (Here[^]). Most of the responses were in favour of Citizen Kane. I saw the movie. My opinion: Its BORRRRRIIIINGGGGG. Just an opinion.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
(btw. from that list I would have recommended Requiem.) You didn't get it :) Maybe you are just to young. Movies have accelerated immensely in the last twenty years, Even "action-packed thrillers" from the mid-eighties are quite sobering nowadays - and Citizen Kane is way older. Movies from that time had to show and explain a lot more things that are considered "given" today. Also, Citizen Kane is an "epic" movie, in the line of shakesperean historic dramas and Ben Hur. This stuff doesn't go down well with todays "viewing preferences" of short pause-when-you-like bites, catering to the viewer with the dullest imagination, least interest and shortest attention span.* Every major production today puts in a romantic story, most of the time in the center, and most even dead serious topics provide a comedic relief character cracking some jokes. That's what I find BOOOORRRRRRIIIING. I am not blaming oyu, just as I understand lots of our movie preferences are conditioned, and if you don't want to break your comfort zone, you might be missing something. You won't know, but my latest gripe is putting a teenage love story in the center of the new Krabat movie. It's just... WHY? WTF? BURN IN HELL! *) If you are "into" movies old and new you might have noticed that today a single frame and a single chord can set a quite complex mood, whereas old movies need much more time and explanation. Hollywood has trained us to a point where they can tell a story with very few material - and some movies in the mainstream are excellent at that, and lots of artsy-fartsy movies wouldn't work if they couldn't rely on that preconditioning of the viewer.
-
(btw. from that list I would have recommended Requiem.) You didn't get it :) Maybe you are just to young. Movies have accelerated immensely in the last twenty years, Even "action-packed thrillers" from the mid-eighties are quite sobering nowadays - and Citizen Kane is way older. Movies from that time had to show and explain a lot more things that are considered "given" today. Also, Citizen Kane is an "epic" movie, in the line of shakesperean historic dramas and Ben Hur. This stuff doesn't go down well with todays "viewing preferences" of short pause-when-you-like bites, catering to the viewer with the dullest imagination, least interest and shortest attention span.* Every major production today puts in a romantic story, most of the time in the center, and most even dead serious topics provide a comedic relief character cracking some jokes. That's what I find BOOOORRRRRRIIIING. I am not blaming oyu, just as I understand lots of our movie preferences are conditioned, and if you don't want to break your comfort zone, you might be missing something. You won't know, but my latest gripe is putting a teenage love story in the center of the new Krabat movie. It's just... WHY? WTF? BURN IN HELL! *) If you are "into" movies old and new you might have noticed that today a single frame and a single chord can set a quite complex mood, whereas old movies need much more time and explanation. Hollywood has trained us to a point where they can tell a story with very few material - and some movies in the mainstream are excellent at that, and lots of artsy-fartsy movies wouldn't work if they couldn't rely on that preconditioning of the viewer.
I think the biggest barrier to anyone younger than 40 watching any move made before 1980 is the pacing. Things just take far longer to unfold. It's not just time required for explanation, it's simply a completely different attitude towards time. Back then time was spent savoring things and allowing them to unfold in a linear manner. Today time is something to be filled with as much as possible. To watch those older movies you have to be far more patient than is required for almost any other modern form of entertainment. I've been watching a lot of classics from the 40's and 50's lately and I'm old enough to appreciate them but the pacing is incredibly different than modern movies. Some of the greatest movies in history from that era would bomb miserably today just from the slower pacing alone. Even into the late 60's this was the case, watched Bullit the other day from 1968, aside from the car chase (which is justifiably famous) in the middle, the pacing was unbelievably slow by today's standards and it was considered an action movie of it's time. By today's standards the car chase in Bullit would be the absolute slowest part of any modern action movie.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
I will be watching Cloverfield, the most criticized movie in that post, next. Lets see how that goes.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
Those handycam effects might cause you headacke...:~
-
I think the biggest barrier to anyone younger than 40 watching any move made before 1980 is the pacing. Things just take far longer to unfold. It's not just time required for explanation, it's simply a completely different attitude towards time. Back then time was spent savoring things and allowing them to unfold in a linear manner. Today time is something to be filled with as much as possible. To watch those older movies you have to be far more patient than is required for almost any other modern form of entertainment. I've been watching a lot of classics from the 40's and 50's lately and I'm old enough to appreciate them but the pacing is incredibly different than modern movies. Some of the greatest movies in history from that era would bomb miserably today just from the slower pacing alone. Even into the late 60's this was the case, watched Bullit the other day from 1968, aside from the car chase (which is justifiably famous) in the middle, the pacing was unbelievably slow by today's standards and it was considered an action movie of it's time. By today's standards the car chase in Bullit would be the absolute slowest part of any modern action movie.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
I think the biggest barrier to anyone younger than 40 watching any move made before 1980 is the pacing. Things just take far longer to unfold. It's not just time required for explanation, it's simply a completely different attitude towards time. Back then time was spent savoring things and allowing them to unfold in a linear manner. Today time is something to be filled with as much as possible. To watch those older movies you have to be far more patient than is required for almost any other modern form of entertainment. I've been watching a lot of classics from the 40's and 50's lately and I'm old enough to appreciate them but the pacing is incredibly different than modern movies. Some of the greatest movies in history from that era would bomb miserably today just from the slower pacing alone. Even into the late 60's this was the case, watched Bullit the other day from 1968, aside from the car chase (which is justifiably famous) in the middle, the pacing was unbelievably slow by today's standards and it was considered an action movie of it's time. By today's standards the car chase in Bullit would be the absolute slowest part of any modern action movie.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
John C wrote:
pacing
That's the word I was looking for :) But that's not all, you are right - it is not only the necessity for a slower unfolding, but also the attitude towards it: the pacing as a degree of freedom that defines scenes, or movies.
-
Old, not-so-old, and more recent movies in this list: M Usual Suspects Dial M For Murder The Sicilian Clan (although French, this movie has been shot in French, Italian and English) Psycho Strangers on a Train The Good, The Bad, and The Ugly Shallow Grave Lock Stok and Two Smoking Barrels Sexy Beast
-
I found that movie very interesting. The problem nowadays is that people do not want to think anymore, they just want flashing action on the screen. Go get yourself a superhero movie, you will probably enjoy it. Just an opinion.
-
Absolutely (not a movie title, just an expression of my agreemnent with you :cool:)
-
Its something that always happens. You a read and then watch a movie based on it. The odds are that you will not like it. It happened to me in Da Vinci Code. The book is far far better than the film.
C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void "Always program as if the person who will be maintaining your program is a violent psychopath that knows where you live." - Martin Golding
When given a choice, watch the movie first, then read the book to figure out what you just saw. Da Vinci Code is a good example of that rule. As it was, I had to watch the movie three times before I thought I understood it.