swordsmanluke @ swordsmanluke @programming.dev

Posts

2

Comments

310

Joined

2 yr. ago

I hope you take this in good humor and at least consider a TUI for your next project.

Absolutely. I see what you did there... 😉

But seriously, thank you for your response!

I think your comment about GUIs being better at displaying the current state and context was very insightful. Most CLI work I do is generally about composing a pipeline and shoving some sort of data through it. As a class of work, that's a common task, but certainly not the only thing I do with my PC.

Multistage operations like, say, Bluetooth pairing I definitely prefer to use the GUI for. I think it is partially because of the state tracking inherent in the process.

Thanks again!

No - but it is the game based on the anime that inspired the phaser design! Er, more directly both the phaser and the Zillion game were based on an anime named Zillion.

The Master System phaser was such a slick design. Perhaps not as iconic as Nintendo's blaster, but I think it's much cooler looking.

As someone who genuinely loves the command line - I'd like to know more about your perspective. (Genuinely. I solemnly swear not to try to convince you of my perspective.)

What about GUIs appeals to you over a command line?

I like the CLI because it feels like a conversation with the computer. I explain what I want, combining commands as necessary, and the machine responds.

With GUIs I feel like I'm always relearning tools. Even something as straightforward as 'find and replace' has different keyboard shortcuts in most of the text-editing apps I use - and regex support is spotty.

Not to say that I think the terminal is best for all things. I do use an IDE and windowing environments. Just that - when there are CLI tools I tend to prefer them over an equivalent GUI tool.

Anyway, I'm interested to hear your perspective- what about GUIs works better for you? What about the CLI is failing you?

Thank you!

Lots of little quality of life things. For instance, in Kotlin types can be marked nullable or not. When you are passing a potential null into a non-nullable argument, the compiler raises an error.

But if you had already checked earlier in scope whether or not the value was null, the compiler remembers that the value is guaranteed not to be null and won't blow up.

Same for other typechecks. Once you have asserted that a value is a given type, you don't need to cast it everywhere else. The compiler will remember.

Let's start a patent troll company that exclusively deals in dark pattern bullshit. Then sue every company that implements any of our terrible patents for as much money as possible. Use the proceeds to bribe lobby congress to pass stronger consumer protection laws.

Kotlin is Java with all the suck taken out.

It's a modern, ergonomic language that runs on the JVM and removes as much GD boilerplate as it can.

It's fantastic.

That one dude still using Delphi is getting screwed.

Also, these salary numbers seem... real low. I get that it's the median so maybe a huge number of overseas engineers are pulling the results down but in my neck of the woods 105K is less than what we pay juniors.

Self-replying to add a couple other classics that aren't already in the thread:

• Penguin Land: A Mr-Driller-like puzzler where you are trying to carefully bring an egg safely to the end of the level - but it can only fall one block distance without breaking. Also, there are polar bears you can crush with boulders.
• Zillion: This game has no business being as good as it is. Side scrolling adventure game where you are tasked with rescuing your captured spy-buddies. You have to loot secret codes from the bodies of fallen enemies, use them to unlock laser doors and progress further into the enemy base. It uses exceptionally large and detailed sprites for the time and is a surprisingly "mature" game for the Era. (Not meaning nudity, just that it is more interesting to someone auth the patience to map out a base and write down secret codes)

Skip the sequel, however. Zillion 2 sucked. a lot.

True, true... yet still more reliable than LoZ's "hold the reset button and hope" method of saving the game...

GOLVELLIUS

This game is a blatant... homage to OG Legend of Zelda. But IMHO it does almost everything better.

The game begins with Link Kelesis entering a cavern where an old woman tells him to take a sword - and some boots because our boy can't even dress himself.

After that, you know the drill. Top-down action rpg mode, slaying monsters, leveling up, finding secrets and better equipment.

Where it improves on the original LoZ is that the Master System was more powerful than the original NES, so the graphics here are brighter and more detailed and the audio is crisper.

The structure of the world is more linear than LoZ - but that means it's a lot harder to get lost. Also, as you unlock gear and powers you can backtrack to discover new secrets in old locations.

