From: Liam Proven <lproven@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Clever code (was Re: Re: Stdin Redirect in Cu History/Alternatives?
Date: Mon, 19 Dec 2022 12:47:44 +0100 [thread overview]
Message-ID: <CAMTenCGY5kyK=m4DOYfcjEyAkEkZ1tjyvxM5E8B1Gq=c+E8BaA@mail.gmail.com> (raw)
In-Reply-To: <dd55cd9a-4ecc-7256-22f2-d63f688b7e81@riddermarkfarm.ca>
On Sun, 18 Dec 2022 at 16:08, Stuff Received <stuff@riddermarkfarm.ca> wrote:
>
> The BB10 i/f was designed by TAT
> (https://www.engadget.com/2010-12-02-rim-buys-tat-blackberry-ui-in-danger-of-becoming-awesome.html).
Oh, fascinating. I did not know that -- thank you!
> > I owned a Blackberry Passport. A lovely device with a lovely OS... but
> > too late and it flopped.
>
> Quite so.
One of the slightly stranger things in the smartphone OS space
recently, for me, has been watching Huawei's response to the licensing
fight with Google.
Huawei now promotes its devices as running "Harmony OS" with a lot of
hot air about microkernels, convergence, cross-platform, blah blah.
It's nothing of the kind. It's AOSP, the open-source core of Android,
with their own skin on top.
I don't think Huawei has the tech skills to build a new OS as it's
claimed it has...
But it could make some of those claims come true if it licensed BB10
and spent a bit on updating it.
--
Liam Proven ~ Profile: https://about.me/liamproven
Email: lproven@cix.co.uk ~ gMail/gTalk/FB: lproven@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053
next prev parent reply other threads:[~2022-12-19 11:49 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 19:38 [TUHS] " segaloco via TUHS
2022-12-11 0:22 ` [TUHS] " Clem Cole
2022-12-11 2:37 ` segaloco via TUHS
2022-12-11 13:59 ` Michael Kjörling
2022-12-11 14:28 ` Steve Nickolas
2022-12-11 15:04 ` Dan Cross
2022-12-13 1:54 ` Larry McVoy
2022-12-11 17:18 ` Adam Thornton
2022-12-11 18:54 ` Michael Kjörling
2022-12-11 19:55 ` Dave Horsfall
2022-12-11 20:03 ` Larry McVoy
2022-12-11 23:22 ` segaloco via TUHS
2022-12-12 2:15 ` [TUHS] Clever code (was " Bakul Shah
2022-12-12 2:44 ` [TUHS] " Steve Nickolas
2022-12-12 3:09 ` Andrew Warkentin
2022-12-12 3:34 ` Larry McVoy
2022-12-12 5:00 ` Kevin Bowling
2022-12-12 5:26 ` Andrew Warkentin
2022-12-12 15:02 ` Larry McVoy
2022-12-12 15:29 ` Clem Cole
2022-12-12 15:39 ` Dan Cross
2022-12-12 16:04 ` Larry McVoy
2022-12-12 16:26 ` Clem Cole
2022-12-12 22:20 ` Liam Proven
2022-12-12 23:10 ` segaloco via TUHS
2022-12-12 23:24 ` Larry McVoy
2022-12-13 2:00 ` Andrew Warkentin
2022-12-13 13:37 ` Larry McVoy
2022-12-13 23:00 ` Andrew Warkentin
2022-12-14 1:05 ` Larry McVoy
2022-12-14 1:40 ` segaloco via TUHS
2022-12-14 6:32 ` Rich Morin
2022-12-14 2:01 ` Andrew Warkentin
2022-12-14 7:49 ` arnold
2022-12-14 11:54 ` Brad Spencer
2022-12-14 12:08 ` [TUHS] Re: (TUHS -> COFF?) Re: Clever code Michael Kjörling
2022-12-14 15:14 ` [TUHS] Microware's OS-9 (was: Clever code) G. Branden Robinson
2022-12-14 22:41 ` [TUHS] " John Cowan
2022-12-14 9:46 ` [TUHS] Re: Clever code (was Re: Re: Stdin Redirect in Cu History/Alternatives? Harald Arnesen
2022-12-15 18:33 ` Liam Proven
2022-12-16 10:42 ` Harald Arnesen
2022-12-18 14:05 ` Liam Proven
2022-12-18 15:08 ` Stuff Received
2022-12-19 11:47 ` Liam Proven [this message]
2022-12-20 8:30 ` Andrew Warkentin
2022-12-20 11:57 ` Liam Proven
2022-12-15 0:29 ` Bakul Shah
2022-12-15 2:54 ` Larry McVoy
2022-12-15 5:36 ` Bakul Shah
2022-12-15 14:02 ` Dan Cross
2022-12-15 14:06 ` Larry McVoy
2022-12-15 14:18 ` Dan Cross
2022-12-15 14:02 ` Larry McVoy
2022-12-15 8:01 ` Andrew Warkentin
2022-12-12 9:48 ` [TUHS] Re: Clever code Michael Kjörling
2022-12-12 21:34 ` [TUHS] Re: Stdin Redirect in Cu History/Alternatives? Dave Horsfall
2022-12-12 21:46 ` Chet Ramey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMTenCGY5kyK=m4DOYfcjEyAkEkZ1tjyvxM5E8B1Gq=c+E8BaA@mail.gmail.com' \
--to=lproven@gmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).