Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #148756 > unrolled thread

C is an improvement on most of its successors

Back to article view | Back to comp.lang.c

Contents

  C is an improvement on most of its successors jacobnavia <jacob@jacob.remcomp.fr> - 2020-01-04 17:36 +0100
    Re: C is an improvement on most of its successors "A. K." <minforth@arcor.de> - 2020-01-04 13:32 -0800
      Re: C is an improvement on most of its successors Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-01-04 22:34 +0000
        Re: C is an improvement on most of its successors Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-01-04 14:52 -0800
        Re: C is an improvement on most of its successors jacobnavia <jacob@jacob.remcomp.fr> - 2020-01-05 00:16 +0100
          Re: C is an improvement on most of its successors Thiago Adams <thiago.adams@gmail.com> - 2020-01-06 04:43 -0800
      Re: C is an improvement on most of its successors jacobnavia <jacob@jacob.remcomp.fr> - 2020-01-05 00:17 +0100
    Re: C is an improvement on most of its successors chad <cdalten@gmail.com> - 2020-01-06 05:44 -0800

#148756 — C is an improvement on most of its successors

Why Is SQLite Coded In C:

https://sqlite.org/whyc.html

Happy new year C coders!

[toc] | [next] | [standalone]

#148771

Am Samstag, 4. Januar 2020 17:37:07 UTC+1 schrieb jacobnavia:
> Why Is SQLite Coded In C:
> 
> https://sqlite.org/whyc.html
> 
> Happy new year C coders!

That SQLite decision was a child of the nineties.

[toc] | [prev] | [next] | [standalone]

#148776

On Sat, 2020-01-04, A. K. wrote:
> Am Samstag, 4. Januar 2020 17:37:07 UTC+1 schrieb jacobnavia:
>> Why Is SQLite Coded In C:
>> 
>> https://sqlite.org/whyc.html
>> 
>> Happy new year C coders!
>
> That SQLite decision was a child of the nineties.

Perhaps, but IMO it still makes sense to write (many) libraries with a
C API as the primary API, and without huge runtime dependencies.

/Jorgen

PS. I note that the "an improvement on most of its successors" subject
    line is Jacob's; the article doesn't speak about C as the best
    language in general, or about successors.

-- 
  // Jorgen Grahn <grahn@  Oo  o.   .     .
\X/     snipabacken.se>   O  o   .

[toc] | [prev] | [next] | [standalone]

#148778

Jorgen Grahn <grahn+nntp@snipabacken.se> writes:
[...]
> PS. I note that the "an improvement on most of its successors" subject
>     line is Jacob's; the article doesn't speak about C as the best
>     language in general, or about successors.

And it's based on a quotation from C.A.R. Hoare about Algol 60:

    Here is a language so far ahead of its time, that it was not only an
    improvement on its predecessors, but also on nearly all its
    successors.

(jacob might assume I'm criticizing his adaptation of Hoare's
quotation.  I'm not.)

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    [Note updated email address]
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]

#148779

Le 04/01/2020 à 23:34, Jorgen Grahn a écrit :

> 
> Perhaps, but IMO it still makes sense to write (many) libraries with a
> C API as the primary API, and without huge runtime dependencies.
> 

C delivers:

o SPEED
o PORTABILITY
o TRANSPARENCY
o SMALL MEMORY FOOTPRINT

Of course I am speaking here about human memory. It is not a huge 
language, you do not need to memorize gigabytes of abstract rules like 
C++, for instance.

[toc] | [prev] | [next] | [standalone]

#148797

On Saturday, January 4, 2020 at 8:16:43 PM UTC-3, jacobnavia wrote:
> Le 04/01/2020 à 23:34, Jorgen Grahn a écrit :
> 
> > 
> > Perhaps, but IMO it still makes sense to write (many) libraries with a
> > C API as the primary API, and without huge runtime dependencies.
> > 
> 
> C delivers:
> 
> o SPEED
> o PORTABILITY
> o TRANSPARENCY
> o SMALL MEMORY FOOTPRINT
> 
> Of course I am speaking here about human memory. It is not a huge 
> language, you do not need to memorize gigabytes of abstract rules like 
> C++, for instance.

I can add some extra qualities:

 - Scalable
   Can be used for embedded devices or to create an SO

 - Keeps complexity under control.
   Different from C++ that allows extension of concepts,
   C keeps everything under the same rules.

[toc] | [prev] | [next] | [standalone]

#148780

Le 04/01/2020 à 22:32, A. K. a écrit :
> Am Samstag, 4. Januar 2020 17:37:07 UTC+1 schrieb jacobnavia:
>> Why Is SQLite Coded In C:
>>
>> https://sqlite.org/whyc.html
>>
>> Happy new year C coders!
> 
> That SQLite decision was a child of the nineties.
> 

Like linux and the UNix system, also started and still mostly C today.

[toc] | [prev] | [next] | [standalone]

#148798

On Saturday, January 4, 2020 at 8:37:07 AM UTC-8, jacobnavia wrote:
> Why Is SQLite Coded In C:
> 
> https://sqlite.org/whyc.html
> 
> Happy new year C coders!

There are some databases that are programmed using Erlang. Now if you want to see where C really shines, look no further than Facebook. They have a backend tool that converts PHP, which is an interpreted language, to C real time. This is because according to some of the engineers at that company, languages like PHP can't handle 2 billion users at any given time. 

Twitter did something similar. But instead, they took the interpreted that allowed them to get access to the core C routines and then proceeded to modify parts of the programming languages that were causing bottlenecks on any give twitter feed.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.c

csiph-web