@hamarisun
on
Board
I have made a board. JavaScript was usually challenging. So i got to work and looked for solutions in the web. Found them and tried to understand what i just pasted in to may file. I must say i do , but not exactly every little bit of it. It was a fun project for me.
@hamarisun
on
Board
7h 14m 11s logged
Finished?
I think I almost finished my project. Few details to change here and there and I’m shipping ! :)
@hamarisun
on
Board
1h 1m 2s logged
deployed the site
just starting the project i have learned how to use git :) and also how to store secrets on github
@hamarisun
on
Myweb
my own webpage
project that i will develop further.
what can you find on my webpage:
@hamarisun
on
orezOS
My webOS
I have made a webOS, orezOS. While i was making the webOS had a few problems especially with: dragging windows, opening/closing windows and calculator.
apps: notes gallery and calculator
languages used: HTML, CSS, JavaScript
@hamarisun
on
orezOS
5h 59m 51s logged
New Apps
I have made a gallery app and a calculator app.
The webOS project is done. It has :
-it has dragable windows
-functional clock (updates every second)
-calculator
@hamarisun
on
orezOS
5h 32m 10s logged
##H2Another app
previously i had made the notes app following the guide. this time i have made photo gallery. Scroll able window!!! Things left to do
-login screen
-super app(calculator probably
@hamarisun
on
Myweb
5h 30m 29s logged
Almost complete?
Rearranged things. Made a real background.
Now i just need to make more sections. But really i had made a few buttons. mostly you can find my github account/projects there.
@hamarisun
on
Myweb
6h 26m 2s logged
Useful stuff learning and adding functions to the webpage.
@hamarisun
on
orezOS
8h 16m 19s logged
apps! im trying to make apps. As usually i m not successful. This time at least i know that i just dont get how Java works due to lenguage barrier. Too bad :|
I’ve rewritten the server using Tokio instead of Threads for improved performance and less server-side overhead.
It utilizes Rust’s async implementation with futures to create a much more lightweight alternative to threads. Basically, you can summon multiple tasks and instead of them being full threads with seperate 8MB stacks and so on, they have way less context switching overhead and a much smaller stack per instance.
In the initial handshake, the client provides its name to the server. If the server receives a message with the wrong name from that client, it will replace the name with the originally given one.
I’m still working on finishing up encryption for all messages and the initial handshake.
@hamarisun
on
orezOS
1h 3m 39s logged
starting the os
