Interesting, but nothing new. Shodan users have known about clueless IP camera owners that leave their cameras on the public internet for years. This is a little more interesting because it's from a well-funded startup rather than independently owned Chinese IP cameras.
The old PIPS ALPR devices aren't online anymore but they had horrible security as well. Just sending a newline to their UDP port would cause them to send you all images as they were being collected in real-time - no authentication needed. And the images had the license plate information encoded in the JPG metadata. I did a talk about it at some point (https://imgur.com/HHcpJOr) and worked with EFF to take them offline
What always strikes me these days, is how old film is now. This "attractive young lady" is likely in her 80s or 90s, if she's still among us. EG, let's take 2025 vs 1965 + 25 years.
There was a time when paintings were the best we knew of the past. Then blurry photos, but we're now over 100 years of motion pictures. Our ancestors had no capacity to see the past, as we have.
I do my best to not blame the past, for most in it were simply ensconced in the culture and mores of the time. And it makes me think that quite surely, many things we do today will be seen as quaint, or improper 100 years from now. Certainly our descendants will think us uncouth, and over things we imagine as proper today. Things we think of as "doing the right thing", will be seen as uncouth, horrible, perhaps vile to our descendants.
Take this out of context statement about the young lady (the context being "the era of the 60s"). Back in the day, women expected such complements. They also expected doors to be opened for them. Chairs pulled out. For a man to stand whenever a woman was to be seated.
In this film, the gentleman says "why are we looking at this woman", yet also felt obliged to couple that with a conditional "she's attractive", for it could be misconstrued as "OMG, why am I looking at this hag!". Societal politeness dictated he do so. He would be doing the young lady a disservice, and seen as impolite by his peers did he not. And further, she'd expect it as her due.
I find today that often people take so many things out of context, from the past. Judge without knowing the circumstances (not saying the parent is judging here). We should understand context, culture, history, before pointing I think.
In the context of the film this has has little to do with politeness. The executive goes on to says of the film "It has to "STIMULATE these men who know far more about the HARD facts of their business".
The woman isn't in the room with the men so you are saying he's being polite to film footage. This is an unintuitive argument.
If you want to test your theory bring up a game show from that era and see if the male host says "You are attractive" to every young female contestant.
If you don't think that's the same thing the dialogue is too idiosyncratic to be explainable in reference to normal social mores.
Yes I read your post where you claimed "Back in the day, women expected such complements"
Either you meant women expected such compliments broadly (as in a game show) or you meant women expected such compliments if featured in the intro of an IBM OCR documentary where a man shows confusion about a woman on screen.
The latter interpretation is ridiculous, yet here we are.
You seem to have missed the context in the post you replied to, and the original. I've said it several times, he said effectively "why am I looking at this woman", but countered with a complement to ensure his statement was not taken incorrectly. EG, he had no issue with the woman in film visually.
You should not be confused, for politeness is not a thing easily turned on and off. It is often automatic. Further, a film is shown to contemporary audiences, and those viewing, audiences of less sophisticated times with media, may find his comment rude otherwise.
Viewing another culture is difficult at best, but I find it more so when it's your culture yet shifted by time or location. An example being British vs US culture.
The statements are the same, but sometimes subtly the meaning not.
Peering into the past is much the same. The language seems the same, but what is conveyed is sometimes different.
I think you're really missing my point, and not really attempting to view this 60 year old film as I suggest culturally.
Regardless, the main point is... viewing the past needs to be taken without finger pointing.
I don't think there is much value responding beyond what I've said. You appear to be slicing concepts out of the whole, and responding to only those portions.
However I don't believe I misunderstand your point. The dialogue is almost certainly scripted, presumably by an advertisement professional. You believe you know why the advertisement person wrote it that way. You think the man was scripted to be "polite" to the woman he was watching in the context of the scene and that particular line. You think your understanding of the society of the time explains the line.
I offered an alternative interpretation. The advertisement professional wanted to begin with something winkingly sexy so had a bunch of guys say a woman was attractive.
I don't even know what to make of the statement that "for politeness is not a thing easily turned on and off." A stock character in an IBM ad doesn't have an internal life so does not struggle to be polite or impolite.
This whole framing would make more sense to me if we were talking about a male game show host (a real living breathing person) trying to be polite to a real life female contestant in an old game show.
Steve Jobs once came to speak at my company when he was running NeXT. Almost nobody came to the talk, in the company cafeteria. The CEO of our company had to make an announcement on the PA encouraging folks to come. Finally, about 20 people (out of ~750) showed up.
He started talking aobut Objective-C and how it was 10x more productive than other programming languages and how easy it is to write good applications quickly with it. Someone shouted out the question: "If it's so easy and fast to write applications, where are all the NeXT killer apps?" There was no good answer....
Killer apps aren't always survivors. Consider how Visicalc fell to Lotus 1-2-3, and how Lotus 1-2-3 fell to Excel. Arguably, the killer app for NeXT was WorldWideWeb. While it's successors weren't developed in Objective-C, the prototype for the world wide web was.
Objective-C itself didn't have much of a chance for many reasons. One is that most APIs were based upon C or C++ at the time. The availability of Objective-C on other platforms will do little to improve productivity if the resulting program is essentially C with some Objective-C code that you developed from scratch yourself. Microsoft was, for various reasons, crushing almost everyone at the time. Even titans like DEC and Sun ended up falling. Having a 10x more productive API was not going to help if it reached less than 1/100th of the market. (Objective-C, in my opinion, was an interesting but not terribly unique language so it was the NeXT API that offered the productivity boost.) Also keep in mind that it took a huge marketing push for Java to survive, and being platform agnostic certainly helpted it. Seeming as Java was based upon similar principles, and a more conventional syntax, Objective-C was also less appealing.
I think the claim was not that the NS* API of NextStep was "10× more productive" but that the Objective-C programming language was. Objective-C is fantastic at calling existing C APIs. It's even easier than doing it in C# or LuaJIT, and much easier than doing it in Python, Perl, Tcl, Java, JS, etc.
You're right that there are programs that are just a thin layer of glue over existing C APIs, and the existing C API is going to largely determine how much effort that is. But there are other programs where calls to external APIs are only a small fraction of the code and effort. If OO was the huge productivity boost Jobs was claiming, you'd expect those programs to be much easier to write in Objective-C than in C. Since they made the choice to implement Objective-C as part of GCC, people could easily write them on other Unixes, too. Mostly they didn't.
My limited experience with Objective-C is that they are easier to write, just not to the extent Jobs claimed. OO makes Objective-C code more flexible and easier to test than code in C. It doesn't make it easier to design or debug. And, as you say, other languages were OO to a similar extent as Objective-C while similarly not sacrificing efficiency, such as C++ and (many years later) Java and C#.
I think there's a good answer to that: to a first approximation, no one bought NeXT machines; therefore, there was no demand for NeXT apps and therefore no one produced any.
But it's unlikely that Steve Jobs of all people would want to provide that explanation.
Around 2001 my company sent me to a training class for Objective-C and as far as I can remember, it's like a small tweak of C++ with primitive smart pointers, so I doubt that it's 10x more productive than any other language. Maybe 1.01x more productive.
That is not correct. Objective-C has a completely different OO system from C++. All they have in common is that they're both extended subsets of C. Retain/release are also not smart pointers; Objective-C doesn't have the C++ features needed to implement smart pointers.
Objective-C++ is a different matter, but it was written many years after the time we are discussing.
I apologize that my memory has faded over the intervening 25 years.
What I do remember is that it's an odd language, but nothing about it suggested that it would even be 2x more productive than C or C++ or Java.
I didn't get to use it much after the week-long class; the only reason the company sent 3 of us across the country for a week is because the CTO had a bizarre obsession with Objective-C and OS X.
I think it's universally agreed at this point that OO didn't provide the order of magnitude improvement in software development velocity that Jobs was touting. I do think ObjC is more flexible than C or C++.
reply