alt Hacker NewsGenuine question(s):
1) why does it matter “my” patch was submitted? I am simply a bystander but can’t help notice a tone of being admitted to a tribe? Am I wrong ? (It’s ok if it’s a tribe just validating my observation is correct or incorrect)
2) is the Linux kernel on its way to obsolescence? Our field of software engineering and how and what it’s applied to is changing at a drastic rate. The os was built for programs to run which were built by programmers. The programmers thought about what the users of their programs needed to get stuff done and use the programs. This paradigm is changing - fast - an in 10 years it’s going to be very diff place where the users simply build programs or their agents etc. thier expectations of the OS and what “services” and interfaces the os exposes is going to change. And at some point the current os architecture is just not relevant. To build an AI first OS it’s prolly easier to build it from the ground up than keep changing Linux. It’s like we can keep trying to slap on jets to the car to make it go faster but it’s prolly just better to build a plane. We still will need to travel just what we use is going to be diff and as such older mechanisms of traveling will just be irrelevant. Why am I wrong ? What am I missing ?
> why does it matter “my” patch was submitted?
If you want your code in the kernel, it has to be accepted. If you don't care, then it doesn't matter at all.
> is the Linux kernel on its way to obsolescence?
Only if computers are, which is unlikely.
> Our field of software engineering and how and what it’s applied to is changing at a drastic rate.
Rate of change is not a useful metric here.
> The os was built for programs to run which were built by programmers.
AI code is still programs written by programmers, it's just some of the programmers are AI.
> The programmers thought about what the users of their programs needed to get stuff done and use the programs.
Yes, this is how you build software useful to the users. This won't change. If you make a program without thinking about how it's used, you haven't made a useful program. There are lots of apps throughout history in this pile, programs that were never fit for use.
> This paradigm is changing - fast
It's not, and it never will. Programs always have to be fit for use, and have to be useful tools for the users.
> - an in 10 years it’s going to be very diff place where the users simply build programs or their agents etc.
This doesn't change anything about Linux or applications, though. 100 years ago you bought meat and veggies grown nearby so your home because we didn't have transportation. Refrigerated trains made it possible to ship food long distances quickly and while cold. However, this did not change the way people ate the food, they still used pots and pans to cook, plates and utensil to eat, etc. Same thing here. Rather than artisanal, hand crafted code we'll use robot-generated code, and it won't matter at all to the user, or how applications need to be fit to the job.