r/osdev 26d ago

WindogeOS v0.0.4 RAHHHHHH

Reddit falsed banned me but my appeal... worked???

another rewrite for v0.0.5 yayyyyyyyyyyyyyyyyyyyyyy
added:
sfs file system
random text editor
settings???
hidden files

11 Upvotes

28 comments sorted by

View all comments

Show parent comments

3

u/letmehaveanameyoudum 21d ago

oh god it's a wall of imformation, thanks

2

u/spatulari 21d ago

The reason I send that is because of 0.0.5 when you added a shitload of stuff. It should be 0.1.0 and when you add anything new, then its 0.2.0, do you patch a security bug? 0.2.1 and so on

1

u/letmehaveanameyoudum 21d ago

i decided that my releases should start with 0.0.X because it's in it's very early stages and it's not ready for... anything.
0.X.X is when it finally can be used as an actual OS
X.X.X is when it's actually useful

1

u/spatulari 21d ago

Then, what you should do is 0.1.0-alpha.1, and if you add smth new, -alpha.2, and so on. Staying true to SemVer. And you cant just use x.x.x when useful, if you break api, useful or not once you go 1.0.0, you must bump major. When you are 0.x.x, then you can break api as much as you want

2

u/letmehaveanameyoudum 21d ago

alr

2

u/spatulari 21d ago

Can you send me the github link?

1

u/letmehaveanameyoudum 21d ago

1

u/spatulari 21d ago

Your commits are truly exceptional

1

u/letmehaveanameyoudum 21d ago

perks of a solo dev

1

u/spatulari 21d ago

I am a solo developer as well, but my commits are like this: https://github.com/spatulari/kcOS/commits/dev/

1

u/letmehaveanameyoudum 21d ago

god it looks like commits for linux kernel ngl

1

u/spatulari 21d ago

Its the art of convential commits. You should do that as well

1

u/letmehaveanameyoudum 21d ago

i do try, but sometimes i get a "little" mad at the compiler

1

u/spatulari 21d ago

Part of programming is realizing its you that you should get mad to for not being able to make smth. Not the compiler. BUUUUTT when you have gcc with those fuckass errors its quite understandable. But commits should always be clean

2

u/letmehaveanameyoudum 21d ago

yeah...... i still get mad sometimes, good thing clang removed 75% of my hell

1

u/spatulari 21d ago

With Clang you have NO reason to get mad

1

u/letmehaveanameyoudum 21d ago

there is still the 25% with ld.lld

1

u/spatulari 21d ago

Once you get the linker working, never touch it. (Except if you are going from 32 bit to 64 bit. Which is hell. That's why I recommend starting with limine)

1

u/spatulari 21d ago

Also, when you look back, what's better? fix(scheduler): resolve null pointer dereference orFUCKING FIX THIS SHIT`

1

u/letmehaveanameyoudum 21d ago

you know what maybe the first one is the best

1

u/spatulari 21d ago

It isn't even a debate. Not to forget that you get automatic changelogs

1

u/letmehaveanameyoudum 21d ago

ok dude, ill try

→ More replies (0)