|
A late reply. I have used it to go from SSD to SSD and HDD to HDD but not HDD to SSD. Works fine.
Lou
Arguing with a woman is like reading the Software License Agreement. In the end, you ignore everything and click "I agree".
Anonymous
|
|
|
|
|
I have been buying Nike Air Monarchs for several years; good quality, good price, they last several months, and they fit the way my feet interact between the ground and my legs.
I welcome ideas from anyone who has worn this shoe for a long time (e.g., more than a month) and has tried another brand/style.
|
|
|
|
|
I have been wearing Nike Air Monarchs for years also. For me, the fit is excellent. The price is really good. Overall, for the money, a really good shoe. Not a lot of complaints.
The only thing that I don't like is the fact that I cannot remove the insert and replace it with a better insert. Most running shoes allow you to replace the insert. Also, running shoes like Asiics, Saucony and I am sure others seem to have a little softer sole which I like.
|
|
|
|
|
For casual walking, I like Camper, Merrell and KEEN shoes.
I've used shoes from the above companies for years now.
BUT,
A couple week ago, I was in Spain and mostly used my Asics shoes because my other shoes were leather and too warm.
I'd rather be phishing!
|
|
|
|
|
If I post some code here and articles would people be interested in UWP? I have some file API's and sample code that could help people. To be honest, I like UWP file operations but they are slightly weird. At the same time have great ways to do chain folder/file creation operations which I like and you can create the simple Append to end of sub/function like before but its a little different then before.
Note:
1. I understand peoples problems with windows 10 updates but I have not had any problems with my updates with the exception of office 2010 because its so old windows will not install them properly the first time.
2.If you install visual studio at all, remember to install the Hypervisor for windows first because it uses that to test windows phone apps and needs time to run before you install studio.
jeffery
|
|
|
|
|
The whole ms uwp concept is a huge waste of a lot of people's time.
Like everything else they've produced over the last few years, they came up with it without even thinking about keeping their feet grounded in reality, and all they've done is take phenomenally uncreative steps (which they probably think are highly creative) in a direction that cannot possibly be the way to the future.
What is currently being done by weChat and facebook is one of the potential roads to "universal" computer products. That much is obvious, because many of the roads in that direction are patently obvious -- it's just a matter of waiting to see who will get it all to come together.
But that won't be ms. Their idea of "universal" is crippled by their new-found lack of vision and creativity. It's a joke, which will be swept under the carpet, within a couple of years (joining all the other dustballs they've previously hailed as the next great thing), and the people who suffer most because of this will be developers who invest their time, skills, and effort into it.
Seriously, you'll do your career better by studying COBOL.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
 Quote: The whole ms uwp concept is a huge waste of a lot of people's time.
Like everything else they've produced over the last few years, they came up with it without even thinking about keeping their feet grounded in reality, and all they've done is take phenomenally uncreative steps (which they probably think are highly creative) in a direction that cannot possibly be the way to the future.
What is currently being done by weChat and facebook is one of the potential roads to "universal" computer products. That much is obvious, because many of the roads in that direction are patently obvious -- it's just a matter of waiting to see who will get it all to come together.
But that won't be ms. Their idea of "universal" is crippled by their new-found lack of vision and creativity. It's a joke, which will be swept under the carpet, within a couple of years (joining all the other dustballs they've previously hailed as the next great thing), and the people who suffer most because of this will be developers who invest their time, skills, and effort into it.
Seriously, you'll do your career better by studying COBOL.
I think I will be fine. COBOL is fine until the government upgrades their mainframes then your out of those jobs and so goes windows XP out the window as well. If you watch ZDNet newsletters or MSN news closely, the mainframes for the nuclear launch systems are being replaced so COBOL will not be used as much anymore. On another note, this is the same talk as windows ME/2000 to XP (i.e. it sucks, too ugly, etc.) which was general Banta fodder and does not talk about the nice improvements at all (i.e. Task Scheduler was great but windows 7 was the best, minimal install footprint for what we were offered, etc.).
Anyways, would anyone want me to post articles on it? I am thinking posting an article despite codeplex shutting down. A lot of it is easy and I have a custom folder path/file based on date created in my current app (i.e. April 24 translates to this file path ..\archives\April\24{name of item searched for}.csv or whatever extension you want).
So, I plan on helping out anyone wanting to take the path of UWP. I am trying to pass Iprogress status in a UWP class library or dll to my main which I do everything out of and so far I cannot seem to get it to work.
P.S. if your wanting to avoid UWP I believe they are still having the developer program for publishing non-UWP apps to the windows store (aka windows only apps). If your a c/c++ native dev. support has been around for a few months now for windows UWP apps to skip at least part of the dotnet framework.
jeffery
|
|
|
|
|
jeffery c wrote: COBOL is fine until the government upgrades their mainframes
"Until".
So, after forty years, it's still "until". Uwp will be lucky to last a tenth of that.jeffery c wrote: On another note, this is the same talk as windows ME/2000 to XP (i.e. it sucks, too ugly, etc.
That's not even remotely the case.
The uwp platform is based entirely on moving all windows products to mobile-phones, not on anything that deserves the term "universal".
What ms "universal" therefore came to mean is "limit all apps on all hardware to the requirements of mobile phones", so, for example, people with huge, expensive monitors were forced to use them as if they were tiny phone screens, because you can only use one app at a time, on a phone.
Nothing that the current management of ms "innovates" is worth investing (read: wasting) your time and effort on. Wait until they get kicked out and replaced by people who've got a clue.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
You have no idea about UWP do you? I rarely develop for windows phone and use the desktop extensions of UWP to skip said non-sense and games for xbox is why I chose it but you can even get around that for xbox one to a certain extent.
Anyways, I basically said you could still develop dotnet framework applications because UWP is a "choice" if your developing for windows 10 not a mandated requirement. Microsoft makes it seem that way but it is NOT. If you believe otherwise Microsoft has fooled you. VB.NET forum is going very well because their are still dot net developers on windows 10.
jeffery
|
|
|
|
|
jeffery c wrote: VB.NET forum is going very well because their are still dot net developers on windows 10.
VB and Windows 10!!!
Please say it 'ant so.
OK, you can dev for uwp with vs, but unless that app can natively move to phone, xbox, surface how does the "U" still stand.
I can put a hi-res mountain photo background on my pc but that doesn't make it a mac.
So why make apps look lie uwp if they're not? That's not lipstick on a pig, rather that's pig-sh*t on a horse.
Sin tack
the any key okay
|
|
|
|
|
Their is c/c++ programming forums too. That was a typo. But your a skeptic so try out UWP for yourself. Just remember about what happened to assembly language. All the years wasted to only be replaced with c/c++. However, I prefer vb.net for most apps because their is not a lot of difference to c# with the exception of games/hardcore apps which I prefer to go to c/c++. I found out with a little help on vb.net forums about how to call do p-invokes on device drivers. Only can be coded in c#? No. For the most part, you can code in native c/c++ for apps.
jeffery
|
|
|
|
|
jeffery c wrote: Just remember about what happened to assembly language. All the years wasted to only be replaced with c/c++
OK, I'm voting for that as daftest question of the month. Maybe the year, but it's only April.
What I can't tell is if you're:
0. A newbie, who's only seen a few shinies, so far, and doesn't know about the far-shiniers that are also available.
1. Just another ms wu-mao.
Note: I don't need you to tell me; I'll see for myself.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
jeffery c wrote: Just remember about what happened to assembly language. All the years wasted to only be replaced with c/c++.
Could you elaborate on this? Or are you just using it in a poor attempt at reductio ad absurdum?
|
|
|
|
|
No, this is really referring to a difference of opinion not absurdity. Because a programming language being irrelevant is bases on overall demand and assembly language and/or fortran or any other language is used in specific scenarios. Those 70-80's languages are only used in nasa mainframes or any mainframe which are mostly irrelevant because of the training tine required to show people how to use one. Time sharing was a big problem because once an connection was established to the machine you could only have a handful of connections depending on the setup. This slowly changed but initially was not. Look up thee enaic computer.
jeffery
|
|
|
|
|
jeffery c wrote: Those 70-80's languages are only used in nasa mainframes
I'm with you that some languages have become less popular, even to the point where they could be called esoteric. Though I'd draw a line at calling them irrelevant.
Perhaps something like Fortran / Cobol tends to be used just (or rather mostly) in legacy systems yes - does that make them irrelevant? Assembly is still used though, quite a bit in fact, wherever you see hardware with extreme limits in resources you're sure to see at least some ASM codes (even in lieu of C), think stuff like a washing machine controller. Another place it gets used often is drivers. Also this new "fashion" of IoT is a prime place for ASM to help out where a higher level language just doesn't provide the full control. And then there's still those who go and optimise after a compiler's done its best.
Not to mention, in some cases certain things are just impossible to do in the higher level language. Even in DotNet there are some features impossible to implement in C# without reverting to IL instead (i.e. DotNet's "ASM").
No matter the language which was used to produce the program, it's rather rare to see users being trained in a language instead of how to operate the program. Think e.g. something like SAP, 99% of all its training is done on end users explaining to them which value to put into what field and what button to click when - not anything about the language used to develop those forms. Why would you think that training on a "mainframe" is any different, especially for the operators? In fact it's probably more useful to train users on a higher level language (for stuff like scripts and automation) while leaving the lower level stuff to actual programmers.
|
|
|
|
|
I level with you on most of this except most users barely know where the power button is on their computer. I worked in IT at a public K-12 school system and the multimedia/computer teachers were the only ones who had half a clue about them(I am from KY). The science teachers do not know how to program or even learn. High science class was the exception probably.
jeffery
|
|
|
|
|
jeffery c wrote: most users barely know where the power button is on their computer
Well, I suggest that you don't make the kind of glaringly deceptive statement that you would use with those people when you post here, in CP, which comprises millions of people who have made a living coding for years (many of us, decades).
The only programming languages that have become "irrelevant" are the faddish languages, which came and went, while the old -- faithful, solid, and trustworthy -- languages are still in use, and still being used creatively, alongside the recent/new-fangled (if you're as old as I am/if you're not) OO languages.
The whole ms "universal" thing will go the way of all their fads, and in short order, because other people are doing better things -- whether individual, gifted developers, who are finding their own ways to do things; or large firms, who are looking to set standards. ms has already lost the battle, no matter what their marketing morons and wu-maos say.
Had windows phone been a success, things might have been different, but they killed windows phone with the very direction they went in for it.
Understand that very clearly: UWP killed the windows phone -- no-one wanted it on their computers, therefore they didn't want it on their phones, either. If something stinks, you don't want to put it in your pocket.
Shame, really, because the baby-blocks thing, with its low-ish graphics overhead, was a good interface for a phone.
Note that I have only really responded to the title of your posting, and not to the content, which is not entirely related to the title (don't get me started on titling things appropriately!), so, in response to your "shall I write articles about it?" question, I reply; Why the Hell not?
There is always something to be learned from every direction taken in computing.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark, sorry for confusion I meant that in the context of my previous IT job. No offense to the programmers on here but normal people can be idiots especially in KY and some do not want to learn. I was referring more to normal users not programmers which deserve a special right to themselves.
jeffery
|
|
|
|
|
Fair enough, but don't forget that "normal people" can be absolute geniuses in areas where developers are absolute idiots.
"Bert isn't good at what I'm good at" doesn't mean "I'm good at what Bert is good at".
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
No. The guy doesn't know anything. He thinks that UWP apps take over our whole screen. Ha ha ha.
|
|
|
|
|
The nuclear bomb launch systems AREN'T written in COBOL.
The bomb simulation routines were written in JOVIAL, a variant of Algol.
Most programs connected with the nuclear industry were written in Fortran. One just needs to look at the infrequent ads from Los Alamos National Laboratories and Livermore Labs to figure this out.
COBOL figures prominently in systems for banks, stock trading, and large bureaucracies such as the IRS and the Social Security Administration.
By the way, ADA was used when the government replaced the creaky Air Traffic Control system serving the USA. The IBM processors used for Air Traffic Control had not been manufactured for a decade or more (no, they were not the 360/370/390 processors) but I think the room-sized processors could have been replaced with small CMOS processors with the identical instruction set.
Reading the ads in Washington Post (during the glory days of the Cold War), one could see that the ELINT (electronic intelligence gathering) systems and COM3 (Command, Control and Communication) systems were also written in assembly language for the unique processors produced by IBM.
Just FYI.
|
|
|
|
|
Thanks for that. I forgot for a moment about Fortran but if I did I would have mentioned it. Was assembly language really used in nuclear systems?
jeffery
|
|
|
|
|
That question jogged my memory and I remembered the name AN/UYK. Googling that, I found they were the computers used by the US Navy. All advertisements in the mid-1970s for that computer were for assembly language programmers. With about 4K of memory, they certainly were programmed only in assembler.
Googling for Semi Automatic Ground Environment, that was a network of 27 computers across the US that were connected to radar sites that scanned the skies for incoming Russian bomber fleets. The vacuum-tube IBM mainframes had a max of 64K of memory. You could be sure that they were too programmed in Assembler.
While SAGE gave the order to launch the missiles, the missiles themselves were controlled by on-board computers with 4K of memory. You could be pretty sure nothing would fit in that memory except assembly language programs.
As the missile fleet was modernised, I am sure the US Department of Defense moved to ADA. Perhaps now, it is in C or C++.
|
|
|
|
|
Agreed. I think the only real, creative "UWP" being developed right now inside Microsoft is the WSL (Windows Subsystem for Linux) a.k.a. cancer. Once those guys have implemented all the syscalls, WSL will be more attractive to develop for than UWP.
|
|
|
|
|
Speaking of COBOL, if you know who Grace Hopper is, I was actually in her office in the basement of the Pentagon once.
The fundamental design of COBOL is good; it was intended to be understood by non-programmers. Most other languages, like C/C++ and PHP, are too cryptic and peculiar.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
