I heard the start menu in Windows 11 is a React native app now. Most pajeet thing I have heard in years.
Not too surprised but still had to look it up and found a video about it, they're using it for the "Recommended apps" part of the start menu, and also in (parts of) the settings app? Even Office isn't safe...
Thank you so much for this. I'm gonna be 100% honest with you I don't understand half of what's going on in that code. But I'm gonna dedicate myself to figuring it out and using that info to improve my game. I've got a "python for dummies" book sitting next to me that I should probably read.
import random
class Gamestate:
def __init__(self,wins=0,losses=0,cash=100):
self.wins = wins
self.losses = losses
self.cash = cash
@staticmethod
def start_game():
return Gamestate()
def gamba_game(game_state):
game_roll = random.randint(1,100)
while True:
bet = input("how much would you like to bet?: $")
try:
stake = int(bet)
if stake > game_state.cash:
print("You don't have that much money!")
else:
print(f"You bet ${stake}")
if game_roll > 51:
print("Yes!")
game_state.wins = game_state.wins + 1
game_state.cash = game_state.cash + stake
print(f"You won ${stake}, \nyour balance is ${game_state.cash}")
break
else:
print("No")
game_state.losses = game_state.losses + 1
game_state.cash = game_state.cash - stake
print(f"You lost ${stake}, \nyour balance is ${game_state.cash}")
break
except ValueError:
print("Invalid input")
def gamba_start(game_state):
print(f"Welcome to the casino! \nYou have ${game_state.cash}.")
while True:
play = input(f"Would you like to play?(yes/no): ")
play = play.lower()
match play:
case "yes"|"y":
gamba_sesh(game_state)
break
case "no"|"n":
print("That's probably a good idea")
break
case _:
print("Invalid input, please try again")
def gamba_sesh(game_state):
gamba_game(game_state)
while True:
if game_state.cash <= 0:
print("Dude I just lost it all")
print(f"wins {game_state.wins}")
print(f"losses {game_state.losses}")
break
else:
play_again = input("Play again (yes/no): ")
play_again = play_again.lower()
match play_again:
case "yes"|"y":
gamba_game(game_state)
case "i need crack":
print("Oh shit guys I gotta go!")
break
case _:
print("One more and I'm out!")
gamba_game(game_state)
game_state_start = Gamestate.start_game()
gamba_start(game_state_start)No, this is actually pretty solid code, but I do have some constructive advice if you're interested.
"yes"|"no", it's helpful to outline them as a variable. This makes it such that if you want to add say "sure" as an option, you only have to change it in one place. I'd also advice looking into the enum module if you start adding a lot of options, it's good for situations like this where you have a set of constant valuesKeyboardInterrupt, which happens if the user uses Ctrl+C in the terminal. This is a really common pattern in any command line software.play_again = input("Play again (yes/no): ")try:
play_again = input("Play again (yes/no): ")
except KeyboardInterrupt:
break # or handle quitting however you'd prefergamba_game you don't need to put the totality of your code in the try block, you can do one of two thingstry:
stake = int (bet)
except ValueError:
print("Invalid input")
continue
# <- rest of code aftertry:
stake = int (bet)
except ValueError:
print("Invalid input")
else:
# <- rest of code aftertyping.Any, and function return types to be None, though most will also try to infer it as well.Gamestate with them addedclass Gamestate:
def __init__(self, wins: int = 0, losses: int = 0, cash: int = 0):
... # You can annotated the member fields if you want, but most tools will infer it from the parameters in __init__
@static_method
def start_game() -> "Gamestate": # You can wrap them in strings, this is helpful in instances like here where the type isn't technically defined yet
return Gamestate()gamba_start, you'd change def gamba_start(game_state): to def gamba_start(game_state: Gamestate):
no and while the message above is comprehensive i will say that i personally try to account for spaces at the beginning or end of an input by using .strip() idk if thats unnecessary and im sure someone will let me know if it is but for example in a small tool im writing for myself where i take an input i put .strip() at the end of my inputs as well as try to catch spaces in my file handling. Again it may just be niggling over nothing but its what i try to practice:
def prompt_user_for_url():
"""Prompts user for the URLs they wish to download
Function takes no arguments and returns a list of the URLs"""
URLS = []
while True:
URL = input(
"┌──────────────────────────────────────────────────────────┐\n"
"│ Enter a video URL or the path to a .txt file of links │\n"
"│ ──────────────────────────────────────────────────────── │\n"
"│ • Each URL in the file should be on its own line │\n"
"│ • Whitespace will be trimmed │\n"
"│ • Leave blank and press [Enter] to proceed │\n"
"└──────────────────────────────────────────────────────────┘\n"
"➤ Your input: "
).strip()
#if the input is blank break the loop.
if not URL:
break
#checks if the url variable is file
if os.path.isfile(URL) :
with open(URL, "r", encoding="utf-8") as file:
URLS.extend([line.strip()for line in file if line.strip()
print(f"✔ Loaded {len(URLS)} link{'s' if len(URLS) != 1 else ''} from the file.")
break
else:
URLS.append(URL)
return URLS
x86 Assembly, rawdog the processor.
in my opinion id start them with something like pascal, its rigid and everything is clear. they can get a hang of what the basics of programming is and still create some fairly useful stuff. then its a matter of what they want to do. if theyre content in working on highlevel stuff and dont care much about lowlevel systems then something like lua or python. maybe JS if theyre doing webdev stuff and then something like c or c++ if they want to do low level stuff. But im not a professional so is suppose someone who works in the industry may have other opinions.
Pascal and BASIC are definitely dated. Pascal probably less so but either way it doesn't matter much for learning languages. I like the simplicity of the syntax of both, they have very clear terminology and conventions. Pascal has some weird stuff going on with it. It's not too much of a hurdle but it would be weird swapping over to the modern languages after that. I think BASIC wins for its extreme simplicity. Someone could definitely have some fun screwing around with it for a while before swapping to something legit. Most of the total newfags I've dealt with would be fine if they started by really comprehending basic crap like if statements and for loops anyway geg. Good answers thanks.
I think for learning, ARM is probably preferable. The reduced instruction set I think focuses attention
Pasting in other people's code from Stack Overflow that you don't understand, and then just banging on it with a hammer till it kind of works for what you're doing.
IMO some flavour of Java, Javascript, or Python (hell even v8+ PHP), especially for those with no prior understanding of what code is. The idea here is to get a grasp of how programs flow, basic data types, and core constructs like conditionals and loops. I'd immediately move anyone who quickly picks up on those concepts to C/C++ to get into memory management so they build an appreciation for just what higher level languages internally handle and abstract away. The key challenge is establishing a strong knowledge of the fundamentals before getting into the real meat of programming, something which higher level languages often speed up the process with given the ease of producing usable things. Already seen far too many devs screw up technical interviews because they glossed over the basic stuff in their learning in favour of the "interesting" concepts.
imo the most pajeet code is that which tries to hammer a round peg into a square hole. They find all sorts of horrific ways to avoid learning something new and potentially complex, such as memory management or a proper systems language. For example, the React Native start menu shit from above or Electron apps that take up around 500 MB per binary.
If I could teach young me to program, I'd teach me Ruby.
I think your opinion really gets lost a bit in the weeds. It's not productive for example, for a beginner to worry about things like language speed. Even trying to find an "optimal" learning language in the first place is a bit of a trap. It's much more important to pick a language and stick with it through at least the first hurdles of "thinking like a computer" and nailing variables, flow control and basic principles behind function design.
terry had a word for this, niggerlicious
Did Terry have any unironically good programing advice? Besides the fact that you should use an ISO to download an operating system becasue that's how the white man does it.