Youtube comments of Jeremy Chone (@JeremyChone).

  1. I love this point by point debunking.
    121
  2. It's pretty amazing how this channel often gets the breaking news with interesting insight before all other channels. Kudos!
    100
  3. Words matter. I think the word “defund” is counter productive.
    67
  4. 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
  5. This is such a well-done coding tutorial for ARM assembler. I am not planning to code assembler, but I like to have a broad understanding of the below layers, and this video is perfect for this as well.
    24
  6. Very good overview of the key caches. Thanks for sharing all of those great knowledge with everybody!
    16
  7. Good video as usual. Our rule of thumb is "Lame Is the New Cool" as far as database choice.
    16
  8. Very well stated. I couldn't have expressed it better. I remain highly optimistic about the language's future, viewing the current situation as growing pains. In less than a decade, Rust has been integrated into the cores of both Linux and Windows. In many respects, it seems the language and ecosystem are advancing a tad too rapidly for the existing leadership structure. My hope is that these warning signs will be constructively utilized, ultimately strengthening and improving the stewardship of Rust.
    13
  9. Great videos. We like to have a "multi-services" architecture where size is more of a deployment detail, thanks to Kubernetes. Also, most important in cloud architecture is to be event-based from the start to avoid Web-Of-Hell service architecture.
    7
  10. We moved from REST to JSON-RPC for all our remote APIs. Much better representation for remote function calls. It made the whole http method to function call mapping gymnastic disappears. We wish we would have done so 10 years ago.
    5
  11. 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
  12. Very nice explanation. On top of password individual hash (stored in the DB), we also use an additional system wide salt, usually stored as a kubernetes secret property. This add another level of security. Also, we also use similar salt technic for the web token signature. Web Tokens embed their expiration, which is updated at each web request (typically as a http only cookie), and the third element is the signature using: ash(user_uuid + user_tsalt + global_tsalt). Also, we do NOT store credentials/access in the token, which is a longer conversation. So, a user row has a psalt column, for the password hash, and a tsalt for the token salt. Anyway, great vide, this is great to find this level of content on YouTube.
    5
  13. wow, what an awesome introduction to SQL optimization.
    5
  14. Good vid. Curious to know the licensing restriction for this type of "distribution."
    4
  15. Why not Redis Stream for Queue?
    4
  16. I'd love to know what you think is messy about the syntax. If you've got any specifics, that'd be awesome.
    4
  17. We use redis stream for our backend event bus/queue. Very fast, and the power of consumer groups really makes it shine.
    3
  18. Interestingly, no mention of SVB's MBS investments. Not sure this analysis is complete. (disclaimer: I am not in the finance industry, just a simple coder)
    3
  19. Very interesting insights from Loubna Ben Allal. It's great to have this expertise on YouTube. Thank you, Loubna, for taking the time for this podcast.
    3
  20. As always, best in class explanation. The narrative to visual sync just make the content so much clearer. Thanks for this high quality content channel.
    3
  21.  @LowLevelTV  Yes, I definitely agree with that. However, though it has a fixed initial learning "tax", it offers a significant recurring return. There are some friction points, which may be in different places compared to other languages, but I've found that the net gain in developer productivity and velocity is significantly higher. I've also noticed that the whole language model encourages me to think about my code design in a more robust way. I'm not exactly sure how to explain it, but code I've [re]written in Rust enables me to dive back in much faster for fixing issues or adding new features. This is why we're transitioning our entire team to Rust for development (both cloud with Axum and device/desktop with Tauri). But I totally agree, higher entry point, but higher return (IMO). Great content, I really appreicate your videos.
    3
  22. I completely agree. I have a similar graph that shows complexity and scale at 7:29. By placing the right tech in the right place, you can flatten the inevitable complexity curve and dramatically increase velocity, which improves both the quality and speed of delivery.
    3
  23. Serverless is a service implementation detail. Not a system architecture design.
    3
  24. @3Blue1Brown Thank you, this is a very well made educational videa, from voide, content order, density, graphics & animations. Thank you. I am defintely going to watch the whole series.
    2
  25. Love the "... as started a carnival so large, that it might take over the country"
    2
  26. Well written and performed. Thanks.
    2
  27. David, you need to do more of those. Your control, honesty, and the way you handle those crazy remarks/questions was so impressive. for example, “I did not go to public school” … wait for him to say private school was the same … and then “I am kidding, I went to public school.” Checkmate and he did not even know he was playing chess. Would love to see a Tucker vs. Pakman interview.
    2
  28. 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
  29. Awesome. Thanks for sharing. Passion all the way.
    2
  30. json-rpc rocks!
    2
  31.  @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
  32. ​ @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
  33. I would assume this architecture work with both cartesian and spherical coordinates? It seems that long/lat was mentioned, but from my understanding, spherical coordinates should used for the query. Btw, DataFrame technology could be great here (specifically Polars/ApacheArrow). Polars with the GeoPolars extension could be a great fit. I will try to do some benchmarking it if I find the dataset.
    2
  34. Is SRT based on HTTP/3 ?
    2
  35. Nice debunking list. Thanks for putting this together. I wish there would be more videos like this one.
    2
  36. Cenk at his best.... "MOMmy knows we are fighting, hiiiii, but she still both gives us guns."
    1
  37. Ben+
    1
  38. So cool as usual. Thanks for all the work.
    1
  39.  @JustinShaedo What do you mean by better supported?
    1
  40.  @JustinShaedo  Hmm, I'm not sure what "natively supported by browsers" means. JSON-RPC is simply JSON over an HTTP POST. In fact, it's a subset of REST in terms of the protocol and HTTP method used. So, assuming we make our requests with the browser's XHR or the new Fetch API, there's nothing more the browser needs to provide to support JSON-RPC over REST, since JSON-RPC is a subset of REST.
    1
  41.  @JustinShaedo  Thank you. Yes, we have been building large applications using JSON-RPC for many years now, and it has worked extremely well. We even provided an API to our clients' developer users, and they loved it. It's very simple: just an HTTP POST with JSON in and out, featuring a minimal top-level structure. It works in any browser, any client, with no stubs or SDK needed. Developers can find more information by searching for jsonrpc online; the specification is incredibly straightforward. In fact, we use it in our rust10x blueprint (a Web App production blueprint), and it works like a charm. I've made an extensive video about it, with more to come. There are many myths about json-rpc, but once its simplicity and versatility are understood, it resolves many issues. No more REST gymnastics for function calling, and best of all, it's protocol-independent. We can use it for network calls, WebView to Backend calls, like Tauri commands, or even in message passing in an actor model. However, there's no absolute best way to code large production applications. If developers are more comfortable with REST or gRPC, that's completely respectable too. Happy coding!
    1
  42. Good analysis. I think the mediator scandal also contributed at accelerating the distrust into big pharma / government.
    1
  43. Frameworks come and go, runtimes stay. #LearnWhatMatters #NativeWebComponents
    1
  44.  @mihailmojsoski4202  2022, customElement
    1
  45. yes
    1
  46. Thanks, great video. On a related topic, somehow, I cannot figure out how to read from PWM? The rp-hal/rp-pico have write example, but not read (I might be missing something).
    1
  47. Good analysis. I like the pandemic vs protest analysis.
    1
  48. So sell done. Thank you.
    1
  49. Intro, content, format, all excellent. Thank you!
    1
  50. Why I did not search for this video a year ago? Very well done and informative. Thanks!
    1
  51. Nice coherent and respectful interview, thanks for sharing. Not that I agree with his points, but I wish more Trump supporters or "anti-libs" would be that coherent. That would help the healing.
    1
  52. But... you are still going to sit this one out.
    1
  53.  @B3Band  Thank you. This was before chatGPT days! (just fixed it, thanks!)
    1
  54. So ironic in so many levels.
    1
  55. I would generally agree, however, there is a nuance. I have a lot of shortcuts, but I also use exclusively the trackpad (on MacBook) which significantly reduces the movement cost of pointer activities. In fact, my wrists barely move, if at all, when I am engaged in pointer activities. Interestingly, what slows me down more is not the pointer actions, but the arrow keys. They are on the keyboard, but still more disruptive to my input flow than a pointer action. Anyway, these things are mostly personal, so it's hard to have a universal best solution, even if there are still some good rules of thumb.
    1
  56. Good intro video. Thanks for your time making it.
    1
  57. This video is not going to age well.
    1
  58. Very cool and great video.
    1
  59. One of these two options really feels like Alex Jones's kind of rhetoric. How much hate someone must have against democrat establishment to believe that they would plan such a thing? Not saying they are angels or do not do dirty political tricks, but again, saying that this guy left because he has secret proof that the Democrats are manipulating the coronavirus context for voting suppression, is ... well, Alex Jones-ish at best. Most of the time @Secular Talk has logical reasoning, but here, bias is taking over any decent logic. Sad to see those kinds of conspiracy theories in a non-Fox channel.
    1
  60. Cool shots. Thanks.
    1
  61. I would recommend to learn Kubernetes first, and use abstraction/layers only if really needed.
    1
  62. Rust
    1
  63. Amazing reporting. Impressive patriotism.
    1
  64. Invert background.
    1
  65. Forget about party line, this is leadership.
    1
  66. Good, down to earth report.
    1
  67. 100% agree, CSS Grid / FlexBox / Variables over any CSS Frameworks.
    1
  68. Very well put
    1
  69.  @ByteByteGo  Yes, this is why I asked. Curious to know if there is some natural convergence between those two protocols.
    1
  70. Such an inspiration.
    1
  71. Correct about crowd size is not necessarily political popularity. In France last Sunday, Zemmour who had the biggest crowd and lot of buzz, completely crash in the first round, with 7% while the three firsts were > 20%.
    1
  72.  @JohnDoe-my5ip  Fair point. We like PostgreSQL.
    1