Bro, I feel like that's just some generic AI written garbage lines

Rust is just another language that brings higher level ergonomics to code lower level stuff and that's it

Nowhere in the Rust book or their website says it's a C replacement. That's a decision individual programmers have to make

You believe? Sure

it's just an ideal balance of simplicity and performance as for lowlevel cross-platform imperative language

^

There are kernels written in micropython too. These kinds of arguments don't invalidate the use case of C. https://github.com/w84death/smolOS

https://github.com/pizlonator/llvm-project-deluge/tree/deluge https://www.theregister.com/2024/11/12/trapc_memory_safe_fork/ Possibly useful links..as option of solutions 🤔

Ada. Fortran? ☺️🙈🤔 ohh yeah difficult situation with zoo of languages 😢

Ada is actually pretty good

Hi all I have a question.What does it mean by kernel configuration file?

I want to install run driver

https://docs.freebsd.org/en/books/handbook/kernelconfig/#kernelconfig-config

https://docs.freebsd.org/en/books/handbook/kernelconfig/#kernelconfig-config

I need to make my own conf file??

no, you copy an existing one

no, you copy an existing one

But can I edit in GENERIC?

no, you copy an existing one

Oh ok

thing is you shouldn't

GENERIC is GENERIC.. if you make changes to it, it's no longer GENERIC.. so you should name it anything else, so that you and everyone else that helps you in the future will KNOW for certain that it's your own kernel and not the one shipped

Should I edit Bus support in MYKERNEL?

There is only ata and scsi controllers except

Hi all I have a question.What does it mean by kernel configuration file?

I mean where to write these lines?

maybe reading the docs on configuring the kernel could be a good start BTW

Hi all I have a question.What does it mean by kernel configuration file?

I solved these, but where should I put device runfw (firmware)?

Rust plebs have been screaming about this since 2014? https://gitlab.com/b17wise/personalDotfiles/-/tree/main/c/buffer_exploit

Reminder that we are not on a PDP-11 and C is not portable assembly

Reminder that we are not on a PDP-11 and C is not portable assembly

I think you misunderstood what portable assembly means

All bare metal languages generate assembly, but C is the closest to them, with the least amount of syscall overhead. The abstraction is so bare minimum that tinyC implementation was like only 60k lines of code

Isn't IR or mlir or GNU gas portable assembly?

I've seen C and to me any command based language seems more like assembly than C, hell C not having registers should tell you how alien it is to assembly.

😳

Well, there was a number of even more bare-metal languages like forth, C-- etc.

Forth is bare metal but not to X86, since forth is based around a stack and X86 is based around registers.

I think that's why it's slow too, slower than python in some cases

I think, but what do I know, the factor folk think compilation optimizations could lead to faster programs, but if you do that then you break the interpretive nature of forth.

Isn't IR or mlir or GNU gas portable assembly?

afaik gnu gas doesn't support universal IR code, as llvm ir for examplle

but i guess you don't want to write projects in llvm ir and so you prefer C

Unless you're tsoding

I could've sworn they had an intermediate representation which is how they achieved the compiler collection

yes thats reasonable

but probably it's stored in memory and discarded after compilation

i'm too lazy to deep dive into gcc

So am I

https://gcc.gnu.org/wiki/GIMPLE

I've seen C and to me any command based language seems more like assembly than C, hell C not having registers should tell you how alien it is to assembly.

C is not assembly itself. C is high level to assembly. C language has registers, just it doesn't directly provide access to specific registers like assembly language. It uses the register keyword as a hint to the compiler to potentially store a variable in a register for faster access. That's it. Direct register access would make C non portable.

One thing you can be sure about is, that C is portable assembly. All bare metal languages can generate assembly but C was the first to do so in a very expressive manner in the history of mankind. And the second is C++/Rust are not C alternative and neither C is alternative to those. There are good reasons to pick one over another but they are merely replaceable

Forgot about fortran

Anybody played warband?

One thing you can be sure about is, that C is portable assembly. All bare metal languages can generate assembly but C was the first to do so in a very expressive manner in the history of mankind. And the second is C++/Rust are not C alternative and neither C is alternative to those. There are good reasons to pick one over another but they are merely replaceable

Also there were lisp machines. Way before C. Talk about expressive!

Also there were lisp machines. Way before C. Talk about expressive!

