The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
... you rewrite a brand new version of a former class of yours ...
and the new version is both shorter and more powerful!
I just rewrite my IoC / IServiceProvider class which was 30% shorter with easier initialization and support for default parameters in constructors!
Now rewriting my serializer (I try to save my document with serializer, to make it easier) for a more compact format and more classes supported out of the box (properties, fields + now ICollection, IDictionary) and easier extensibility (with surrogate! simpler that custom serialization)! And it looks like it's gonna be much shorter too already! with text and binary stream support!
(though this one is unfinished..)
Well, congratulations ! I look forward to reading the CP article.
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
each side can see the other side's IP in the packet header
but if we run for example tracert codeproject.com we see that a packet goes through a number of gateways between the client and the server .Isn't it supossed that each gateway changes the last gateway's IP address with its own so it can get the packet back ?
if it is so then how codeproject see my IP and not the IP of the last place the packet went through ?
In any TCP/IP connection, the client's originating IP address is known to the server so they can return a response. You can spoof your IP but you won't receive any data back. The originating IP can often be the outside router IP. The trace you did merely shows the various hosts in the route from client to server. The originating IP is still transferred for the reason mentioned above. Hope this helps.
An excellent example of layered protocols. IP, the lower layer, handles the node-to-node messages, as your tracert shows. But a couple of levels higher, the http headers convey the endpoint IP addresses required for end-to-end intelligence. Something like Wireshark will pull the packets apart for you, if you're interested.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
So I'm now working on my old desktop PC[^].
It turns out to be a sloooooow machine... What happened!?
I've used this for years without problems, but I've barely used it for a good year and it takes about four hours to install some updates (52, about 400 mb) and another four hours to install Visual Studio 2015 CE
It hangs regularly, just doing nothing and then suddenly doing that thing I clicked on seconds ago.
Sometimes even my music just goes like "brrrrr" for about half a second because somehow my computer can't process any more stuff... IT'S NEVER DONE THAT!
Perhaps I should look into upgrading some hardware or even buying something new...
give it a good dusting, push everything into the sockets
Yeah, it wasn't very dusty and the hardware was tightly secured into the sockets.
Run a disk check, memory check, check check
Yep, it seemed SQL Server was running all kinds of stuff that I never use, but installed once to play around with. Other than that no problems though.
I did a clean install about two years back. Maybe I should do that again... I've got most files backed up anyway.
If it's still slow after that it's clearly the hardware that's the problem.
First time you're giving me actual good advice by the way, thanks.
I'd thank you with an awesome song, but we all know how that's going to end
When a horse gets used to cantering and galloping, but then you dump it in a field to do nothing but graze for a year, everything about it weakens a little.
Given that you installed a fair number of updates (including, I presume, some cumulative ones), I'd give it a couple of cold reboots, just to make sure that everything is cleared out.
If you have Java installed, completely disable their update checker. If that thing finds an update, it seems to slow everything down until you either apply the update or kill the damned thing (I ended up renaming the .exe -- belt & braces, you know)
I wanna be a eunuchs developer! Pass me a bread knife!
They explained it at build.
As the PC grows older, the Windows registry gets more momentous and everything get slow.
Problem they are working on with Windows 10.
UWP don't use the registry no more!
Dunno about other apps though...