[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #15078: x86_64 hybrid aka beos_compat
From:       "Haiku" <trac () haiku-os ! org>
Date:       2019-05-27 11:31:26
Message-ID: 060.4a7998023a24a0d5b6a7b66c8b289595 () haiku-os ! org
[Download RAW message or body]

--===============1042565584106002810==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

#15078: x86_64 hybrid aka beos_compat
---------------------------+----------------------------
   Reporter:  kallisti5    |      Owner:  nobody
       Type:  enhancement  |     Status:  new
   Priority:  normal       |  Milestone:  Unscheduled
  Component:  System       |    Version:  R1/Development
 Resolution:               |   Keywords:
 Blocked By:               |   Blocking:
Has a Patch:  0            |   Platform:  All
---------------------------+----------------------------

Comment (by pulkomandy):

 Hi,

 It's fun to read that "32bit users should contribute more instead of
 complaining". I'm still running only 32bit systems here even if my
 hardware is 64bit able.

 This is valuable to me as a developer because I'm still occasionally
 running old BeOS stuff (SynC Modular, but a bunch of things from
 HaikuArchives as well, lastly I started toying with BeDC which is a nice
 base for a syslog analyzer, unfortunately the app itself is closed source,
 I'll consider a rewrite if I start using it regularly).

 We should still finish and merge the 32bit compat for 64bit systems. And I
 would be quite happy to drop both gcc2 and 32bit support at the same time,
 when that times comes. I think it's still a bit early for this, given that
 the maintenance costs are not that high. I'll accept that people do not
 care too much about gcc2 compat and that we start moving more and more
 things to gcc8 (as is done for WebKit, for example - app_server would
 probably be next because of HarfBuzz if we want to integrate the complex
 text rendering work).

 I'd say we can handle this small steps at a time, when there is a good
 justification to do it. We can also see when users complain and try to fix
 things (rewrite the apps/drivers/add-ons that need to be replaced, in the
 worst case).

-- =

Ticket URL: <https://dev.haiku-os.org/ticket/15078#comment:8>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.

--===============1042565584106002810==--

[prev in list] [next in list] [prev in thread] [next in thread]