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/)R

Redkey

@ Redkey @programming.dev

Posts
0
Comments
96
Joined
3 yr. ago

  • Falsehoods programmers believe about languages

    Jump

  • Icons that are based on English puns and wordplay are easily understood by speakers of other languages.

    This reminded me of one of those Top Gear "drive across a foreign country in weird vehicles" specials where Jeremy Clarkson needed to borrow a cable to jump-start his car, and laboriously mimed out jumping for "jump", and walking a dog for "lead", to a perplexed local. Richard Hammond was cracking up but finally managed to point out what a fool Clarkson was being.

    Geolocation is an accurate way to predict the user’s language.

    And as an addendum to this, in 2025 nobody should be using Windows' "Non-latin/-unicode character set" setting to guess the user's preferred language. That's a pre-WinXP kludge. I'm specifically looking at you, Intel integrated graphics software writers, but you have plenty of company, don't worry.

  • Why fastDOOM is fast

    Jump

  • Why be like that? Whether you think their position is silly or not, this person obviously gets called out on this a lot. And rather than pitch a fit over being needled about it for the umpteenth time, they responded with links that ought to satisfy any genuine curiosity. Considering the times I've seen an empty "Go educate yourself!" as a response from petulant children, I'd say buddy did us a solid. They don't owe us a personalized response.

  • SQL Noir

    Jump

  • Yep, surveillance_records.person_id is the same as surveillance_records.id, which is incorrect. I looked at the Github repo and there's already a report for it.

    What I don't understand (and apparently this is my problem, not a bug) is how we're supposed to narrow the list down to three suspects in the next-to-last step, as the "Case Solved" text describes (Yeah, I cheated). The interviews with the two witnesses give a partial hotel name and a check-in date, but that returns dozens of results. The ending messsge congratulates us for reducing that list by using the surveillance records in some way, but I can't see how. The only other detail I have is "The guy looked nervous", which doesn't seem to have any connection with the surveillance records.

  • Not incorrect.

    Jump

  • Sure, but as far as I'm aware, no other large group of LISP users exists. My contention isn't that most AI researchers use LISP now, but that most LISP programmers are (were?) AI researchers.

    I've been trying to learn about early AI work, and I'm finding that to get any practical details you're almost guaranteed to have to wade through LISP code, although at least it's usually pretty well commented.

  • Not incorrect.

    Jump

  • LISP: You are an AI researcher and a nerd.

  • "Works for me"

    Jump

  • I use 10ten (previously Rikuchamp) for Japanese. I don't think it does full translation, but it gives thorough dictionary lookups (from WWWJDIC) as mouseover tooltips. Very useful if you're trying to learn the language, but maybe not so much if you just want to read stuff quickly. I think it's now available for every major browser, but I mostly use it on FF.

  • StackOverflow has lost 77% of new questions compared to 2022. Lowest # since May 2009.

    Jump

  • A few years ago I had a software problem, and in the course of trying to solve it I found someone with almost the identical problem on SO, although no-one had posted a solution. Later on, I managed to piece some facts together and come up with a solution that worked for me. Trying to make life easier for others having the same problem, I posted my solution to that SO question, along with a brief explanation of what I thought the underlying problem was, and how my solution addressed it.

    I got several upvotes, and one or two comments from people saying it worked for them too, which was nice. There was also a post from someone it didn't work for, and they outlined why they thought that might be, which was constructive.

    Unfortunately there was also some salty grump who weighed in just to tell me that my solution wasn't "correct". Not that it didn't work mind you, just that it wasn't good enough for them. As far as I bothered to look into their vague comments, my solution may have fixed the issue more as a side-effect than directly, but it did fix the issue. Meanwhile this person offered no alternative instructions of their own.

    As time goes on, I seem to run across this sort of -- not just unhelpful but "anti-helpful" -- attitude more and more often on SO.

  • How to run current file in Kate?

    Jump

  • That's kind of the bare bones of how it works, underneath all the abstraction layers and pretty GUIs.

    Then it evolves.

    First, you start splitting your code into multiple source files, either because your programs get too big to keep scrolling up and down one huge file to cross-check things, or because you want to incorporate someone else's code into your program, and it's more than just one or two functions you can easily copy and paste. You can still keep compiling and linking all of this in one step, but the command gets so long that you make a shell script/batch file as a shortcut.

    After that, you might want to mix-and-match various source files to target different platforms, or to make other bulk changes, and you start going down the rabbit hole of having your shell script take arguments, rather than having a dozen different scripts. And then one day you take another look at "make" and realize that whereas before it seemed like impenetrable overengineering, it now makes complete and obvious sense to you.

    Then you discover using "make" (or a similar utility) to split compilation and linking into separate steps, which used to seem nonsensical, but now you're dealing with codebases that take more than a couple of seconds to compile, or precompiled libraries or DLLs, and you get comfortable with the idea of just hanging on to compiled object files and (re)using them when the source for that part of the program hasn't changed.

    And finally (maybe) you look at some of the crazy stuff in fancy IDEs and understand why it's there; that it's just representations of all this other stuff that you now know about and feel competent with. I say "maybe" because I've been programming for over 35 years, occasionally professionally but mostly as a hobbyist, and there are still things in IDEs that I either don't understand, or don't see the point of having them. But knowing the underlying principles makes me feel comfortable enough to ignore them.

  • How to run current file in Kate?

    Jump

  • I hadn't heard of Kate before, so I can't offer much hands-on advice. I dug around and found a "handbook" here: https://docs.kde.org/stable5/en/kate/kate/index.html

    Unfortunately it does look like you need to define a project to compile/run anything, which appears to require manually creating a .kateproject file in the directory as outlined here: https://docs.kde.org/stable5/en/kate/kate/kate-application-plugin-projects.html#project-create

    I had exactly the same problem when I moved from languages that were interpreted or combined the IDE and runtime environment into one, and starting to use languages which had their own external compiler. Unfortunately, open source project user documentation is often terrible for beginners (what I found above for Kate seems to be no exception), and IDEs often seem to be written by people who don't really expect anyone to actually use the included build options (to be fair, most folks seem to like using their own separate build utilities, so probably this is often the case)

    If you can tell us which compiler or interpreter you're using (e.g. gcc, clang, Python), someone can probably tell you how to compile and/or run a single-file program from the terminal with a fairly simple command.

  • Most descriptive bug report

    Jump

  • Despite this, I still bet that they post "nvm fixed it" an hour or two later.

  • Deleted

    Permanently Deleted

    Jump

  • Whoops! When I looked at the second time that the shift value is calculated, I wondered if it would be inverted from the first time, but for some reason I decided that it wouldn't be. But looking at it again it's clear now that (1 - i) = (-i + 1) = ((~i + 1) + 1), making bit 0 the inverse. Then I wondered why there wasn't more corruption and realized that the author's compiler must perform postfix increments and decrements immediately after the variable is used, so the initial shift is also inverted. That's why the character pairs are flipped, but they still decode correctly otherwise. I hope this version works better:

     
        
