Comments by "Jeremy Chone" (@JeremyChone) on "Fireship" channel.

  1. Pretty good overview. Just a little nit pick for @0:58: Mutability is not a deciding factor for a value placed Heap vs. stack. In Rust, it cannot because mutability is an attribute of the handle, not of the value. Now, dynamically sized elements are placed on the Heap, and the developer can force anything to be on the Heap by using constructs like Box. Anyway, great video. Hope many will look at Rust.
    40
  2. First nice video as always. I would recommend developers to give a fresh shot at native web components, and use the browser as the framework. Once you use custom elements, shadow DOM and slots correctly, the component model is very scalable, framework less, and native. Frameworks come and go, but runtimes always need to be learned. #LearnWhatMatters
    5
  3. Good vid. Curious to know the licensing restriction for this type of "distribution."
    4
  4. We use redis stream for our backend event bus/queue. Very fast, and the power of consumer groups really makes it shine.
    3
  5. This is awesome. Building a Rust desktop app template right now and this could be a great fit. I need to see how simple it is to embed. I looked at Sled, and while very nice, makes schema evolution kind of hard.
    2
  6.  @rand0mtv660  Good point, but I think it is more about the momentum of a previous belief that the DOM did not have a component model than a fresh assessment of the current state. It was relatively accurate before the customElements/ShadowDOM era, but now, developers would gain a lot by embracing those runtime constructs as their component model. I am not losing hope because we see that happening in the CSS world, where the web dev community is starting to realize the value of modern CSS (CSSGrid/FlexBox/CSSVariables) over CSS Frameworks (.e.g., Boostrap, ...). Anyway, just sharing my perspective from our experience of building big apps with small teams. Btw, Svelte seems to be elegant and well thought out, so it is not a criticism of Svelte.
    2
  7. ​ @rand0mtv660  btw, I also think that the original web components documentation was confusing for app developers, as it looked like you had to have <template> tags in the page for the web components, where in fact it is completely independent.
    2
  8. Frameworks come and go, runtimes stay. #LearnWhatMatters #NativeWebComponents
    1
  9.  @mihailmojsoski4202  2022, customElement
    1
  10. yes
    1
  11.  @B3Band  Thank you. This was before chatGPT days! (just fixed it, thanks!)
    1
  12. I would recommend to learn Kubernetes first, and use abstraction/layers only if really needed.
    1
  13. Rust
    1
  14. Good, down to earth report.
    1
  15. 100% agree, CSS Grid / FlexBox / Variables over any CSS Frameworks.
    1