3 ms·

Also I bet >50% of personal computer e waste is bog standard x86-64 by now. No need to support a vast array of hardware.

Gud 1y ago
Have you considered any advantages with ensuring code is portable?
- hnlmorg 1y ago
  Isn’t that an advantage by itself?
Imustaskforhelp 1y ago
> No need to support a vast array of hardware I hope you understand how unique netbsd is, it is one of the only systems which can be compiled so easily with just a single script even from linux or other systems and its rump kernel etc. drivers from what I know are (modular?) so they could be used with other kernels as well if any kernel wants ie. You never know where the innovation can be, I feel like that each kernel/operating system can bring a new idea, as an example, templeOS uses Holy C which basically is Just in time C (iirc) and that means that you can just edit files of templeOS and restart and those changes would occur I know TempleOS is niche and a meme OS but I feel like that there are a lot of ideas and unique operating systems and I have heard that netbsd can be good in giving driver support to. This is just one of many things, and I feel like the main point of NetBSD and the likes are fundamental hackability, they can run on things like routers as well although most run openbsd/freebsd but still. I don't see a reason not to unless you are speaking monetary (ie. it may take some extra funds developing/hosting but that is chump change) but I feel like NETBSD is a novel project with respectable goals and they aren't going to change just for this. More Options are a good thing. if I can have a project run on Netbsd, then its very easy to port it over to any other vast array of hardware as well, and that hardware includes extremely embedded hardware as well I guess
- ghostly_s 1y ago
  > I hope you understand how unique netbsd is, it is one of the only systems which can be compiled so easily with just a single script even from linux or other systems and its rump kernel etc. drivers from what I know are (modular?) so they could be used with other kernels as well if any kernel wants Aren't competing kernels already shipping support for this hardware? Surely the project has to have more selling points than "can be compiled with a single script."
  - Imustaskforhelp 1y ago
    Support for x86_64? I meant in the sense that since NetBSD supports soooo many devices, it can also help innovation in other kernels if need be as well by being able to take driver support via its rumpkernel as well if need be And to be honest, I feel like there is this sense of freedom knowing that you can have a system which is portable, if some script can run on my pc on netbsd, chances are if its not too specific, it could run on your pc or even your toaster lol! https://laughingsquid.com/netbsd-toaster/ https://laughingsquid.com/netbsd-toaster/ Netbsd can run on any device possible and I really appreciate it. >Surely the project has to have more selling points than "can be compiled with a single script." Personally I have only heard good things about netbsd but I don't have much expertise in it (sorry), I can recommend you to take a look at smolbsd which looks really cool for uni-kernel purposes as well https://news.ycombinator.com/item?id=45582758 https://news.ycombinator.com/item?id=45582758 I feel like that there is a lot more things that can be done with netbsd as well or other open source projects in general as well
    - tredre3 1y ago
      > Netbsd can run on any device possible and I really appreciate it. That's more of a meme than reality and I wish people would actually look into it before mindlessly repeating the trope. I did, when I wanted to run a new OS on a niche device, and the reality is very different. Nowadays Linux works on a lot more hardware than NetBSD does. Yes, NetBSD nominally supports a few more architectures than Linux (very few, especially that μClinux is now upstreamed), but the driver situation for the rest of the system means that it can't run on most devices from those architecture anyway.
deleted 1y ago
[deleted]

Gud 1y ago

Have you considered any advantages with ensuring code is portable?

hnlmorg 1y ago
Isn’t that an advantage by itself?

Imustaskforhelp 1y ago

> No need to support a vast array of hardware I hope you understand how unique netbsd is, it is one of the only systems which can be compiled so easily with just a single script even from linux or other systems and its rump kernel etc. drivers from what I know are (modular?) so they could be used with other kernels as well if any kernel wants ie. You never know where the innovation can be, I feel like that each kernel/operating system can bring a new idea, as an example, templeOS uses Holy C which basically is Just in time C (iirc) and that means that you can just edit files of templeOS and restart and those changes would occur I know TempleOS is niche and a meme OS but I feel like that there are a lot of ideas and unique operating systems and I have heard that netbsd can be good in giving driver support to. This is just one of many things, and I feel like the main point of NetBSD and the likes are fundamental hackability, they can run on things like routers as well although most run openbsd/freebsd but still. I don't see a reason not to unless you are speaking monetary (ie. it may take some extra funds developing/hosting but that is chump change) but I feel like NETBSD is a novel project with respectable goals and they aren't going to change just for this. More Options are a good thing. if I can have a project run on Netbsd, then its very easy to port it over to any other vast array of hardware as well, and that hardware includes extremely embedded hardware as well I guess

ghostly_s 1y ago
> I hope you understand how unique netbsd is, it is one of the only systems which can be compiled so easily with just a single script even from linux or other systems and its rump kernel etc. drivers from what I know are (modular?) so they could be used with other kernels as well if any kernel wants Aren't competing kernels already shipping support for this hardware? Surely the project has to have more selling points than "can be compiled with a single script."
- Imustaskforhelp 1y ago
  Support for x86_64? I meant in the sense that since NetBSD supports soooo many devices, it can also help innovation in other kernels if need be as well by being able to take driver support via its rumpkernel as well if need be And to be honest, I feel like there is this sense of freedom knowing that you can have a system which is portable, if some script can run on my pc on netbsd, chances are if its not too specific, it could run on your pc or even your toaster lol! https://laughingsquid.com/netbsd-toaster/ https://laughingsquid.com/netbsd-toaster/ Netbsd can run on any device possible and I really appreciate it. >Surely the project has to have more selling points than "can be compiled with a single script." Personally I have only heard good things about netbsd but I don't have much expertise in it (sorry), I can recommend you to take a look at smolbsd which looks really cool for uni-kernel purposes as well https://news.ycombinator.com/item?id=45582758 https://news.ycombinator.com/item?id=45582758 I feel like that there is a lot more things that can be done with netbsd as well or other open source projects in general as well
  - tredre3 1y ago
    > Netbsd can run on any device possible and I really appreciate it. That's more of a meme than reality and I wish people would actually look into it before mindlessly repeating the trope. I did, when I wanted to run a new OS on a niche device, and the reality is very different. Nowadays Linux works on a lot more hardware than NetBSD does. Yes, NetBSD nominally supports a few more architectures than Linux (very few, especially that μClinux is now upstreamed), but the driver situation for the rest of the system means that it can't run on most devices from those architecture anyway.

deleted 1y ago

[deleted]