Starting a new #React project to prove that I know how to use it. It'll be a life tracker where you can journal, track moods, and have todos and stuff. Seems like an attainable goal that's complex enough to get people to see that I know what I'm doing.
I'm using only "popular" #webdev tools for the project and it's antithetical to everything I've done for a personal project before because I always try to make my projects as small as possible. If I was building this normally, I anticipate it would be <100kb, but I'm certain the final result will be >800kb at the smallest... maybe I can at least make it accessible.
It's been about 1 year since I started working on @Readlebee, so I wrote a blog post about my experience so far:
https://robbie.antenesse.net/2020/09/11/one-year-of-readlebee.html
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.
Sheesh, some of these new CSS things are game changers:
Excellent. Now when I ask for #webdev help and opinions, I can potentially get replies from both Mastodon *AND* Twitter! I'll be UNSTOPPABLE!!!
β¨ FLASH POLL! β¨
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!
https://alamantus.itch.io/time-to-page
It's roughly 40x larger than the original version because it's built using #React, #Redux, and #Bootstrap, 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:
I'm doing the #Redux 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 #Readlebee's front end in #React 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 #Choo that's easy to learn and understand anyway and that everyone ought to be using instead.
I'm planning on streaming some #Readlebee 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 #webdev Fediverse friends! When it comes to #frontend (or #node) #coding, what do you prefer?
ES6+ #JavaScript (aka EMCAScript) or #TypeScript?
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 #browsers do when you first load them:
https://css-tricks.com/what-happens-when-you-open-a-new-install-of-browsers-for-the-1st-time/
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 #Goodreads 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 #question:
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 #Goodreads alternative project! It's pretty empty atm, but now there's a central base where we can discuss and start working from:
https://gitlab.com/Alamantus/book-tracker
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:
https://gitter.im/book-tracker/general
I'm excited to see where this goes!
A professional web developer, hobby game developer, conlang enthusiast, and maker of highly specific niche software named Robbie Antenesse. β οΈ CAUTION: Here be swears β οΈ
Other Mastodon Accounts:
Tabletop Gaming - @Alamantus
Linguistics & Conlanging - @Alamantus
Cooking & Food - @Alamantus
Books & Reading - @Alamantus
Backup - @Alamantus