top 50 comments

sorted by: hot top controversial new old
[–] 15 points 2 hours ago (2 children)

As a mobile developer, I got an email from google saying they're going to be adding new memory restrictions in apps and it'll crash if you exceed them.

Thanks google, for buying all the ram, and then punishing us for it.

  • source
  • hideshow 2 child comments
  • [–] 2 points 50 minutes ago

    i can see how this might evolve... someone, the app developer or the user, will end up having to pay google to let an app use more ram than google allows it to for 'free'.

  • source
  • parent
  • [–] 1 point 46 minutes ago
    [–] 5 points 1 hour ago (1 child)

    If it makes you feel better, Chrome has a limit of 4GB.

    (Source: I work on a very large enterprise webapp and we have OOMed many times)

  • source
  • hideshow 1 child comment
  • [–] 11 points 4 hours ago (4 children)

    The one thing that the Fediverse wanted to destroy: not being able to cross post across social media software.

    What people do: 📸

  • source
  • hideshow 4 child comments
  • [–] 1 point 1 hour ago*

    I fucking LOVE things breaking when the other node inevitably goes down, or the person deletes there post.

    The URL to the originating instance is right there.

    Edit: the microblogging quote post standard is just a URL as well.

  • source
  • parent
  • [–] 3 points 2 hours ago (2 children)

    You can lead a horse to water but you can't make it drink.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 hours ago (1 child)

    Look, that water is complicated. Cross-post a Peertube video in a response to this comment. Lemmy and mbin and piefed etc. do mostly inter-operate transparently, I even see folks from Mastodon occasionally, they're the ones that relentlessly @ people, but that's about as far as this anus will distend.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 3 hours ago

    Another idea: ban all public-userspace devs from have more than 2GB ram on their dev systems.

    If it's going on the market for joe-schmoe, ya gotta make it work on a complete shitbox before shipping.

  • source
  • [–] 24 points 5 hours ago (4 children)

    Hot take: node.js was a mistake

  • source
  • hideshow 4 child comments
  • [–] 14 points 6 hours ago (8 children)

    No monitors above 1920x1200 and they must code in bright sunlight at least 8 hours a day. I'm convinced some websites look like ass because the developers haven't look at anything below 4k. Maybe ever. Some may not have seen sunlight in years. Not everything needs to be made for dark viewing with white text everywhere.

  • source
  • hideshow 8 child comments
  • [–] 6 points 5 hours ago* (1 child)

    Oh god, yes, I wish they had to work in a bright environment. Every other website (and even some desktop applications) feel like it was coded by someone who hasn't left their basement since Obama was still in office.

    I mean, seriously, how can people unironically say stuff like 'black text on a white background hurts my eyes'? Turn on the fricking lights damn it. Staying in badly lit environments is bad for your eyesight anyway.

    Also, while we're at it, I am also not a fan of grey text on a grey background. Okay, rant over.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 5 hours ago (3 children)

    Designer != Web developer

    Your anger is misdirected.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 12 points 5 hours ago (2 children)

    Bold of you to assume most sites and apps have designers.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 5 hours ago

    Even the ones that don't agree following designers, just not ones they work with.

    Those giant JavaScript frameworks, and more importantly for design, CSS frameworks don't pop out of thin air. .

    The entire world was and still is in material design because it reads the blessed Google design.

  • source
  • parent
  • load more comments (1 reply)
  • [–] 6 points 5 hours ago*

    ban my boss from forcing me to include gigabytes worth of javascript.

    making me do it with 2gb ram is only going to make me suffer while trying to do it.

  • source
  • [–] 48 points 9 hours ago* (last edited 6 hours ago) (4 children)

    2GB? Barely enough for the VM of the Docker of the flatpack for the cloud mouse driver's DRM!

  • source
  • hideshow 4 child comments
  • [–] 9 points 8 hours ago (3 children)

    Dicker is the new container virtualization technology.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 57 points 10 hours ago (6 children)
  • load more comments (2 replies)
    [–] 4 points 6 hours ago

    My work laptop has 64GB and it legitimately takes 5mins to delete my node_modules folder 💀 Though that might just be an SSD speed bottleneck ig

  • source
  • [–] 24 points 9 hours ago* (7 children)

    4k fullscreen uncompressed picture is a bit under 24MB. (3840*2160/1024/1024*3 = 23.73)

  • source
  • hideshow 7 child comments
  • [–] 13 points 7 hours ago (3 children)

    Which is why you show a lower-res preview as default. Don't want to wait a fucking minute to decide if i like your picture or not.

    Which reminds me, Chrome/ium/Firefox's dev tools have a bandwith limiting feature. A lot of so-called web developers don't know that.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 5 points 4 hours ago* (2 children)

    Really? I did a little web dev as a side role when I worked in a small shop and even I knew about those tools.

    Reducing load times under highly throttled speeds was like crack to me.

    Yes entire page load was 120kB. But what about 76kB? 2 hours well spent damn it!!

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (2 replies)
    [–] 20 points 9 hours ago (6 children)

    I want to load more than one website at a time, so 2GB is generous

  • source
  • hideshow 6 child comments
  • load more comments (6 replies)
    load more comments
    view more: next ›