The game's characters vary wildly in tone from angry old ladies berating you for lacking the funds to shop to meandering fairies commenting on snow cones.

I replay Golvellius every few years on whatever the handheld platform dujour is. ...I think it's about time to give out a spin on the steam deck again.

Anyway. If you like that classic Zelda vibe, give Golvellius a spin. It's seriously one of the best games I played on the old Master System.

I'm thinking my kids Necromancer may learn a thing or two about the dangers of powerful, undead underlings...

Liches are a big responsibility. You can't just create unlife and walk away!

Argh. I hate that argument.

Yes - "Rewriting history" is a Bad Thing - but o argue that's only on 'main' (or other shared branches). You should (IMHO) absolutely rewrite your local history pre-push for exactly the reasons you state.

If you rewrite main's history and force your changes everybody else is gonna have conflicts. Also - history is important for certain debugging and investigation. Don't be that guy.

Before you push though... rebasing your work to be easily digestible and have a single(ish) focus per commit is so helpful.

• review is easier since concerns aren't mixed
• If a commit needs to be reverted it limits the collateral damage
• history is easier to follow because the commits tell a story

I use a stacked commit tool to help automate rebasing on upstream commits, but you can do it all with git pretty easily.

Anyway. Good on you; Keep the faith; etc etc. :)

I DM for my kids. Our first dungeon ended with an ogre-mage sending undead after the party.

The heroes made quick work of most of the zombies and skeletons - and critted the ogre-mage so fast that the dungeon was cleared in record time...

And then the party's necromancer (My oldest) decided to raise the ogre-mage. And made them his undead lich-thrall, with instructions to rule the dungeon until the necromancer's return to the region...

Huh.

Though they are often synonyms, simple != easy.

Simple is uncomplicated.

Easy is unchallenging.

Super Mario Bros. is a simple game, but not necessarily an easy one.

My wife has hella aphantasia. And facial blindness. She jokes that she would make the world's worst eyewitness to a crime - she wouldn't be able to recognize the perp or be able to describe 'em even if she could!

But as it has turned out, she's been having trouble hearing as she's grown older. We keep the subtitles on and avoid dining in even slightly noisy restaurants. Anything besides nearby face to face speech is a crapshoot.

So she saw an audiologist who ran the standard battery of tests and said "Your hearing is fine.... But have you heard of auditory processing disorder?" Turns out that a portion of our auditory processing overlaps with a bit of our visual processing. For my wife, whose visual systems don't all work right, her ability to filter noise and extract meaningful sound has started to degrade a bit. Mechanically her hearing is fine. But she can't process the signal right - possibly related to her aphantasia.

There's a lot we don't know yet about aphantasia. Like synesthesia, it's only been described medically in the very recent past. But if you ever start struggling to understand conversations... Check for auditory processing disorder alongside the rest.

For my wife... well, sge was able to get hearing aids - which look sleek now - and it's been night and day. Instead of shifting frequencies, these are like noise canceling headphones on steroids. She's suddenly able to follow conversations in noisy environments that would have been impossible before! So... if any of that sounds (heh) familiar - there's help available!

😱

Net removal of 1500 LoC...

I'm gonna make you break this up into multiple PRs before reviewing, but honestly, if your refactoring reduced the surface area by 20% I'm a happy man.

Harsh - but the first of these to make me actually lol

Have you checked the internet archive? No guarantees, but if anyone in the world has a backup of an old text- based site... it's them.

Mechanically - both games are puzzle games in the same rough 3d-platform-puzzler vein as Portal. Instead of solving puzzles with teleportation however, you've got laser beams and force fields.

On a more metaphysical level, the first game is a philosophical investigation of what it means to be human - to be alive and an individual.

The sequel is a meditation on what makes societies succeed or die.

Both games are fun, the puzzles are just hard enough to be interesting with a sprinkling of well-hidden secrets. But the real reason to play The Talos Principle is if you've got an interest in philosophy - the storylines are deeply interested in asking some very big questions. ... and they don't provide answers either - the game poses questions and allows you to answer as you see fit.