|
Why this time? DOOM is 25% off - and that's tempting. But ... if I buy it, I'm gonna play it. And I have to cook Christmas dinner tomorrow; the chances of that happening while DOOM is lying unplayed on my PC are ... um ... rather low.
Elephant!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Isn't there an IoT device that regulates your oven temp by how much you play DOOM? That way, you could play and cook dinner at the same time!!!
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Most of it's pretty easy - Sous Vide on at 10:30 @ 62.5, turkey goes in @ 11:00. Pud goes in steamer at 12:30, Potatoes go in at 12:45 (Roasty), 13:00 (Hasselback), 13:14 (Dauphinoise). Purees are made, they need heating (Sous Vide again), Pigs in blankets, stuffing, sprouts - in oven @ 13:30, but there is prep to do (parboiling, slicing, poaching, ...) and DOOM will cut into that! 
I remember well how fast time flew when playing 1 and 2 ...
But ... the demo was good ... (even if the "Classic Map" secret was rather underwhelming).
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Damnit. I gave in, and bought it.
But I won't play it tomorrow at all. Honest ... arrgh, this will be difficult ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
The shotgun's the best!
The shotgun's the best!
The shotgun's the best!
The shotgun's the best!
The shotgun's the best!
(If that didn't work first time, read it again)
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Never played a computer game except Solitaire - Doom looks incredibly violent
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
It's only a little more violent than Solitaire - you can get some really nasty paper cuts from those bouncing card when you win. And the Solitaire "Deathmatch Mode" could get extremely bloody. I remember one time when I took the ferry to Shelbyville. I needed a new heel for my shoe so I decided to go to Morganville, which is what they called Shelbyville in those days. So I tied an onion to my belt, which was the style at the time. Now to take the ferry cost a nickel, and in those days, nickels had pictures of bumblebees on them. Give me five bees for a quarter you’d say. Now where were we, oh ya. The important thing was that I had an onion on my belt, which was the style at the time. They didn't have white onions because if the war. The only thing you could get was those big yellow ones ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: the Solitaire "Deathmatch Mode"
That's not the usual solitaire, it's Concentration.
Turn up a Revenant and an Arch-vile when you've only got the chainsaw, and you'm buggered.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Top 10 post of the year!
|
|
|
|
|
This is when I stock up my games for the rest of the year.
Stellaris and Endless Space 2 for under $50? Yes, please!
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
Maybe don't go back for seconds ? [^]
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot
|
|
|
|
|
We have overcrowded and underfunded hospitals, yet this represents some people's priorities...
|
|
|
|
|
Something I take for granted is that my browser will connect to my servers which will connect to other servers in my hosting setup and that there will be a form of communication that will allow data to be requested and received.
But I have no idea how it all works at a low level. Zero.
I know that my code will make use of the .NET TCP/IP libraries and that they will handle the work of talking to the OS, which will invoke the drivers, which will use my WiFi hardware, which will talk to my ISP, which will route the communication to the server I requested. The .NET libraries will take care of handling the handshaking to establish a connection, and the sending and receiving the data itself.
But I've always wondering how this works. At low level. As in: what does the OS say to Broadcom driver to make the antennae do stuff. What commands does the driver send to the firmware? What (and how?) does the firmware do to make the antenna emit an electromagnetic signal and how does the firmware handle all the electromagnetic radiation it picks up to enable it to listen to the right signal?
Another thing that's always bugged me is the nature of the (necessarily) discontinuous communication. It's not a continuous sine wave with a continuous stream of data going to and from. The data is broken into packets and there is acknowledgement and error correction in the packets being transmitted. Which implies some kind of state management going on.
Which then raises the question of how does something like SignalR work when there are 10,000 connections (and what is a "connection"?) to a server and the data travels back and forth on a connection that's long term, not short term like a HTTP request (small furrowed brow thinking about HTTP Keep-alive)
None of this is important to a developer, and yet it kind of is important to a developer in the same way garbage collection, disk access patterns and thread scheduling. You don't need to know them, but knowing them gives you the knowledge to make informed decisions.
Does anyone know of a write-up of this stuff anywhere? Failing that: would anyone be interested in taking a stab at an article that walks through the life cycle of a bit of data travelling from code through the libraries to the OS to the drivers to the firmware to the hardware, via the ISP, across the routers, to the other and and back?
I think it would be fascinating.
cheers
Chris Maunder
|
|
|
|
|
... then a miracle happens...
|
|
|
|
|
I call it "magic", and allow myself to be amazed, without asking too many questions.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Chris Maunder wrote: ...
I think it would be fascinating.
I see that all Australian traits have vanished. It's efectivbely a Public Holiday seeing as Monday is right before Christmas Day this year. I'd have thought you would be hooking in to the piss by now on a sunny Sunday afternoon there in downtown Toronto and not thinking anything work like until at least 02-01-2019.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Why do you think I'm here thinking about radio waves? This is not a sober preoccupation.
At least it shouldn't be.
cheers
Chris Maunder
|
|
|
|
|
A book could be written on this topic. I don't think I want to write it though.
I would start by reading up on the OSI model of network layers. The highest level is the application and it goes all the way down to signals on a wire or in radio waves. It can be very informative.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I'd probably need the abridged version. Possibly a version involving sock puppets to explain the hard bits.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: Possibly a version involving sock puppets to explain the hard bits.
Would you prefer Agro or Elmo as the Compere?
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Animal.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: would anyone be interested in taking a stab at an article
Rick above has the right idea. That's not an article; it's a book.
We went over the OSI layers back when I was in college. While it might make for an interesting read all these years later, I actually don't want to start thinking about it at this level. Somehow I'm thinking I'd fall into the trap of knowing just enough to be dangerous, and then start trying to "optimize for the wrong things".
|
|
|
|
|
Quote: I think it would be fascinating.
I think it would be long.
|
|
|
|
|
Easy stuff. The foot bone is connected to the ankle bone, etc, etc.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
Chris Maunder wrote: None of this is important to a developer, and yet it kind of is important to a developer in the same way garbage collection, disk access patterns and thread scheduling. You don't need to know them, but knowing them gives you the knowledge to make informed decisions.
Actually I'm not so sure that is true, if it really matters (say real real-time apps) then there will be mechanisms developed to work with & around it.
Consider database design, was a time the way hard disks worked mattered to bot the database server developers and the app developers, so people optimised with the hardware in mind. Now databases can be distributed, on different media, even on unknown media (cloud).
Even the way new hardware works, for instance if you read up on SSD's vs disks even though the o/s treats them the same the old rules don't apply, yeah you may still play around witch caching/buffering but optimising say refresh block sizes/transfer speeds for the hardware, not a factor that matters
Network low level magic: knowing how it works, well there's one common way it does it for lan, about 3 common different methods for wireless, about 5 different common methods for WAN... there's nothing to optimise because one network session may use any one or more of these at the same time.
Knowing how your network connection at low level is working right now will not give any clue as to what will be happening later, and "later" could be hours, minutes or even milliseconds.
At high level app level nothing about the current connection at lowest level is useful to the app because it may be different before it can even apply whatever optimisations or rules to cater for what it found. The speed is about the only useful factor, but even that doesn't dictate low level say packet sizes or negotiation/error correction overheads...
yawn, got called in to monitor some app, waste of half a day that I could have used for sleeping, but whatever, charging for a full day even though it's only 10 AM and I'm done 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
