Let me address this. I am not forcing anything on anybody. I am only stating my opinions. Feel free to ignore me, it is that simple.
Yes, we can write a Haiku book, and we have.
But we cannot incorporate BeBook’s contents, or modify BeBook itself.
So the Haiku book will eventually obsolete the bebook once all information is available.
1 Like
A little question, to maybe make this whole thread a little bit useful and constructive :
As of now, should the Haiku Book be considered additional to the Be Book, or should it be taken as complete ? Like, if one wants to understand the workings of some parte of the OS, or how to code something, should this person study both books, or only the Haiku Book would be enough ?
3 Likes
You’d first read the Haiku book, and if that is incomplete or unclear than read the BeBook, and then the actuall sourcecode.
(If the Haiku book is found to be unclear in some aspects it is a good idea to then see if one can update the documentation in that regard)
1 Like
Technically they are ports.
I think what @pvalue is referring to is software originally written for Haiku.
Let’s take an example. Do you know Zello? It’s an application that turns a phone into a walki talkie. It is widely used in logistics companies. Imagine creating such an application, but for Haiku. In this case it would be a dispatcher. You know, to manage messages between different carriers.
Obviously, right now Haiku is not mature enough to be used in a large enterprise environment, such as a logistics company. But it could be used in small companies. A good example of this would be to create a small application to manage a small store: manage the warehouse, make inventories, print customer invoices…
I think the state of haiku is quite good, actually.
- It has a stable basis, it crashes significantly less than a few years ago
- It is quite fast and reactive (also much better than a few years ago)
- It has quite good hardware support for a niche OS, especially with the wlan drivers.
- It has i great range of software directly available in haiku-depot, games, office, cad, webbrowsers …
Of course more native applications would be very welcome, but you have to be reasonable and realistic. Nowadays we even have wine support. - It has great and unique features like indexable and searchable file attributes, file translators and packagefs
What is missing?
For ME it is:
- Disk encryption
- Multi Monitor Support
- Webcam Support
- KVM Drivers
- Multiuser
Back in the 90’s - mid 2000’s, maybe. Nowadays, this is all platform agnostic stuff generally done via a web based interface. As such - there is nothing Haiku can offer. For inventory, hand held devices with barcode readers are pretty normal. These are either going to be in a phone or small tablet form factor running Android, iOS, Linux or an custom embedded OS. Developing this type of stuff in a full desktop OS SDK would be absolute overkill - way more likely to be React Native, Flutter or something like that - platform agnostic. I do Android dev and there is pretty much nothing you can’t make an Android phone do these days - even just using stock hardware. But with BLE/Bluetooth and USB-C you can pretty much connect to anything.
I don’t know.
Layers and layers of web technology to do a simple task.
Would a bloated application come out?
I’d rather use Kexi to make forms visually, and create a small, fast, and specific application.
Everything else is making it bloated.
That’s precisely the Haiku philosophy, fast, small, optimized, simple…
1 Like
Flutter and React Native are no different that doing the app natively. And Flutter will also work on the Web, and React.JS is not such a massive jump. So - not, not bloated.
I also think you don’t really seem to appreciate how hard writing the app you suggested is and make it actually scale. If more than one user it doing any operation concurrently, you need a server to host the core logic and synchronisation. Any type of database needs to also be centralised… Sure you could write a toy app on a single user system with one concurrent user. But it is pretty useless in a real world situation.
Do you know how small businesses really work?
Or family businesses?
You’d be surprised to know that of those small businesses, the most advanced, use Excel for everything (no macros).
1 Like
So aim low and hope for the best? Not the best business model. I get why you think that is a good idea, but aiming low and not designing for scaling the app means that that is all it will ever be able to achieve - low business, small capacity, single user. Maybe there is a market for this, but it is not a flagship product that will drive growth and adoption of Haiku. It sounds more like a personal product for fun on the side.
Working in the industry for 25 years, it is a lot harder to maintain a small volume product because users will ask for the world. There is just as much work in creating what you talk about and actively avoiding the complexity will make is less likely to fit future demands.
Yes, I would be surprised. Very surprised. Small businesses that do everything on Excel tend to stay small or disappear.
That’s not what I had in mind, but it’s still good