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

help-circle

  • My advice: don’t change anything else right now.

    The temptation is high to pack it all in at once; make all the big changes.

    2 hours a day is a lot. Not too much, just a lot. So, since you asked, don’t change your diet yet. Get into the groove of building this new thing into some level of consistency. Once you’re 90 days in, start modifying something else. Diet. Sleep. Intensity.

    Work on one routine at a time.

    Now if you’re going too far into calorie deficit then you can think about what your energy needs are but keep the other changes to bare necessity.



  • I can’t imagine that being the case for most users. I’m absolutely a power user and I keep being surprised at how consistently high the performance is of my base model M1 Air w/16GB even when compared to another Mac workstation of mine with 64GB.

    I can run two VMs, a ton of live loading development tooling, several JVM programs and so much more on that little Air and it won’t even sweat.

    I’m not an Apple apologist - lots of poor decisions these days and software quality has taken a real hit. While 16GB means everyone’s getting a machine that should last much longer, I can’t see a normal user needing more any time soon, especially when Apple is optimizing their local machine learning models for their 8GB iOS platforms first and foremost.















  • Good enough? I mean it’s allowed. But it’s only good enough if a licensee decides your their goal is to make using the code they changed or added as hard as possible.

    Usually, the code was obtained through a VCS like GitHub or Gitlab and could easily be re-contributed with comments and documentation in an easy-to-process manner (like a merge or pull request). I’d argue not completing the loop the same way the code was obtained is hostile. A code equivalent of taking the time (or not) to put their shopping carts in the designated spots.

    Imagine the owner (original source code) making the source code available only via zip file, with no code comments or READMEs or developer documentation. When the tables are turned - very few would actually use the product or software.

    It’s a spirit vs. letter of the law thing. Unfortunately we don’t exist in a social construct that rewards good faith actors over bad ones at the moment.


  • As someone who worked at a business that transitioned to AGPL from a more permissive license, this is exactly right. Our software was almost always used in a SaaS setting, and so GPL provided little to no protection.

    To take it further, even under the AGPL, businesses can simply zip up their code and send it to the AGPL’ed software owner, so companies are free to be as hostile as possible (and some are) while staying within the legal framework of the license.