zare_st
Otherwise you're just switching port (16-bit) value to arbitrary 32-bit identifier.
It's a war, things have changed.
If a line of code belongs in a project with one file and a main() function, the presumption of impact of that code line on overall code paths is trivial.
If that line of code belongs in a library procedure used by a million LOC project, presumption cannot be done if you don't the project internals and tooling.
Rewriting entire systems or frameworks because one thinks that it's hard to implement a certain class of features is almost always a recipe for disaster.
I'll show myself out
FreeBSD had to mock several parts of systemd in order to port newer GNOMEs that are dependent on systemd. rc still runs this software, but unfortunately software depends on systemd sockets which is absurd design choice but here we are. Again mocking the absurd interprocess part is the way to go, as opposed to supporting entire specification and API of systemd.
"Any unix" doesn't cut it, too general, too broad. You did ask in dual sense in your original question but then you specifically stated FreeBSD as an example; so I'm answering for FreeBSD specifically.
The problem that I have with opinion in your post is an implication about groups of people - people with skills that should supposedly write a systemd clone for FreeBSD or other Unices, and people without skills that are supposedly waiting for the first group to do some work so they can enjoy systemd on *BSD or wherever. Let me be blunt here, I can assure you this is not the case. Systemd is not a factor for anyone in BSD world and it's a factor only for people that would like to migrate from Linux and retain their usual workflow and muscle memory.
In practice this means more seamless 'isolation' in Linux case but that isolation is weak. Which perfectly corresponds to FreeBSD looking at server uses 99% of the time and Linux looking at the desktop too.
About your conclusion, I don't think that's based on anything so please do write on what facts do you base the assessment that FreeBSD has no resource limiting and isolation features, and that it would be a 'separate implementation', as FreeBSD always tends to upgrade and not change tools and interfaces, and that there is not enough interest from anyone to implement it, as most major FreeBSD features are actually paid for by FreeBSD sponsors.
Besides "daemon writers" could just default to foreground, because if it's ran as a daemon it is ran from a script hence nobody cares for extra option typing such as -d --daemon, it's written once in a file, as opposed to doing "program --foreground" every time you want it to run in front of you
You'd rather start here https://www.romhacking.net/games/884/ and read a romhacking guide. The asset editors and utilities might be enough. More advanced stuff by some asm hacking which may come in form of preexisting patches. Usually it requires understanding only a portion of game's architecture and memory layout.
If you're really keen to start such a project, as I would be keen on playing it, you're likely to spend entire first phase development in level editor getting the sprites and maps right.
If there is a thing, and topic about it has reached the internet discussions, the participants will have an opinion regardless of their actual practical knowhow about the thing. They'll form their opinion otherways. Platforms like Reddit favour a master opinion due to score and moderation system, so one out of N wrong theories will surface as the master opinion.
In real life, if you ask bunch of random people about the thing they don't know, you get wildly different answers, and largely no-one will back up anyone there. Certainly not in enough force to push a confidently wrong answer up as the "people's opinion"
They sent us custom BIOSes until it got stabilized and said they'll put the patch in the following BIOS releases.
The thing is neither Intel nor AMD nor Supermicro can test edge cases at max usage in niche environments without paying money, but they would really love to claim with backup they can be integrated for such solutions. If Intel wants to test stuff in space for free they have to cooperate with NASA; the alternative is in-house launch.
Reddit is ok and quite cool for targeted discussion on targeted sub-reddits. But all the general subreddits visited by general population and everything that pops once in a while on the front page is a target for hive mind.
For HN comparison, there is a lot of "wrong" here too, but here you can find a cited academic study from one good American university that reveals most of the botfarms and fake news disseminators come from western sphere. If you try to claim on Reddit or anywhere on the internet that fake news champion is not Russia+China+whoever is evil, your entry will get buried.
Also, ask yourself who's the median redditor. For my country's national subreddit the median redditor is a high school kid from the capital.
Official nvidia drivers have been added to FreeBSD repository 21 years ago. I can't count the number of different types of drivers used for ATi/AMD in these two decades. And none had the performance or stability.
The stuff you're talking about isn't about browsers its about the websites.
If you had a website that uses javascript to parse MD or any other markup, spit it out as trivial HTML with light DOM, client-side formatting can do everything you want.
The problem is that modern websites use patterns that workaround users' capability to customize the presentation of the website. They do not want you to look at their site the way you want.
Similar type handler is engaged with XML. Unless you can utilize W3C standards to implement a custom markup language using XML/XSLT and have it work across browsers without plugins.
SVG is vector graphics.
For another full markup to be even considered there would have to be one that's widely adopted and realized through plugins. Nobody is making interventions in standards to open up venues for easy implementation of custom markups when those markups are used by 0.001% of publishers.
Asking genuinely, I don't know, but it's an important fact to take into account if you're planning ahead.
I don't expect that url.html is a static html file. I expect it to be server-side generated in 2024. For me site.com/page and site.com/page.html are the same. I do not expect different behavior from my web client side. So I may switch backend engine every year, and I'll just route the request sfrom page.html and that's it.
What's way worse than this is using non-HTML extensions for emitting html. I go to pichost.com/image.jpg and I get a webpage served. This is a bad pattern and it needs to go away. I'm not even going into responding differently depending on user-agent or referrer, if you have combination of these you get JPG returned, if you don't you get a webpage returned.
The question isn't whether Dyson speheres radiate, the question is can we detect an artificial megastructure and my answer is no, based on the hypothetical Dyson design.
Of course everything radiates heat I did not think I have to get down to that level in commenting here.
The data is analyzed as a dynamic system. Radar just looks at a bounce. If you setup radar incorrectly you might get false hits and no returns on valid targets. If you use a wrong model in analysis of astronomical data you're never getting anywhere close to a correct result.
On the other side VirtualBox the software application is designed to integrate with the desktop well, VNCing into the guest is not an alternative to this.
I hope efforts will be made in FreeBSD world too against its bhyve hypervisor.
The terminology issue is curious but it has been already covered here lately in a topic about Linux direct rendering manager, DRM. The acronym was used in a narrow circle of people compared to "the whole ICT", as were keyboard-video-mouse devices. Less than 1% of professionals deal with Linux internals on that level, and less than 1% of professionals are server room on-site engineers. There wasn't collective consciousness about these terms so they got reused.
Also LVM is taken by something else (storage) and LKVM would be confusing.