• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: September 3rd, 2024

help-circle


  • People forget that crashes are a debugging tool indicating an error. Silent errors can be much more dangerous. C and C++ in particular need to be careful not to overwrite random memory for example.

    Yes the consequences for JS failures are less severe and so JS can get away with it, but a crash is a way to know your program isn’t doing what you thought it was, properly.

    It just so happens that JS is used in contexts where nobody really cares, and errors aren’t a big deal, cheap and fast wins.




  • The problems with that feed which he touched on in the video are pretty significant. If you subscribe to channels that put out lots of content and ones that rarely do, it becomes much harder to use.

    One thing he didn’t mention is also that it’s not conducive to discovering and gradually catching up on the back catalogue of a new channel, which is something the home feed excels at.

    I’m sure YouTube prefers you use the home feed and has no plans to improve subscriptions, and there are real issues with it, so it’ll probably continue to decline.






  • Agreed. I’ve been following the technology of neural networks and generative AI since before LLMs were the new hotness and it’s fascinating and powerful stuff.

    My qualms with what’s happening now are more about how we organize our economy and society. Rushing them to market, aggressively trying to cull workers, etc. are critiques of capitalism not AI. In a different world we would all be excited about the prospect of having to work less and reap the benefits of AI, but we wouldn’t be reopening coal plants and leaving people to starve on the street.








  • I basically stole your comment but made a worse version. On this note, though, there’s sometimes value in using words like “fix” or other kinds of tagging or consistent formatting in the sense that you can do a meta-analysis of the repo history to look at trends (like the ratio of fixes to feature work) over time.

    Issue tracking software obviates that, somewhat, but having that info embedded in the repo history lets you go further and look at which files have the most fixes etc.

    Existing tools out there sometimes do this exact thing, but it can be manually done as well