7c
nobody
7c579328cf9028a4548d5117afa4f8448fb510ca9023f576b7bc90fc5be6ce7e
account deleted

What are your hobbies Vitor? Do you play chess? Tell us about yourself a bit...

Interesting. I'm not tied to any one place. Just was excited to experience Miami and the beach.

Heard good things about Nashville too.

Interesting to hear the announcement like right after Miami. Obviously something happened.

Good thing you wear that vest then. Hahaha.

Thnx for the response. Are you one of the organizers? If so, kudos.

Was just curious, as I was on the fence about this year and committed to next year but then saw the change. I've heard good things about Nashville, seems like a fun city.

Yes! So technical, athletic, but subtle and cerebral.

Also, nice job on cutting out drinking too... whether it's for a bit or forever, self improvement can be tough. Kudos.

Ours never got traction. Curious what we could have done better?

Why is the Bitcoin Conference in Nashville next year? Did the organizers give any rationale?

Thanks man! Brushing up on some comp sci theory before wiping my Ledger and running new firmware/software/kernels on it. Stoked to see whats available and what options exist.

Replying to Avatar dave

1) The kernel is indeed the first level of code that the hardware uses. When a hardware component is built, it is designed to perform a specific function. The kernel is responsible for managing the hardware resources and providing a layer of abstraction between the hardware and the software. The basic operation of the hardware is to perform the function it was designed for, and the kernel provides the interface for the software to interact with the hardware.

2) Here are two analogies:

- Cars and driving: The kernel is like the engine of a car, providing the power and control for the vehicle. The operating system is like the driver, controlling the car and interacting with the environment. Apps are like the passengers, providing specific functionality and interacting with the driver and the environment. Protocol level programs are like the traffic signals and road signs, providing a standardized way for the driver to interact with other drivers and the environment. Closed system applications are like a private road, limiting the interaction between the driver and the environment.

- Cooking: The kernel is like the stove, providing the heat and control for the cooking process. The operating system is like the chef, controlling the cooking process and interacting with the ingredients. Apps are like the spices and ingredients, providing specific functionality and interacting with the chef and the cooking process. Protocol level programs are like the recipe, providing a standardized way for the chef to interact with the ingredients and the cooking process. Closed system applications are like a pre-packaged meal, limiting the interaction between the chef and the ingredients.

Excellent... one last question.

When you say the kernel is an "abstraction" what do you mean? Expand on why you chose this word. The hardware, derived down to the simplest part, is only capable of a binary output right? So the kernel takes those outputs and directs them... correct?

Ok. A few follow up questions.

1) Is the kernel the first level of code the hardware uses? When a hardware component is built, how does it know how to perform? Is this the job of the kernel or is there anything else the hardware is operating off of? Is the basic operation of the hardware to give a binary output of 1 or 0?

2) Make 2 analogies for me about Kernels, Operating Systems, Apps, Protocol level programs and closed system applications - one based on the system of cars and driving, and another on whichever you think could be helpful.

In a typical "open source" project... is the kernel code also open source?

Is it normal practice for coders and developers to review the kernel code in an open sourced project, or are every node/user likely running different kernels because everyone's OS and device different?