*it

Chatgpt is a thing, not a person

Not at all. I would not expect any riir project to reimplement the entire stack in rust. This is not calling a random C dependency. This is literally calling the OS’s API. Literally there’s just this and the kernel.

As you said its goal is to rewrite a C codebase. The C codebase is coreutils. The correct way to getuser is to use the OS’s API, which happens to be inside libc.so, which has nothing to do with coreutils, it’s an entirely different codebase. End of the story. The OS’s API needs to be exposed as a c library, because c is the only language that can be imported from any other language. If you were to rewrite it in rust, it would use extern 'C' and it could not be any other way. And uutils would still import it from libc.

Maybe one day we’ll see a rust rewrite of libc (tho it doesn’t make much sense), but this has nothing to do with uutils.

If you are asking for a rust wrapper around the correct way to getuser, you have literally posted it. You can find it in uutils.

Also, being compliant is just being compliant. I wouldn’t expect it to be called something like POSIX.rs unless it were implementing every part of POSIX. Which is clearly not what we have here. Or are you suggesting that bash should be called POSIX.c, because it’s in c and it’s POSIX compliant?

Well, if you want to be pedantic, I’ll entertain you a bit more.

You see, C and Unix were “born” together. So sometimes, POSIX intertwines them in weird ways. In this case, getlogin is declared in unistd.h because it’s part of the Unix standard API, however the POSIX standard states that it must be implemented in libc. So the POSIX compliant way to getlogin is to call into libc, which doesn’t need to be glibc, you could use musl and avoid the GNU dependencies. If rust’s stdlib were to offer a getlogin function, the proper approach would be to still call libc. It’s like if on windows you were to call into Win32 to getuser, except on *nix it’s the same file as libc.

If you want to replace the getlogin implementation, the POSIX compliant place to do it is not in coreutils but in libc, like the aforementioned musl library does.

So the key here is that getlogin is not art of the c system API. It is actually part of the POSIX APIs, it is just “located” inside of libc, which by the way, does not need to be GNU if you are concerned with uutils’ philosophy.

I would like to interject for a moment. What you are referring to as coreutils Is actually coreutils+libc+Linux… And fill the rest yourself.

The “anti rust” crowd spends half of their time yapping about how you still need c in some places, then why did you get upset with calling into libc here? Are you suggesting to rewrite every rust program in C so you can have only c calling into c?

I know that’s not what you meant… But those are all digital…

Assuming in pounds, I think the average American does this by standing up. It’s not really impressive.

You can tell this technician will fix the card from how he keeps that cigarette on his ear

I highly doubt that the birthrate in Italy is 1.14

The government and the media doesn’t stop yapping about how it’s declining and we are going extinct.

This happens of course for economical reasons, and the government comes up with the most half assed “solutions” to ever cross human mind. Like “reduce VAT taxes on diapers and powder milk” like that is gonna make any difference.

The point still stands. The victim thinks it’s empathy building, and wants to impose it, the CEO will think it’s “work ethic building” or some fake buzzword like that.

There hasn’t been a 26 C in like a week

I think most of them will be amused by how frustrating it is.

They believe they became CEO because of their innate ability and hard work. And that every other worker should have a harder time than them. And if they ever experienced the hiring process, they would make it more frustrating on purpose, for the same reason.

How can I be sure? This post proves that even the victims want to impose their same suffering on someone else. Now imagine if someone as entitled as a CEO were to experience that.

France 🤢

Come here in Italy where there is no tipping culture and you can hate pickpockets all you want

Wait, you mean like permanently? Like Maud?

Nah, boy. You gotta own it all the way

3 coffee shots. And that’s it

Snow in the plains. And the bottom part of the Marmolada glacier

• they both suck in different areas and excell in others
• Vim is only useful when SSH-ing into an embedded device. Emacs can’t even do that. So I agree…
• Tautology
• Tautology
• Yes, but you still need C in a handful of situations

Adding:

• All Unix style shells suck, and the shell should not be based on human readable text, but on serializable objects like in powershell
• The kernel should support windows style acls

But if it had that issue, you could have solved it by mounting gtk settings info the flatpak

Some apps Will draw their own cursor and there’s nothing you can do about it. However, what’s happening here might be something else, so, are these apps in flatpak?

I’ll give you a fast-forward of the subjects you need to study to actually learn this stuff (with links). Many of these are part of typical computer science curriculums. However, most will exclude at least some of this to its fullest. Note that it’s a lot of knowledge, you might find it frustrating to just deep dive into it on your own, don’t take it the wrong way, maybe follow an actual course and you will be guided into all of this. Maybe I’ll also try to give a run-down, skipping the preupedeitic knowledge… later… if I have time.

P.s.: to get the general feeling you don’t really need to know all of this tho. Just skim it. And dive deeper if you like it.

• Any respectable computer scientist needs to know at least some first order logic https://en.wikipedia.org/wiki/First-order_logic
  • Read the semantics part. You don’t need everything, but you must understand what it means for a Formula to be a logic consequence of a set of formulas
  • Read a bit the deductive systems part. I find “natural deduction” (in detail here https://en.wikipedia.org/wiki/Natural_deduction) easier to understand (more… Natural) however, your mileage may vary, many people find it confusing, hence why “sequent calculus” was invented. We’ll use the sequent calculus later
• You need to know lambda calculus https://en.wikipedia.org/wiki/Lambda_calculus If you know any functional programming language it will be easier, but it’s optional
  • You can learn it on its own, but it fits better as part of a “foundations of computer science” course. I don’t have a link for that.
• You also need to know a bit of programming in basically any strongly-typed language. This will give you some kind of general idea of what types and type systems are.
• Now you can put together what you know of types and sequent calculus, and learn what type derivation rule are https://en.wikipedia.org/wiki/Typing_rule
  • Now you understand the meme
  • You can also check out what type systems are as a whole https://en.wikipedia.org/wiki/Type_system
  • We have skipped Curry-Howard, but you can see how typing rules look a lot like logic deduction rules, in particular sequent calculus
• Hooray, time for Curry-Howard https://en.wikipedia.org/wiki/Curry–Howard_correspondence they basically notice the same similarity you just noted, but take it a step further, they can do it because they know other logics other than first order logic
• The next step, if you are interested, are theorem provers, which are the direct application of the correspondence https://en.wikipedia.org/wiki/Proof_assistant
  • Check out rocq or agda