"Screen real estate"
-
I see the UX guys use this term frequently. Why not just call it "visual estate" or "virtual estate" For example: We need to consider the available visual-estate for the widget. instead of saying, We need to consider the available screen real estate for the widget.
I think you should just go with the flow, it's hard to change commonly used jargon. I always had problems with people saying SEQUEL instead of SQL, but I stopped bothering ... :-\
-
I think you should just go with the flow, it's hard to change commonly used jargon. I always had problems with people saying SEQUEL instead of SQL, but I stopped bothering ... :-\
RickZeeland wrote:
I always had problems with people saying SEQUEL instead of SQL, but I stopped bothering ...
Yes, that drove me bonkers for a year or two, too, but I've got used to it over time.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
-
I see the UX guys use this term frequently. Why not just call it "visual estate" or "virtual estate" For example: We need to consider the available visual-estate for the widget. instead of saying, We need to consider the available screen real estate for the widget.
-
I think you should just go with the flow, it's hard to change commonly used jargon. I always had problems with people saying SEQUEL instead of SQL, but I stopped bothering ... :-\
Those use SEQUEL probably old or learned from old... As today I do not meet anyone using that form anymore...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
-
I see the UX guys use this term frequently. Why not just call it "visual estate" or "virtual estate" For example: We need to consider the available visual-estate for the widget. instead of saying, We need to consider the available screen real estate for the widget.
The problem with "screen real estate" isn't the "real estate" bit, it's the "screen" bit. People should just say "real estate", everyone knows what they mean. Also people should say "sequel" for "SQL".
-
Those use SEQUEL probably old or learned from old... As today I do not meet anyone using that form anymore...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
Weird, all the tech folks that I know call it SEQUEL.
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
-
Weird, all the tech folks that I know call it SEQUEL.
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
- Sequels usually suck. 2) SQL reminds me more of 'squeal' than of 'sequel'. 3) Mickeysoft often makes me feel like squealing. So let's more adequately call it a squeal server and give it our squeal of approval.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
Those use SEQUEL probably old or learned from old... As today I do not meet anyone using that form anymore...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
-
- Sequels usually suck. 2) SQL reminds me more of 'squeal' than of 'sequel'. 3) Mickeysoft often makes me feel like squealing. So let's more adequately call it a squeal server and give it our squeal of approval.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
That would just sow confusion, because we already use SQUIL :/
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
-
I think you should just go with the flow, it's hard to change commonly used jargon. I always had problems with people saying SEQUEL instead of SQL, but I stopped bothering ... :-\
RickZeeland wrote:
I always had problems with people saying SEQUEL instead of SQL
Same here. I have also seen people saying LINQ as LINQUEUE. :doh: But unlike SEQUEL I doubt I will ever get used to this sickness.
You have just been Sharapova'd.
-
I see the UX guys use this term frequently. Why not just call it "visual estate" or "virtual estate" For example: We need to consider the available visual-estate for the widget. instead of saying, We need to consider the available screen real estate for the widget.
Why not display area?, why real estate at all. We're not talking acres or hectares!
I do all my own stunts, but never intentionally! JaxCoder.com
-
RickZeeland wrote:
I always had problems with people saying SEQUEL instead of SQL
Same here. I have also seen people saying LINQ as LINQUEUE. :doh: But unlike SEQUEL I doubt I will ever get used to this sickness.
You have just been Sharapova'd.
Like nails on a chalkboard...
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
-
RickZeeland wrote:
I always had problems with people saying SEQUEL instead of SQL
Same here. I have also seen people saying LINQ as LINQUEUE. :doh: But unlike SEQUEL I doubt I will ever get used to this sickness.
You have just been Sharapova'd.
-
Why not display area?, why real estate at all. We're not talking acres or hectares!
I do all my own stunts, but never intentionally! JaxCoder.com
-
RickZeeland wrote:
I always had problems with people saying SEQUEL instead of SQL
Same here. I have also seen people saying LINQ as LINQUEUE. :doh: But unlike SEQUEL I doubt I will ever get used to this sickness.
You have just been Sharapova'd.
met any of the "see hash" or "see hex" mob yet? heck even had a "see hex symbol" (together with some demented finger waggling) once. thus far luckily never met a "see hashtag" or "see pound" looser yet, but gonna bet they do exist.
Message Signature (Click to edit ->)
-
RickZeeland wrote:
I always had problems with people saying SEQUEL instead of SQL
Same here. I have also seen people saying LINQ as LINQUEUE. :doh: But unlike SEQUEL I doubt I will ever get used to this sickness.
You have just been Sharapova'd.
-
Why not display area?, why real estate at all. We're not talking acres or hectares!
I do all my own stunts, but never intentionally! JaxCoder.com
Looking at the latest phones, I'm not so sure.
-
I think you should just go with the flow, it's hard to change commonly used jargon. I always had problems with people saying SEQUEL instead of SQL, but I stopped bothering ... :-\
If they were consequent in the pronunciation of abbreviations, they'd call the continent the "UI".
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
RickZeeland wrote:
I always had problems with people saying SEQUEL instead of SQL, but I stopped bothering ...
Yes, that drove me bonkers for a year or two, too, but I've got used to it over time.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
i call it sequel just to make people mad at me.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
-
i call it sequel just to make people mad at me.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
I'm actually a bit inconsistent on it, I'll generally say: SQL T-SQL SEQUEL SERVER
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
