Skip Navigation

Posts
1
Comments
285
Joined
3 yr. ago

  • NixOS isn't great for non-programmers, I bet, but for programmers it's amazing.

  • I really should learn some Rust 😂

  • Wait until DHH finds NixOS, where we can configure everything via single configuration. Even multiple machines.

    I love Debian for what it taught me, but I'm not sure if I'll ever use anything else.

  • Expected git, got multiple programming languages. Nice.

  • How are the dataframe libraries on Ruby?

  • I like Bread on Penguins - very informative now that Luke Smith has turned away from Linux and towards Communist Philosophist or whatever he now turned into.

  • No colours? But how am I going to look down on the other three quadrants?

    But for real, how did you make it? Hold up, did you screenshot draw.io? You absolute madlad!

  • VAIgans.

  • I think it was Denmark and/or a province (?) of Germany

  • The doxxers got doxed. Sucks to be them.

  • don’t come at me, pendants.

    Did you do that on purpoise? :3

  • I don’t need reproducibility to the extent that NixOS provides

    Alright, that's fair. As a programmer, I've been having a blast using it - being able to quickly setup my laptops almost the same as my desktop is such a breath of fresh air, then being able to copy over most of my config to a WSL setup to employ nix to get there 90% of the way on a Debian or Ubuntu WSL system is just so nice.

    But if you don't need its features, or aren't a programmer, I can very much imagine you'd rather stick to a more stateful system.

  • Alan Turing, I bet

  • If it wasn't several PB (yes, petabytes) of data I'd want a backup.

  • Nee hoor, dat doen wij helemaal niet!

  • they can’t fathom going to a woman for honest advice.

    Honest advice may not be good advice. I could tell a person "go kill yourself", and be VERY honest about it. Yet it's not good advice, now is it?

  • Start with pen and paper - no computer, because that'll just distract you.

    Write down what kind of game you want to make. Sketch out what you want your player to see when they play the game (top down, third person, first person; which UI elements should they see? Health? Mana or power bars? Selected items?). Does it have a story of sorts? What kind of setting (future, past, fantasy, sci-fi). 2D or 3D? What kind of visual style are you going for (realistic, cartoony, abstract?).

    This will be your Game Design Document. You don't have to get it perfectly at the first go - iterate over it, scratch things that you feel won't work.

    Once you have something that looks like a minimally viable product (MVP), THEN you can start making something in Godot, Game Maker, or Love2D. Because now you have something to follow along. Try to get something out ASAP, because feedback from people who are not you is important. Maybe you made something that feels fun to you, but no one else likes it - you would want to know that as soon as possible, not after toiling away for 5 years.

    Do not start caring about "what is the fastest programming language". Even the slowest of languages are fine, because you're learning how to build a game, not how to program like a pro.

  • Pretty sure .compact also still works.

    Slap .compact after a URL and you'll see a mobile version of reddit from like 2006.

    edit: THEY REMOVED IT! D: RIP .compact - I've visited you about 5 times, ever.