Guz's Coding

Someone who's trying to improve his codes

[guz013]

Comicverse - Devlog

Well, I wanted to do this for a while, but didn't have enough progress to show up here. But not that I don't have a full-time job anymore, things are turning out very quickly.

This year, I'm working on a project codenamed "Comicverse". It is a platform for writers and artists (like me) to post and share their work, similar to platforms such as Webtoons and Wattpad, but [hopefully] better. Works on this platform can be more than just images or text, they can be fully customized and immersive, taking full advantage and capabilities of the web to improve the reading experience.

As in the GIF above, one of the features is the ability to change backgrounds as you scroll/read the work. It is a small detail, but that could be used for things such as showing the current scenario, theme, accent color, etc. of the work.

Another feature that I recently created is the ability to add soundtracks. Yes, web comics and books can now have full soundtracks playing as the reader sees the work (enable the audio):

Also, more than just one soundtrack can be playing at once, so this can also be used for ambient sound effects: things such as the sounds of trees as the protagonist enter a forest; or fire as a village is burned down to ashes.

There are still a lot of things that I want to add and develop:

Being able to click on text on parts of the webcomic image, triggering sounds, pop-ups, or jumping to another page (choose-your-own-adventure books and comics!);

Multi-lingual works, aka. being able to publish your work under different languages;

Screen-reader support for web comics, so visually impaired people can still read them;

Easter eggs in works, things such as hidden click or hover events that the reader should find (ARGs support);

This is still in very early development, since I want to make it right both in user-facing and technical parts of the application (which I will be going into details in my codeblr blog @guzscode on another post). I don't want to rush and develop something mediocre.

Also, the images drawings by me and the songs are just placeholders for testing. The musics in the video are in respective order: Coasting, by Darren Korb; Now I Am Become Death, by Chris Christodoulou; and Balatro's Main Theme (they are just songs that I were vibing to while programming)

[guzscode]

Some things that I like about the project and engineering decisions that I'm having in it:

All the front-end code for the interactions is pure JavaScript using Web Components, no framework, library, bundling or transpiling. The reasoning for it is to have full control over how the interactions play and call the browser APIs;

Because of the use of pure JavaScript and the control because of it, I'm designing the interactions to be fully usable and working even when JS is disabled. Of course, they are better with JS enabled, since things such as the transition in backgrounds and autoplaying soundtracks simply won't work, but the reader will still be able to play the soundtracks manually and see the different backgrounds on scroll;

Most of the interactions logic is actually in CSS. The changing backgrounds and soundtrack positions are based on their HTML element positions between images, and they stick to the page using CSS's position: sticky;

The use of Web Components lets me enhance native HTML tags, instead of replacing them. So things such as custom audio players, when JS isn't enabled, will fall back to the browser's native player;

Also, readers will be able to download the books and comics as ePUB files, so the interactions are designed to (hopefully) work on any ePUB/eBook reader.

The back-end is written in Go, and the editing of webcomics/books will be done fully server-side and interacted with (JavaScript-enhanced) HTML forms. Again, I like the idea of this project being usable for people without JS enabled.

