I disagree with you on most of this, obviously, but this I agree with. ![]()
Thank you for staying engaged and posting a response.
I disagree with you on most of this, obviously, but this I agree with. ![]()
Thank you for staying engaged and posting a response.
What a ghastly thought.
One of the recent studies on the use of LLMs for coding reveals that, while developpers are more productive, the net result is writing and rewriting a lot of code in work in progress branches, but if you look at the main branch, where things land after being reviewed and tested, things actually slow down.
So, people work more, get more exhausted from doing so, and the code doesn’t meet the quality standards. So, yes, you can write code faster. In Haiku, this isn’t what we need. We already have quite a backlog of merge requests to review, and there’s no way we’re going to trust an LLM to do it for us.
Anyway, do what you want with your own project. I find attacks on Axel’s existing DriveEncryption work (not by you, but by other people here) unacceptable. Axel has already replied himbself, but I will add for completeness that his work on DriveEncryption and integrating it in a package managed Haiku led to the development of the launch daemon, as a way to give 3rd party packages more control on the boot process (previously this would be done by patching a shell script that handled the boot sequence). That is the kind of improvements that we get from trying to do things the right way, keeping the “big picture” in mind. And sometimes it doesn’t bring us where we wanted to go, and makes us takes large detours. But I would say it’s all worth it.
Well, I had not finished yet all the posts here, but I found a bit exaggerated expression - everyone - for all of those activities enlisted here : mostly covered by development.
Even for reading phisycally the code lines of Haiku needs knowledge where you find and also find a piece of development - especially if those touches more services and system places in the code tree.
I understand anyone’s passion while try to defend a perspective, but please avoid such words those too general and paint any of you a bit different picture than you may be really are.
It happened since I read the forum, and some of them a red alert to me to begin or continue a thread.
Most of the members, here, are not developers. If you want to use the word - everyone - try to step into other’s boots before use it .. and really, really issue those … if it fits to really everyone.