Technically CS is what originally launched the steam platform. I realize it's a HL mod, but with 1.6 it became "stand alone". I realize it still used the HL engine and everything, but CS was the only game on steam at that time, not HL.
Now if you'll excuse me, I have to be technically correct somewhere else on the www.
"regular unencrypted DNS resolver" is still better than "manipulative unencrypted DNS resolver". For the purposes of resolving thepiratebay.org, the former is sufficient.
That said, whatever the fuck DNSCrypt is what you could use for integrity is DNSSEC. Seems like overkill in this case, though.
It's almost as if the diagram targets scientifically curious laypeople, so your nerd rage about this irrelevant detail (given the context) is a bit over the top.
The "ATX era" beginning in the mid 90s does not mean that the "AT era" ended at that point. I've seen AT crap being used well into the early 2000s. Nobody abandoned their AT computer just because the ATX spec was released.
I've seen it on basically every tower-case AT computer I've had the displeasure to open (maybe a dozen) in what would be mid to late 90s in Germany. No, I don't remember make and model. From memory, one was a 386SX with 33 or 66 Mhz and one was a 486DX with 100 MHz. I think there was also a Pentium 90 among them. Each case (typically big towers) would have a super bulky 230V-rated actual power switch connected directly to the power cord.
I won't be doing extra research on which manufacturers did it and which did not do it since I ultimately don't care whether or not AC on/. believes me.
If you take the input, transmit it to the server, apply it there, update the game world and stream back the results, you'll see noticable latency.
To hide such latency, games often run the game logic locally. It's not authoritative, but well..most of the time it works well enough. Console gamers already get a crappy experience so I don't expect people to complain.
Well I've seen enough XT and AT that had their switch at the front. It's almost like this detail wasn't formally specified and manufacturers did whatever they thought made sense.
As if ONE EXTRA SET OF WIRES from the PSU is that much of a problem when you've already got cables running from the PSU all over hell and back.
Tell ya what, you can gripe when the PSU just has one cord going to the motherboard, and when the necessary cables for the other peripherals all carry data and power on the same cable.
I think you need some basic electrical education, maybe hit up youtube etc, even that might be enough to teach you the subtle difference between low voltage wiring and cables directly connected to mains; both in terms of safety and other unimportant things like fire hazards etc.
It is not like joe sixpack is going to disconnect power when replacing a hard disk or what not.
"But the computer is off, what could go wrong?" -You
Till then, you're really just griping without any actual hindsight.
Without actual hindsight? I don't think you meant to say this, but hindsight is really where all this comes from. But don't let this get into your way of pulling absurd statements and assumptions out of your ass.
Hell, I actually wonder if you've ever opened up any case at all.
And I wonder whether you have ever opened a PSU, because even the PCB inside it *has to have* (in the EU at least, not sure about 3rd world shitholes like the US) a clear separation between primary and secondary side, with extra insulation such that nothing may even get close to the primary side.
And now you're coming along with the "great idea" of extending the primary side to the outside of the PSU across the interior of the case to the front panel and then back, where two of those wires are always live, even when your "nice bulky switch" is off. Great job.
Instead, smarter people came along, relocated the physical switch back into the PSU where it belongs at the same time as finally managing to implement useful things like software power off, wakeonlan.
Up until here, I was gonna blame everything you wrote on the Dunning-Kruger effect, but after noticing that your only argument against it is that you personally like the feel of that big bulky switch, I have to clue you are, in fact, retarded. I kind of feel sorry for you.
This is the classic Linux apologist response to excuse its lack of usability.
It's not. I don't even like Linux, despite arguing for it in this thread. For the last 7 years I've run most of my stuff on NetBSD. So don't call me a "Linux apologist", I loudly curse about it every day when having to use it at work.
When Windows doesn't work out of the box it's all whining about Microsoft and how crap Windows is but when Linux doesn't work out of the box it's just a case of blame the stupid user who doesn't want to learn.
If something doesn't work in Windows, I'm on my own and have to resort to guessing or trying random suggestions found on the www. That's at least what I am whining about.
If something doesn't work in Linux, it can be troubleshot in a systematic manner, on any level you need to. This is a huge advantage. Not for you, but for me. Stop thinking everything is about you.
Why is it so difficult to understand that there can be OS that cater to people who want to use appliances, as well as OS that cater to people who want to use general purpose computers? Nobody is saying you're a bad person for wanting the appliance, but fuck off with the attitude that every OS needs to be an appliance just so that you can use like one.
So what does mom do when she upgrades to the next stable release and finds herself confronted with an upstream change in a configuration file that was also touched locally (perhaps by you, or by the installer) and thus needs admin attention? This is the point where I, and probably you, do a 3-way merge, but what does your mom do? Oh, she doesn't have to because she doesn't keep her system up to date in the first place? Well too bad.
Seriously, "Pop!_OS"? That's the dumbest name I've heard in a while. I suppose the underscore is supposed to look "modern", because random punctuation is what the kids use -- oh wait, that was maybe 20 years ago.
Slashdot Mirror
I'm not entirely sure whether astronauts are actually less costly than regular fuel. Maybe they're using those who wouldn't have flown anyway?
Nice try.
- Sent from my NetBSD desktop via my NetBSD router
Technically CS is what originally launched the steam platform. I realize it's a HL mod, but with 1.6 it became "stand alone". I realize it still used the HL engine and everything, but CS was the only game on steam at that time, not HL.
Now if you'll excuse me, I have to be technically correct somewhere else on the www.
B-but that was 2005. The year of FreeBSD on the desktop was 2011, if anyone wondered, and the year of NetBSD on the desktop 2013.
Sucks to be you, pals.
Damn, that true?
APK, I want to install your host file program, where can I download it? And is it any good?
You can't fix the damn system because it's closed source and named Windows XP POS, where the 'POS' part is oddly appropriate.
"regular unencrypted DNS resolver" is still better than "manipulative unencrypted DNS resolver". For the purposes of resolving thepiratebay.org, the former is sufficient.
That said, whatever the fuck DNSCrypt is what you could use for integrity is DNSSEC. Seems like overkill in this case, though.
use a DNS resolver other than the one provided by your ISP. 8.8.8.8 or 1.0.0.1 come to mind.
Wakes up, phones home? What about the part where it unsolicited upgrades itself to Windows 10?
Thanks for the advice, it even improved the experience! The moon was *entirely* gone!
It's almost as if the diagram targets scientifically curious laypeople, so your nerd rage about this irrelevant detail (given the context) is a bit over the top.
The "ATX era" beginning in the mid 90s does not mean that the "AT era" ended at that point. I've seen AT crap being used well into the early 2000s. Nobody abandoned their AT computer just because the ATX spec was released.
I've seen it on basically every tower-case AT computer I've had the displeasure to open (maybe a dozen) in what would be mid to late 90s in Germany. No, I don't remember make and model. From memory, one was a 386SX with 33 or 66 Mhz and one was a 486DX with 100 MHz. I think there was also a Pentium 90 among them. Each case (typically big towers) would have a super bulky 230V-rated actual power switch connected directly to the power cord.
I won't be doing extra research on which manufacturers did it and which did not do it since I ultimately don't care whether or not AC on /. believes me.
If you take the input, transmit it to the server, apply it there, update the game world and stream back the results, you'll see noticable latency.
To hide such latency, games often run the game logic locally. It's not authoritative, but well..most of the time it works well enough. Console gamers already get a crappy experience so I don't expect people to complain.
protip: ifconfig eth0 192.168.1.10/24 does the same thing with less typing
How does that matter? The crappy design is running mains through to the front panel. It has been done.
Why does it matter which specific manufacturers did it?
Well I've seen enough XT and AT that had their switch at the front. It's almost like this detail wasn't formally specified and manufacturers did whatever they thought made sense.
I bet I could open your PC case right now and find goddamned spaghetti wiring all over your interior.
You would not be wrong, but apparently it doesn't stop you from missing the point.
As if ONE EXTRA SET OF WIRES from the PSU is that much of a problem when you've already got cables running from the PSU all over hell and back.
Tell ya what, you can gripe when the PSU just has one cord going to the motherboard, and when the necessary cables for the other peripherals all carry data and power on the same cable.
I think you need some basic electrical education, maybe hit up youtube etc, even that might be enough to teach you the subtle difference between low voltage wiring and cables directly connected to mains; both in terms of safety and other unimportant things like fire hazards etc.
It is not like joe sixpack is going to disconnect power when replacing a hard disk or what not.
"But the computer is off, what could go wrong?"
-You
Till then, you're really just griping without any actual hindsight.
Without actual hindsight? I don't think you meant to say this, but hindsight is really where all this comes from. But don't let this get into your way of pulling absurd statements and assumptions out of your ass.
Hell, I actually wonder if you've ever opened up any case at all.
And I wonder whether you have ever opened a PSU, because even the PCB inside it *has to have* (in the EU at least, not sure about 3rd world shitholes like the US) a clear separation between primary and secondary side, with extra insulation such that nothing may even get close to the primary side.
And now you're coming along with the "great idea" of extending the primary side to the outside of the PSU across the interior of the case to the front panel and then back, where two of those wires are always live, even when your "nice bulky switch" is off. Great job.
Instead, smarter people came along, relocated the physical switch back into the PSU where it belongs at the same time as finally managing to implement useful things like software power off, wakeonlan.
Up until here, I was gonna blame everything you wrote on the Dunning-Kruger effect, but after noticing that your only argument against it is that you personally like the feel of that big bulky switch, I have to clue you are, in fact, retarded. I kind of feel sorry for you.
No, that's what we have now. Maybe you're too young to have experienced the pre-ATX time?
Yeah and what a crappy design that was, with the power wires going all the way through the case to the front panel.
Ok, do we have any reason to assume that this is in fact supposed to be pronounced in the Xhosa language?
This is the classic Linux apologist response to excuse its lack of usability.
It's not. I don't even like Linux, despite arguing for it in this thread. For the last 7 years I've run most of my stuff on NetBSD. So don't call me a "Linux apologist", I loudly curse about it every day when having to use it at work.
When Windows doesn't work out of the box it's all whining about Microsoft and how crap Windows is but when Linux doesn't work out of the box it's just a case of blame the stupid user who doesn't want to learn.
If something doesn't work in Windows, I'm on my own and have to resort to guessing or trying random suggestions found on the www. That's at least what I am whining about.
If something doesn't work in Linux, it can be troubleshot in a systematic manner, on any level you need to. This is a huge advantage. Not for you, but for me. Stop thinking everything is about you.
Why is it so difficult to understand that there can be OS that cater to people who want to use appliances, as well as OS that cater to people who want to use general purpose computers? Nobody is saying you're a bad person for wanting the appliance, but fuck off with the attitude that every OS needs to be an appliance just so that you can use like one.
So what does mom do when she upgrades to the next stable release and finds herself confronted with an upstream change in a configuration file that was also touched locally (perhaps by you, or by the installer) and thus needs admin attention? This is the point where I, and probably you, do a 3-way merge, but what does your mom do? Oh, she doesn't have to because she doesn't keep her system up to date in the first place? Well too bad.
Nice ad, comrade.
Seriously, "Pop!_OS"? That's the dumbest name I've heard in a while. I suppose the underscore is supposed to look "modern", because random punctuation is what the kids use -- oh wait, that was maybe 20 years ago.
Good fucking grief.