Avatar

MonadDecepticon

@monaddecepticon

{x | x ∈ Hask} U {x | x ∈ Cybertron} he/him eastern europe art / computers / creatures

Imperial collapse speed run

It would be prime time for Canada and Mexico to pincer that mutha ...if war didn't suck absolute ass

At this point I just feel bad for the people of the USA

..and all of us on the outside who are affected whether we want to or not

Emacs is not as supportive of alternate keyboard layouts, it seems

That is, the default keybinds are based around a QWERTY keyboard

Other then C-x and C-c, it feels to me more that the default keybinds are simply mnemonic and less location based.

- P = previous

- N = next

- F = forward

- B = back

- Y = yank

And so on.

Whereas HJKL for vim is directly dependent on the keys beeing on the home row.

oh yes, the mnemonic devices of

Backwards -- b | f -- forwards

Previous -- p | n -- next

a | e -- end

^ beginning as in alphabet...?

v -- kind of a down arrow

meta v -- kind of an up arrow...?

I'd like to see an Emacs for media players. Everything configurable, everything Lisp scriptable, everything a little janky. Let me create playlists that mix CDs, MP3s and Blu-ray bonus features. Let me "crop" MCR's 'Blood' to remove the 90 seconds of silence, but only when playing in shuffle mode. Or maybe something different. Let me choose!

you can start out with EMMS and see how far it gets you

But yes, all standalone software should be a VM (I'm ok with smalltalk if lisp is not everyones cup of tea) with an editor+debugger first and then that folded into whatever the domain is.

The EQUUSIR BEST BOX combines modern high-end technology and current knowledge of quantum physics with the holistic body concept of the energy centers. The goal of the application is to meet the requirements: to maintain long-lasting physical health and to continuously increase the athletic performance.

The box supports the restoration and harmonization of the body’s own energy fields of the horse.“

Avatar
corporateaccount

it’s a horse microwave

In Prince's funky name, amen.

Millennial here. All the above and:

Please send me the training or tutorial in a written format with maybe some screenshots if necessary. I don't want a video tutorial. I don't want to waste time trying to scroll to the exact moment in the instructions that I need and then have to pause and replay it because I missed the .01 seconds of actually relevant information.

Please. Text. Maybe some images for clarification. I can read. I promise.

Skimmable, SEARCHABLE instructions. If they're long, there should be a hyperlinked table of contents.

Elder Millennial here cosigning HARD

If you really need to show a movement, embed a gif or 15-scond-or-less video in the text, like Jod intended.

Something I ran into during my time working at the university library. They wanted me to take over a particular task for the coming semester, and I needed to be trained on the software we used for it. This training was being done primarily by having Teams meetings with the software rep and other employees who had experience with the software. Early in the process, I asked for a copy of the manual.

There wasn’t one. The software rep swore up & down that there was no written documentation at all. They had “webinars”, which they thought were more than sufficient, and the rep insisted nobody had asked for a text version before. I asked them to double-check; okay, fine, your public-facing documentation has all pivoted to video, but surely a manual exists. Y’all made this software, someone must have written down how it worked at one point.

At our next meeting, they told me they’d looked into it & indeed no manual had ever been written. They insisted that all documentation on how to use the software had been recorded in video form & nowhere else.

Flabbergasted. Who decided software documentation & training should rely on the oral tradition? This company is clearly insane. And then this came up again with another piece of software from a different company. The art of the technical manual has apparently died a quiet death at some point with few people noticing, and now How To Use Computer is passed down from senior employee to junior employee like we’re apprentice blacksmiths in the 1600s.

Introduction to the OSR

what's an OSR? it's a game that's kinda like old-school D&D. or is old-school D&D. or is compatible with old-school D&D. an OSR game generally has some or all of the following principles:

  • low character power with highly lethal combat. in old-school D&D a 1st-level fighter has d8 hit points and a longsword does d8 damage, and you die at 0HP. this is not to ensure characters die all the time but to emphasize the next bullet point:
  • emphasis on creative problem solving. most situations cannot be solved by straightforward use of your abilities (such as charging into every situation with swords drawn, if a fighter), so the game tests lateral, outside-the-box thinking.
  • emphasis on diegetic progression. spells are found, not obtained automatically on level-up. you get XP by finding gold more than killing monsters. most of your cool abilities come from magic items. making alliances & hiring followers is encouraged.
  • focus on managing inventory, resources, risk, and time. the players are constantly faced with meaningful decisions; this is the heart of the game.
  • very sandbox-oriented. the focus on creative problem solving means the game must be accommodating to players taking a course of action the GM didn't plan for. use lots of random tables to generate emergent story. some elements of new simulationism.
  • high tactical transparency, i.e., the optimal course of action is rarely system-specific, and ideally very possible for a new player to intuit.
  • usually semi-compatible with old D&D, but not always. usually rules-lite, but not always.

what does the OSR mostly NOT do?

  • focus on character builds. these change the focus too much to be on the rules than the fiction, can create situations where stuff everyone should be able to do is an ability locked to one class, and impede tactical transparency.
  • resolve everything with a die roll. combat uses dice to be scary, unpredictable and most importantly not your default course of action. everything else should bring up dice rarely - dice are your plan B when your plan A fails. the best plans need no dice.
  • use linear storytelling or put players into a writer/GM role. linear storytelling gets in the way of the decision-making so core to the playstyle; letting players write details into the setting is mutually exclusive with them discovering it.
  • rules for everything. 400 pages of crunch is worse at simulating a believable world than the GM and players' shared understanding. OSR games rely constantly on GM ruling.

mostly still applies to all the above. making your system a "pure" OSR game comes second to doing what's best for your game.

oooops I bought some PDFs again.

This is such a great write-up

You are using an unsupported browser and things might not work as intended. Please make sure you're using the latest version of Chrome, Firefox, Safari, or Edge.