Just your typical internet guy with questionable humor

  • 20 Posts
  • 336 Comments
Joined 1 年前
cake
Cake day: 2023年6月22日

help-circle


  • Another thing the sequels didn’t have: accompanying games. The gaps between movies weren’t filled exclusively by live action and animated series

    Sure, only Revenge of the Sith actually had an actual “the movie the game”, but the 90s and early 2000s saw a number of amazing Star Wars games (and some less than stellar), most only partially related to movies, others with completely news stories, which definitely helped keep people interested in the universe, even if they didn’t like the movies. KOTOR, Republic Commando, Battlefront, X-Wing series, Dark Forces series.

    Meanwhile, during the Disney years, we had Battlelootbox 1 and 2, Squadrons, Jedi Fallen Order+Survivor and… that’s about it (also some Lego Star Wars stuff). The mobile stuff might as well be SW skins of whatever is the current mobile trend.






  • I know the post is a joke, but the main difference is that Luke was on the winning side at the end of ep 6, redeeming his father and avenging old Ben, while OB1 saw his entire world, the Republic and the Jedi, being destroyed at the end of ep 3. He became a target and “traitor”, so hiding was the only sane choice.

    Also, while OB1 readied himself to fight Anakin, it was the latter that jumped to strike first. Luke tried to kill Ben while the kid was asleep.

    As others said, Luke retiring or wanting to be left alone because he fucked up big time isn’t a problem per se. The way his reasoning is treated, especially for trying to kill Ben Solo, is what left a LOT to be desired. “Oh, I had recurring nightmares that he’d fall to the dark side”. Well, did you confide that with anyone? It’s not like Yoda, Anakin or Obi-Wan’s force ghosts would rat him out. - My memory is hazy, but I don’t remember him saying, or the movie showing, what he tried besides cold blooded murder to avoid such a fate.


  • Luke didn’t need to personally kill Snoke, but helping the Republic he helped reinstate would make sense. He wasn’t just a jedi or force user, he was also a great pilot, the backwater kid that blew up the first death star and one of the many pilots that helped defend the Hoth base against the Imperial assault.

    Maybe the whole jedi and force thing went way too much over his head, to the point where everything else stopped being important to him. I don’t remember how exactly it was depicted in TLJ, but I don’t recall him saying anything about the New Republic, whether or not he cares about it anymore or why.







  • Yes, you got the gist of how it works.

    To give a bit more context, functions are basically snippets of code that are executed when called. One way to look at the input("What's your name?") function is this (not how the actual function looks like, just an abstraction):

    function input(text_to_show):
        print(text_to_show)
        input_from_user = get_keyboard_input()
        return input_from_user
    

    That return is something you will see often in many functions, and when you call a function, that’s the result it sends to the line that called. So, if input was actually coded like this:

    function input(text_to_show):
        print(text_to_show)
        input_from_user = get_keyboard_input()
        return 1
    

    Every time you called it, you would receive 1 as a result. In your example, nam = input('Who are you? ') would always assign 1 to nam, because the return is 1 rather than the variable that receives whatever you typed in.



  • If you meant cell phones and tablets, that’s mostly due to the different architecture. RISC processors are super energy efficient, which also makes them much cooler to run.

    x86-64 is a CISC architecture, which tends to be much more power hungry. There are only a couple of very low power Celeron CPUs that work under 10W of TDP, while that’s very common among phones’ CPUs.




  • With 65 percent of projects adopting Agile practices failing to be delivered on time

    They’re not “failing to deliver”, they’re being Agile in disappointing everyone involved!

    Projects where engineers felt they had the freedom to discuss and address problems were 87 percent more likely to succeed.

    Which shouldn’t surprise anyone, but I know some managers, directors and users loathe the idea of the people who’ll do the actual job having any say other than “yes, sir”.

    In highlighting the need to understand the requirements before development begins, the research charts a path between Agile purists and Waterfall advocates.

    Good documentation is critical and process-agnostic. If people can read and understand it, it’s good. It’s something that can be used as a shield and weapon against users/higher ups who want too much, it can create a trail of responsibility.



  • I mean, you’re using hardware from a company that is very blatantly anti consumer rights - thou shall not repair, thou shall not upgrade, thou shall not use third party anything, thou shall use Metal, for we despise OpenGL; not to mention that you have even less control on the mobile devices unless you pay a developer fee.

    The fact that MacOS has some FOSS under the hood is completely irrelevant.