|
I'm so sorry, I'm really, really sorry...
... but I just kicked off the Win8.1 download.
|
|
|
|
|
You, you, you, you, bad man. No more gin in your feeding bottle for you.
Steal candy from a baby's hand, that we can live with.
Steal money from a pensioner's handbag, that we can live with.
Steal money from a bank to give to an MP, that we can live with.
But when it comes to installing 8.1, have you no shame, no integrity, no civil decency, no pride?
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
|
|
|
|
|
Quick! Before it finishes, upgrade to Windows 7!
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 – ∞)
|
|
|
|
|
You will soon 'ENJOY' the new OS.
The side bars flashing up at unwanted moments will please you no end.
---------------------------------
Obscurum per obscurius.
Ad astra per alas porci.
Quidquid latine dictum sit, altum videtur .
|
|
|
|
|
How could you do that to it?
while (!working) {
Reboot();
}
|
|
|
|
|
You shameless man! You've done the dirty deed, then announced it to the world. See you tonight on the 'What were they thinking?' news.
It was broke, so I fixed it.
|
|
|
|
|
Don't be sorry!! 
8.1 really is awesome.
|
|
|
|
|
So you got in a gin fused state and got bold enough to start the download, as OG says quick stop the download and upgrade to Windows 7.
|
|
|
|
|
It could be worse.
You could be getting 8.0.
|
|
|
|
|
8.1 from 8.0 or 8.1 Update 1 which I see is in the wild, but not yet released...
|
|
|
|
|
Just please be sure to wash your hands before petting the dog. The poor beast doesn't deserve to catch anything nasty...
Will Rogers never met me.
|
|
|
|
|
We use log4cxx. And it sucks. Why?
The source wasn't updated since 2010 - Getting it to compile with the newer, more strict VS compilers needs a lot of customization and digging around in the code. Add Qt and you are in serious trouble. Now what? Yes, use the custom build. Does it work? Y... no. It is a real PITA to configure the appenders, and the File Appender is missing a reference. Documentation? No, not at all (not only is any internal documentation missing, even the official one on the project page is lacking of content).
I suddenly feel with people who think writing their own logger is easier and cheaper.
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf Wondratschek
|
|
|
|
|
I feel your pain. Have you taken a look at BitFactory.Logging? We use it and have never had a problem. Of course it might not fit your requirements 100% but it might be worth a look at. The chap who developed it, Lorne Brinkman, is really quite decent and ready to help out.
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
|
|
|
|
|
Septimus Hedgehog wrote: Have you taken a look at BitFactory.Logging
I wish I could, but we have a Tool Portfolio, and whatever is in there needs to be used.
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf Wondratschek
|
|
|
|
|
Quote: The source wasn't updated since 2010 - Getting it to compile with the newer, more strict VS compilers needs a lot of customization
I feel your pain but playing devil's advocate, your complaining that "old" software does not work with new software. I'm not so sure it is the old software that sucks. It has worked well for many people. Just saying. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
RyanDev wrote: It has worked well for many people.
Who most likely used something pre-VS with weak check of the C++ restrictions. It's cr@p code, and that is why I stand up for common logging standards - We have the RFC 5424 (aka Syslog), why would you want to use some fancy custom format?
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf Wondratschek
|
|
|
|
|
I have never used log4 but know of people that have used it. It may be bad code. I actually don't know.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I'm sure that it is of use, and I used log4net [same stuff, ported to .Net] with no problems - It is just that C++ compilers are known for... Aaahm... frequent changes and therefore may not be the best thing to let code rotten for 4 years. My 5 cents.
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf Wondratschek
|
|
|
|
|
Fair point.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Logging frameworks are over-rated, imo. In order for such a framework to be useful in a wide variety of situations, it must be quite complicated and extensible (having some kind of plugin or registration architecture, configuration and so on). However, actual logging requirements for any individual application are pretty straightforward and can be managed with a simple logger interface with one or more implementations for testing, deployment etc. This means that any worthwhile general logging framework is always overkill for every application in which you use it.
|
|
|
|
|
Tell that our PM - We have a Tool Portfolio, and whatever is in that Portfolio we are forced to use.
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf Wondratschek
|
|
|
|
|
Can't agree more.
My logging coding practice is always done in this order :
-First I Console.Write.
-Then if Console.Write does not fit anymore because of some feature, I replace them with "Logger.Write" Logger being one of my classes, then inside I use the TraceSource class. (the standard .NET log lib).
Astronauts say : "yeah but you have to break your code anywhere"... Is it such big of a deal to replace all Console.Write in your code to Logger.Write ?
Never understood why people fear so much refactoring code... f*** the advantage of software is that it is soft and we can change.
Such over bloated logging framework exists only because some developer prefer to develop a plugin instead of modifying the code when features change... then we end up with config mess. (I have scars, and also from my own old code)
The though process of architect astronaut are as such :
-"My client does not know where to log stuff, so instead of taking a decision, I will allows everything by using the pluggable logging framework X"
Then for very sick astronauts the second question is : (I was one of those, and looking back, I would put my fist in my younger face... I was reading too much martin fowler)
-"My client does not know which pluggable logging framework to use... so I need to develop an extensible logging framework-framework to change logging framework X if it is not good"
And then you end up with 5 layers of interface from different logging frameworks.
Such logging framework over rating is a symptom of an indecisive team.
It was a long response but I get so much scars of these indecision that it made me on fire.
Suffered from until I learned the "Don't ask permission, take the decision and apologize if it does not fit".
|
|
|
|
|
I have consulted the interwebs to try and decide what to do today.
Seems legit[^]
|
|
|
|
|
Why is Uhura black?
William Shatner!
---------------------------------
Obscurum per obscurius.
Ad astra per alas porci.
Quidquid latine dictum sit, altum videtur .
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