This is ridiculous Flan I don't think you've ever used FORTRAN or Classic LISP. Those languages are very different from C. C was special because it could do low-level tasks very quickly. It was used to rewrite UNIX V4 and then V5 and so on, though early C compilers weren't perfect, they were good enough to generate native assembly on many different architectures, which made UNIX spread like viruses. It's well known that C's unique blend of expressiveness over assembly with sufficient memory level control just like assembly still makes it unique.

Compare the C answer to any of the assembly languages here https://rosettacode.org/wiki/100_doors In what way does C compare to any of them at all.

Compare the C answer to any of the assembly languages here https://rosettacode.org/wiki/100_doors In what way does C compare to any of them at all.

Have you ever written anything in assembly and then the same thing in C and tried to use the same code across different architecture?

No. I've only have ever had X86.

I have written code from forth and know that forth machines existed with its assembly language, and forth does not look like C

No. I've only have ever had X86.

With assembly, you'll need to put machine level instructions (OPCODE mnemonics) sets. These instruction sets were native to each architecture/board specific and don't work in another. With C, you can generate native optimised assembly from the same code base. The C compiler can generate native assembly (though that depends on the Implementation of the compiler)

So why is C portable assembly and not pascal? If you have to build an AST then your language is not assembly

C doesn't support SIMD though, you have to optimize by hand no?

So why is C portable assembly and not pascal? If you have to build an AST then your language is not assembly

Pascal had manual memory management?

C doesn't support SIMD though, you have to optimize by hand no?

What? Why do you think <immitrin.h> for?

It maps directly to SIMD instructions

Fine

C is NOT assembly language, but it generates native assembly. And that depends on the implementation of the C compiler and how well it does. But what I was saying is that when people treat C is "it can do everything, so let's write the next desktop environment" in it, then the next "Music app" in it, then you are looking at manual memory management on a large codebase without a significant compiler checks (because C is less opinionated than Rust) and that leads to all sort of possibilities to access footguns

But if you treat C as portable assembly, start small and stay small, you have a fairly manageable code base even with limited man power

C is NOT assembly language, but it generates native assembly. And that depends on the implementation of the C compiler and how well it does. But what I was saying is that when people treat C is "it can do everything, so let's write the next desktop environment" in it, then the next "Music app" in it, then you are looking at manual memory management on a large codebase without a significant compiler checks (because C is less opinionated than Rust) and that leads to all sort of possibilities to access footguns

There are tools to write secure C. Rust is not the first nor the best or prettiest secure language. I"ll pass the hype this time

There are tools to write secure C. Rust is not the first nor the best or prettiest secure language. I"ll pass the hype this time

Same

c is jut diy everything, the security of c code represents the knowledge and experience of the dev

c is jut diy everything, the security of c code represents the knowledge and experience of the dev

I mean I write some of my own tools in Rust for fun, but the selling point of Rust should be "high level ergonomics without garbage collection" rather than "It's C/C++ killer, let's rewrite everything". Oh well, Rust project never said that either, it's just Rustaceans who does

I mean I write some of my own tools in Rust for fun, but the selling point of Rust should be "high level ergonomics without garbage collection" rather than "It's C/C++ killer, let's rewrite everything". Oh well, Rust project never said that either, it's just Rustaceans who does

rust project says that they are Nintendo and you shouldn't do any funny thing with the rust project name

rust project says that they are Nintendo and you shouldn't do any funny thing with the rust project name

You mean Rust foundation?

You mean Rust foundation?

idk properly, just saw some terms somewhere, that's all i remember my memory is a mess

this is a true nintendo moment

this is a true nintendo moment

Lol that's crab lang policy

Lol that's crab lang policy

crab lang isn't rust? or am i missing some context?

crab lang isn't rust? or am i missing some context?

Hahahaha

BTW for those who use memstick images to install FreeBSD: https://x.com/cperciva/status/1860394948258078732

BTW for those who use memstick images to install FreeBSD: https://x.com/cperciva/status/1860394948258078732

I know hybrid ISOs from Linux distributions but not from FreeBSD. Does FreeBSD build a hybrid ISO by default?

I know hybrid ISOs from Linux distributions but not from FreeBSD. Does FreeBSD build a hybrid ISO by default?

Since long time ago

Since long time ago

What's the tool to create such images?

What's the tool to create such images?

I think isohybrid tool

BTW for those who use memstick images to install FreeBSD: https://x.com/cperciva/status/1860394948258078732

yeah, i all of the time just put the bootonly iso on ventoy usb