4 ms·
You could always just write your own OS that only cares about running your app. Of course you are always going to run into problems if your program uses functio
by casey2 2y ago
You could always just write your own OS that only cares about running your app. Of course you are always going to run into problems if your program uses functions that you didn't design around. I think any Linux user could tell you that Windows programs don't run on Linux, so I don't know how you could have thought that there was some sort of portability guarantee between these two operating systems or even subsets of them.
If this is some OOP propaganda then I'm sorry but you got duped and the c++/qt community should act more professionally.
- p0w3n3d 2y agoI don't really get what is this OOP propaganda you're referring to. What I mean is that "build-anywhere run-anywhere" sounds really misleading, almost like Java's write-once run-anywhere. Of course you can always say "real programmers do not write ... blablabla" (in other words No True Programmer fallacy) but this is not solving anything, isn't it? I mean, let's make a sufficient abstraction that will allow real cross-system development?