scoutt

35 ms·

1. 331.▲
   by scoutt 6y ago

   > it's just byte buffers! At the end of the day, all things are.
2. 332.▲
   by scoutt 6y ago

   I've been doing bare-metal embedded for a long time now, and believe me, I don't want to be the negative guy , but I stopped the video at the third "the compiler inserts runtime checks" . A thing I don't want in m
3. 333.▲
   by scoutt 6y ago

   > Android incorporates a patched GPLv2 Linux kernel. This has nothing to do with "So we have broad adoption of GPL software" . Android (AOSP) is Apache. We don't have "broad adoption of GPL software". This scena
4. 334.▲
   by scoutt 6y ago

   To be pedantic, Android is under Apache[1] license, not GPL. And the apps you install in Android are (and can be) closed source (most of them). The hypothetical scenario you describe is the one where you build Linux from scratch and you fin
5. 335.▲
   by scoutt 6y ago

   I am all in for Rust in the kernel (as drivers) and I am really curious of how they will manage sharing memory across boundaries (user <--> kernel spaces). For example, an H264 encoder/decoder module in the kernel: let's say
6. 336.▲
   by scoutt 6y ago

   I wonder in which category Rust's RefCell runtime-borrow-checks fall into.
7. 337.▲
   by scoutt 6y ago

   Don't worry. I've just started to explore Rust (coming from 20 years of embedded C). I was just sad I didn't see bare-metal represented in the examples and status-quo stories.
8. 338.▲
   by scoutt 6y ago

   We poor embedded developers are always forgotten :( Grace, the only C/C++ dev, does stuff like "Grace has already decided to use a thread-per-core model and minimize cross-thread communication".
9. 339.▲
   by scoutt 6y ago

   From TFA > Hover the cursor over the images to see the remastered VGA version. If you're on a iOS device, you can simply tap the images
10. 340.▲
    by scoutt 6y ago

    When you think about masters/slaves, do you think about black people only? If so, why? There are countless examples in the history of the world about slaves, including different ethnics, in every continent. May they have a word on this
11. 341.▲
    by scoutt 6y ago

    www.arewebibleyet.com
12. 342.▲
    by scoutt 6y ago

    Thanks. I'm familiar with all these concepts except for Rust closures and its relationship with multithreading. I was talking about that at the lowest (OS) level, the thread mechanics is exactly what C presents us as a thread (and all
13. 343.▲
    by scoutt 6y ago

    I have no doubt that it works well in Rust (with its core concepts and caveats). I was really referring to the parent comment which said that the author of the article seems to be complaining about something that applies only to a specific
14. 344.▲
    by scoutt 6y ago

    Thanks. My question emerged from the fact that all the Rust threads examples I see are in the closure form || {} .
15. 345.▲
    by scoutt 6y ago

    Thanks. > a closure which is generally easier to use I didn't experimented much with closures so I can't discuss about simplicity yet (but the article explains that "Closures can be pretty radioactive" ). > within
16. 346.▲
    by scoutt 6y ago

    I started recently learning Rust, and a thing I don't understand is why they decided that threads have to be done this way and not simply wrapping what is available in the OS (I know that at some point, at the core, a Rust thread is th
17. 347.▲
    by scoutt 6y ago

    > The problems the author is describing might apply more to library authors I don't know much about Rust, but I found the examples in the article kind of simple . As far as I can see, the author is trying to spawn a new thread and
18. 348.▲
    by scoutt 6y ago

    > Times are changing. The same thing was said when C# came out, 20 years ago. "Now hardware is cheaper and software costlier"... "C# is the language of the future and will replace X language (and X++ too)"... "Ju
19. 349.▲
    by scoutt 6y ago

    Any runtime security measure produces overhead (array bounds checking, dynamically checked borrow rules like Rust RefCell, etc.), at least in computational cycles. There is no magic formula. Calculating mandelbrot fractals to measure spee
20. 350.▲
    by scoutt 6y ago

    AFAIK, memcpy is not a simple loop, in a way that it can align the copies to match the architecture. For example, with the right conditions (aligned memory), it can copy 32 or 64 bits at a time for most of the loop, and the remaining thro
21. 351.▲
    by scoutt 6y ago

    I think the most destructive thing is that you can overflow the destination buffer. With memcpy_s you have to specify the destination buffer size so you can (supposedly) prevent it.
22. 352.▲
    by scoutt 6y ago

    Together with parent comment, this is exactly how I feel every time I use something that is not C (I do mostly embedded). Like: ok, I can use a slice here, but what is a slice? what thing is it doing that I don't know? where's th
23. 353.▲
    by scoutt 6y ago

    > memory is not a problem and the goal is safety. People keep repeating this. What about embedded systems? For instance, I have to know how an object is structured and how is allocated, exactly and without surprises. The behavior has to
24. 354.▲
    by scoutt 6y ago

    What if pair bonding is part of the formative process?
25. 355.▲
    by scoutt 6y ago

    You can't apply that rule to all instructions. For example, movslq becomes move_sign_extended_double_word . ARM instruction QADD16 would be signed_saturating_parallel_halfword_wise_addition . QASX: signed_saturating_parallel_add_and
26. 356.▲
    by scoutt 6y ago

    MMU is mostly for managing virtual memory. Memory protection is "kind of" a consequence. Most RTOSes out there work just fine even without MMU or MPU.
27. 357.▲
    by scoutt 6y ago

    Thank you! OK. I was thinking to assemble a "Press F5 to debug" solution to speed up my learning process. I'm used to command line tools and hacking stuff together too, so I should be fine if that is the current state of the
28. 358.▲
    by scoutt 6y ago

    > firmware/os dev stuff Can I ask which IDE do you use for writing code and for debugging? I read your book (which I think is a great starting point), and now I wanted to start playing with Rust, but for embedded (ARM, bare-metal).
29. 359.▲
    by scoutt 6y ago

    Are you familiar with the term sealioning ?
30. 360.▲
    by scoutt 6y ago

    > programming languages directly influence programmer productivity A complete re-write (preceded by a very deep analysis) is exactly the opposite of productivity. > problems with these languages that new languages have addressed. And