Yeah that's a complete non-starter. All the info needs to be in the README and/or web page.

You need to login and read new replies.

Yeah that's a complete non-starter. All the info needs to be in the README and/or web page.

I often reply something like that.

I often get the suggestions from users, make changes and post a new reply. I am still surprised because that project have 500 stars even I am the creator of that project. (Many script developers use that in their projects.)

This is why I create the website.

Even if you use poorer-than-native wording, it can be understandable enough for a native speaker to fix it.

I tried but failed because I tried to use a translator to translate the UI of another project. Many foreigners can't understand it.

So the only solution is provide less but the same information for all languages.

More information I provided, more bugs in the information I provided. (For example, out of date.)

All of this has been a distraction from this question: Why is NSudo useful?

The answer to that question should be in the README and website.

As far as we've seen, it's a reimplementation of "Run As" and hasn't convinced us to use it.

At the moment I have zero clue why I should download nsudo

I forget to say. At the moment I have zero clue for intoducing nsudo because it has many features and I can't explain it without examples.

All of this has been a distraction from this question: Why is NSudo useful?

Many examples can explain that. For most users, they choose NSudo for running as TrustedInstaller because they want to modify the system files and registry without the access denied.

For example, they use NSudo for running command which can disable Windows Defender.

But it's only a small part in NSudo because it's a runtime enviroment customizer.

Strictly, the project still not finished.

It supports customize the process priority, current directory, access token mandatory level, access token privileges, run in a new console or current console today.

I will add the app container support, memory limitation support, cpu core/numa limitation, more detailed access token privileges customization and etc in the future.

So I don't know how to introduce simply.

Also it will support the configuration files to save the enviroment configurations customized by user in NSudo.

It also has the SDK for developers.

So it's not a runas, strictly. Because I may implement the user mode sandbox and debuggers in it if I like.

The only word I can describe it is "a powerful system administration tool" if I need to explain it simply.

Hello! Another non native English speaker here. I think you made quite a good description of what your program does in this group. You could copy/paste and reorganize it l, and create a freely readable "readme/what is nsudo/why nsudo". If you don't feel sure with English, just write a (not too long) dual language page, in English and your native language. Then add a little notice with a link to contact you to help for translation. Keep up the good job 👍

I forgot a thing. Iirc, you are Chinese. So, you speak one of the most common languages of the world. If you add a line in chinese asking for help in translating, I think you will easily find someone who can care about it. (At least in the towns. I went to China in 2012 for business reasons and, while people in the cities speak English very well, in the countryside I found people who never heard other languages and who believed all of the world could at least understand Chinese! Weird experience for an European, but funny. I loved staying in your country, it has nice landscapes)

Are there any successful ones?

Take it easy, man

Many examples can explain that. For most users, they choose NSudo for running as TrustedInstaller because they want to modify the system files and registry without the access denied.

This is useful. I had that issue. The user can install a program, but when some system modifications are needed, installation crashes

I forget to say. At the moment I have zero clue for intoducing nsudo because it has many features and I can't explain it without examples.

a feature list is not a bad idea

https://webhouses.co.uk/lite/

I don't have words, ridiculous

It's not a bad idea 🤔 GNU/Linux disguished under Windows skins

https://webhouses.co.uk/lite/

This is normal, it will keep happening 😏

@Pessmike I will try it. @Fuseteam Feature list? Yes. I will add it to the index page.

It's not a bad idea 🤔 GNU/Linux disguished under Windows skins

I don't think it's a good idea.

Because I don't think GNU/Linux is a good solution. (Unless it has framework with a stable ABI for kernel mode drivers first.)

Second, every linux developers should not use pipe oriented scripts. (Use object oriented scripts instead, for example, the Python.) Why the stuff originally create under posix love creating lots of f**king process? Because it uses shell scripts, more f**king pipes, more f**king (forked) process.