long main () {
    char output;
    unsigned char shift;
    long temp;
    
    if (i < 152) {
        shift = (~i & 1) * 7;
        temp = b[i >> 1] >> shift;
        i++;
        output = (char)(64 & temp);
        output += (char)((n >> (temp & 63)) & main());
        printf("%c", output);
    }

    return 63;
}

    EDIT: I just got a chance to compile it and it does work.

  • Java Was The Future

    Jump

  • I first learned about Java in the late 90s and it sounded fantastic. "Write once, run anywhere!" Great!

    After I got past "Hello world!" and other simple text output tutorials, things took a turn for the worse. It seemed like if you wanted to do just about anything beyond producing text output with compile-time data (e.g. graphics, sound, file access), you needed to figure out what platform and which edition/version of Java your program was being run on, so you could import the right libraries and call the right functions with the right parameters. I guess that technically this was still "write once, run anywhere".

    After that, I learned just enough Java to squeak past a university project that required it, then promptly forgot all of it.

    I feel like Sun was trying to hit multiple moving targets at the same time, and failing to land a solid hit on any of them. They were laser-focused on portable binaries, but without standardized storage or multimedia APIs at a time when even low-powered devices were starting to come with those capabilities. I presume that things are better now, but I've never been tempted to have another look. Even just trying to get my machines set up to run other people's Java programs has been enough to keep me away.

  • Deleted

    Permanently Deleted

    Jump

  • I don't know if this will work or even compile, but I feel like I'm pretty close.

     
        
long main () {
    char output;
    unsigned char shift;
    long temp;
    
    if (i < 152) {
        shift = (i & 1) * 7;
        temp = b[i >> 1] >> shift;
        i++;
        output = (char)(64 & temp);
        output += (char)((n >> (temp & 63)) & main());
        printf("%c", output);
    }

    return 63;
}

  • Developer stages of grief

    Jump

  • Re: the Acceptance stage.

    Years ago I worked at a family-run business with a good working environment. The staff were once told a story of how, earlier in the company's history, a manager made a mistake that caused the company a substantial monetary loss.

    The manager immediately offered their resignation, but the owner said to them, "Why would I let you go now? I've just spent all this money so you could learn a valuable lesson!"

    So yeah, generally, most managers' reaction to accidentally deleting vital data from production is going to be to fire the developer as a knee-jerk "retaliation", but if you think about it, the best response is to keep that developer; your data isn't coming back either way, but this developer has just learned to be a lot more careful in the future. Why would you send them to a potential competitor?

  • Sometimes I want to call malloc, just as a treat

    Jump

  • It's a persistent dynamic memory allocation that's accessed by multiple processes! :)

  • JavaScript's days are numbered

    Jump

  • Of course! There's already a proposal for a replacement Temporal object.