I can see this happening. The value of Windows kernel is pretty much gone, all it is is another expense on Microsofts budgets, so they could just shed the whole thing. They would mainly be concerned with porting all of their.NET stuff over to Linux as a migration pathway, which is already happening. I can could see them dropping the Windows kernel and replacing it with Linux kernel, basically Windows becoming a Linux distribution, maybe even dropping their C++ compiler and their C-land toolchain as well. It would still be called "windows' but much of the internals would be Linux stuff like the kernel, who knows, maybe even Wayland for graphics stack. A compatability layer (like WINE) for Windows applications to run on top of it. Maybe Microsoft will just fix up WINE to be good enough as a migration path.
Another possible cause are GMOs. Many GMOS are toxic due to their side-effects. But many are also designed to essentially have a built in toxn, bt toxin, built into them. This toxin is toxic to insects. So you have all of this GMO crap around, GMO corn, GMO soy, GMO this and that, and this stuff can end up basically everywhere. Remember that the GMO crop plant will become a wild plant. So your going to have these GMO things growing wild in forests and it produces its own built in insecticide that kills insects that eat it. Do you realize how dangerous this is? GMOs also have been shown to be harmful to humans, such as to affect gut microbiome and to be leading to an increase in diseases. Remember, YOU CANNOT CONTROL these GMOs, they will spread through the environment so you are going to have these GMOs growing wild in forests and so on, its just going to throughly contaminate the environment.
Of course Roundup Ready crops also come coated with pesticide residue which could kill insects that try to eat it.
These GMO crops and pesticide coated crops do not become isolated on the fields where they are grown, they end up everywhere, in peoples homes, in trucks, in garbage and trash piles, etc.
Not only that but you have that the environment has become permeates with inslecticide and herbicide, not only on fields but all over peoples lawns, their homes, it all circulates widely through the environment ending up in lakes and rivers and so on, moves through the food chain, etc.
I think it is insecticides and herbicides. A recent study found roundup to be responsible largely for Honeybee Colony Collapse. You also have the huge amounts of insecticide people add to their lawns to control things like cinchbugs and snails, the vast amounts applied around peoples homes to control household pests, etc, the herbicides added to fields also affect insects and move up the food chain. All of this stuff washes with the rain into rivers and bodies of water and circulates through the environment.
This is an utterly INSANE remark. We have so many problems just trying to support a few billion with constant concerns over resource depletion and habitat destruction. An energy crisis and this is with oil, carbon reserves etc. No oil, no coal on mars. Where is all of vast amounts of energy going toi come from for what is a much much higher energy survival coast for being able to survive on mars or in these hostile foreign worlds, where you need vast energy supplies just to be able to breath? These insane ideas and remarks actually threaten to make our situation worse by stressing already finite resources on these crazy schemes.
Agreed, basically, the way they would have it, 2+2=5 would be true, under relativist perspective, if you think it is. There is no more objective reality with these people. They are going after empericism and mathematics and so on as being tools of oppression and being racist!
you are certainly not immune to the H1B program or whatever they call it wherever you are from. Companies are using H1B program to lay off American engineers to be replaced with cheap Indian labor , or the offshoring trick alternatively. This is why you should demand the program be abolished and that you need to realize that there is no "labor shortage", especially not with 50% of jobs set to be automated out of existance in the next few years. The labor shortage thing is a lie to justify laying off american workers.
They get their new mainframes from IBM of course, which also provides repair parts. Many of them use IBM mainframes for which there is an upgrade path to newer mainframe models built on todays technology. This is the case with the z/OS stuff which originated as System 360. IBM prides itself in full backwards compatability, mostly the case that an app written in 1965 for System 360 should still run on a 2018 IBM mainframe. Upgrading to a new mainframe is a fine solution. mainframes are designed to provide high uptime and are price competitive with commodity hardware
This is a good point. There are still dialup internet providers so someone who wants to keep using TIVO without broadband could subscribe to a dialup ISP and then set up a Linux box with the modem and configure a NAT router between the modem/PPP and their ethernet network.
There are quite a few BBSs that run over the internet, like ones based on WWIV which are run for nostalgic purposes. They probably still have dial up support. If your looking to avoid the internet, another option is NeighborNet where you run ethernet cables to your neighbors or bridge your wifi networks and set up your own community network. You could have a chain of such networks involving many people if you can get many to participate. Configure routers to route the packets around between the subnets. If you want to get fancy, you can even run your own BGP server!
C++ has some of the features you mention, such as vectors. Proposals to introduce C++ to the kernel are quickly rejected.
Kernel code is bound to be difficult. I've often thought, for drivers, maybe a compatibility layer that presents a nice stable API can be provided for people to write drivers for (not forced, the internal API can also be exposed), but as another option.This would avoid cluttering kernel internals with backwards compatability stuff but would provide a nice stable API for drivers to use.
Operationally it could be better simply to base everything out of KSC and the Orlando area so the control center and the launch site are not separated by 1000 miles. You could also say manufacturing should be based in the KSC/Orlando area so you are not forced to truck in big components halfway across the country. Just put everything around the launch sites. Orlando even has UCF which was set up for training astronauts and engineers to supply the space program `
I never understood why these companies do not simply write their software using Qt so that it will work across the operating systems, it makes financial sense to maintain just one code base that will run on all OSs.
You don't necessarily even need rpm or debs, there is also appimage, snapd, docker or flatpack which are being supported on most of the Linux distros. You shouldnt need to mess with the init system. Hypothetically if an init job is needed there are cross distro ways such as a sys v init file which is supported by systemd and most init systems. systemd has many new capabilities but fully supports the sys v unix init system, so you are not forced to use systemd's own init file format.
systemd also supports sys v init files, so an application that wants to be cross-distro can use those, if it really needs an init entry . systemd's own declarative format offers a lot of new features sys v didn't have, but you are not forced to use them due to systemd sys v init support.
Shouldnt be a problem. systemd fully supports sys v init files, which will work on most init systems. So sys v init files are the lowest common denominator that will work on most things.
No, its not a valid point. If you write a program with Qt,, it will run on all desktop environments, distributions, etc. It will even run on Windows and MacOS, and even in a web browser. Theres no need for an app developer to worry about the desktop environment.
Excellent explanation and you expose why this idea that "we HAVE to detect the flesystem being used" nonsense shows they don't know what they are doing. Just use xattr calls and if the exist, you can copy them over. no need for low level calls and dirty tricks.
An application should never try to bypass the main documented filesystem calls to try to access lower level calls that are not intended for applications. There are a variety of filesystem APIs for use by applications, including the aio calls for non blocking operation. No need to try to find a backdoor.
Actually, systemd is more modularized than the old init system, there are at least 40 independent binaries, and supports the use of d-bus to interconnect independent programs. it also supports the old sys v init files so systemd IS the traditional unix init system, since it fully supports the old paradigm. Yes, it significantly extends the initialization system with new capabilities, but your old sys v init files work perfectly well with systemd, and its perfectly acceptable to use sys v init for existing init files or writing new init files. This completely destroys the myths and propaganda from the anti-systemd people, its all hogwash. Before people spout some lie about systemd, please get your facts straight: http://0pointer.de/blog/projects/the-biggest-myths.html. The anti-systemd stuff is a pack of lies.
Its systemd, not systemD. systemd fully supports sys v init fine, so thats an option for cross distro support for initialization. This is also why the anti systemd propoganda is nonsense, people can still start their jobs with sys v init files if they want to, systemd adds significant new capability but does not remove any of the older interfaces and models. It only adds on to the older init systems.
The story is ignorant, and apparently written by someone who doesn't know squat about Linux. There is FUSE which is a stable way to add a filesystem driver. The desktop environments and file managers are irrelevant because they use the same filesystem API, and the same API for an app to draw to the screen (X and Wayland). You can use either Qt or Gtk for your GUI application, and it will work on any of the desktop environments. If you write your app for Qt it will run perfectly well on a Gnome desktop environment, if you write in Gtk it will run perfectly well on KDE, because they use the same underlying X or Wayland API. I don't know how many times this has been expained to tech journalists over the years but they still can't get it through their thick skulls. The filesystem variety is also irrelevant becuase the filesystems also support the same filesystem APIs. No userspace software should directly interact with a filesystem. We have flatpack, snapper, appimage, and docker for cross distro packages so that need is being covered. Because systemd supports Sys V Init files, you can use Sys V Init files to start a service and it should work on most distros, systemd or not. The service command is supported by most distributions. So increasingly there are cross distro common denominators for people who are writing applications. The variety of distros, desktop environments, filesystems and init systems is a strength, but there can exist a lowest common denominator cross compatible interface for applications to access.
The big reason people should use Linux is to free themselves from proprietary closed source OS that is designed to take away your freedom. You will notice that while SteamOS claims to be open source, actually the critical parts of it like the client, are closed source. I am all for Windows compatibility as a way for people transition away from windows while taking their apps with them. However the compatibility layer needs to be able to work on fully open source OSs otherwise people would just be giving up one proprietary OS with vendor lock in for another proprietary OS with vendor lock in. You should not have to use a particular Linux distro to be able to benefit from Windows compatibility. Wine is the best solution since it is open source. People need to work on making that better rather than fragmenting with another closed source platform.
Slashdot Mirror
I can see this happening. The value of Windows kernel is pretty much gone, all it is is another expense on Microsofts budgets, so they could just shed the whole thing. They would mainly be concerned with porting all of their .NET stuff over to Linux as a migration pathway, which is already happening. I can could see them dropping the Windows kernel and replacing it with Linux kernel, basically Windows becoming a Linux distribution, maybe even dropping their C++ compiler and their C-land toolchain as well. It would still be called "windows' but much of the internals would be Linux stuff like the kernel, who knows, maybe even Wayland for graphics stack. A compatability layer (like WINE) for Windows applications to run on top of it. Maybe Microsoft will just fix up WINE to be good enough as a migration path.
Another possible cause are GMOs. Many GMOS are toxic due to their side-effects. But many are also designed to essentially have a built in toxn, bt toxin, built into them. This toxin is toxic to insects. So you have all of this GMO crap around, GMO corn, GMO soy, GMO this and that, and this stuff can end up basically everywhere. Remember that the GMO crop plant will become a wild plant. So your going to have these GMO things growing wild in forests and it produces its own built in insecticide that kills insects that eat it. Do you realize how dangerous this is? GMOs also have been shown to be harmful to humans, such as to affect gut microbiome and to be leading to an increase in diseases. Remember, YOU CANNOT CONTROL these GMOs, they will spread through the environment so you are going to have these GMOs growing wild in forests and so on, its just going to throughly contaminate the environment.
Of course Roundup Ready crops also come coated with pesticide residue which could kill insects that try to eat it.
These GMO crops and pesticide coated crops do not become isolated on the fields where they are grown, they end up everywhere, in peoples homes, in trucks, in garbage and trash piles, etc.
Not only that but you have that the environment has become permeates with inslecticide and herbicide, not only on fields but all over peoples lawns, their homes, it all circulates widely through the environment ending up in lakes and rivers and so on, moves through the food chain, etc.
I think it is insecticides and herbicides. A recent study found roundup to be responsible largely for Honeybee Colony Collapse. You also have the huge amounts of insecticide people add to their lawns to control things like cinchbugs and snails, the vast amounts applied around peoples homes to control household pests, etc, the herbicides added to fields also affect insects and move up the food chain. All of this stuff washes with the rain into rivers and bodies of water and circulates through the environment.
This is an utterly INSANE remark. We have so many problems just trying to support a few billion with constant concerns over resource depletion and habitat destruction. An energy crisis and this is with oil, carbon reserves etc. No oil, no coal on mars. Where is all of vast amounts of energy going toi come from for what is a much much higher energy survival coast for being able to survive on mars or in these hostile foreign worlds, where you need vast energy supplies just to be able to breath? These insane ideas and remarks actually threaten to make our situation worse by stressing already finite resources on these crazy schemes.
Agreed, basically, the way they would have it, 2+2=5 would be true, under relativist perspective, if you think it is. There is no more objective reality with these people. They are going after empericism and mathematics and so on as being tools of oppression and being racist!
Why not simply use cash? Safe, simple, private, secure.
you are certainly not immune to the H1B program or whatever they call it wherever you are from. Companies are using H1B program to lay off American engineers to be replaced with cheap Indian labor , or the offshoring trick alternatively. This is why you should demand the program be abolished and that you need to realize that there is no "labor shortage", especially not with 50% of jobs set to be automated out of existance in the next few years. The labor shortage thing is a lie to justify laying off american workers.
They get their new mainframes from IBM of course, which also provides repair parts. Many of them use IBM mainframes for which there is an upgrade path to newer mainframe models built on todays technology. This is the case with the z/OS stuff which originated as System 360. IBM prides itself in full backwards compatability, mostly the case that an app written in 1965 for System 360 should still run on a 2018 IBM mainframe. Upgrading to a new mainframe is a fine solution. mainframes are designed to provide high uptime and are price competitive with commodity hardware
This is a good point. There are still dialup internet providers so someone who wants to keep using TIVO without broadband could subscribe to a dialup ISP and then set up a Linux box with the modem and configure a NAT router between the modem/PPP and their ethernet network.
There are quite a few BBSs that run over the internet, like ones based on WWIV which are run for nostalgic purposes. They probably still have dial up support. If your looking to avoid the internet, another option is NeighborNet where you run ethernet cables to your neighbors or bridge your wifi networks and set up your own community network. You could have a chain of such networks involving many people if you can get many to participate. Configure routers to route the packets around between the subnets. If you want to get fancy, you can even run your own BGP server!
If people did that it would certainly address a lot of their concerns about C without needing a new language
C++ has some of the features you mention, such as vectors. Proposals to introduce C++ to the kernel are quickly rejected.
Kernel code is bound to be difficult. I've often thought, for drivers, maybe a compatibility layer that presents a nice stable API can be provided for people to write drivers for (not forced, the internal API can also be exposed), but as another option.This would avoid cluttering kernel internals with backwards compatability stuff but would provide a nice stable API for drivers to use.
Operationally it could be better simply to base everything out of KSC and the Orlando area so the control center and the launch site are not separated by 1000 miles. You could also say manufacturing should be based in the KSC/Orlando area so you are not forced to truck in big components halfway across the country. Just put everything around the launch sites. Orlando even has UCF which was set up for training astronauts and engineers to supply the space program
`
I never understood why these companies do not simply write their software using Qt so that it will work across the operating systems, it makes financial sense to maintain just one code base that will run on all OSs.
You don't necessarily even need rpm or debs, there is also appimage, snapd, docker or flatpack which are being supported on most of the Linux distros. You shouldnt need to mess with the init system. Hypothetically if an init job is needed there are cross distro ways such as a sys v init file which is supported by systemd and most init systems. systemd has many new capabilities but fully supports the sys v unix init system, so you are not forced to use systemd's own init file format.
systemd also supports sys v init files, so an application that wants to be cross-distro can use those, if it really needs an init entry . systemd's own declarative format offers a lot of new features sys v didn't have, but you are not forced to use them due to systemd sys v init support.
Shouldnt be a problem. systemd fully supports sys v init files, which will work on most init systems. So sys v init files are the lowest common denominator that will work on most things.
No, its not a valid point. If you write a program with Qt,, it will run on all desktop environments, distributions, etc. It will even run on Windows and MacOS, and even in a web browser. Theres no need for an app developer to worry about the desktop environment.
Eh, WRONG. X11 apps will work fine on Wayland.
Excellent explanation and you expose why this idea that "we HAVE to detect the flesystem being used" nonsense shows they don't know what they are doing. Just use xattr calls and if the exist, you can copy them over. no need for low level calls and dirty tricks.
An application should never try to bypass the main documented filesystem calls to try to access lower level calls that are not intended for applications. There are a variety of filesystem APIs for use by applications, including the aio calls for non blocking operation. No need to try to find a backdoor.
Actually, systemd is more modularized than the old init system, there are at least 40 independent binaries, and supports the use of d-bus to interconnect independent programs. it also supports the old sys v init files so systemd IS the traditional unix init system, since it fully supports the old paradigm. Yes, it significantly extends the initialization system with new capabilities, but your old sys v init files work perfectly well with systemd, and its perfectly acceptable to use sys v init for existing init files or writing new init files. This completely destroys the myths and propaganda from the anti-systemd people, its all hogwash. Before people spout some lie about systemd, please get your facts straight: http://0pointer.de/blog/projects/the-biggest-myths.html. The anti-systemd stuff is a pack of lies.
Its systemd, not systemD. systemd fully supports sys v init fine, so thats an option for cross distro support for initialization. This is also why the anti systemd propoganda is nonsense, people can still start their jobs with sys v init files if they want to, systemd adds significant new capability but does not remove any of the older interfaces and models. It only adds on to the older init systems.
The story is ignorant, and apparently written by someone who doesn't know squat about Linux. There is FUSE which is a stable way to add a filesystem driver. The desktop environments and file managers are irrelevant because they use the same filesystem API, and the same API for an app to draw to the screen (X and Wayland). You can use either Qt or Gtk for your GUI application, and it will work on any of the desktop environments. If you write your app for Qt it will run perfectly well on a Gnome desktop environment, if you write in Gtk it will run perfectly well on KDE, because they use the same underlying X or Wayland API. I don't know how many times this has been expained to tech journalists over the years but they still can't get it through their thick skulls. The filesystem variety is also irrelevant becuase the filesystems also support the same filesystem APIs. No userspace software should directly interact with a filesystem. We have flatpack, snapper, appimage, and docker for cross distro packages so that need is being covered. Because systemd supports Sys V Init files, you can use Sys V Init files to start a service and it should work on most distros, systemd or not. The service command is supported by most distributions. So increasingly there are cross distro common denominators for people who are writing applications. The variety of distros, desktop environments, filesystems and init systems is a strength, but there can exist a lowest common denominator cross compatible interface for applications to access.
The big reason people should use Linux is to free themselves from proprietary closed source OS that is designed to take away your freedom. You will notice that while SteamOS claims to be open source, actually the critical parts of it like the client, are closed source. I am all for Windows compatibility as a way for people transition away from windows while taking their apps with them. However the compatibility layer needs to be able to work on fully open source OSs otherwise people would just be giving up one proprietary OS with vendor lock in for another proprietary OS with vendor lock in. You should not have to use a particular Linux distro to be able to benefit from Windows compatibility. Wine is the best solution since it is open source. People need to work on making that better rather than fragmenting with another closed source platform.