Jump to content

sham1

Members
  • Content Count

    36
  • Joined

  • Last visited

  • Days Won

    2

sham1 last won the day on July 7 2018

sham1 had the most liked content!

About sham1

  • Rank
    Scarcely Lethal
  • Birthday 10/30/1998

Profile Information

  • Gender
    Male

Recent Profile Visitors

865 profile views
  1. So... I am once again back. I hate real life and other stuff getting in the way of doing stuff, but what may one do? I hope that I won't once again forget to visit this here forum. In other news, I am ATM home celebrating the delay of Article 13. Feels good to have representatives that actually think for once.
  2. sham1

    TF2 general

    Sometimes you just love Valve pubs It makes for some good target practice though. Although cp_process does seem to usually have some good matches.
  3. sham1

    Meltdown and Spectre CPU Vulnerabilities

    Man, I just love the doom and gloom perpetuated by tech media around Spectre and Meltdown. Yes, getting access to memory pages you shouldn't get access to it not good, but come on. It's not the end of the world. Although, with Meltdown specifically, we have to get Intel to fix this since KPTI (or whatever is the equivalent for Windows peasants) is... well, it slows down context switches such as with SYSCALLs and such. Granted, if PCIDs were to be used you could just switch your TLB without doing a very slow TLB flush (since you know, TLB misses are like cache misses, a bad thing), since PCIDs allow you to retain multiple TLBs.
  4. Speaking of hacking, I took a peek into the source of catbot (the code is on Github, with no license, not that it'd matter for this kind of thing anyhow), and I have to say... as much as I don't like to admit this, I'm simply impressed by the thing. Purely on a technical standpoint, obviously. I hope that Valve doesn't take the easy way out and just outright ban every Linux user, because... well, I for one would be quite pissed.
  5. IO! SATURNALIA! Anyway, god damn. It's good to be back. All free time has been gone into being a good student... Welp, I guess now everything will start getting easier as I finally start getting into the actual rhythm. So... how has everyone been?
  6. I know right, that isn't even below the freezing point of water. EDIT: As far as passwords are concerned, you'd probably like some sort of password manager to get some nice randomness without you having to remember all those characters... Although to be honest, I'd rather just ditch passwords as authentication methods as a whole and instead would use public-key authentication...
  7. sham1

    Jungle Inferno Update Thread

    I'd say that the jetpack could use some buffs. If nothing else, I'd love to be able to do a second launch after having been launched already to get that sweet mid-air mobility.
  8. Umm, one question. How is this thread not pinned?
  9. sham1

    Hello!

    But there are two reactions: liking and upboating.
  10. sham1

    TF2 general

    Beep boop, son, beep boop.
  11. sham1

    TF2 general

    Anyways, since we are swiftly going towards 31st of October and thusly towards Scream Fortress, let us just remind ourselves of the basic truth of the world: We are, and we will always be, in the beam.
  12. sham1

    Happy 10th Birthday, Team Fortress 2

    But does it count as an update if it's a regression?
  13. /me sees colour scheme /me pukes Seriously, what is this!?
  14. sham1

    Happy 10th Birthday, Team Fortress 2

    And how accurate are those estimates usually? Probably accurate-ish, however you still cannot predict it perfectly, which really either leads to delays or you being reluctant to release any estimations and just saying soon. Publishing that kind of estimation will lead to expectations and if it's not met, it's somewhat of bad PR(Not that this is better, mind you). Also, as has been mentioned, the TF team is small, because of the whole "work on whatever you want" and basically nobody wanting to work on TF2...
  15. sham1

    Happy 10th Birthday, Team Fortress 2

    Let me just remind you that you cannot estimate developer time, no matter how hard you try.
×