• 2 Posts
  • 119 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.





  • While I don’t know this is the case, I can say from experience that in large enterprise organizations compliance departments will and do actively prevent the release of features and even commits if they don’t comply.

    While that’s not an excuse for challenging them, I could definitely see a stressed out mid level just trying to make there manager happy and move on with life.






  • What the tech is being marketed as and what it’s capable of are not the same, and likely never will be. In fact all things are very rarely marketed how they truly behave, intentionally.

    Everyone is still trying to figure out what these Large Reasoning Models and Large Language Models are even capable of; Apple, one of the largest companies in the world just released a white paper this past week describing the “illusion of reasoning”. If it takes a scientific paper to understand what these models are and are not capable of, I assure you they’ll be selling snake oil for years after we fully understand every nuance of their capabilities.

    TL;DR Rich folks want them to be everything, so they’ll be sold as capable of everything until we repeatedly refute they are able to do so.



  • You must not write much Kotlin then? It’s far more than sugar when a language fixes core issues in another.

    It’s a modern, statically typed language that addresses many of Java’s longstanding limitations with robust type safety, expressive functional features, coroutine-based concurrency, and extensibility — all integrated natively. Interoperability with Java is a strength, not a sign of dependency.

    Calling Kotlin merely syntactic sugar is like saying Swift is just Objective-C with prettier syntax — it misses the deep improvements in language design, safety, and developer experience.