Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)F
Posts
3
Comments
945
Joined
3 yr. ago

  • Sure, never claimed anything different. Runtime type safety != type safety.

  • Deleted

    Permanently Deleted

    Jump
  • I wonder how they're doing these days

  • There are plenty of libraries to provide type safety at runtime.

  • Yes it is? It isn't strictly sound, but it is type-safe aside from explicit escape hatches (which other type-safe languages also provide).

  • Wait, why would wind and water be rare on other planets? Finding good places to do water-based renewables is probably gonna be difficult on most planets, but shouldn't most planets with atmospheres have wind?

  • Deleted

    Permanently Deleted

    Jump
  • Cook, Serve, Delicious ass order

  • I always wonder if fish fear cats/dogs that watch them. I hope not, because it seems quite entertaining!

  • It wouldn't be an issue if you didn't keep skipping soul leg day!

  • Is a toilet still the same after it has been flushed?

  • I switched to LibreWolf when the privacy policy fiasco happened a while ago. It's funny how every few weeks Mozilla manages to demonstrate why I won't switch back.

    The new CEO has also already lost me with this gem:

    He says he could begin to block ad blockers in Firefox and estimates that’d bring in another $150 million, but he doesn’t want to do that. It feels off-mission.

    Even taking the statement at face value, it's unacceptable for it to just "feel off-mission". It should be a clear "no, never" instead of some wishy-washy answer.

    But reading between the lines, such a statement is not just an off-the-cuff remark, but at best a threat to their users, and at worst a way to gauge the blowback of such a decision. They must have already taken it seriously enough to come up with the $150 million.

    If I had to put up a number, I'd guess there's a 25+% chance that Firefox will drop Manifest V2 in the next few years.

  • "Those are some nice vegetables you got there. Truly would be a shame if someone snuck onto your field every night and took a perfect cartoon bite out of every single one..."

  • That is not a good enough reason to justify its existence.

    There is no better reason to justify the existence of any technology than it having objective advantages, even if there are drawbacks as well!

    You can very well say that fossil fuel companies should continue to exist because look at how long it’s been around with all the expertise people have. Surely they should stay around, right?

    You're pretending that I'm making a completely different argument. Don't do that. I never mentioned "how long it's been around with all the expertise people have". There are literal objective advantages. Why are you pretending they don't exist?

    Please also see my other comment

    So people should choose a model that decreases development speed & increases complexity as well as the potential for bugs/side effects, just because "it's the right way to go". People have been trying to embrace the cascade for a long, long, long time, and it keeps causing issues in larger applications that simply don't happen with non-cascading approaches.

    Why do you pretend like these aren't real advantages?

  • See, that's a great example of a critique that nobody with professional experience would make.

  • There is a natural tendency to try reinvent something when you don’t understand it enough to be comfortable with it. Then that new thing lacks the maturity and scrutiny that the old thing went through to survive the test of time.

    While this is something that does happen, there's also a tendency for people in the industry to dismiss new things without actually looking into the pros and cons.

    Doesn't it give you pause that many very experienced Frontend & CSS developers see objective advantages in Tailwinds utility class approach? Of course there are also objective disadvantages, don't get me wrong. But that means that these tools should be used whenever their advantages can shine and their disadvantages don't cause issues.

    Any developer that can't clearly name the issues with regular CSS that Tailwind attempts to solve either hasn't been developing long enough to encounter these issues, or hasn't actually tried to understand what Tailwind is.

  • That's what Tailwind looks like to people who think they know CSS.

  • Lots of software has non-reproducible build artifacts due to e.g. timestamps being inserted, or due to non-stable algorithms being used during compilation. They presumably managed to remove all sources of randomness from the image they build.

  • "HEY! HEEEEEEEY! nom COME HERE! nom YOU WON'T BELIEVE WHAT I FOUND! nom nom WE SHALL NOT STARVE TODAY!"

  • You just unlocked a core direwolf20 memory

  • Do you think they never checked for that before?