Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kernel-intro-sources: add elixir reference #245

Conversation

arnout
Copy link
Contributor

@arnout arnout commented May 6, 2024

This reference exists in the embedded system development slides, but not in the kernel training. Elixir is kind of important if you ask me :-)

While using the bootlin materials for an internal training, there are a few improvements I made (at least, I consider them improvments myself). Since you probably don't agree with all of them, I'm making separate PRs for each. Feel free to close the PR if you disagree with the idea.

This was swiped from
slides/sysdev-linux-intro-sources/sysdev-linux-intro-sources.tex

Signed-off-by: Arnout Vandecappelle <[email protected]>
Copy link
Contributor

@miquelraynal miquelraynal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I was the one who removed the slide in the first place. There are a number of reasons why I considered removing this:

  • I believe if you are down to learning how the kernel works internally, you already are familiar with some text editor. And the text editor mostly does not matter.
  • We have URLs towards Elixir all over the place.
  • We already give the "take whatever editor" advise in the labs (one of the first labs) and we even advise to use Elixir in one of the vert first labs.

And most importantly, I wanted to reduce the time before people were getting into some real coding, which is usually a part that is enjoyed by trainees, as the introduction was a bit too long.

I don't have any strong feeling either, so I'll let others comment :-)

@Tropicao
Copy link
Contributor

Hello,
to add my 2 cents, I am slightly in favor of not adding such change. My arguments will be pretty similar to some from Miquel:

  • this is already covered in the labs, where people will actually start manipulating the kernel source code (but indeed, not with as many details as with this change)
  • it is up to people to select their development tools, and they will likely already have their own before starting learning about kernel development (for the common tools like text editor I mean)

@arnout
Copy link
Contributor Author

arnout commented Oct 28, 2024

It was useful for me, but I understand your reasoning. Closing.

@arnout arnout closed this Oct 28, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 28, 2024
@Tropicao
Copy link
Contributor

ACK. I've propagated the comment request internally, and the overall opinion was shared by other trainers/colleagues.
Nonetheless, many thanks for your multiple other contributions to the training materials !

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants