|
dandy72 wrote:
Are they suggesting UWP is no longer a thing?
Confusing. UWP will still exist for Windows Store apps - won't it?
|
|
|
|
|
I can only imagine UWP will go on, it's just that Windows 10 Mobile will no longer be part of the platform UWP apps are expected to be run on.
But who knows...Microsoft hasn't been able to clearly communicate what it is they want us developers to be targeting since (IMO) Windows 8 was introduced, no doubt because they're still trying to figure it out themselves and making it up as they go along.
I miss the WinForms days - honestly.
|
|
|
|
|
|
Only for those who invested in writing apps for it: for the rest of us it's a relief that our platforms won't have to be compromised so badly by the need to support poor-quality mobiles in future.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: poor-quality mobiles
Are you talking about the hardware, or the software?
I can only speak for personal experience, but it seems to me like it's a lot easier to find underperforming hardware running Android than Windows phones. Granted I've only had Android tablets (not phones), but they've all been noticeably sluggish, stop responding altogether or spontaneously reboot. I've seen zero improvement in that regard with my Android 4.3, 4.4 and 6.0 tablets. (Don't get me started on OS upgrades actually being made available...)
OTOH, it took a Microsoft support engineer to point out to me that my Lumia 640 was actually considered a rock-bottom device with little RAM for the OS to work with, because I've very rarely run into some operation that seemed to take an unreasonable amount of time to complete. The UI's always remained fast, fluid and responsive, and I've never had to touch anything twice because I thought it hadn't registered the first time around.
As someone who doesn't look for/install all sorts of crapware, I still consider WP10 to be a perfectly fine OS, and I'd rather keep using it than the crash-prone and downright "glitchy" Android devices I've had the misfortune of been subjected to.
|
|
|
|
|
dandy72 wrote: OTOH, it took a Microsoft support engineer to point out to me that my Lumia 640 was actually considered a rock-bottom device with little RAM for the OS to work with, because I've very rarely run into some operation that seemed to take an unreasonable amount of time to complete. The UI's always remained fast, fluid and responsive, and I've never had to touch anything twice because I thought it hadn't registered the first time around.
I totally agree.
|
|
|
|
|
And yet even Bill Gates and the head of Windows 10 had both switched to Android a while ago ...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
He, no doubt, has more use for a phone than I do.
To put things into perspective, I only bought my first phone less than a year ago, and that's only because it was cheap and upgradable to Windows Phone 10. It has no SIM card, and I don't plan on getting one.
|
|
|
|
|
I'm using a Lumia 640 LTE, and I fully agree with your assessment based on my personal experience.
|
|
|
|
|
|
hope the next visual studio will be less than 20gb and they remove all the related stuff and vms..
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Guy walks into a foobar...
Where is he?
... such stuff as dreams are made on
|
|
|
|
|
Hip-deep in the foo-doo.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Inside the "Matrix".
I am not the one who knocks. I never knock.
In fact, I hate knocking.
|
|
|
|
|
Asia
Format Success.
Welcome to your new signa&*(gD@@@ @@@@@@*@x@@
|
|
|
|
|
Since you said a 'guy' - implies male.
If he eats anything, would that make it a Foo Man Chew?
modified 9-Oct-17 10:24am.
|
|
|
|
|
While reading, whenever I come across the jargon "foo" or "foobar", it throws me off so hard that it takes me about a minute to recover.
And then I wonder, why "foo"?
Somewhere, I saw that is was a toned down version of the WW2 military term FUBAR ( up beyond all recognition).
In the same place, I also saw that it was intentionally used to keep the reader focused on the concept being discussed through the code rather than the code itself.
Any thoughts?
PS: After javascript, it is "Foo" on the hate list.
I am not the one who knocks. I never knock.
In fact, I hate knocking.
|
|
|
|
|
It's one of the phrases that has crept into common use. Newspapers and magazines use the term, seemingly without knowing what it means. These are the same newspapers and magazine that would not print the long version of the phrase.
|
|
|
|
|
Tim Carmichael wrote: It's one of the phrases that has crept into common use. I noticed even SNAFU is used by 'respectable' US broadcasting companies.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
I knew there was another one, but couldn't remember it... thanks for the reminder!
|
|
|
|
|
"Foo" probably does come from UBAR, but "foobar" (or "foo macron") is the mean of the whole set of "foo"s available.
Since in most systems the number of ed items tends to infinity, "foo bar" is generally considered difficult to calculate.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
My upvote for a funny comment. I feel better.
I am not the one who knocks. I never knock.
In fact, I hate knocking.
|
|
|
|
|
There is also some history in the jargon file.
I think they can be less confusing sometimes than single-letter names (a, b, c etc, does not apply to obvious single-letter names such as i,j,k for loop counters and x,y,z for coordinates) or meaningless numbered names (test1, test2, tmp1 .. tmp10).
It doesn't throw me off at all and I am actually confused about how that could even happen.
|
|
|
|
|
For me test1, test2 is actually better. Then I can remember where I am in the code without going back. Foo for me is like smoke, not really concrete in meaning. And that uncertainty throws me off.
I don't know if I explained my point well but I hope you understood.
I am not the one who knocks. I never knock.
In fact, I hate knocking.
|
|
|
|
|
I found this (from wikipedia) fascinating, having grown up as a model train enthusiast with my dad:
The use of foo in a programming context is generally credited to the Tech Model Railroad Club (TMRC) of MIT from circa 1960.[1] In the complex model system, there were scram switches located at numerous places around the room that could be thrown if something undesirable was about to occur, such as a train going full-bore at an obstruction. Another feature of the system was a digital clock on the dispatch board. When someone hit a scram switch, the clock stopped and the display was replaced with the word "FOO"; at TMRC the scram switches are, therefore, called "Foo switches". Because of this, an entry in the 1959 Dictionary of the TMRC Language went something like this: "FOO: The first syllable of the misquoted sacred chant phrase 'foo mane padme hum.' Our first obligation is to keep the foo counters turning."[5] One book[which?] describing the MIT train room describes two buttons by the door: labeled "foo" and "bar". These were general purpose buttons and were often re-purposed for whatever fun idea the MIT hackers had at the time, hence the adoption of foo and bar as general purpose variable names.
|
|
|
|