[haiku-3rdparty-dev] Re: Haiku 2.0 -- Unbuntu Touch -- impressions
- From: Jonathan Schleifer <js-haiku-3rdparty-dev@xxxxxxxxxxx>
- To: haiku-3rdparty-dev@xxxxxxxxxxxxx
- Date: Sun, 29 Sep 2013 22:49:54 +0200
Am 29.09.2013 um 22:30 schrieb ciprian.nedisan@xxxxxxxxxxxx:
>>> 1) The latest arm socs have quad-cores with up to 2.3 GHz. This
>> is
>>> nearly the power of a re>
>> Where did you get that from? This couldn't be more untrue:
>
> http://en.wikipedia.org/wiki/Tegra#Tegra_4i
> http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)#Snapdragon_
> 800
>
> my i7 is 1.9 GHz (with turbo 2.something)
I can't see any performance comparison there. Does that mean you are
*seriously* just comparing GHz numbers and cores here? Following that logic, do
you *honestly* think that a Pentium 4 clocked at 3.8 GHz is faster than a
single core of an i7? I *really* suggest you look at some benchmarks.
> I have an acer s5 i7 , and I was especially search for an ultrabook
> with low noice, at that time, no ultrabook was said to be very
> silent. Perhaps it's not "significant loud", but even when it's
> very slightly working, it is annoying to me.
I'm pretty sure you bought a laptop with broken fan control / a too small fan.
Even with my old Core 2 Duo MacBook Pro, I usually only hear the fan when
compiling or gaming. And the idle power consumption only got better with
i3/i5/i7, not worse.
>> Just because
>> e.g. LyX will run on Android, it won't be usable on Android
>> without a significant amount of work redesigning the UI. A desktop
>> UI simply isn't usable on a touch device. You could run LyX on
>> your tablet, but then what? The toolbar would not be usable. The
>> menu? Unusable. Typing a formular? A real pain. After 10 minutes
>> of trying to use it, you would give up on it.
>
> If the tablet is 10 inch, why not, there are notebooks that are
> just 11 ich, so I guess 10 ich should be fine, especially with a
> great display of more than 300ppi? And perhaps even connecting it
> to a beamer. The idea of ubuntu touch, to connect e.g. your phone
> to a bigger monitor, and then the UI adapts to it, and you have a
> full pc.
This has nothing to do with the display size, but with being able to hit
buttons. While a mouse cursor has an accuracy of 1 pixel, you can be glad if
your finger has an accuracy of 100 pixels.
> 6) Handwriting becomes very useable on ipad with the new stylus
>> of
>>> adonit http://adonit.net/ , which will come also to android.
>> That
>>> means, in future you can save paper, for doing calculations,
>>> homework, etc, or playing doing some sketches.
>>
>> Have you actually tried it? You can barely fit a simple equation
>> on a single page because you have to write in big letters as the
>> accuracy is not high enough. The strokes you draw are very big.
>
> Yes, that's a problem, but this new stylus promises to solve it,
> with addional sensors connected over bluetooth, take a look at
> their site, and see the results.
A pen can't increase the digitizer's resolution. I tried it on my iPad, wasn't
really usable - at all.
>> Oh, and there already is a work-in-progress Haiku port to ARM,
>> just like there is for PPC.
>
> Yes, work in progress, but I guess nobody expects to haiku full
> haiku running on arm in the next 10 years, with this work-in-
> progress.
>
> And yes I mean at first just running on ARM. We will have to see
> when the kernel will boot up, then porting all the additional
> software and especially drivers, would be a monumental work. Even
> now we don't have HW accelerated Graphics-drivers.
It already boots up in an emulator to some point. Haiku's kernel is quite
similar to the BeOS kernel, which already abstracted hardware in order to be
able to run on PPC and x86. Porting is an effort that is doable, but there
needs to be enough interest. I guess so far there just hasn't been an
interesting enough platform for someone to actually port it to. I guess the
Raspberry Pi would come closest to what would be an interesting target, but
then again, it uses an obsolete ARMv6 processor.
> Google Glass is running on (modified?) android.
I'm pretty sure it includes proprietary, closed, native code. Like most Google
Apps for Android.
> Running on "arm" doesn't mean "another linux distro", being able to
> handle different screen sizes, and adapt the UI to your screen-
> size, doesn't also mean "another linux distro", and also managing
> high screen resolutions, doesn't mean that.
Well, I can plug screens of different sizes and use them in Haiku. I can change
the UI to my liking. There is already work on support for retina displays
(IIRC). So for that part, it's mostly done or can be done. But the touch part
is the issue here.
> As I noticed with my chess game, running at 800x600 resolution,
> could make the game not that easy to play, at too high resolutions
> the same. That means, even at regular screen sizes, it can happen
> that the UI is not working that well for you, OR the developer has
> to put more work, to figure out, how to fit as many as possible
> screen resolutions.
Why does a chess game need to assume a resolution instead of having a resizable
window that just scales accordingly? If you use vector graphics or OpenGL, this
is a no-brainer.
> Related to the UI:
> having an dogmatic approach is not the best idea. The UI of
> haiku/beos
> beos didn't become to be like that, because it was perfect, it
> became like that
> also because of technical possibilities. In the last 25 the
> hardware had an evolution, that means, perhaps one can or should
> take use of it, and try to improve the UI. Nothing on this world is
> perfect, even less the UI of haiku. And since, I was writing many
> thousands of lines of c++ code related to the UI of Haiku, I have a
> little idea.
It's not about being perfect, it's about not ruining yet another OS by trying
to make it compatible with touch devices. Look at Gnome 3, look at Windows 8.
That's what happens when you try to have one OS that runs on computers and
touch devices.
> The attitude of "it's perfect" doesn't help in fact, because you
> can not make good progress like that, I was even asking the people
> to tell me that is bad about the documentviewer I was writing, how
> to change, what new ideas. Critics can (must not) help to make
> progress. When somebody tells you that something is bad, than you
> have the chance to improve something, but if you are told "it's
> perfect" then you learn for sure nothing new.
But having yet another OS that makes everything unusable because it tries to
run everywhere, but nowhere well, is not an improvement!
> bloat is a generic expression. Like saying "putting mass on your
> body", well but mass can mean fat, but also muscles.
> Being more leight, doesn't mean automatically it's better than
> having more mass in form of mucles.
I'm *really* not sure Haiku is the right OS for you. Not being bloated is one
of Haiku's main features. It's targeted at people who want to get things done,
not have bells and whistles and stupid installation wizards because copying
files is too complicated for them.
> A lot of the "bloat" is still missing to haiku. Like full HTML5
> support and the v8 javascript engine (for enhancing the pdfviewer)
> and the list is very long.... of missing bloat.
I wouldn't call a modern rendering engine bloat. Sure, it's big, but for
today's web, it's necessary. And a browser does not bloat the OS ;). It's an
application running on the OS, not the OS itself.
--
Jonathan
Other related posts:
