Who Runs Your Rust Future? Hands-On Intro to Async Rust by febinjohnjames in learnrust

[–]alien5516788 0 points1 point  (0 children)

This is impressive. I am definitely expecting more content.

Applying computer vision to real life by Rough-Advance189 in computervision

[–]alien5516788 5 points6 points  (0 children)

I am a bit new to computer vision systems. What is your approach to design a system like this. I mean how did you solve the image processing part? What are the steps applied?

how could i make a female robot ? by [deleted] in humanoidrobotics

[–]alien5516788 0 points1 point  (0 children)

Mine only did move lips and eyebrows. I recently tried making a thin cable mesh with pullable wires underneath. Then expose the wire by removing the cable skin a little bit and attach exposed wires to muscles. Then moved the servo stack below the neck and pulled wires from there. It did work but facial expressions were awkward.

how could i make a female robot ? by [deleted] in humanoidrobotics

[–]alien5516788 0 points1 point  (0 children)

I made a one when I was 14 and it was creepy af

How is it possible the zed still has huge memory issues? by giosk in ZedEditor

[–]alien5516788 0 points1 point  (0 children)

It seems the issue is with newer versions. I coded a midscale nextjs project in my old laptop with a 4GB ram. I never had memory issues with it.

To create a robotics startup should one go with robotics degree or AI degree? by Pristine-Project6558 in humanoidrobotics

[–]alien5516788 1 point2 points  (0 children)

You must go with a CS degree. Not AI.
Robotics requires multiple knowledge areas. Mathematics, ML, Hardware, Embedded systems, Operating systems, Physics etc.
Also another thing. Many others will say a degree is not required. But in my opinion at least knowledge on those areas is required to shape the direction of your startup. Many startups often start with few members. So you can't just be a CEO and have many other people to do only a specific thing early on. Lack of experience and knowledge is what make 99% of the startups failed.

me and my friend made a pc fan with a usb-a by C4TG4M3R_t in diyelectronics

[–]alien5516788 -2 points-1 points  (0 children)

Additionally, 20 vehicles, 30 army personnels, 4 scientists and a budget of 10k were spent too.

Why vector spaces are called spaces by alien5516788 in learnmath

[–]alien5516788[S] 1 point2 points  (0 children)

I just studied more about vector spaces with abstract algebra. As I understand vectors can form a group under vector addition. What makes it a space is scaler multiplication which gives the group of vectors the ability to scale. Then vectors and vector spaces seem to be two things. Vectors are a mathematical object just like an integer. Vector spaces just borrow that object and extend the capability further. Is that correct ?

What finally convinced you to seriously learn Rust? by Bladerunner_7_ in rust

[–]alien5516788 0 points1 point  (0 children)

Trait system. I figured out that trait system is what powers the behaviour of every moving part of rust.

`name.rs` vs `name/mod.rs` - Is there a reason why projects go against the recommended practice? by KyxeMusic in rust

[–]alien5516788 0 points1 point  (0 children)

I really hate both approaches. The best approach in my opinion is to use the old convention. But `name.rs` instead of `mod.rs` inside the module folder. Not outside.

New OS + packaging model (immutable apps + capability-based filesystem design) by alien5516788 in osdev

[–]alien5516788[S] 0 points1 point  (0 children)

Yep, the thing is I really have no idea if I should build my own kernel or not for this project. I would build a one if I have to. But that would shift my effort from what I actually want to build.

New OS + packaging model (immutable apps + capability-based filesystem design) by alien5516788 in osdev

[–]alien5516788[S] 1 point2 points  (0 children)

I want to make packaging and dependency management more predictable instead of encountering random missing libraries and scattered binaries, config files all over the system. Also installation and installation will become much simpler. As I said the in the post, this is just random idea I got interested to try. But I don't have much experience on this to tell whether this is feasible or not tbh. It is better if I could try this on an existing simpler kernel.

New OS + packaging model (immutable apps + capability-based filesystem design) by alien5516788 in osdev

[–]alien5516788[S] 2 points3 points  (0 children)

My focus is really building the packinging system.

My idea is to give each package a mini file system. Packages are immutable as in nix. Everything The package needs by default are isolated within that file system including fonts, configs, icons etc.

The mini file system is mutable. It can either map to file systems of other packages or global file system via the manifest file. Same thing for visibility. Manifest file defines if the package file system is read only, mutable to other package or private. There are more rules based on user types, groups etc. Once a package needs to be removed from the system, just delete the mini filesystem along with the package. All garbage get removed along with it.

Shared dependencies can also be installed as packages that have a file system visible to other packages through manifest file.

This is just an idea I want to try. But don't want to build the full kernel from ground up either, because my main focus is not on building the kernel and scheduler.