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/)T
Posts
0
Comments
417
Joined
3 yr. ago

  • All feedback in the post is welcome.

    Would it be rude to recommend a grammar checker? The topic and supporting arguments for the post are fine (if a little disorganized, but that's common for blog posts). I just found the run-ons a bit distracting.

    Otherwise, I agree that the internet is getting shittier. More ads, more walls to defend against scraping, less accessibility, etc. There's no real metric for how well a page presents its contents, only metrics for specific things like load times, layout shift, and so on. I also suspect that, over time, page scoring will shift toward which sites present the data in ways that are more usable by LLMs.

  • This is a very pedantic complaint. Given that you haven't read past the first sentence, I'm not really sure what to discuss here.

    "Smart pointer" is commonly used to refer to reference-counted pointers that free automatically.

  • While interesting, this entire article works with a static MyStruct. This means the type already is Any, and if you define MyTrait: 'static, then you can do the downcast by first casting to an Arc<dyn Any> and using one of the downcast methods.

    For non-'static types, downcasting soundly is incredibly difficult. You need to somehow get the correct lifetime back from the trait. You're better off using unsafe at that point anyway. If the trait itself holds the lifetime (impl<'a> MyTrait<'a> for MyStruct<'a>), then that can help with it, though I'm not really sure how lifetime variance plays into the soundness of a downcast here.

    Finally, at the end, I'd rather just use an assert! over an unchecked assertion. I know the goal is to look at the assembly with that assertion in place, so it makes sense why they used it here. In practice, an actual assertion is a lot better because the compiler gets the same information from it and you get validation at runtime that the information is correct.

    Anyway, great article! The goal was to explore how Arc casting works, and I think it does a great job at showing and explaining that.

  • SQLite allows for more efficient querying of data than doing it by hand, can enforce constraints on the data, and I can query it from my shell.

    Of course it's not going to replace a commonly-used format for a domain. If no such format exists, it's a perfectly acceptable data format for data that's tabular in nature. And it can by sync'd/backed up the same as any other file.

  • I don't know why it's worth arguing (both of you) over the versioning scheme of a LLM-assisted/generated project that was posted by a new user with no other activity, but anyway...

    PyPi (and Python) do not require semver, nor do all packages in the ecosystem use semver. However, Python tooling depends on packagers following a semver-esque versioning scheme while still allowing some freedom to maintainers to pick a scheme that works best for them.

  • One.

    The recent news was about network traffic, not market share. Anyone talking about increased market share is making up their own conclusions from the data.

    The data is interesting, but not sufficient for that kind of conclusion.

    Edit: other market share articles are interesting if they actually show new data and aren't making up a conclusion.

  • Code shows signs of LLM use, in case anyone's curious. Unless, of course, you normally type em dashes in your documentation I suppose.

    Anyway, this feels to me like a small part of what is essentially a durable task framework. If you need atomicity and durability, consider one of those. If all you need is atomicity, a database guarantees it through so many methods, from inserts to locks*.

    *Edit: and transactions, of course, but long running transactions aren't usually a good idea.

  • To answer the question posed in the title: if you’re processing images given to you by strangers, you should normalize RGB values by 255.

    The author isn't advocating for you to do so. They are just exploring the two approaches. Even in the sentences following this one where they mention where 256 might work, they conclude with your colleagues breaking it all anyway by using 255.

  • Sure, Mexico has its problems, but I wouldn't dare classify a whole country of people as stupid.

    And Canada?

  • I would guess it's a lot of people finding out the price of the Steam Machine ($1049 with no controller is a lot!) and deciding instead to run Linux on a PC instead

    If this were the case, then they'd be zipping through the waitlist. I've been waitlisted since release (with the small hope that prices come down by the time it's my turn, otherwise I'll most likely give up my spot lol) and I've seen no emails about it since then.

    They have been selling them, but they are also struggling to get RAM allocation. My guess is that they are being held back by RAM (and possibly storage to a lesser extent) and aren't able to make them fast enough to satisfy the current demand.

    Many tech influencers have been advocating Linux due to how bad Windows is and how great Linux is at this point. I'd expect most growth to be coming from there.

  • The Cloudflare chart would probably be pretty representative given how much traffic goes through it.

  • 1 million line PR? LGTM

  • I don't understand specifically the copyright issue with respect to "trained on x data"

    It's a question of whether the output of the LLM is a derivative work of the training data. From a copyright standpoint, if the work is derivative (and not fair use), then it needs to follow the terms set by any licenses you have to its parent works.

  • Stabilize yeet.

  • You can, if you can afford it. Most people can't afford, let alone find, LPCAMM2 memory. This, of course, includes Framework.

  • I feel like you have to review new laptops (and the Steam Machine, for that matter) without considering the price these days. Normally, specs without a price means nothing, but no new releases in the space are going to be worth the cost.

    Where this is more interesting, in my opinion, is compatibility with the older Framework 13. If you can buy the individual components from the pro variant that you want, it might be possible to upgrade without draining your bank account. Avoiding the LPCAMM2 modules seems like the best way to do that, which unfortunately means skipping on the mainboard (and processor).

    Hopefully we see prices drop sometime soon. I think at a lower price, it'd be worth considering. At the current price, very few computers are worth buying.

  • This depends, but not because of piracy. If you have to bypass DRM to download the music, you may be violating DMCA §1201 (even if you are otherwise allowed to use the music).

    Edit: This obviously doesn't apply to GitHub, but might to YouTube.

  • The final example just boils down to writing the whole program in assembly, doesn't it? The C function just returns a pointer to a static string, which you might as well do in assembly yourself since it's less code to do it that way (you can omit the whole function signature).

    In any case, the article does a great job introducing the various compilation stages the C program goes through in order to become an executable.