The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I have been reading this poem for sixty years, and learning ... or un-learning ... every time I read it.
«While I complain of being able to see only a shadow of the past, I may be insensitive to reality as it is now, since I'm not at a stage of development where I'm capable of seeing it.» Claude Levi-Strauss (Tristes Tropiques, 1955)
I can tell you what I got out of that poem in regards to thinking clearly and by extension intelligence... it's something I deal with constantly being in IT. Sometimes the "smartest" people can have the least in life and suffer from lack of experience. You can't very well experience anything but thinking if all you do is think and nothing else. And since experience is the real teacher in life, one has to beg the question if "intelligence" is really intelligent if the cost of too much of it is to have no experiences.
Ironically, whether or not the mind over thinks or under thinks, the result is still being slow in life. Go figure.
And like you, I believe wisdom is what remains after you unlearn what's been learned from the status quo.
If you are developing an app using the UWP platform and Visual Studio 2017, you may run into the same issue I experienced after the VS update of yesterday:
I have been working on a UWP app and could create its installation package without any issues, until VS 2017 was updated yesterday. This morning, creating an installation package caused somewhere between 20 and 30 errors! This same version worked flawlessly before the VS update. The tips from VS were useless: For example: You have invalid Java Script files in your solution. I don't have a single JS file. Yuck!
After some trial and error, (and some cussing, I blush to disclose) I tried the following: I deleted both versions of the Windows 10 SDK I had on my machine and installed only the very latest version (build 16299.15.*****) Voila! Problem solved. Apparently, for reasons I don't understand, the updated version of VS 2017 wants that particular SDK.
So if you are working on an UWP app and the latest version of VS 2017, you may need the very latest Win 10 SDK.
thanks for the update ! I wish I could still blush
«While I complain of being able to see only a shadow of the past, I may be insensitive to reality as it is now, since I'm not at a stage of development where I'm capable of seeing it. A few hundred years later another traveler despairing as myself, may mourn the disappearance of what I may have seen, but failed to see.» Claude Levi-Strauss (Tristes Tropiques, 1955)</
Over the past couple of years or so, my computer became horribly cluttered with all kinds of junk, and lately it started some funky behavior. So I decided to do a clean install of the Windows 10 Fall Update. I downloaded the tool to create Fall Update install media. The systems drive was re-partitioned to meet UEFI requirements. I was doing quite well (or so I thought) until the install was complete and I tried Edge for the first time. Every time I tried to run a search in Edge, the browser would freeze. I couldn't shut it down and restarting the computer had no effect. Edge remained frozen and useless.
You can do just about anything in VB.NET - it does, after all, reference the same framework as any other .NET language. IT may not always be the most efficient language, though for most smaller projects, and esp not involving heavy graphic work, it is just as good as any other.
I'm sure you know all this really. Sorry - but I have a bee in my bonnet about people dissing VB. I see a kind of intellectual snobbery at play when "real programmers" have a go at it, which is quite unwarranted.