• 382 Posts
  • 2.91K Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle

  • In theory, it’s simple:

    • All states participating in the Constitution are what make the Constitution
    • Breaking he constitution breaks the Republic of the USA
    • Each individual state is left to figure out what they want to do if that contract is dissolved

    Trump is too weak to even conceive of doing such a thing, so he’s going to try and bend the rules as much as possible. What they want is for states to keep sending them tax money so they can keep going on their conquest.

    Once they break the Constitution pact, no money, and their Southern States immediately collapse into a pile of dust.

    The military outposts of the US which hold all the scary stuff are all in Dem-friendly states. They will assume those assets with the National Guard, and that’s it for DC.

    Trump WANTS to dissolve the Constitution, but his idiot handlers are right to stop him. They know they would be destroyed in IMMEDIATELY if they said it out loud.

    Instead, they are trying to play semantics and make things work for them. The judicitbranch isn’t going for it, so now they want to attack that.

    The problem being that if you try and change the Constitution, alter it, or otherwise redefine what it says, then you need 3/4 state participation. That will never happen. They have a small participation of votes, and they’re trying to get an constitutional amendment on bullshit.

    They can’t change the Constitution, they can’t stop the Judicial from doing the right thing, and they are too stupid and/or lazy to garner support for their dumb plans, so they’re just throwing spaghetti at the wall.





  • just_another_person@lemmy.worldtoLinux@lemmy.worldNew to this
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    3 hours ago

    What I always tell junior devs that want to get familiar:

    1. Find a use-case. Don’t just use it because you have FOMO
    2. Run a desktop environment as your daily driver when you can. You’ll learn a lot.
    3. Try installing packages first, and after you’re comfortable with that, try building a project you intend to use from scratch. It’s a get primer, and gives a ton of context of how software development works along with the dependency chains with the operating environment.
    4. Don’t take a GUI as the “easy route” in spite of non-GUI sokutions. Get familiar with what makes the software run, and customize accordingly.