Other accounts (verify ownership):

  • @moseschrute@lemmy.ml
  • @moseschrute@lemmy.zip

aspe:keyoxide.org:JOVNV7OHSJCZMPZCCWS5TZI34A

  • 10 Posts
  • 247 Comments
Joined 1 year ago
cake
Cake day: October 6th, 2024

help-circle







  • moseschrute@lemmy.worldtoEurope@feddit.orgfolkhögskolor
    link
    fedilink
    English
    arrow-up
    2
    ·
    14 days ago

    Please don’t apologize! I can tell you are a nice person. Though I can’t make promises, a top 3 list of things you would add/fix is always helpful. If enough people ask for something specific, it becomes more likely that it will be added. Improvements to post/comment sharing is a pretty comment request, so that will happen eventually.


  • moseschrute@lemmy.worldtoEurope@feddit.orgfolkhögskolor
    link
    fedilink
    English
    arrow-up
    3
    ·
    14 days ago

    Blorp dev here. Linking to comments specifically are a bit broken. Links to posts work better. I’ll see if I can fix that, sorry.

    Potentially, I was thinking about adding a special share link that looks like:
    blorpblorp.xyz/share/…

    That link would promp the user if they want to continue in Blorp or view on the original/their own instance.






  • I agree, storing in a consistent unit is the way. That doesn’t solve conversion/rounding issues, but it does simplify things.

    Though you can run into floating point errors when editing in one unit vs storing in another. For example, maybe the user entered 2 in unit A, then it’s converted to unit B and stored in the db. However, when it’s converted back to unit A, it’s 1.999999. Fortunately rounding fixes this. We say unit A and B get 2 decimals of precision, and 1.999999 becomes 2.00.


  • You think timezones are annoying? Try handling metrics that use imperial and metric, need to be rounded to different precisions across a large system, and are sometimes recorded in a different unit than it’s viewed in. Slap some floating point error on there, and you got yourself a fun time.

    I spent all day working on bug where backend was categorizing 19.9999 as falling between <20, but frontend was rounding it to 20 and categorizing it as >=20.

    Edit: just to be clear, I don’t really think this is more difficult than date/time. But it does remind me a lot of solving date/time issues.



  • I feel like I’m this weird combination where I love the design of their products - are there other aluminum laptops that are as sleek as Apple? But on the other hand, I also think something modular like framework would be sick. I guess that’s the issue is you can’t have the sleek fully aluminum design and have it be modular/repairable. But I will say this, my M2 Max MacBook Pro has been a beast for 2 years, and it shows no signs of slowing down.


  • I know this is a joke. Apple is bad for some reasons and good for others. I think there are technologies where the bad clearly outweighs the good (e.g. anything Facebook/Meta). I don’t think Apple is as clear cut. That doesn’t mean we shouldn’t put serious pressure (government regulation?) on them for the bad things. IMO Lemmy lacks the nuance for things that aren’t clear cut.

    Here’s an example. Apple laptops are insanely well built +1 points. Apple silicon delivers incredible battery life and performance, and has pushed ARM into the mainstream +1. Apple locks down software and hardware too much -1. Apples labor practices -1. I would love to see better Linux support for Apple silicon (I think it’s exists, but idk how well it works).