Not as of yesterday, no.

And that’s fine, I certainly have no shortage of things to occupy my time, I’d just hoped to be able to help make the SDF even more awesome :)

I’m giving up on this Lemmy FWIW. I signed up over at lemmy.ml

I could be wrong but I think this is a general issue within the SDF. It’s an incredible organization and I value my membership in it very highly but I wish it were easier to pitch in and volunteer to make things better.

I think I’ll give lemmy.ml a shot. It’s run by the Lemmy developers so seems like chances are good it’ll continue to function properly :)

Ah well, we live in an imperfect world. I’m grateful for them in any case! :)

Well, I sent an application email with my resume and the best proposal I could think of to volunteer@ a couple weeks back. We’ll see what happens I guess :)

Ooh thanks for the link that’s super helpful!

I don’t think Pascal is clunky! I think it represents a point on the evolution of programming languages and is still well loved by a LOT of people! Just google Free Pascal or Lazarus Pascal.

The back catalog is amazing too. They’ve interviewed SO MANY amazing luminaries from the Atari’s past and present.

I love how much modern computing culture has its roots in the good old Amiga, and folks who didn’t own one are totally clueless about it.

One could, but I would argue that this idea pre-supposed a very ascetic class of programmer, and that depending on one’s goals in learning how to program, recursion can be a useful concept but saying it should be the one litmus test for any learning platforms seems highly questionable to me.

Are there any off the shelf available 68K based computers these days? I wasn’t aware of one but that would be cool :)

AMIGA 2023!!! :)

Also, how would that ‘weirdness’ impact using the device in a teaching context?

What would you like to see instead? Z80? Something else?

Oh I totally agree. The Lua idioms can be confusing and the documentation ecosystem is currently in a place where if you already know Lua well it’s incredibly helpful, but bridging the gap for beginners is a challenge - one worth embracing!

It’s not a distribution.

It’s a bag of Lua files you can use to get started.

Also, it’s not for you :) Users who know enough to hold such opinions aren’t the target audience.

Do you folks choose OpenBSD over FreeBSD because of its enhanced security or are there other reasons to recommend it for folks looking for an alternative to Linux?

That’s not just understandable but how could it be any other way?

Heck just Vim itself is layer upon layer of powerful functionality. Now layer in the immense potential of Neovim’s Lua based plugin ecosystem and client/server architecture? 🤯

Give yourself the time to learn. Focus on just the things you need to get the task you’re doing RIGHT NOW done, then focus later on things that can level up your knowledge and productivity.

I’ve been thinking about making Neovim tutorial videos for Youtube. If I did, what kinds of things would be useful to you?

I just loved everything about this show. It was way more erudite than it had any business being, ESPECIALLY considering the vapid television offerings of its time.

Darn, now I wanna go re-watch the series :)

Hi!

kickstart.nvim maintainer here, please don’t follow the advice given in the video to just dump init.lua into place.

Please follow the instructions in the README for the repo and git clone it into your $XDG_CONFIG_HOME instead.

If you just copy pasta init.lua things will break. This is a result of converting Kickstart to lazy.nvim

Also, it’s a bit frustrating. That video is out of date as it’s prior to the conversion to lazy.nvim

You should rather than just dumping init.lua in place actually git clone the repo into your ~/.config directory. There are instructions for that in the README.

I appreciate your honesty about the README!

You say it didn’t make sense, was it:

1. Too long so you felt overwhelmed and stopped?
2. Too complicated in some way? Which bit caused you to stall out?

I feel like we need to do better here, but also I’m not a writer myself so I could definitely use all the specific feedback we can get.

Please feel free to file bugs, even if it’s “I don’t understand what <$tech_phrase> means” or similar. I’ll action ever single one of them :)

Remember Compute! magazine? :) I Lived for that thing :)