So I don't like sys v init, but I also don't like systemd too. (Why systemd don't introduce a database-based infrastructure like Windows Registry or the similar implementation in gnome desktop? We need to remember lots of different types of commands to use systemd features.)

I also don't like systemd, there are better alternatives such as openrc, runit or even the good'ol sysvinit. BTW, text config and logs are better to process than binary files

I admin some GNU/Linux desktops. There are some harsh edges to polish but in general, the OS runs fine

A virtual machine with ReactOS would be a good solution to run some windows-only propietary software inside those GNU/Linux desktops

You don't have to remember those commands you have tab complete :p

Disguising Linux as windows is a terrible idea

That is the same as disguising a turd as a cupcake

💩

It's not like there has been any decent attempts either. Most disguises have obvious mistakes that just end up being noticed very easily

Disguising Linux as windows is a terrible idea

not so bad in case of jerk border control officer inspecting laptops

Latest ReactOS-AMD64 tech demo (built by Illen) : https://drive.google.com/open?id=168x2WCNjdp3urfmeTfTBfsCe84bjb4Qf

OpenGL should work here 🙂

(ofc software rendering only)

OpenGL should work here 🙂

Add D3D12 WARP and Vulkan frontends maybe for the software rendering?

By the way, should D3D WARP just work on ReactOS?

By the way, should D3D WARP just work on ReactOS?

does the tech demo have fancy music playing?

does the tech demo have fancy music playing?

Yes, but not yet 👌

👀

i hope its some good ass demo music

This picture usually makes things clear.

👍🏻

So I don't like sys v init, but I also don't like systemd too. (Why systemd don't introduce a database-based infrastructure like Windows Registry or the similar implementation in gnome desktop? We need to remember lots of different types of commands to use systemd features.)

Windows Registry is a terrible idea, and a worst implementation. As an example, it's faster to export the registry to a file, and text search, than to do a native binary search. File systems are databases, in some way. Also, they have the flexibility needed for configuration structures.

So I don't like sys v init, but I also don't like systemd too. (Why systemd don't introduce a database-based infrastructure like Windows Registry or the similar implementation in gnome desktop? We need to remember lots of different types of commands to use systemd features.)

You need to remember lots of registry paths in Windows Registry 🤷🏻‍♂. Even worst, it has a sparse design, so it's not unusual to have to change vales across many diversal paths for a single app

You don't have to remember those commands you have tab complete :p

+ Agree.

Latest ReactOS-AMD64 tech demo (built by Illen) : https://drive.google.com/open?id=168x2WCNjdp3urfmeTfTBfsCe84bjb4Qf

Just a gray screen here (in VirtualBox it works fine tho)

I don't agree with you about that. There are many, many open source projects even without documents, only the note. (For example, the autonomous driving.)

That something exists does not implies it's convenient. If you want to promote your software, a short description of what it does and why (or when) use it is very appealing.

Honestly I wouldn't pick Microsoft as an example. They're bad at it too.

Yes. At my job we have a lot of headaches with APIs with wrong documentation (return true if success, it said, but it was the reverse, or something like that).

Rust's web page is a good example. Get inspiration from it; "Why Rust?" gives programmers a reason to consider it.

Agree.

This. I am not downloading every app I encounter just to see what it is

Also agree.

You need to login and read new replies.

Many examples can explain that. For most users, they choose NSudo for running as TrustedInstaller because they want to modify the system files and registry without the access denied.

This.

For example, they use NSudo for running command which can disable Windows Defender.

This.

But it's only a small part in NSudo because it's a runtime enviroment customizer.

This.

It supports customize the process priority, current directory, access token mandatory level, access token privileges, run in a new console or current console today.

And this.

All that makes a start of README.

You can put that.

Hello! Another non native English speaker here. I think you made quite a good description of what your program does in this group. You could copy/paste and reorganize it l, and create a freely readable "readme/what is nsudo/why nsudo". If you don't feel sure with English, just write a (not too long) dual language page, in English and your native language. Then add a little notice with a link to contact you to help for translation. Keep up the good job 👍

Exactly what I thought.

@movAxAx Thanks about NSudo's thing. But I don't think using text file for managing complex configurations is a good idea because of the performance.

you can cache it tho

Windows Registry is a terrible idea, and a worst implementation. As an example, it's faster to export the registry to a file, and text search, than to do a native binary search. File systems are databases, in some way. Also, they have the flexibility needed for configuration structures.

I don't think all things are files is a good idea. Why I must to add a virtual file system implementation in an embedded device?

the registry also exports to a file

you can cache it tho

Sometimes it can't solve the problem. For example, Microsoft's Update Databases XMLs, 10 GiB of size. Load it with long time.

and how is a not-file going to solve bloat?