#haikuos — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #haikuos, aggregated by home.social.
-
@mason also, I’ll have to update the #haikuports version of #chez #scheme this weekend too, the patches I used to make it run on #haikuos have been adopted upstream and now released. Thus we can simplify that port!
-
Arrived home to newly acquired, old books. I read all three of these in my youth, but I foolishly gave away my copy of “Programming the Be Operating System”,when I left the UK, and two of my Spike Milligan memoirs were lost in a cellar flood in Munich. I feel a wonderful circular sense of completeness now. #beos #haikuOS #books
-
On April 22, 1999 @shacker, H. Bortman and C. Herborth released the BeOS Bible, an iconic book about #BeOS. 📕 #HaikuOS #BeOSBible http://birdhouse.org/beos/bible/welcome.html - The book is available at https://openlibrary.org/books/OL7407210M/BeOS_Bible_The
-
How do you know early when #Haikuos is preparing for a new release? It's when I start asking people to have a look at our #i18n / #translation tool and help complete translations for various languages.
For beta releases, our policy is to include only languages where the translation is at least 60% complete. This time we need help to reach this in Belarusian, Croatian, Bulgarian, and Slovenian.
Lithuanian and Slovak are above 60% but may need some help too.
-
How do you know early when #Haikuos is preparing for a new release? It's when I start asking people to have a look at our #i18n / #translation tool and help complete translations for various languages.
For beta releases, our policy is to include only languages where the translation is at least 60% complete. This time we need help to reach this in Belarusian, Croatian, Bulgarian, and Slovenian.
Lithuanian and Slovak are above 60% but may need some help too.
-
How do you know early when #Haikuos is preparing for a new release? It's when I start asking people to have a look at our #i18n / #translation tool and help complete translations for various languages.
For beta releases, our policy is to include only languages where the translation is at least 60% complete. This time we need help to reach this in Belarusian, Croatian, Bulgarian, and Slovenian.
Lithuanian and Slovak are above 60% but may need some help too.
-
And, with the kind support and assistance of Matthew Flat, the #haikuos port of #chez #scheme has landed in the main branch of the repository! That should allow a simplification of the #haikuports package in the future too!
-
Never mind just Linux; this would seem to raise serious issues for any group producing their own kernel without an army of lawyers on staff e.g. *BSD, RedoxOS, Graphene, ReactOS, Haiku, illumos and perhaps even plan9 and operating system textbooks and learning frameworks like FluxOSKit. There is furthermore some significant scariness about packets crossing borders rendering ppl liable for violations of all this when passing through spaces wherein USA agents may apprehend them.
#telix #Linux #BSD #NetBSD #FreeBSD #OpenBSD #RedoxOS #GrapheneOS #ReactOS #HaikuOS #illumos #plan9 #Hurd #FluxOSKit
-
I've just updated my little #HaikuOS laptop, a Panasonic CF-19 with an Intel Core 2 Duo 1.06 Ghz and 3 GB RAM. It's just awesome how fast this old system still is with Haiku OS. I write this via #Tokodon on the laptop and i miss this wonderful simple UI of BeOS/Haiku OS on my daily driver with #Linux.
-
Phase 2 took a step forward. Someone else fixed a threading issue and that made everything pass on the HEAD of the git repository for #Chez #scheme on my #haikuos build box. So I've just submitted the PR to the upstream project to re-establish Haiku support in Chez. Let's see how that goes.
Reminder, the #haikuports version of Chez Scheme is already available.
I've done a bit of experimenting getting #racket to build, but I'm not there yet. #Akku looks promising too.
-
The #chez #scheme port got merged in the #haikuports repository just under an hour ago.
Yay. Happy hacking #haikuos users who love Scheme (there must be at least four of us!).
-
The #chez #scheme port for haiku is progressing through review. I was impressed with the speed and quality of reviewing that was done so far. As a first time contributor to #haikuports it's really nice to get the feedback and tips. #haikuos #scheme
-
Well, I had to learn more that I was expecting (particularly about how tests work in the #chez #scheme code), but I've just submitted the PR on the #haikuports
repository. If that port gets accepted I'll have a go at getting the new #haiku machine types for Chez added to the upstream project.I might then move towards getting #racket up and running on #Haiku on the basis of the Chez port. #haikuos
-
A little update on my efforts to port #chez #scheme to #Haikuos . I'm pretty sure (as per my last post) that its running fine, but there are certain aspects of Haiku that need to be properly reflected in the test suite.
Chief among these areas is the filesystem - some file operations that the test suite expects to fail, which simply succeed. Some of this is because Haiku, as a single-user OS, basically gives you root rights across the whole filesystem.
-
Did some more archive spelunking and found some more Corum III for BeOS goodies; I've added a page to my portfolio with everything I've found so far:
https://taffer.ca/portfolio/corum3/
I haven't been able to find the BeOS source code.
-
#plptools, the #Psion comms suite for Linux and other *NIX-related OSes (see below), is currently going through an overhaul.
We're currently wading through almost 30 years of technical debt, improving thread safety and code readability. Slowly, we're reintroducing abandoned features and adding new ones.
My co-conspirators @jbmorley and @captfab have done the bulk of the work on this. I've been doing a lot of testing with physical hardware, as well as working on the ports and getting a better understanding of the current build system (autotools with gnulib) to get a clearer idea of whether it still works for the project today.
Primary supported OSes:
- Linux
- macOS
Secondary supported OSes (stable, but support will be slower):
- #FreeBSD 14.x
- #NetBSD
- #HaikuOS (With caveats - Haiku's USB serial is broken, but the the main Git branch of plptools has a workaround. Regular hardware RS232 works well.)
Coming soon:
- #OpenBSD (mostly works, but some stability issues in plpftp)
- FreeBSD 15.0 (won't compile, possibly an issue with gnulib)
In the distant future:
- Windows
The current main branch feels stable to us (more stable than the last release). If you want to give it a go, you can get it from here:
-
Vitruvian OS 0.3 has reached general availability!
#Linux #BeOS #Vitruvian #VitruvianOS #Haiku #HaikuOS #Computers #Laptops #TechNews #TechUpdates #Kernel #LinuxKernel
https://officialaptivi.wordpress.com/2026/03/26/vitruvian-os-0-3-has-reached-general-availability/
-
Can't wait to see how #Commodore will implement the new Age Verification Requirement in the the PET, VIC-20, C64, C128 and Amiga Workbench.
Same for #Plan9 , #OpenBSD , #IRIX , SerenityOS , FreeDOS , #ReactOS , OS2 , #HaikuOS , Minix3 , RISCOS , AROS , CPM , Solaris and KolibriOS...
The answer: They won't because it's ridiculous.
-
XFS on HaikuOS
Not major functionality changes or bug fixes anymore(All critical ones are already fixed 🙂) but a little bit of code refactoring.
- I found that every directory headers prefixes with Extent which is wrong, extents are basically what blockRun is in BFS so removed those prefix.
- Renamed Extent.cpp file to BlockDirectory.cpp since it implements block directory functionality.
-
Ich suche in meiner #Freizeit eine neue niedrigschwellige #Herausforderung technischer Natur für mich.
Liebäugle schon eine kleine Weile damit #Haiku auf einem (vernünftigen...) Endgerät zu installieren und eine Zeit lang als #DailyDriver einzusetzen.
Nur so. Zum Spaß.
https://www.haiku-os.org/"Berichterstattung" wäre hauptsächlich hier.
Auch wenn ich meine Entscheidung davon nicht beeinflussen lasse, hat das #Fediverse Interesse an den Erfahrungen die ich in dem Moment machen würde?#HaikuOS #haiku_os #AlternativeBetriebssysteme #AlternativeOS #BeOS
-
Ich suche in meiner #Freizeit eine neue niedrigschwellige #Herausforderung technischer Natur für mich.
Liebäugle schon eine kleine Weile damit #Haiku auf einem (vernünftigen...) Endgerät zu installieren und eine Zeit lang als #DailyDriver einzusetzen.
Nur so. Zum Spaß.
https://www.haiku-os.org/"Berichterstattung" wäre hauptsächlich hier.
Auch wenn ich meine Entscheidung davon nicht beeinflussen lasse, hat das #Fediverse Interesse an den Erfahrungen die ich in dem Moment machen würde?#HaikuOS #haiku_os #AlternativeBetriebssysteme #AlternativeOS #BeOS
-
Ich suche in meiner #Freizeit eine neue niedrigschwellige #Herausforderung technischer Natur für mich.
Liebäugle schon eine kleine Weile damit #Haiku auf einem (vernünftigen...) Endgerät zu installieren und eine Zeit lang als #DailyDriver einzusetzen.
Nur so. Zum Spaß.
https://www.haiku-os.org/"Berichterstattung" wäre hauptsächlich hier.
Auch wenn ich meine Entscheidung davon nicht beeinflussen lasse, hat das #Fediverse Interesse an den Erfahrungen die ich in dem Moment machen würde?#HaikuOS #haiku_os #AlternativeBetriebssysteme #AlternativeOS #BeOS
-
Ich suche in meiner #Freizeit eine neue niedrigschwellige #Herausforderung technischer Natur für mich.
Liebäugle schon eine kleine Weile damit #Haiku auf einem (vernünftigen...) Endgerät zu installieren und eine Zeit lang als #DailyDriver einzusetzen.
Nur so. Zum Spaß.
https://www.haiku-os.org/"Berichterstattung" wäre hauptsächlich hier.
Auch wenn ich meine Entscheidung davon nicht beeinflussen lasse, hat das #Fediverse Interesse an den Erfahrungen die ich in dem Moment machen würde?#HaikuOS #haiku_os #AlternativeBetriebssysteme #AlternativeOS #BeOS
-
XFS on HaikuOS
1. Fixed SMAP violation on reading files through vfs_read() call, looks like something changed since previously memcpy used to work in this call.
2. XFS partitions can now be scanned and identified.
3. Fixed bug on directory name comparison, previously we didn't accounted for length of string which could incorrectly report names as equal when one name is a prefix of another (e.g. "dir1" and "dir10")
-
Not feeling too good about the state of tech lately, so I threw a little money at Haiku to help them with their important work on creating alternatives.
-
#MAME 0.285 compiles on #HaikuOS after adding a small upstream patch (a missing
#include).If you're struggling to compile the latest version of MAME (I bet #FreeBSD and #NetBSD probably have the same issue), give this a go: https://github.com/mamedev/mame/commit/ffde4d3920ae99d2730db83982ffa9f8fbd8abd2
Anyway, there's a PR on HaikuPorts for the update, so it should be with you lovely people in the next few days.
-
Here's a thing that may get talked about #FOSS projects but if it does, I've never seen it. The issues with lack of diversity across gender and racial divides are well known but there is also a strong bias towards those comfortable with conflict.
I am retired. I have time. At various point across that time I have submitted patches to projects. The only positive experience I have had is doing #Hacktoberfest and submitting to the #ObsidianOCR project. Literally every other project was a negative experience. That one I actually submitted some substantial code changes, fixing bugs and adding capabilities. All were accepted, a few slightly modified but forward progress happened.
Literally **every other** patch I have submitted to every other project was immediately met with an argument. In none of these cases were I doing anything major. In all of these cases I looked first at coding style documents to make sure I conformed to whatever was desired for that project. In every case, rather than pursue an unpleasant argument about subjects for which I had no strong feelings, I said "fuck it" and walked away.
#HaikuOS was one of these. When you build the whole project from scratch (at least a year+ ago) there were tens of thousands of build warnings. The vast majority were trivial and ignorable but the insidious thing about that situation is that it a) masks important warnings that lead to bugs and b) leads to a culture of ignoring the very things warning you of problems.
I was more than willing to do the tedious and boring mechanical work of making warnings go away. I did not mind finding 30,000 warnings and making it 29,990 then lathering, rinsing and repeating. What I did not want to do was fight about it.
Which is exactly what happened. I asked in the dev chat about it before hand. These warnings were largely about implicit casting of variable types. You can fix it by changing the definition or casting at assignment. Let's say for any one error there are a dozen ways to fix it. I picked one that seemed reasonable, ran it up the chat flagpole and went for it. All attempts to get these contributions were met with me trying to justify why I used this type instead of that type or why I cast instead of changing the variable type or why I changed the variable type instead of casting. Whatever itch I was looking to scratch, this was not it. Instead I took the old laptop on which I had installed HaikuOS, powered it down and put it in a closet where it still sits.
A similar thing happened with the audi_connect integration for #HomeAssistant. Various functionalities broke, including starting climate control outside of EMEA. I found this the first cold day this year when my school day automation did not warm up my car. Turns out that the calls for that service had all been hard-coded to the EMEA specific versions. There was region setting code littered throughout this honestly ugly and chaotic file. I took some of that code and copied and pasted over the hard-coded version on my local install. Lo and behold, Home Assistant could turn on my heater.
I submitted this as a pull request and again, immediately had to justify why I did this and not that. I hate python and don't really know the deep idiosyncracies and best practices, nor am I ever going to learn that. I do know that I originated nothing. I took code that was already in the file and moved it to another place and made broken shit not broken. Even so, I was asked to justify why I did it that way. I wanted this fight even less than the other one so I thought "fuck you guys. My install works and I tried to do the right thing but I'm not going to fight you for that right."
What brought this all to mind is that I saw an update to the audi_connect component today. I opted out of that. I don't know for a fact this doesn't break it again. I'm certainly not applying this update right before two weeks of sub-freezing lows in my part of the country that is used to more temperate winters. I don't feel like rolling back and I absolutely am not spending the energy to dig through code I hate in a language I hate to figure this out again.
#FOSS is a good thing. I'm glad it exists. We should acknowledge that people with a temperament for argumentativeness are often the ones who often succeed in this game as it currently exists. There is a reason Linux is guided by someone with the personality of Torvalds and Wordpress with Mullenweig. They are assholes. I have coding capacity and periodically feel like using it. I will focus solely on micro-projects, ones so small that assholes don't have hill large enough to be king of.
Did I do everything right? Absolutely not. Does it have to be this way? Absolutely not.
-
Here's a thing that may get talked about #FOSS projects but if it does, I've never seen it. The issues with lack of diversity across gender and racial divides are well known but there is also a strong bias towards those comfortable with conflict.
I am retired. I have time. At various point across that time I have submitted patches to projects. The only positive experience I have had is doing #Hacktoberfest and submitting to the #ObsidianOCR project. Literally every other project was a negative experience. That one I actually submitted some substantial code changes, fixing bugs and adding capabilities. All were accepted, a few slightly modified but forward progress happened.
Literally **every other** patch I have submitted to every other project was immediately met with an argument. In none of these cases were I doing anything major. In all of these cases I looked first at coding style documents to make sure I conformed to whatever was desired for that project. In every case, rather than pursue an unpleasant argument about subjects for which I had no strong feelings, I said "fuck it" and walked away.
#HaikuOS was one of these. When you build the whole project from scratch (at least a year+ ago) there were tens of thousands of build warnings. The vast majority were trivial and ignorable but the insidious thing about that situation is that it a) masks important warnings that lead to bugs and b) leads to a culture of ignoring the very things warning you of problems.
I was more than willing to do the tedious and boring mechanical work of making warnings go away. I did not mind finding 30,000 warnings and making it 29,990 then lathering, rinsing and repeating. What I did not want to do was fight about it.
Which is exactly what happened. I asked in the dev chat about it before hand. These warnings were largely about implicit casting of variable types. You can fix it by changing the definition or casting at assignment. Let's say for any one error there are a dozen ways to fix it. I picked one that seemed reasonable, ran it up the chat flagpole and went for it. All attempts to get these contributions were met with me trying to justify why I used this type instead of that type or why I cast instead of changing the variable type or why I changed the variable type instead of casting. Whatever itch I was looking to scratch, this was not it. Instead I took the old laptop on which I had installed HaikuOS, powered it down and put it in a closet where it still sits.
A similar thing happened with the audi_connect integration for #HomeAssistant. Various functionalities broke, including starting climate control outside of EMEA. I found this the first cold day this year when my school day automation did not warm up my car. Turns out that the calls for that service had all been hard-coded to the EMEA specific versions. There was region setting code littered throughout this honestly ugly and chaotic file. I took some of that code and copied and pasted over the hard-coded version on my local install. Lo and behold, Home Assistant could turn on my heater.
I submitted this as a pull request and again, immediately had to justify why I did this and not that. I hate python and don't really know the deep idiosyncracies and best practices, nor am I ever going to learn that. I do know that I originated nothing. I took code that was already in the file and moved it to another place and made broken shit not broken. Even so, I was asked to justify why I did it that way. I wanted this fight even less than the other one so I thought "fuck you guys. My install works and I tried to do the right thing but I'm not going to fight you for that right."
What brought this all to mind is that I saw an update to the audi_connect component today. I opted out of that. I don't know for a fact this doesn't break it again. I'm certainly not applying this update right before two weeks of sub-freezing lows in my part of the country that is used to more temperate winters. I don't feel like rolling back and I absolutely am not spending the energy to dig through code I hate in a language I hate to figure this out again.
#FOSS is a good thing. I'm glad it exists. We should acknowledge that people with a temperament for argumentativeness are often the ones who often succeed in this game as it currently exists. There is a reason Linux is guided by someone with the personality of Torvalds and Wordpress with Mullenweig. They are assholes. I have coding capacity and periodically feel like using it. I will focus solely on micro-projects, ones so small that assholes don't have hill large enough to be king of.
Did I do everything right? Absolutely not. Does it have to be this way? Absolutely not.
-
Here's a thing that may get talked about #FOSS projects but if it does, I've never seen it. The issues with lack of diversity across gender and racial divides are well known but there is also a strong bias towards those comfortable with conflict.
I am retired. I have time. At various point across that time I have submitted patches to projects. The only positive experience I have had is doing #Hacktoberfest and submitting to the #ObsidianOCR project. Literally every other project was a negative experience. That one I actually submitted some substantial code changes, fixing bugs and adding capabilities. All were accepted, a few slightly modified but forward progress happened.
Literally **every other** patch I have submitted to every other project was immediately met with an argument. In none of these cases were I doing anything major. In all of these cases I looked first at coding style documents to make sure I conformed to whatever was desired for that project. In every case, rather than pursue an unpleasant argument about subjects for which I had no strong feelings, I said "fuck it" and walked away.
#HaikuOS was one of these. When you build the whole project from scratch (at least a year+ ago) there were tens of thousands of build warnings. The vast majority were trivial and ignorable but the insidious thing about that situation is that it a) masks important warnings that lead to bugs and b) leads to a culture of ignoring the very things warning you of problems.
I was more than willing to do the tedious and boring mechanical work of making warnings go away. I did not mind finding 30,000 warnings and making it 29,990 then lathering, rinsing and repeating. What I did not want to do was fight about it.
Which is exactly what happened. I asked in the dev chat about it before hand. These warnings were largely about implicit casting of variable types. You can fix it by changing the definition or casting at assignment. Let's say for any one error there are a dozen ways to fix it. I picked one that seemed reasonable, ran it up the chat flagpole and went for it. All attempts to get these contributions were met with me trying to justify why I used this type instead of that type or why I cast instead of changing the variable type or why I changed the variable type instead of casting. Whatever itch I was looking to scratch, this was not it. Instead I took the old laptop on which I had installed HaikuOS, powered it down and put it in a closet where it still sits.
A similar thing happened with the audi_connect integration for #HomeAssistant. Various functionalities broke, including starting climate control outside of EMEA. I found this the first cold day this year when my school day automation did not warm up my car. Turns out that the calls for that service had all been hard-coded to the EMEA specific versions. There was region setting code littered throughout this honestly ugly and chaotic file. I took some of that code and copied and pasted over the hard-coded version on my local install. Lo and behold, Home Assistant could turn on my heater.
I submitted this as a pull request and again, immediately had to justify why I did this and not that. I hate python and don't really know the deep idiosyncracies and best practices, nor am I ever going to learn that. I do know that I originated nothing. I took code that was already in the file and moved it to another place and made broken shit not broken. Even so, I was asked to justify why I did it that way. I wanted this fight even less than the other one so I thought "fuck you guys. My install works and I tried to do the right thing but I'm not going to fight you for that right."
What brought this all to mind is that I saw an update to the audi_connect component today. I opted out of that. I don't know for a fact this doesn't break it again. I'm certainly not applying this update right before two weeks of sub-freezing lows in my part of the country that is used to more temperate winters. I don't feel like rolling back and I absolutely am not spending the energy to dig through code I hate in a language I hate to figure this out again.
#FOSS is a good thing. I'm glad it exists. We should acknowledge that people with a temperament for argumentativeness are often the ones who often succeed in this game as it currently exists. There is a reason Linux is guided by someone with the personality of Torvalds and Wordpress with Mullenweig. They are assholes. I have coding capacity and periodically feel like using it. I will focus solely on micro-projects, ones so small that assholes don't have hill large enough to be king of.
Did I do everything right? Absolutely not. Does it have to be this way? Absolutely not.
-
Here's a thing that may get talked about #FOSS projects but if it does, I've never seen it. The issues with lack of diversity across gender and racial divides are well known but there is also a strong bias towards those comfortable with conflict.
I am retired. I have time. At various point across that time I have submitted patches to projects. The only positive experience I have had is doing #Hacktoberfest and submitting to the #ObsidianOCR project. Literally every other project was a negative experience. That one I actually submitted some substantial code changes, fixing bugs and adding capabilities. All were accepted, a few slightly modified but forward progress happened.
Literally **every other** patch I have submitted to every other project was immediately met with an argument. In none of these cases were I doing anything major. In all of these cases I looked first at coding style documents to make sure I conformed to whatever was desired for that project. In every case, rather than pursue an unpleasant argument about subjects for which I had no strong feelings, I said "fuck it" and walked away.
#HaikuOS was one of these. When you build the whole project from scratch (at least a year+ ago) there were tens of thousands of build warnings. The vast majority were trivial and ignorable but the insidious thing about that situation is that it a) masks important warnings that lead to bugs and b) leads to a culture of ignoring the very things warning you of problems.
I was more than willing to do the tedious and boring mechanical work of making warnings go away. I did not mind finding 30,000 warnings and making it 29,990 then lathering, rinsing and repeating. What I did not want to do was fight about it.
Which is exactly what happened. I asked in the dev chat about it before hand. These warnings were largely about implicit casting of variable types. You can fix it by changing the definition or casting at assignment. Let's say for any one error there are a dozen ways to fix it. I picked one that seemed reasonable, ran it up the chat flagpole and went for it. All attempts to get these contributions were met with me trying to justify why I used this type instead of that type or why I cast instead of changing the variable type or why I changed the variable type instead of casting. Whatever itch I was looking to scratch, this was not it. Instead I took the old laptop on which I had installed HaikuOS, powered it down and put it in a closet where it still sits.
A similar thing happened with the audi_connect integration for #HomeAssistant. Various functionalities broke, including starting climate control outside of EMEA. I found this the first cold day this year when my school day automation did not warm up my car. Turns out that the calls for that service had all been hard-coded to the EMEA specific versions. There was region setting code littered throughout this honestly ugly and chaotic file. I took some of that code and copied and pasted over the hard-coded version on my local install. Lo and behold, Home Assistant could turn on my heater.
I submitted this as a pull request and again, immediately had to justify why I did this and not that. I hate python and don't really know the deep idiosyncracies and best practices, nor am I ever going to learn that. I do know that I originated nothing. I took code that was already in the file and moved it to another place and made broken shit not broken. Even so, I was asked to justify why I did it that way. I wanted this fight even less than the other one so I thought "fuck you guys. My install works and I tried to do the right thing but I'm not going to fight you for that right."
What brought this all to mind is that I saw an update to the audi_connect component today. I opted out of that. I don't know for a fact this doesn't break it again. I'm certainly not applying this update right before two weeks of sub-freezing lows in my part of the country that is used to more temperate winters. I don't feel like rolling back and I absolutely am not spending the energy to dig through code I hate in a language I hate to figure this out again.
#FOSS is a good thing. I'm glad it exists. We should acknowledge that people with a temperament for argumentativeness are often the ones who often succeed in this game as it currently exists. There is a reason Linux is guided by someone with the personality of Torvalds and Wordpress with Mullenweig. They are assholes. I have coding capacity and periodically feel like using it. I will focus solely on micro-projects, ones so small that assholes don't have hill large enough to be king of.
Did I do everything right? Absolutely not. Does it have to be this way? Absolutely not.
-
Here's a thing that may get talked about #FOSS projects but if it does, I've never seen it. The issues with lack of diversity across gender and racial divides are well known but there is also a strong bias towards those comfortable with conflict.
I am retired. I have time. At various point across that time I have submitted patches to projects. The only positive experience I have had is doing #Hacktoberfest and submitting to the #ObsidianOCR project. Literally every other project was a negative experience. That one I actually submitted some substantial code changes, fixing bugs and adding capabilities. All were accepted, a few slightly modified but forward progress happened.
Literally **every other** patch I have submitted to every other project was immediately met with an argument. In none of these cases were I doing anything major. In all of these cases I looked first at coding style documents to make sure I conformed to whatever was desired for that project. In every case, rather than pursue an unpleasant argument about subjects for which I had no strong feelings, I said "fuck it" and walked away.
#HaikuOS was one of these. When you build the whole project from scratch (at least a year+ ago) there were tens of thousands of build warnings. The vast majority were trivial and ignorable but the insidious thing about that situation is that it a) masks important warnings that lead to bugs and b) leads to a culture of ignoring the very things warning you of problems.
I was more than willing to do the tedious and boring mechanical work of making warnings go away. I did not mind finding 30,000 warnings and making it 29,990 then lathering, rinsing and repeating. What I did not want to do was fight about it.
Which is exactly what happened. I asked in the dev chat about it before hand. These warnings were largely about implicit casting of variable types. You can fix it by changing the definition or casting at assignment. Let's say for any one error there are a dozen ways to fix it. I picked one that seemed reasonable, ran it up the chat flagpole and went for it. All attempts to get these contributions were met with me trying to justify why I used this type instead of that type or why I cast instead of changing the variable type or why I changed the variable type instead of casting. Whatever itch I was looking to scratch, this was not it. Instead I took the old laptop on which I had installed HaikuOS, powered it down and put it in a closet where it still sits.
A similar thing happened with the audi_connect integration for #HomeAssistant. Various functionalities broke, including starting climate control outside of EMEA. I found this the first cold day this year when my school day automation did not warm up my car. Turns out that the calls for that service had all been hard-coded to the EMEA specific versions. There was region setting code littered throughout this honestly ugly and chaotic file. I took some of that code and copied and pasted over the hard-coded version on my local install. Lo and behold, Home Assistant could turn on my heater.
I submitted this as a pull request and again, immediately had to justify why I did this and not that. I hate python and don't really know the deep idiosyncracies and best practices, nor am I ever going to learn that. I do know that I originated nothing. I took code that was already in the file and moved it to another place and made broken shit not broken. Even so, I was asked to justify why I did it that way. I wanted this fight even less than the other one so I thought "fuck you guys. My install works and I tried to do the right thing but I'm not going to fight you for that right."
What brought this all to mind is that I saw an update to the audi_connect component today. I opted out of that. I don't know for a fact this doesn't break it again. I'm certainly not applying this update right before two weeks of sub-freezing lows in my part of the country that is used to more temperate winters. I don't feel like rolling back and I absolutely am not spending the energy to dig through code I hate in a language I hate to figure this out again.
#FOSS is a good thing. I'm glad it exists. We should acknowledge that people with a temperament for argumentativeness are often the ones who often succeed in this game as it currently exists. There is a reason Linux is guided by someone with the personality of Torvalds and Wordpress with Mullenweig. They are assholes. I have coding capacity and periodically feel like using it. I will focus solely on micro-projects, ones so small that assholes don't have hill large enough to be king of.
Did I do everything right? Absolutely not. Does it have to be this way? Absolutely not.
-
Still playing with the Framework 12, now the system is a triple boot, as I installed FydeOS in addition of #popos and #haikuos .
There, tablet mode is working quite well:
* with a virtual keyboard respecting the selected layout in the OS,
* the physical keyboard and touchpad being disabled in tablet mode.Unfortunately, there is no screen rotation despite the option being active in the settings.
As much as I don’t like chrome, I must admit the system is really nice to use.
-
Still playing with the Framework 12 laptops.
So yesterday evening, I installed Haiku. Strangely enough I had to install using the beta5 iso, as installing with the 3 latest nightly isos just failed 🤔
However, after the successful installation, upgrading to the latest nightly just worked fine 🤷♀️The system is installed in UEFI mode in dual boot with Pop OS and using rEFInd as a boot manager.
Now some observation about Haiku on the Framework 12:
* While in the live environment during installation the trackpad works, once Haiku is installed and booted, it does not work 😪
* The WiFi is working contrary to the installation on my Thinkpad T450 😀#haikuos #framework12 #popos #uefi #refind #dualboot #thinkpad
-
Open drivers for NVIDIA Turing+ GPUs released for @haiku:
https://github.com/X547/nvidia-haiku/
https://discuss.haiku-os.org/t/haiku-nvidia-porting-nvidia-driver-for-turing-gpus/16520/162With this, it is now possible to have GPU acceleration in public builds of Haiku for the very first time!
-
Open drivers for NVIDIA Turing+ GPUs released for @haiku:
https://github.com/X547/nvidia-haiku/
https://discuss.haiku-os.org/t/haiku-nvidia-porting-nvidia-driver-for-turing-gpus/16520/162With this, it is now possible to have GPU acceleration in public builds of Haiku for the very first time!
-
Open drivers for NVIDIA Turing+ GPUs released for @haiku:
https://github.com/X547/nvidia-haiku/
https://discuss.haiku-os.org/t/haiku-nvidia-porting-nvidia-driver-for-turing-gpus/16520/162With this, it is now possible to have GPU acceleration in public builds of Haiku for the very first time!
-
Open drivers for NVIDIA Turing+ GPUs released for @haiku:
https://github.com/X547/nvidia-haiku/
https://discuss.haiku-os.org/t/haiku-nvidia-porting-nvidia-driver-for-turing-gpus/16520/162With this, it is now possible to have GPU acceleration in public builds of Haiku for the very first time!
