• 4 Posts
  • 35 Comments
Joined 8 months ago
cake
Cake day: August 16th, 2024

help-circle
rss




  • Key thing to bear in mind is that we think of “chicken” as a single animal, but industrial farming has selectively bred chickens into very different camps.

    Meat chickens grow very big very quickly, and are killed for meat long before adulthood. You’d need to pause production a long enough time for them to grow into adulthood, then they would eventually lay eggs, but at a much slower rate than egg chickens, and requiring a lot more food (because of how big they are)





  • I’m not American so nobody got my vote, but seems to me like the issue is with the swathes of people choosing facism rather than progressives who chose not to vote.

    Choosing how to act in a world like ours is tricky, anyone following a sense of right and wrong (even if I disagree with their judgement) instead of fear, hate, greed or whatever gets a gold star in my book.


  • I use Cosmic and really like it- have used i3, Awesome and Gnome in the past for a while too, I really likes them.

    The most time I spent with a set up was Awesome + rofi, which I really enjoyed. I customised literally everything and spent hours tweaking stuff.

    That was super fun, but in all honesty my workflow is more or less:

    1. Open up a terminal (alacritty, tmux + fish shell + helix editor)
    2. Open up a browser (Firefox, have played with others but there’s always some quirk where I give up)
    3. That’s it.

    Honestly, all the tweaking is fun for me, but with my workflow I have like 0 requirements for anything fancy. Daily driving cosmic is going nicely for now, and seems to mostly get out of my way.


  • Sounds like it’s working great for you- I wish it would for me too! I’m not OP but some of my main gripes are:

    • Most calls have, for at least one caller, a wierd lag time where the call doesn’t start for 10 seconds or so

    • Quite frequently (I’d guess 5 calls a month) a call will be disrupted by teams failing completely for someone on the call (camera not working, not being able to join etc)

    • It uses a lot of RAM even when idling

    • It has hundreds of features, like “together mode” that bloat the software without adding to its core functionality

    • The UI is a confused mess, and the conceptual split between teams, channels and chats is messyat best.

    On top of that, I don’t find teams makes me more productive, if feels like a constant distraction that modern corporate culture requires me to have, even though its a net drop in productivity. This last point is more on instant messengers as a whole, but it doesn’t place me in a very charitable or forgiving mindset for interpretting Team’ multitude of flaws.







  • I have a Fairphone 4 and would definitely give them the biggest recommendation I could.

    Any part can be replaced with a screwdriver which is an order of magnitude better than I’ve seen with other brands. I dropped and broke my phone screen and although I had to buy a new screen, after that I had a phone working as if it was brand new.

    I also got mortar into my usb charging socket and was able to replace the charging socket.

    You might be able to tell that I’m not the best at looking after things, I’m working on this but in the meantime, fairphone have saved me at least two situations where I’d normally need to buy a new phone. Can’t recommend them enough.







  • I have advice that you didn’t ask for at all!

    SQL’s declarative ordering annoys me too. In most languages you order things based on when you want them to happen, SQL doesn’t work like that- you need to order query dyntax based on where that bit goes according to the rules of SQL. It’s meant to aid readability, some people like it a lot,but for me it’s just a bunch of extra rules to remember.

    Anyway, for nested expressions, I think CTEs make stuff a lot easier, and SQL query optimisers mean you probably shouldn’t have to worry about performance.

    I.e. instead of:

    SELECT
      one.col_a,
      two.col_b
    FROM one
    LEFT JOIN
        (SELECT * FROM somewhere WHERE something) as two
        ON one.x = two.x
    

    you can do this:

    WITH two as (
         SELECT * FROM somewhere
         WHERE something
    )
    
    SELECT
      one.col_a,
      two.col_b
    FROM one
    LEFT JOIN two
    ON one.x = two.x
    

    Especially when things are a little gnarly with lots of nested CTEs, this style makes stuff a tonne easier to reason with.