Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #100563
| From | jt@toerring.de (Jens Thoms Toerring) |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: Pine 64 |
| Date | 2016-12-28 22:56 +0000 |
| Organization | Freie Universitaet Berlin |
| Message-ID | <eciu8fFgsigU1@mid.uni-berlin.de> (permalink) |
| References | <o3uqp5$2bo$1@dont-email.me> <d2f3ad19-0111-4062-8d14-77dd4fcf17c4@googlegroups.com> |
Malcolm McLean <malcolm.mclean5@btinternet.com> wrote:
> On Tuesday, December 27, 2016 at 10:44:22 PM UTC, jacobnavia wrote:
> >
> > I bought one of their marvels, a small circuit, not much bigger than a
> > phone, with an arm64 quad core CPU, 2GB Ram, Linux, ethernet, and
> > everything you would need to ssh into it from my mac. The circuits
> > starts at 15 US$, but I invested more, and for around 30$ I bought a
> > transparent case, and the high end model with the 2Gigs.
> >
> That's the way it's going to go. Those devices will be embedded
> everywhere, except in mass-market electronic products where you have
> to shave every cent off the hardware costs, and there will still be
> a market for very restricted processors.
True - why (even when not considering costs) a put a gigantic
processor with GBs of memory in something that will do nicely
with a 32-bit processor, running at say 200 MHZ, and never
needing more than 32 MB of memory? (I'm just rogramming for
such a system, and its's still overspeked, using less than
half the memory and less 1% of the available CPU time, 99.9%
of it waiting for anything to happen;-)
> It's a great opportunity to establish B64. The question is exactly
> how to define a 64 bit near-subset of C.
I may be a bit stupid, but what does 'B64; stand for? And what
kind of "subset of C" are you writing about?
The arrival of these cheap and "small" systems (from the modern
point of view - two decades ago they'd have been marketed as
"workstations";-) is indeed a good thing in allowing people
to get their hands dirty on low level stuff, something hardly
anyone would dare to do on his/her "main" machine. And good
for C since it's the "lingua franca" in these environments.
Regards, Jens
--
\ Jens Thoms Toerring ___ jt@toerring.de
\__________________________ http://toerring.de
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-27 23:44 +0100
Re: Pine 64 raltbos@xs4all.nl (Richard Bos) - 2016-12-27 22:54 +0000
Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 00:41 +0100
Re: Pine 64 raltbos@xs4all.nl (Richard Bos) - 2016-12-28 12:14 +0000
Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-28 13:39 +0100
Re: Pine 64 raltbos@xs4all.nl (Richard Bos) - 2016-12-28 12:45 +0000
Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-28 14:02 +0100
Re: Pine 64 Keith Thompson <kst-u@mib.org> - 2016-12-28 10:11 -0800
Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-28 10:50 -0800
Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 22:55 +0100
Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-29 12:21 +0100
Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-29 21:38 +0100
Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-30 10:10 +0100
Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-28 21:53 +0100
Re: Pine 64 raltbos@xs4all.nl (Richard Bos) - 2016-12-28 19:54 +0000
Re: Pine 64 Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2016-12-27 18:03 -0500
Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 00:36 +0100
Re: Pine 64 Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2016-12-27 18:44 -0500
Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 00:54 +0100
Re: Pine 64 Noob <root@127.0.0.1> - 2016-12-28 11:27 +0100
Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 12:10 +0100
Re: Pine 64 Noob <root@127.0.0.1> - 2016-12-28 12:59 +0100
Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-28 10:10 -0800
Re: Pine 64 supercat@casperkitty.com - 2016-12-29 08:30 -0800
Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-29 13:22 +0100
Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-29 07:47 -0800
Re: Pine 64 Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-12-29 17:03 +0000
Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-29 04:50 -0800
Re: Pine 64 Reinhardt Behm <rbehm@hushmail.com> - 2016-12-29 21:25 +0800
Re: Pine 64 Keith Thompson <kst-u@mib.org> - 2016-12-29 09:28 -0800
Re: Pine 64 Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-12-29 14:22 +0000
Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-29 13:28 +0100
Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-28 14:12 -0800
Re: Pine 64 BartC <bc@freeuk.com> - 2016-12-28 22:23 +0000
Re: Pine 64 Gareth Owen <gwowen@gmail.com> - 2016-12-29 18:43 +0000
Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-28 21:59 +0100
Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 23:43 +0100
Re: Pine 64 jt@toerring.de (Jens Thoms Toerring) - 2016-12-28 22:56 +0000
Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-28 16:00 -0800
Re: A programming language called 'B64' Noob <root@127.0.0.1> - 2016-12-30 16:08 +0100
csiph-web