BeGroovy Forums
Welcome, Guest. Please login or register.
March 29, 2017, 03:11:17 AM

Login with username, password and session length
Search:     Advanced search
Welcome to the BeGroovy Forums. Let us know what you think of the Haiku Alpha 4.1 release.
35809 Posts in 5215 Topics by 289 Members
Latest Member: macsociety
* Home Help Search Login Register
+  BeGroovy Forums
|-+  Recent Posts
Pages: [1] 2 3 ... 10

 on: January 02, 2017, 05:51:11 AM 
Started by NoBeForMe - Last post by NoBeForMe
2016 was a quiet year for Haiku, little was planned and less was achieved. Haiku Inc remained a dusty retirement home, where people go when their actual enthusiasm for Haiku has waned, to pop up once in a while and apologise for not having found the time to do their jobs, and then insist that only they can be trusted with this important role and there's no room for outsiders to do the chores they haven't found time for. Better, they seem to feel, that nobody does it than that there be any risk that it's done badly. Accordingly donations slowed to a trickle and trust in Haiku Inc. declined further. As usual noises were made about the need for contracted work to focus on delivering Haiku R1, as usual the actual work being paid for tended to be orthogonal to shipping Haiku R1. Begeistert continued to shrink in line with the Haiku community, fewer attendees and less to discuss.

Noises were made about upgrading Haiku's web site, in the end it seems their forums were migrated but the rest of the site was left alone.

One of the half-finished new things that delayed Haiku in the past, HPKG, has matured to the point where in 2016 we saw several repositories (depots?) announced by third parties.

Another attempt to ship a beta of Haiku R1 is seemingly under way. Although it spawned several bike-shedding discussions that could ensure it never sees the light of day, and it involves a branch strategy that will unavoidably divide Haiku's very small group of developers between effort to ship Haiku R1 and wild new extravagances, at least they got as far as proposing a concrete way forward and agreeing, or at least agreeing to disagree, over how to actually do it. Developers were initially split on questions of what exactly should ship, and this inevitably lead into re-opening the decision on 64-bit Haiku and on ABI compatibility. Should Haiku strive primarily to be compatible with BeOS R5? Or had people stopped caring, some time in the last 15-20 years, about BeOS and so Haiku should be its own thing? Did anybody really have 32-bit hardware to run a 32-bit Haiku release on? The answer to that seemed to be "Yes" although much less emphatically so than the last time this was brought up. Tangents also formed on the API design generally (it hasn't aged well, although nobody seemed willing to say that out loud) and on the need to get past GCC 2.x as the system's main compiler. Haiku R1 may yet prefer GCC 4.x (or by then more likely GCC 6.x) in order that software developers are able to make use of modern language features.

 on: August 15, 2016, 01:35:33 PM 
Started by Euan Kirkhope (UK) - Last post by MYOB
As you've already paid for it and the resellers who had stock have sold out, you're not really harming anyone just burning an image if you want it to use it. If its for nostalgia purposes they do turn up cheaper.

The package management thing has almost settled down in Haiku although I still think its vastly breaking from any concept of simplicity. People who got seriously annoyed about it breaking binary builds that they had been told would be broken mystifies me though.

New job has me nearly entirely working over RDP or ssh to the point that I'm considering using the third monitor on my work desk for a Haiku box to see if its workable. Previous job I tried but was stymied by how bad the OWA client was on older Exchange in non-IE browsers; although come to think of it I've not checked the new one in Web+ either. If I can't use a system day to day my interest in it wanes hideously and what little I can bring to it vanishes - when I was last productive - doing VLC maintenance etc - BeOS BONE was still pretty usable.

 on: August 12, 2016, 10:12:32 AM 
Started by Euan Kirkhope (UK) - Last post by altp

I'm still looking for a BeOS 5 disk. I lost mine in my last move :-/

There is one up on ebay now for $350. yikes!

BeOS was always a niche OS. At this point, except for nostalgia, there is really no reason to even try to get Haiku up and running. I'd still love to get a hold of a BeBox, just to add to my collection and have available to mess with ... but the people that have them don't seem to want to part with them (for obvious reasons).

Haiku was a great idea, unfortunately it lost momentum. Just throwing money at it won't fix it. You would need to put together a team of people that are passionate about developing an operating system that most people don't know even existed and far fewer will ever look at again.

 on: July 11, 2016, 11:25:22 AM 
Started by Euan Kirkhope (UK) - Last post by NoBeForMe
In some ways BeOS / Haiku fans are still better off than the Amigans.

