|
Nagy Vilmos wrote: [Windows] 8.1 is good and I find it hard to see the problems people claim.
Me too. At first it was strange and I had to think of how do I do this and that, but I quickly got over that.
I used to keep using old desktop applications because they were familiar, but lately have been replacing them with metro1 applications as my preference.
I think that most people are uncomfortable with change. The 'who moved my cheese syndrome' and need to be forced to adopt anything new; to wit Windows XP. It didn't help that the next version was Vista which put the resistant to change folks in epileptic seizures, but there was nothing wrong with Windows 7. So why the resistance to changing from XP?
Windows 8/8.1 has gotten them twitching again. It will take dropping support for Windows 7 before they will have to upgrade and then in due time when there is another paradigm shift they will be lamenting 'why doesn't it work like Windows 8'.
1 - I know I am not supposed to say metro but it sounds better than modern.
Once you lose your pride the rest is easy.
I would agree with you but then we both would be wrong.
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am.
JimmyRopes
|
|
|
|
|
It is partly about change taking some getting used to. But going from a multi-window, multi-tasking environment like the desktop (which has been around since Win95 and even back then was an extension of the multi-window paradigm of Windows 3.0 and probably earlier) to a single-app-at-a-time model is not just change, it is regression, and objectively worse.
|
|
|
|
|
You can run 2 apps at a time if you split the screen.
If you need more then you still have the desktop for other apps.
Once you lose your pride the rest is easy.
I would agree with you but then we both would be wrong.
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am.
JimmyRopes
|
|
|
|
|
Yes, you still have the desktop, because the desktop is vastly superior and Microsoft realised they couldn't actually take it away.
Two apps is marginally better than 1 but I (even when I'm not doing techie stuff) generally have about 20 windows open and I'm looking at at least 3 of them at any one time (e.g. browser, game, VOIP app).
|
|
|
|
|
*sigh*
Use the tiles as a full screen start menu.
Reconfigure images and pdf's to open in a dekstop app.
If you still suffer from tile allergy, install a "classic" start menu.
-- OR --
Never again complain about all those stupid, backward and narrow-minded users who complain about the changes you made.
|
|
|
|
|
Agreed completely.
Some things took some getting used to, but overall, it hasn't taken me any longer than I needed when switching from any prior OS to the next version (has there ever been two consecutive versions of Windows where MS hasn't shuffled things around just for the sake of it?)...
I use 8.1 every day, but frankly, I never see any of the much-maligned Metro crap as I'm always in the desktop environment.
In other words, just because Metro is there doesn't mean anyone has to use it. I use 8.1 just like I've been using previous versions of Windows.
|
|
|
|
|
I liked Windows 7 and would have preferred that MS had continued in that direction.
But if you HAVE to use Windows 8, then "yes" - Windows 8.1 is better than Windows 8. Marginally perhaps, but still so much that I would say: Don't install Windows 8, but if you must, use Windows 8.1
Anything that is unrelated to elephants is irrelephant Anonymous ----- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 ----- I'd just like a chance to prove that money can't make me happy. Me, all the time
|
|
|
|
|
I think 8.1 is better because they've fixed the desktop so it's actually usable again (without third party tools like Classic Shell), haven't they? The one-app-at-a-time Metro UI is just totally terrible for a computer environment, as it has been since 8.0, but if you boot to desktop you never have to see that (as long as you fix a few file extension associations that open up there like PDF ... grr).
|
|
|
|
|
|
WOW !!!
In code we trust !
|
|
|
|
|
A ghost writer no doubt....
"The whole idea that carbon dioxide is the main cause of the recent global warming is based on a guess that was proved false by empirical evidence during the 1990s." climate-models-go-cold
|
|
|
|
|
|
THESE PEOPLE REALLY BOTHER ME!! How can they know what you should do without knowing what you want done?!?!
-- C++ FQA Lite
|
|
|
|
|
Interesting!
But did you notice under his profile, he is being shown as a "Member since Thursday, January 2, 2014 (6 months)", but if you look at his reputation graph, it's showing the rep points since 2009.
Whether I think I can, or think I can't, I am always bloody right!
|
|
|
|
|
No I didn't. Shall I call the police or something?
Regards,
Rob Philpott.
|
|
|
|
|
Just now. After you gave the link.
Don't mind those people who say you're not HOT. At least you know you're COOL.
I'm not afraid of falling, I'm afraid of the sudden stop at the end of the fall! - Richard Andrew x64
|
|
|
|
|
It's a feature.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
|
Sandeep Singh Shekhawat wrote: You are always right!!
Please, tell my wife!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
He is most definitely a Legend Author. Especially with his 0 upon 0 amounts of articles he wrote
Wow! I must say I think I am short 20K author points by the look of it
Loading signature...
. . . Please Wait . . .
|
|
|
|
|
It seems to me that it is "enterprisey" to write layer of abstract code.
In fact I am often criticized as "not liking layers"
So first I'd like to say what I thing about architecture then ask my question
A crux of contention is:
=======================
I would argue writing layered code is not an end of its own (at least not reasonably).
I would argue an end of its own is (simple maintainable code, i.e.) probably be these few properties:
- modular (people can work on their bit independently)
- dependencies flow down (top level use low level, low level do NOT use top level)
- simplest / unobtrusive as possible shell / architecture to glue stuff together
this *might be* layered / interfaced too but this is not the purpose...
What I often see and I wonder how prevalent and wonder how common it is
=======================================================================
Layered / interfaced as hell code which takes weeks to understand to solve problem as simple as adding 1 + 2.
Is that a common pattern? I suspect it is!
|
|
|
|
|
Super Lloyd wrote: is not an end of its own
Correct.
Super Lloyd wrote: Is that a common pattern?
Not in my experience. But it depends on the how big a project it is too. I have written only one application with more than a Data Access Layer beneath the application.
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
I always keep my UI layer and any DB layer separate - it is simpler to just ram code accessing the DB directly from a View, but so totally unmaintainable beyond trivial examples that I just don't do it. I also almost always have a 'service' layer which stitches the two together, rather than calling the Db later from the UI layer.
Other than that, I tend to be fairly flexible on layers depending on the project.
I agree about the over-complexity introduced sometimes - my logic is that a well written and modular project can be expanded into more abstract layers, should that be necessary, quite easily if it is easily maintainable and modular in the first place - and building abstraction on abstraction just because it makes some intrinsic sense to a developer, in my experience, slows development and can increase bugs as new developers don't understand how it hangs together - and nobody ever spends the time to train newbies!
Quote: Super Lloyd wrote: simplest / unobtrusive as possible shell / architecture to glue stuff together
That's the one that gets me most. When someone uses some framework or other (especially if they use something and then modify it, and don't document anything) I have often found that the use of the framework has been chosen without much knowledge - so the developers learn on the job, invent work-arounds, until the whole thing is a bit of a mess, nobody really understands how it is meant to work, and new devs coming into the project don't have a cat in hell's chance of being productive for weeks.
Still, I'm an old fart, so what do I know?
PooperPig - Coming Soon
|
|
|
|
|
I usually keep some sort of scheme like in these two excellent articles
1. Building a Framework - Part I (DAL)[^]
2. Building a framework - Part II (Utilities)[^]
although that can differ a bit from project to project. My major concerns regarding this, is code separation. It forces me to keep things simple. It also allows me to reuse things, which is handy when you're working on multiple applications.
|
|
|
|
|
What? Something like this?[^]
Regards, Stewart
|
|
|
|