C Programming Language

1002 readers

1 users here now

Welcome to the C community!

C is quirky, flawed, and an enormous success.
... When I read commentary about suggestions for where C should go, I often think back and give thanks that it wasn't developed under the advice of a worldwide crowd.
... The only way to learn a new programming language is by writing programs in it.

irc: #c

🌐 https://en.cppreference.com/w/c

founded 2 years ago

MODERATORS

snowe

[email protected]

modev

A Modern C Development Environment (interrupt.memfault.com)

submitted 1 year ago by JimmyWorldEater to c/c_lang

11 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago (2 children)

I guess the biggest benefit is that you can ship it directly from there and don't have to rewrite your application because Debian ships with an outdated version of some core library

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

So it's not a dev environment at all. It's a runtime.

If your code only works on your machine, to the extent that you literally have to ship a copy of your entire machine, your code sucks.

"it works on my machine" is an excuse. And a shitty one at that.

edit, and this way, after a week or two, your container will be the one using an outdated version of a library, not the system.

[–] TheTrueLinuxDev 1 points 1 year ago

I concur, there was a few problems that might come up on various platforms like Windows not implementing C11 standard threads and other stuff, you would instead use TinyCThread library that works like a polyfill.

All problems and challenges are workable, if the problem with Debian is out of date library, you could set up CI/CD for release build that rebuild your software when update occurs and static link the updated dependencies.

Back to your point, if they didn't design their code and architecture to be multiplatform like in C, they need to re-evaluate their design decisions.

[–] CameronDev 5 points 1 year ago (1 children)

But then your shipping your entire Dev Env as well? Including vscode? Seems a bit antithetical to what docker containers are meant to be? Or do you then just strip the container back down again?

[–] [email protected] 1 points 11 months ago

With vscode's "Remote Containers" plugin at least, it's clever enough to install that into the container after building the image. So the image built from the dockerfile doesn't contain the vscode stuff.