• 13 Posts
  • 1.49K Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle



  • Yep, some code examples from the official documentation. This:

    printPersons(
        roster,
        (Person p) -> p.getGender() == Person.Sex.MALE
            && p.getAge() >= 18
            && p.getAge() <= 25
    );
    

    …is syntactic sugar for this:

    interface CheckPerson {
        boolean test(Person p);
    }
    
    printPersons(
        roster,
        new CheckPerson() {
            public boolean test(Person p) {
                return p.getGender() == Person.Sex.MALE
                    && p.getAge() >= 18
                    && p.getAge() <= 25;
            }
        }
    );
    

    …which is syntactic sugar for this:

    interface CheckPerson {
        boolean test(Person p);
    }
    
    class CheckPersonEligibleForSelectiveService implements CheckPerson {
        public boolean test(Person p) {
            return p.gender == Person.Sex.MALE &&
                p.getAge() >= 18 &&
                p.getAge() <= 25;
        }
    }
    
    printPersons(roster, new CheckPersonEligibleForSelectiveService());
    

    The printPersons function looks like this:

    public static void printPersons(List<Person> roster, CheckPerson tester) {
        for (Person p : roster) {
            if (tester.test(p)) {
                p.printPerson();
            }
        }
    }
    

    Basically, if you accept a parameter that implements an interface with only one method (CheckPerson), then your caller can provide you an object like that by using the lambda syntax from the first example.

    They had to retrofit lambdas into the language, and they sure chose the one hammer that the language has.

    Source: https://docs.oracle.com/javase/tutorial/java/javaOO/lambdaexpressions.html


  • Yeah, I’m just saying that the benefit of using such a regex isn’t massive (unless you’re building a service which can’t send a mail).

    a@b is a syntactically correct e-mail address. Most combinations of letters, an @-symbol and more letters will be syntactically correct, which is what most typos will look like. The regex will only catch fringe cases, such as a user accidentally hitting the spacebar.

    And then, personally, I don’t feel like it’s worth pulling in one of those massive regexes (+ possibly a regex library) for most use-cases.



  • Well, and remember: If in doubt, send them an e-mail. You probably want to do that anyways to ensure they have access to that mailbox.

    You can try to use a regex as a basic sanity check, so they’ve not accidentally typed a completely different info into there, but the e-mail standard allows so many wild mail addresses, that your basic sanity check might as well be whether they’ve typed an @ into there.


  • I always hated the implementation for .toString() of Duration. It gives you a string like that: PT8H6M12.345S (not a hash)

    Apparently, it’s an ISO 8601 thing, but what the hell am I supposed to do with that?
    It’s not useful for outputting to end users (which is fair enough), but I don’t even want to write that into a log message.
    I got so used to this just being garbage that I would automatically call .toMillis() and write “ms” after it.

    Well, and not to gush about Rust too much, but I recently learned that its debug string representation is actually really good. As in, it’s better than my Java workaround, because it’ll even do things like printing 1000ms as 1s.
    And that’s just like, oh right, libraries can actually provide a better implementation than what I’ll slap down offhandedly.



  • Yeah, I came to Rust from Scala and Kotlin, where equality is default-implemented (for case class and data class respectively, which is basically all we ever used), so this meme surprised me a bit.

    I do actually like that you can decide a type cannot be compared, because sometimes it really just doesn’t make sense. How would you compare two HTTP clients, for example? But yeah, it certainly is a choice one can disagree with.




  • Hmm, I don’t know anything about Whoogle, but from other privacy-conscious search engines, I would expect it to work when you use that URL in your bookmark.

    Three things I can imagine:

    • Something in your hosting stack strips the URL parameters, like maybe your reverse proxy, if you use one. You might be able to see in the Whoogle or web server logs, which URLs actually reach it. Might need to set it to debug/trace logging.
    • Maybe there’s a flag in the Whoogle configuration you need to enable to accept these preference URLs.
    • It’s a bug in that Whoogle version.


  • I mean, the bulk of the work on this happens for the fun of it. The underlying game engine, Luanti, has a really lovely community. Some folks love creating mods/content, others love playing that content.

    If you really want a hard reason, it’s that Microsoft bought Minecraft and has forced changes, such as a Microsoft account being a requirement now.
    Microsoft has a long history of being extremely hostile to the open-source / libre software community, so after the news broke the community definitely bundled together even moreso to create our own Minecraft, with blackjack and hookers screwdrivers and mese.