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

AVincentInSpace

@ AVincentInSpace @pawb.social

Posts
1
Comments
204
Joined
3 yr. ago

  • Linux Cat

    Jump

  • it won't... do anything

    it'll wait for you to type ten lines (the default for head without arguments), buffer them (bc tail must buffer its input), then spit them back at you, and exit

    • head takes the first N lines of its input (if -n <number> is not specified, the default is 10 lines, and default reading from stdin, which in this case is your terminal) and prints them to its stdout (which thanks to the pipe, goes directly to cat's stdin), then signals end-of-file.
    • cat accepts any number of filenames and conCATenates them (hence the name), writing their contents one after the other to stdout. with only one file as argument (the most common case in practice) it will simply write that file's contents to stdout. with no arguments (as in this case) it will simply copy everything from its stdin (in this case head's stdout) to its stdout (in this case tail's stdin). the cat command could be completely omitted from this invocation (leaving simply head | tail) and it would work exactly the same.
    • tail reads its entire input (like head, it defaults to reading from stdin unless a filename is specified) and buffers it, then, when the end of the file is reached, it prints the last N lines is read (again defaulting to 10 unless -n <number> is specified) to stdout (in this case your terminal).

    put all together, head will wait for you to type a line, then will pass it on to cat, which will then immediately pass it on to tail, which will add it to a buffer and wait for another line. rinse and repeat until you have typed 10 lines, and then head will exit and the pipe between it and cat will close. cat, noticing the closed pipe, will exit in turn, causing the pipe between it and tail to close. tail, seeing an end of file signal on its input pipe, will cough up the last 10 lines in its buffer and then exit. since head only sent it 10 lines, this is the entirety of its input. so it will spit back everything you typed.

    If you press Ctrl+D to send head an end-of-file signal before you have typed 10 lines, head will exit immediately, causing cat to exit, causing tail to output everything it had in its buffer so far.

  • Blind ah

    Jump

  • consider: this also fits the meter of everybody wants to rule the world

  • Runk

    Jump

  • And scrubbed it of any mention of Ronald's name before pulling it out onstage. Don't forget that.

  • Runk

    Jump

  • If I had a dollar for every copyleft project whose maintainer became Ronald, I could found a tech company.

  • You'll think of a great one later

    Jump

  • cmon man this is easy

    "and I'm the only one you'll ever see"

  • didn't think so

    Jump

  • I don’t think anyone is arguing against some of the very real applicable uses of llms in fields like data or even medicine

    You haven't been on Lemmy very long, have you?

  • didn't think so

    Jump

  • Jesus Christ that's cynical.

  • didn't think so

    Jump

  • The sort of AI that reads radiology scans has almost nothing in common with the sort of AI that develops drugs has almost nothing in common with large language models. A key difference is that the first two require orders of magnitude less processing power. If that was all AI was used for, we wouldn't be claiming people's houses under eminent domain in order to build beefier power lines for AI datacenters, and the EPA wouldn't be loosening environmental regulations on power plants devoted exclusively to AI datacenters. We would also be able to afford computer parts.

  • Cory Doctorow: The people who tell you ‘AI is changing everything’ are lying

    Jump

  • ...So you insist that AI power use isn't a big problem right now, but your best case scenario for the future is that humanity gets nuked out of existence. By nukes that were designed using help from LLMs, which they haven't been shown to be able to help with.

    You seem like a very serious person who is worth debating.

    As for the data use thing, firstly, I don't know why the choices are between the actual work and hearsay. I don't know where you got those two options from. I also don't know what would be producing the hearsay (human? LLM? If the latter, are we straight up admitting to copyright laundering? Also, I thought training LLMs on output of previous LLMs caused model collapse). I especially don't know why you're asking me to speculate on what creatives want immediately after attacking my ability to speak on behalf of creatives. But since you are apparently asking me to do that, I think they'd prefer the hearsay, since the point is that they don't want the model to be able to imitate their work for anyone who asks for cheap, and in so doing, put them out of a job. Or worse, have the model agree to a job they would have said no to, and damage their credibility and brand.

  • Cory Doctorow: The people who tell you ‘AI is changing everything’ are lying

    Jump

  • Okay. I'm not sure how that excerpt proves he's an industry plant. It sounds like he's talking about the massive financial crater that will be left behind when the fact that zero companies in the AI sector that do not manufacture hardware are profitable catches up with them and the bubble pops, which I personally think he's right about.

  • Cory Doctorow: The people who tell you ‘AI is changing everything’ are lying

    Jump

  • I don't know about other industries, but I'm a programmer, and I firmly believe that people who cannot be bothered to put in the hours to learn to do so the old fashioned way, should not make software.

    Vibe coding is how you get software designed by people who do not know how to design software and implemented by a chatbot that is infamous for writing buggy, insecure, impossible-to-maintain code.

  • Cory Doctorow: The people who tell you ‘AI is changing everything’ are lying

    Jump

  • Frontier level models are finding novel solutions to decades-long unsolved maths problems.

    Such as?

    Because if you're talking about that recent proof of the Collatz conjecture, I've got bad news.

    Also let me know when they figure out how to stop making stuff up, or at least to understand the difference between a sequence of tokens that represents a true fact and one that does not.

  • Cory Doctorow: The people who tell you ‘AI is changing everything’ are lying

    Jump

  • This is cool, but it is a completely different kind of AI from LLMs.

  • Cory Doctorow: The people who tell you ‘AI is changing everything’ are lying

    Jump

  • Do a little research. AI power usage isn't that much of a problem yet.

    Okay.

    https://www.yahoo.com/news/us/articles/pollution-musk-unpermitted-xai-power-100200381.html

    https://www.msn.com/en-us/money/markets/epa-exempts-off-grid-ai-power-plants-from-acid-rain-program-caps-affecting-60-sites/ar-AA28YctM

    https://www.fastcompany.com/91229319/ai-data-centers-could-make-your-electric-bill-go-up-by-70

    https://www.cbsnews.com/news/georgia-power-ai-data-centers-eminent-domain/

    Power usage from AI data centers has already eclipsed power usage from all other data centers combined. If you can come up with a scenario where AI hasn't doubled in scale by 2030 by belching smoke into the atmosphere, I'll concede the point.

    A lot of really good data is copyrighted

    Yeah, and that's too fucking bad. If the people who made it don't want it to be used for AI training (and I don't think I've ever met a creator who has done the research on AI who does, even if they got paid), it shouldn't be.

  • Cory Doctorow: The people who tell you ‘AI is changing everything’ are lying

    Jump

  • David Revoy (open source comics artist) is tired and frustrated of people calling his human art, AI-generated

    Jump

  • Pro tip: when copying a link to a Lemmy/Piefed/Kbin/etc post, please make sure you use your instance's option to copy the link to the post on its original instance (the instance the post was made on), rather than simply copying the link to the post on your instance out of your URL bar. On your instance's web interface, that option is in the More drop down next to the Boost button, just below the post title. (On a Lemmy instance, the link to the original post is the Fediverse icon right next to the upvote and downvote buttons, and you can right click and Copy Link from there).

    Obviously, when you open a post in the browser on an instance that isn't yours by clicking a link (for example, this link to this same post on my instance, which is a vanilla Lemmy instance), you can't interact with it, because you aren't logged in, because you don't have an account on that instance. To interact with it, you need to open the same post through your own instance.

    If you have a link to a post on the instance it was created on, you can simply paste that URL (the whole thing) into your instance's search bar to open it on there, so you can vote/comment/etc. Some mobile apps can even do this automatically. However, this doesn't work if you paste a link to a post through an instance other than the instance it was created on. In order to interact with the post you just linked to, people have to click the link to open the post on your instance, then click the button on there to copy the original link, before pasting it into their own instance. It's polite not to make them go through that extra work.

    Judging by your account age, it seems you're new to Lemmy, so you probably didn't know that. Just something to keep in mind for future. :)

  • Soft-deprecating chrono and chrono-tz

    Jump

  • rkyv is not like serde. There is no process of deserialization. The function rkyv::access(...) takes a &[u8], performs a consistency check, then casts the pointer it was passed to the desired type and returns Result<&T, Err>. I will say this again: "deserialization" in rkyv is a reference-to-reference conversion.

    As you can imagine, it's very fast, but the tradeoffs are massive. The serialized bytes must exactly match the memory layout of a struct (usually distinct from the type being serialized) called the "archived type" (which must be #[repr(C)] or #[repr(transparent)], and which is most commonly generated from the fields of the struct being serialized using a derive macro). More importantly, there is nowhere to stick deserialization code which could convert a Unix timestamp to a jiff::Timestamp.

    You can't really implement custom serialization schemes for third party types with it, at least not unless you want to define that #[repr(C)] struct yourself, and/or you're okay with actually deserializing (in rkyv, the Deserialize trait accepts a reference to the archived type and returns an owned value of the serialized type, usually by effectively cloning it) and the performance cost that entails, and with how my codebase is currently architected, I'd have to redo it every time I used the value. rkyv support kind of has to be baked into a library from the get-go for it to be worthwhile.

  • Ever noticed how cult-like the AI community is?

    Jump

  • Please resist responsibly

    Jump

  • What country do you live in?

    If it's anywhere near the west, odds on their leader is either already fascist or facing serious competition in the polls from one.

    What's stopping YOU?

  • Nix / NixOS @programming.dev
    AVincentInSpace @pawb.social

    My new user experience has been awful and I'm not sure what I'm doing wrong. Could really use some guidance.