• 3 Posts
  • 184 Comments
Joined 3 years ago
cake
Cake day: June 10th, 2023

help-circle










  • A source map is a file that maps minified code (such as ES5 or any Javascript) to the original source code (e.g. ES Modules, Typescript, etc). This makes it easier for developers to debug problems. Source maps aren’t unique to Frontend web development, but the scenario in the article is.

    Imagine if I asked you to fix an English subtitle typo in a film that was subtitled in a language you’re unfamiliar with (maybe Mandarin). At first you wouldn’t understand anything in the film, other than the pretty pictures, and struggle to find the correct segment to fix. But later I provide you with an English subtitle file and timestamp for the movie, so you could go find the actual place to fix the issue. This is kind of what source maps are like, they allow us to map from compiled code to the original, making it easier for us to debug and context switch less, saving a lot of time. They also allow us to better understand the original intent, since it’s the actual source.

    The source code is the original source at the time it was recorded for the Apple App Store on the web. But will quickly become out of date as changes are made frequently by Apple.




  • Following the advice of TC has made my dishes cleaner, so this insight doesn’t really matter to me personally. It’s good to do research and find answers, but pods just don’t work as well in my experience, while also being worse for the environment.

    But yes, Cascade ActionPacs were a genuine innovation when they launched because the mix of powder and liquid was an actual improvement, and for reasons that are not particularly achievable with powders, because the funny look of pacs really does have a functional purpose.

    Great if it works for some folks, maybe they’re not testing with enough variables to account for all water types, and all environmental conditions. Perhaps there are common situations not being accounted for due to the markets incessant need to build a single device marketed at everyone, where conditions will always vary.






  • I agree, for folks that don’t align with common use cases something like Trash is great. But there are always common configs, in all things that the masses would benefit from. For example, with blocklists you often have users who want to block all ads, porn, only ads from large companies but not small businesses, politics, etc. Different strokes for different folks.

    Same is true with Sonarr & Radarr, where you have users who prefer different things, like foreign content, subtitled content, audio quality, specific video formats, etc. Chances are there is a configuration that would strike a balance for the masses and make most users happy. Just like most users are happy with a general ad blocklist without having to think much about what it is or isn’t blocking.

    I’ll probably check out Cleanuparr for my own needs, that looks like a step in the right direction.



  • I appreciate the advice, but I’m not solely referring to the customization of filtering, of course it has the ability to do that, almost every comment in this thread is about that. The feature I am raising is about syncing community maintained txt blobs, Trash tells us exactly how to sync the guide with Sonarr/Radarr, but not without additional software or manual effort.

    Trash may offer excellent filters, but they are often incomplete, and do not promote community involvement. A URL pointed at a single source of truth inherently would, this is a popular approach with blocklists all over the web. If a user wants to modify the list, and has to post to a single moderated source, everyone benefits. But currently as a user you either setup syncing orchestration or you manually copy Trash. Neither of which lends itself toward keeping the community up to date.

    If you are aware of a way to have Sonarr/Radarr pull directly from a single source of truth and update itself, that would be great though.