AmigaOS 4.1 Final Edition came out in 2014. They have two new AmigaOne series machines supposedly coming on sale any time now. They still have a public annual show (AmiWest in California) and so it looks superficially as though things are pretty good for them.

But beneath the surface it's an ugly mess. AmigaOne hardware is dependent on desktop-class PowerPC processors. But since Apple switched to Intel (ten years ago, though preparations had begun long before that) there's no mass market for those and thus nobody making them. So a lot of squinting is used to find alternatives that kinda, sorta, can be used for a desktop. Chips with a non-standard FPU, or weird bus designs are selected and then the consequences visited on people already paying a lot more than for a similar PC five years earlier. Short runs of weird hardware, sold by sketchy part-time businesses lead to a whole bunch of extra trouble beyond what you'd always expect for a niche product.

Software is worse. The story familiar to Be fans of too few people trying to do too many jobs is there, but also something much worse. Key people working on AmigaOS are incompetent. With talent so scarce it's not done to say "You're hopeless, go make a Solitaire clone or something" and so gradually more of the system is maintained by people who ought not to be allowed outside unsupervised, never mind writing an OS. Many years ago, with multi-processor PCs still a fairly new phenomenon some of these people breezily declared that a multi-processor Amiga system was easy, they'd already figured out how to do it, they just didn't need to right now. Don't worry though, all the design decisions are made, it'll be ready to go whenever the Amiga needs it. Those who had some idea how the Amiga system works were, to say the least, sceptical, but they were shouted down.

And then of course everything went multi-core. Your phone is probably at least dual-core. Even the scavenged PowerPC CPUs for new Amigas were multi-core. Support was duly announced, to be delivered in Amiga OS 4.2 in the summer of 2010. "People said it was impossible" trumpeted the team's manager. And they did say that, for obvious reasons. Release dates were pushed back, status updates that said basically "Everything apart from actually making it work is done" were written, more release dates were pushed back. For a while there was an attempt to quietly walk the whole multi-core support idea back. At one AmiWest, buried in a slide deck there was an idea floated, maybe AmigaOS 4.2 won't have multi-core support after all, couldn't it be in a later version instead? Fans were stubborn, this was the whole point of AmigaOS 4.2, why delay the key feature? Nobody wanted to say "Because it doesn't work, it won't ever work" and that's how they arrived at the naming AmigaOS 4.1 Final Edition with its implied promise that OS 4.2 must be coming soon. Two years later "Final Edition" seems like a mistake again. What do you call the edition after the final one ? "Revenge of the Final Edition" ? "Son of Final Edition" ?

 on: July 07, 2016, 10:22:10 AM 
Started by Euan Kirkhope (UK) - Last post by Deej

I know what you mean.  I moved to Mac several years back, and pretty much just moved on from BeOS/Haiku.  Although, if I ever win the Powerball lottery (suppose I would need to buy tickets as a pre-req for that), the Haiku org could probably expect a huge donation to kick start it big-time.  Razz

I still leave the site up... although I don't know for how much longer.  Historical relevance seems to have gone out the window...

Good to hear from you though - hope all is well in your world!

 on: June 18, 2016, 08:08:20 AM 
Started by Euan Kirkhope (UK) - Last post by Euan Kirkhope (UK)
its been a bit slow in Haiku world these last 10 years.  Sad

I must confess I lost all hope around the time of the package manager debacle.

Still we're not far from Begroovy's 20 anniversary!

 on: May 08, 2016, 09:59:53 PM 
Started by bbjimmy - Last post by bbjimmy
Why basic?

If it does everything I need, why not? I can do in very few lines in basic what would take many hundreds of lines in c++ and get the mostly same result.  Yes, c++ can be faster, but who is counting the miliseconds when responding to a button press? With Haiku, yab it is faster than Windows and c++.

 on: October 27, 2015, 06:37:23 AM 
Started by bbjimmy - Last post by altp
Why basic?

 on: October 27, 2015, 06:35:24 AM 
Started by NoBeForMe - Last post by altp
Looks like a Beta 1 release in 2015 is slipping away...

Shame that Bebits and Haikuware went away.

Someone should try a crowd funding solution for it. Get reorganized, set realistic goals, line up some people that can work on it full time and use the funding to pay them.

It would, at the very least help show how much interest is out there for Haiku ...

 on: October 16, 2015, 12:37:08 AM 
Started by H-kon - Last post by Meanwhile
As for laptops, there still is this (overlooked) source which has user submitted BeOS/Haiku/Zeta compatibility info on 108 models:

Pages: [1] 2 3 ... 10
Powered by MySQL Powered by PHP Powered by SMF 1.1.15 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!