It's been about 1 year since I started working on @Readlebee, so I wrote a blog post about my experience so far:

TL;DR: the development process is very different than what I'm used to because I'm trying to do it "right," and that slow process has been discouraging, but I'm hopeful that I'll get something to show for my work relatively soon.

Excellent. Now when I ask for help and opinions, I can potentially get replies from both Mastodon *AND* Twitter! I'll be UNSTOPPABLE!!!

wishy-washy dev framework bullshit 


Only 15 minutes to answer!

I'm gonna finally redo my whole portfolio site from scratch! What should I use?

I just finished and uploaded my updated Audiobook Time-to-Page Converter!

It's roughly 40x larger than the original version because it's built using , , and , but it looks nice and I added some extra features, so I'm happy with it! Plus it's still a lot smaller than I expected it to be; I was expecting a full megabyte!

Overall, it was a pretty good experience! And the source is on my GitHub if you're interested:

Well... and are kinda starting to grow on me 😬 They're *exhausting* to work with, but the structure and flow is pretty interesting and almost fun!

Sheesh, why am I SO upset over ? Is it really just that I can't conceptualize a single reasonable use case for it? What makes me reject it so hard?

If I don't fall in love with it and React and all the other bullshit that modern uses, I'll never be hireable anywhere else!

I'm doing the course on freeCodeCamp right now, and holy fucking shit, I can't believe how stupid this is. Why would *any* self-respecting programmer want to add this much overhead to their work process? This is one of the stupidest ways I've ever heard of to accomplish what it's trying to do. Jesus christ!

I really hope something very compelling shows up by the time I finish this course or else I'm just going to be seriously concerned for web developers' mental states from now on.

Should I write 's front end in instead of what I'm currently using for professional skill-building purposes and maybe a greater range of developer familiarity, or should I keep using the tiny framework I'm currently using that I love called that's easy to learn and understand anyway and that everyone ought to be using instead.

I'm planning on streaming some development on Thursday at around 7 or 8 pm Mountain Time, so stay tuned if you're interested! As it gets closer, I'll post the exact time and the link!

Hey there Fediverse friends! When it comes to (or ) , what do you prefer?
ES6+ (aka EMCAScript) or ?

Also, which might make you more likely to contribute code if you're interested in the project?

I just saw this, which wrangles up some tests performed to see what freshly-installed do when you first load them:

Pretty interesting stuff!

Ah fuck, I'm not confident I can make a good experience with just Open Library and I can't for the life of me figure out how to get anything useful out of the MediaWiki API. I'm worried I'll be required to store book data so it can be cleaned and made actually useful 😫

Can anyone help me find an API that's free (or cheap) that'll be good to use for getting book data? ISBNdb looks great, but it's a little pricey for a $0 budget project...

I feel like this is a stupid realization, but I finally realized that I need both a front-end AND a back-end framework for a full stack app.

Like, I've done this before. Why did it take my 3 days to realize that??

Ugh, I can't decide. Should I use NodeJS or PHP to build my alternative? I can't decide, and I don't know what would be "best" not only for handling users safely but also for maximum installability/platform support (for future federation)

I don't really have a preference for either, but I want to choose the best option for maintainability and resistance to obsolescence... Any thoughts?

I was just about to ask this :
Is a single-page web app framework necessary at all if the interactivity is minimal? Why not just use traditional pages?

But as I was writing it, I realized that the biggest reason for making a single-page app for a website (in my opinion) is that the user only needs to load the files *once*, then the whole site is at their fingertips. They don't need to download resources for each page. But browser caching helps with that nowadays. How helpful is it really?

Alright, friends, I've set up a repo and a chat for the nameless alternative project! It's pretty empty atm, but now there's a central base where we can discuss and start working from:

If you have questions or want to discuss the project or contribute, check out the Gitter link, which lets you log in with a GitHub, GitLab, or Twitter account:

I'm excited to see where this goes!

@hummingrain @codingquark @Stoori @carbontwelve @tootbrute

Well, I've thought about it several times now, which means I have to at least start the project: a proper open source that's maybe potentially federated.

I have no idea if it's a project I'll finish, but I certainly want it to exist, so I'm willing to work on it! If anyone wants to contribute or team up with me, I'd be glad to have the help! I'll probably write it in PHP and JavaScript because that's what I know and it's available in most web hosting!

Ok, friends, I've been holding on to it for quite some time, but I've finally decided to publish the lists of words that I used in my old Game Idea Generator as an NPM package:

If you end up using it in a project, please let me know! I'd love to see it!

PS: That link has a link to the Game Idea Generator in the first paragraph. :)

Show more

cybrespace: the social hub of the information superhighway jack in to the mastodon fediverse today and surf the dataflow through our cybrepunk, slightly glitchy web portal support us on patreon or liberapay!