• 3 Posts
  • 27 Comments
Joined 2 years ago
cake
Cake day: June 24th, 2023

help-circle


  • IMO, deno’s approach was bad as it was reinventing the wheel, so one had to relearn. And then they brought package.json which they said they wouldn’t. This again got people to unlearn and relearn things.

    Bun, on the other hand, acts like what Typescript is to Javascript. It’s just feels like superset of Node, instead of completely different tool.

    I expect Bun will get more success than Deno.

















  • I know what I do.

    I go to ChatGPT, type my problem and copy the solution to my codebase.

    If it doesn’t work, I search my issue over Stackoverflow or DDG, and copy from there.

    And once the code fails in production, which is always, I repeat the process again to find the new solution which will then fail in next iteration.

    So don’t you ever tell me I don’t know what I do. I may not know what code I’m writing or for what, but I very well know what I’m doing.


  • These are primarily the data stored by your health apps and sos information.

    If you’ve Android health info stored for emergency cases, some apps with right permission can access it. You know to save your life.

    Likewise, your health record on your health apps like Google/Apple/Samsung health store a lot of information about you like steps, sleep trends, heart rate, diabetes, water intake, and even period regularity.

    In normal cases these records should only be known to you or shared with apps you approve.

    Threads has no business normally to request these data, but if they want go serve you relevant ads, these become quite useful information.

    They can show you sanitary products when you’re on period, or show ads for meds when you’ve high blood pressure. None of these should be monetised, but they can very well will be.