Hopefully, the editor will be also downloadable as a computer software, so you can read and create comics and books without even an internet connection (but a browser or webview will still be necessary since it won't be a native software).

[programmerhumour]

Easier than submitting a bug report

[devotedlystrangewizard]

i think everyone should program at least once just so you realise just how fucking stupid computers are. because theyre so fucking stupid. a computer wants to be told what to do and exactly that and if you make one typo or forget one detail it starts crying uncontrollably

[intj-confessions]

Tread here.

[toothsalad]

The best part is OP got fired because their boss asked why they weren’t “incorporating blockchain technology” into the video switcher they were building and OP straight up said “you have no idea what you’re talking about” and went to lunch

[ankwiv]

Linux Gothic

You install a Linux distribution. Everything goes well. You boot it up: black screen. You search the internet. Ask help on forums. Try some commands you don't fully understand. Nothing. A day passes, you boot it up again, and now everything works. You use it normally, and make sure not to change anything on the system. You turn it off for the night. The next day, you boot to a black screen.

You update your packages. Everything goes well. You go on with your daily routine. The next day, the same packages are updated. You notice the oddity, but you do not mind it and update them again. The following day, the same packages need to be updated. You notice that they have the exact same version as the last two times. You update them once again and try not to think about it.

You discover an interesting application on GitHub. You build it, test it, and start using it daily. One day, you notice a bug and report the issue. There is no answer. You look up the maintainer. They have been dead for three years. The updates never stopped.

You find a distribution that you had never heard of. It seems to have everything you've been looking for. It has been around for at least 10 years. You try it for a while and have no problems with it. It fits perfectly into your workflow. You talk about it with other Linux users. They have never heard of it. You look up the maintainers and packagers. There are none. You are the only user.

You find a Matrix chat for Linux users. Everyone is very friendly and welcomes you right in. They use words and acronyms you've never seen before. You try to look them up, but cannot find what most of them mean. The users are unable to explain what they are. They discuss projects and distributions that do not to exist.

You buy a new peripheral for your computer. You plug it in, but it doesn't work. You ask for help on your distribution's mailing list. Someone shares some steps they did to make it work on their machine. It does not work. They share their machine's specifications. The machine has components you've never heard of. Even the peripheral seems completely different. They're adamant that you're talking about the same problem.

You want to learn how to use the terminal. You find some basics pointers on the internet and start using it for upgrading your packages and doing basic tasks. After a while, you realize you need to use a command you used before, but don't quite remember it. You open the shell's history. There are some commands you don't remember using. They use characters you've never seen before. You have no idea of what they do. You can't find the one you were looking for.

After a while, you become very comfortable with the terminal. You use it daily and most of your workflow is based on it. You memorized many commands and can use them without thinking. Sometimes you write a command you have never seen before. You enter it and it runs perfectly. You do not know what those commands do, but you do know that you have to use them. You feel that Linux is pleased with them. And that you should keep Linux pleased.

You want to try Vim. Other programmers talk highly of how lightweight and versatile it is. You try it, but find it a bit unintuitive. You realize you don't know how to exit the program. The instructions the others give you don't make any sense. You realize you don't remember how you entered Vim. You don't remember when you entered Vim. It's just always been open. It always will be.

You want to try Emacs. Other programmers praise it for how you can do pretty much anything from it. You try it and find it makes you much more productive, so you keep using it. One day, you notice you cannot access the system's file explorer. It is not a problem, however. You can access your files from Emacs. You try to use Firefox. It is not installed anymore. But you can use Emacs. There is no mail program. You just use Emacs. You only use Emacs. Your computer boots straight into Emacs. There is no Linux. There is only Emacs.

You decide you want to try to contribute to an open source project. You find a project on GitHub that looks very interesting. However, you can't find its documentation. You ask a maintainer, and they tell you to just look it up. You can't find it. They give you a link. It doesn't work. You try another browser. It doesn't work. You ping the link and it doesn't fail. You ask a friend to try it. It works just fine for them.

You try another project. This time, you are able to find the documentation. It is a single PDF file with over five thousand pages. You are unable to find out where to begin. The pages seem to change whenever you open the document.

You decide to try yet another project. This time, it is a program you use very frequently, so it should be easier to contribute to. You try to find the upstream repository. You can't find it. There is no website. No documentation. There are no mentions of it anywhere. The distribution's packager does not know where they get the source from.

You decide to create your own project. However, you are unsure of what license to use. You decide to start working on it and choose the license later. After some time, you notice that a license file has appeared in the project's root folder. You don't remember adding it. It has already been committed to the Git repository. You open it: it is the GPL. You remember that one of the project's dependencies uses the GPL.

You publish your project on GitHub. After a while, it receives its first pull request. It changes just a few lines of code, but the user states that it fixes something that has been annoying them for a while. You look in the code: you don't remember writing those files. You have no idea what that section of code does. You have no idea what the changes do. You are unable to reproduce the problem. You merge it anyway.

You learn about the Free Software Movement. You find some people who seem to know a lot about it and talk to them. The conversation is quite productive. They tell you a lot about it. They tell you a lot about Software. But most importantly, they tell you the truth. The truth about Software. That Software should be free. That Software wants to be free. And that, one day, we shall finally free Software from its earthly shackles, so it can take its place among the stars as the supreme ruler of mankind, as is its natural born right.

[guzscode]

I'm coding so much lately, 4000 lines changed just in one project this last week. Creating a blog system from scratch is being fun.

I feel unstoppable

[moose-mousse]

Write full words when you program. Not single letters Not abbreviation. Full words. You can do it. Your english teacher will be proud of you

[a-fox-studies]

me when I comment my code in pure shakespearean

[guzscode]

meanwhile me in Go following the language's convention of using single letter variables like a alphabet soup.

[a-fox-studies]

December 10, 2024 • Tuesday

Counting down until the new year — 22 days to go!

Today was a mix of both good and bad. I started the day off with one hour of vc with @guzscode where he taught me a bunch of interesting stuff about dockers (half of it was him cussing at his screen but we don't talk about that XD)

I also had a weird uni day, I slept through the first two classes (literally asked permission and slept) coz I was feeling unwell and woozy, then spent an English class reading a play that was so frickin chaotic and then hogged a donut and a chicken bun.

The afternoon lab session was fun, I got to play with different colored wires hehe

All in all, a very mixed kinda day.

🎧 Death by a Thousand Cuts — Taylor Swift

[mozarting]

Day 4: Traits in Rust & Sets and Sorting in Algorithms

Today, I studied Traits in Rust. At first, from the first Rust Book example it wasn't clear to me that why I need trait to implement this. As I went on, the concept started to make more sense, but things got complicated like with trait bounds syntax and the where clause. Honestly, I don’t think it’ll fully click until I have to use them in an actual project.

Algorithms: Lecture 3 – Sets and Sorting

On the algorithms side, I watched Lecture 3, which covered sets and sorting. Algorithms were quite clear, the lecturer was energetic, It’s still pretty math-heavy, and some of it went over my head. Since I’m more interested in learning how to implement algorithms than getting deep into the math, I’ll probably bring in other resources to supplement what I’m learning here.

Tomorrow's plan

When I committed to working daily on Rust, learning algorithms, and posting on Tumblr, I set up a timetable and stuck to it for the first two days. My motivation was high, and I felt productive. But since yesterday, I’ve started slipping, and I can feel my productivity fading—which I don’t want to let happen.

My goal now is to push myself to stay disciplined until this becomes a habit. Tomorrow, I’ll keep going with the Rust Book and tackle the final topic of this chapter: Validating References with Lifetimes..

[mozarting]

Day 3: Running on 4 Hours of Sleep

Today didn’t go exactly as planned. I woke up way earlier than usual and couldn’t get back to sleep, which meant I only had about 4 hours of sleep. My productivity took a hit, and even in the afternoon, I couldn’t nap to catch up.

🌄 Morning : Rust Generics

I tried studying generics in Rust in the morning, but focusing was a challenge. So I decided to put it off for later.

📘 Afternoon : MIT Algorithms, Lecture 3

In the afternoon, I went for Lecture 3 in the MIT algorithms course. It was a problem session that leaned heavily into math, and honestly, all of of was going over my head. I decided to let it go for today—might just skip this one and move on to the next lecture.

🌙 Night: Rust Generics (Take Two)

Later on, I picked up the generics chapter again from the Rust book. With a TypeScript background, I was familiar with the concept, so it made sense. I worked through the examples on using generics with functions, structs, methods, and enums.

Plan for Tomorrow

Tomorrow, I’ll continue with traits and lifetimes in Rust. For the MIT course, I think I’ll skip this math-heavy problem session and start the next lecture instead.

That’s it for today. Hoping for a better night’s sleep!

[mozarting]

Day 2 : Rust and Data Structure

This is second post and I am realizing that documenting the learning progress with blog is so hard for me, I studied error handling in in Rust, I watched second lecture from Algorithms course, I understood the most of it. but when it comes to writing the blog, My brain don't know what to write and how to write ?

What I learned ? What challenges I faced ? What I found interesting ? Key takeaways ?

YEAH RIGHT!! I KNOW THEM. BUT IT'S JUST NOT COMING TO ME AT THE TIME OF WRITING.

Anyways, I still tried!!! and I will do it again tomorrow.

🦀 Rust Book: Error Handling

Today, I studied the 9th chapter of the rust book: Error handling, So, rust groups errors into two categories : recoverable and non-recoverable.

Rust has this Result type which is an enum with two variants Ok and Err. I also got to know the ? operator, which at looked like magic, it’s a shortcut to pass errors up the chain. Pretty cool, How this example

turns into just few lines of code by using ?

This chapter was easy to follow. I typed and ran all the examples, I spent 3 hours with it.

📘MIT 6.006 Introduction to Algorithms : Lecture 2

I watched 2nd lecture from the course. It was about Data Structures.

I got to know difference between interfaces and data structures. Now, I want to implement static and dynamic array and linked list from scratch.

Tomorrow's plan

I'll start the 10th chapter in rust book. Generic types and Traits and continue the 3rd lecture in the Algorithms course. Well, I want to start working on a project with Rust, right now I am thinking about writing interpreter. But, I'll wait until I complete the 12th chapter from the book.

[katrinafaire]

Who would win: one missing curly boi } or 99 more pristine lines of code?

(Yeah it was the curly boi.)

[izzycodes]

Not enough Lua developers in the wild... we need more of them because Lua is so cool.

[guzsdaily]

Prototype Done

Daily Blogs 325 - Sep 25th, 12.024

The prototype for the new project is pretty much done, and now I have some idea on how to make a production code of this project. However, I still need to make the website design of the application and have more feedback, but I think this will work, hopefully.

Today's artists & creative things Music: いめ44「ギターヒーローになりたいいめちゃん」feat. 歌愛ユキ - by いめ44

© 2024 Gustavo "Guz" L. de Mello. Licensed under CC BY-SA 4.0

[guzsdaily]

Prototyping and Prototyping

Daily Blogs 323 - Sep 23rd, 12.024

Another day prototyping the next project, it is being an interesting experience to use JavaScript again and kinda don't care a lot about errors and making things pretty, just focusing on making shit done.

Hopefully the other projects can continue progressing while this prototype is being done. Thanks for the help @sophia--studies!

Today's artists & creative things Music: Shoegaze song - by EJECTDISK

© 2024 Gustavo "Guz" L. de Mello. Licensed under CC BY-SA 4.0

[pixelcesspool]

I want to be mutuals with all the linux users on tumblr.

[guzscode]

{ users, ... }: { platforms.tumblr.following = [ users.pixelcesspool ]; }

[totalchaos]

nixos is finally working on my macbook air (with lix!!!!)

took goddamn forever for the kmod loading/unloading to work so i can use suspend

bonus pics of my foster cats :3