Although the volunteers and modestly paid developers are working hard to make Haiku a finished product, they are pointlessly working harder to port applications then should be necessary.
Specifically... developers are having to not only port over applications, which is a difficult enough task already... but to also make sure that when the apolications are ported.... they point to specific paths in the system that have the .self directory embedded within.
To be absolutely clear...no other Posix based operating system throws this unnecessary hurdle upon anyone who wishes to compile applications. These markers are clearly designed to be tied to specific versions of Posix software.
If you have upgraded Ubuntu or Open Suse in the last 5 years... you will know issues with package versioning has been long resolved...its a non issue now.
Yet the Haiku developers insist that these porting shackles are somehow better.
Anyone that has experience and puts thought into this knows its a grand waste of time.
The arrogance of the developers who insist this approach is somehow "the right way" coupled with a staunch adherence to this poorly thought out strategy is worthy of anyone-who-has-donated-to-the project's wrath and anger.
Because the difficulty serves to keep a useable Haiku off of user's computers DUE TO THE LACK OF A FULL SUITE OF APPLICATIONS THAT SHOULD OTHERWISE BE AVAILABLE.
The breakage to otherwise working Haikuware software evidences the unnecessary additional shackles that make the porting process even more difficult. What is worthy of outrage is that it is unnecessary.
Haiku has MUCH BIGGER BUGS TO SQUASH.
IS THERE A REASON TO waste time and money fixing problems we created outselves?
NO. THERE IS NO REASON.
Haiku lacks shared memory. This is why we don't have the big name open source applications.
BUT WE WON'T GET TO THE BIG ISSUES ANY TIME SOON IF WE KEEP DRINKING THE PACKAGE MANAGER KOOL AID.
No comments:
Post a Comment