Programming Circlejerk

144 readers

42 users here now

Community to talk about enlightened programming takes

Rules:

read and follow the programming.dev code of conduct
no flamewars
mark your unjerks
only programming related content allowed
link to the original source
do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.

founded 2 months ago

MODERATORS

[email protected]

Not knowing how to write C means you are objectively a very bad engineer (sopuli.xyz)

submitted 2 months ago by [email protected] to c/[email protected]

37 comments fedilink hide all child comments

URL: https://www.linkedin.com/posts/ahmadnwirah_not-knowing-how-to-write-c-means-you-are-activity-7294682256160260096-0g

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

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

How close is it to actual assembly from an existing CPU?

[–] [email protected] 3 points 2 months ago* (last edited 2 months ago)

Far, but being a programmer is usually not about using assembly anymore

Edit: to elaborate a bit, TIS-100 has an overcomplicated architecture but oversimplified command set, and restricts the coder way more than the real assembly (e.g. you have a limit on line length of 12 chars or somewhat close, and that includes the opcode itself). Imo these design decisions allow it to be interesting and simple enough to comprehend, but severely limits what can be implemented on that architecture in reality without requiring for lots of boilerplate