|
I would be more curious how popular that specific question is on google.
I couldn't find an answer to my question. I did find the Wikipedia page for the OP question. Wikipedia was launched in 2001 and the page for that question was added in 2005.
And then I thought about looking up the oldest page
Wikipedia:Wikipedia's oldest articles - Wikipedia[^]
Kind of interesting not because of the pages but rather the history of why they really have no idea what the original page was.
|
|
|
|
|
So I am not the only one asking about that  Now that there are two of us, I took the time to see if Wikipedia could help me, and found this:
Due to trailers initially being shown after, or "trailing", the feature film, the term "trailer" was used to describe the promotion; despite it coming before, or "previewing", the film it was promoting. This practice was found to be somewhat ineffective, often ignored by audiences who left immediately after the film.
So, historically, they were trailing the main feature. Thanks for making me look it up
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Thanks for doing the legwork on that 
I suspected as much.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Well, at least until someone comes up with a dumb name for them, like "prequel".
Preler?
modified 2hrs 5mins ago.
|
|
|
|
|
Nowadays they're also called teasers, isn't it?
|
|
|
|
|
|
Thanks. Never knew the technicalities of these terms.
|
|
|
|
|
...and then, there are teasers that reveal so much they might as well be called trailers.
There's probably a fine line between the two.
|
|
|
|
|
They're meant to tease you.
And there's a tease in every trailer court.
Hence trailer, because they called call them ho's.
If you can't find time to do it right the first time, how are you going to find time to do it again?
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
this_guy_tho.jpg[^]
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
 Maybe it’s one of those Impossible dogs (that got Joey Chestnut disqualified from the main event)
TTFN - Kent
|
|
|
|
|
 when i first looked i thought it said vegan. could have been a vegan burger.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
It does say vegan. I was joking about it saying Megan.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Perhaps the tat on the other arm says "never"? 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Stadium hot dog?
Yeah, I'd be willing to bet there ain't much meat in those.
|
|
|
|
|
I always tell my vegan friends that McDonalds should count as vegan.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
The shortest horror story: On Error Resume Next
|
|
|
|
|
I've always thought exactly that.
Except I don't have any vegan friends. At least, not any self-admitted ones. That I'm aware of.
|
|
|
|
|
I'm creating a data bank of MCQ (Multi Choice Questions) and their answers so that an app can be built around it. Regarding the actual storage format, I have two ideas:
- An array of objects with keys (
q for question, a for choice-a, etc.). - An array of arrays.
The first one is obviously more readable. Here is a brief sample of what I have so far:
{
"data": [
{
"q": "What kind of language is Python?",
"a": "Compiled",
"b": "Interpreted",
"c": "Parsed",
"d": "Elaborated",
"r": "b"
},
{
"q": "Who invented Python?",
"a": "Rasmus Lerdorf",
"b": "Guido Van Rossum",
"c": "Bill Gates",
"d": "Linus Torvalds",
"r": "b"
}
]
}
The app will read the q key to print the question, then present the four options (a, b, c and d). And the last key (r) will store the right answer. This is very much readable when viewed as a JSON file also. However, what I am thinking is that once the data-bank grows in size into hundreds/thousands of QA, a lot of space will be wasted by those keys (q,a,b,etc.) isn't it? In this case, an array like this is more efficient from storage perspective:
{
"data": [
[
"What kind of language is Python?",
"Compiled",
"Interpreted",
"Parsed",
"Elaborated",
1
],
[
"Who invented Python?",
"Rasmus Lerdorf",
"Guido Van Rossum",
"Bill Gates",
"Linus Torvalds",
1
]
]
}
In this case, each array will have 6 items viz. the question, four choices and finally the index of the correct choice (1==Interpreted, etc.).
Which of these two formats is better? Feel free to suggest any third format which is even better than these two.
|
|
|
|
|
I like the 1st better.
The 2nd, for me anyway, would be harder to keep track of square brackets.
If you can't find time to do it right the first time, how are you going to find time to do it again?
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
|
First, the question should probably be asked in "Design&Architecture[^]" forum.
Second, my preference would be for something like:
{
"data": [
{ "q": "question",
"a": ["answer1", "answer2",...],
"ok": 1
},
...
]
}
---
Edit: My suggestion allows you to have a variable number of answers to each question. Not sure if it's important or not for your application.
Mircea
|
|
|
|
|
Neither. Unless your married to the idea of encoding the indexing, I'd go with something like this personally based on the info given:
{
data: [
{
"question": "What kind of language is Python?",
"answers:": [
{ "answer": "Compiled", "correct": false },
{ "answer": "Interpreted", "correct": true },
{ "answer": "Parsed", "correct": false },
{ "answer": "Elaborated", "correct": true }
]
},
{
"question": "Who invented Python?",
"answers": [
{ "answer": "Rasmus Lerdorf", "correct": true },
{ "answer": "Guido Van Rossum", "correct": false },
{ "answer": "Bill Gates", "correct": false },
{ "answer": "Linus Torvalds", "correct": false }
]
}
]
}
Handles questions with multiple correct answers, and both questions and answers are easily expandable without breaking backwards compatibility. The biggest issue with your options is that the moment the requirements change (and requirements /always/ change) the format is going to get mangled in a non-backwards-compatible way. Your current format cleverly avoids objects/properties to save space by treating the head and tail of each array uniquely. What happens when requirements dictate that relationship can no longer hold? For example, questions with multiple correct answers. Cleverness is an avoidable dependency, so unless space is that critical of an issue I would tend to go with the more flexible option that gives me less headaches down the road.
|
|
|
|
|
Of the options provided so far, that gets my vote. And I'm too lazy to suggest my own.
|
|
|
|
|
| #1
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I read the thread in The Insider News tracking off to the novel 'When Worlds Collide', and looked up the 1951 movie adaptation at IMDb, curious to see if they had made the movie in color or B/W. The movie is in color - but the 1954 ad poster reproduced in Wikipedia, as well as all the photos from the movie shown at IMDb is is in black and white.
Why is that? Was is really that much more expensive in 1951 / 1954 to make color photo prints and color ad posters that you couldn't afford it on a USD 1M budget (note that this is 1 mill 1951 USD!)? Or is there some other plausible explanation?
According to IMDb, the movie won an Oscar for Best Special Effects. The trailer (available at IMDb) suggests that the Oscar was well deserved, especially for a movie released 73 years ago!
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
