The reason you “git blame”

  • 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • Not defending LMG’s mistakes, but GN’s opinion that you should not ask for comment doesn’t hold water.

    GN definitely has an agenda here. He made several comments that made it quite clear he’s resentful of LTT’s success.

    While I don’t think anything he reported is false, it’s all wrapped in a narrative that relies on implications. He certainly makes a whole lot of hay about a few small mistakes and heavily implies LTT is in the pockets of their sponsors and a conspiracy theory that LTT is only successful because of some connections and preferred treatment by YouTube.

    He’s very much trying to establish a narrative that LMG is wildly corrupt and undeserving of their success. However, a lot of it comes across as sour grapes.

















  • Bluesky is still in beta. It’s intentionally not open to the general public because federation hasn’t yet been opened up and they only have one instance running.

    The nice thing about Bluesky’s architecture (over ActivityPub) is the fact your content and identity is portable. So you can move over to a different instance as they start to come online.

    I think the important takeaway from articles like this is the fundamental misunderstanding of decentralized social protocols. It shouldn’t be on one central authority how things are moderated globally. These kinds of articles kind of prove the point.


  • I was a big fan of Vue 2. Vue 3 is a completely different library if you choose to adopt the composition API (which is where everything is headed). If everyone is going to have to learn a totally new composition pattern, might as well look at what else is out there.

    Kinda similar to the big overhaul between Angular 1 and 2

    Vue 3’s Composition API and composables are more similar to React functional components and hooks than it is to Vue 2 and its Options API. That’s not to say that React Hooks and Vue Composables are apples-to-apples. They still have different approaches to reactivity and so on, but the programming model is more familiar between the two.

    Coming to Vue 3 from 2 was a bit of whiplash. However I’ve been working with it for a few days now and have come to appreciate how much more flexible and powerful it is to have access to Vue’s reactive primitives anywhere - you don’t have to write all your business logic in the scope of a Vue instance.

    That said, it comes with a much higher learning curve. Vue 2 gave you guardrails, an easily understood component class structure, etc. That’s what I liked about it as it scaled well to large teams. Whereas React scaled to a large team quickly turns into a complete mess. Ask 10 different React engineers and you’ll get 10 surprisingly different approaches to how to implement components and architect applications.