Otaku, gamer, self-taught programming student and professional procrastinator from Brazil. In fact, I am procrastinating at this very moment. I love boomer shooters too.

  • 1 Post
  • 5 Comments
Joined 3 years ago
cake
Cake day: September 6th, 2021

help-circle

  • Sou brasileiro, e apoio muito o estudo do português. É uma língua rica, complexa e linda. Para mim, não há obras literárias iguais aos clássicos brasileiros e portugueses, especialmente quanto ao belíssimo uso da língua portuguesa.

    Amo Machado de Assis e recomendo muito as suas obras que, além de mostrarem a beleza do português, continuam intrigantes e divertidas. Também recomendo as obras de Fernando Pessoa, caso opte por um escritor português.


  • whou@lemmy.mltoProgrammer Humor@programming.devC++
    link
    fedilink
    arrow-up
    7
    ·
    5 months ago

    well, if I have an object on the heap and I want a lot of things to use it at the same time, a shared_ptr is the first thing I reach for. If I have an object on the heap and I want to enforce that no one else but the current scope can use it, I always reach for a unique_ptr. Of course, I know you know all of this, you have used it almost daily for 7 years.

    In my vision, I could use a raw pointer, but I would have to worry about the lifetime of every object that uses it and make sure that it is safe. I would rather be safe that those bugs probably won’t happen, and focus my thinking time on fixing other bugs. Not to mention that when using raw pointers the code might get more confusing, when I rather explicitly specify what I want the object lifetime to be just by using a smart pointer.

    Of course, I don’t really care how you code your stuff, if you are comfortable in it. Though I am interested in your point of view in this. I don’t think I’ve come across many people that actually prefer using raw pointer on modern C++.


  • I’ve downloaded and tested it for a bit and it does look a bit too good to be true. The source code is licensed under AGPL, and the F-Droid app page didn’t show any anti-features. And I also really liked the app itself.

    However, while it does enable self-host of the same data (and it’s pretty easy too. you can even self-host from your phone! I wish more note apps did this) and manual exporting/importing, the cloud syncing (even to a third-party server of your choice) is locked behind a paywall. While I do understand paying for a service to save my data, it does bother me that I can’t sync with my own servers, which should not require any service from their part.

    The app also includes a login feature that lets you use a specific text-oriented Chinese social media (that also seems to be fully open source and AGPL licensed!). Honestly, I wouldn’t be bothered by it especially since it’s opt-in, and doesn’t seem to do anything with your notes unless logged-in. Though I don’t know how self-hostable it is, and even if it were, the app does not give me the option to enter my own server.

    And to top it all off, it has a bullshit AI feature (that seems opt-in). I don’t think I need to explain why this is very icky.

    Considering everything, it seems like an awesome app for people that use the specific social media it is optionally coupled with. But anyone that doesn’t and prefers to sync your data to a self-hosted server will be left without options. Also, you must consider that it apparently doesn’t seem to phone home, according to F-Droid, though it is very strange that the network, social media, and especially AI features are not mentioned at all as anti-features. So if you would want to be sure, I’d recommend you to read the source code and deduce yourself if it doesn’t phone anywhere you haven’t allowed to by default.

    I personally wouldn’t use it myself, but if you trust it doesn’t phone home, don’t care about manually exporting and importing your data, and isn’t bothered by the weird network features, I’d say it’s a great notes app.