HackerTrans
TopNewTrendsCommentsPastAskShowJobs

jimmytucson

no profile record

comments

jimmytucson
·الشهر الماضي·discuss
So the record labels sue the AI companies for copyright infringement and get settlement money and licensing deals in return, then the artists have to sue the record labels for a piece of that new revenue. The labels won't just pay the artists under the CBA, the artists' union has to take them to court to prove the "new use" provision applies.

And meanwhile, slop music is satisfying some of the demand for art, so even if artists do get their slice of the pie, they are not the only bakers anymore.

Seems like programmers whose code was used to train AI coding agents could make an analogous case but I guess much of their code was open source or given up to the models freely?
jimmytucson
·قبل 4 أشهر·discuss
Pretty much mirrors my experience using GPT to generate images creatively. I tried to generate an image to accompany a Robert frost poem and it made something... plausibly related. But not what I was describing. I spent the next 90% of the time making it 10% closer to what I wanted but it never got all the way there.

I’ve given it different levels of open-endednes, give this flow chart an aesthetic like this mechanical keyboard, or generate an SVG of this graphic from a 70s slide show, but it never looks quite like what I have in mind.

In the end, I think you only use this stuff to generate images if you’re prepared to accept whatever comes out on approximately the first try.
jimmytucson
·قبل 4 أشهر·discuss
They have this. It’s called batch pricing and it’s 50% off.
jimmytucson
·قبل 4 أشهر·discuss
> I have said that, in my opinion, all was chaos, that is, earth, air, water, and fire were mixed together; and out of that bulk a mass formed – just as cheese is made out of milk – and worms appeared in it, and these were the angels. The most holy majesty decreed that these should be God and the angels, and among that number of angels there was also God, he too having been created out of that mass at the same time, and he was named lord with four captains, Lucifer, Michael, Gabriel, and Raphael. That Lucifer sought to make himself lord equal to the king, who was the majesty of God, and for this arrogance God ordered him driven out of heaven with all his host and his company; and this God later created Adam and Eve and people in great number to take the places of the angels who had been expelled. And as this multitude did not follow God's commandments, he sent his Son, whom the Jews seized, and he was crucified.

Even though this sounded nuts to people in Menocchio’s time, it’s not completely implausible. The whole thing about order arising from undifferentiated chaos is pretty Greek, as is the idea of life arising spontaneously from decaying matter (Aristotle believed that). God arising from some preexisting substance is kind of radical but I’m sure there were precursors to that too. The rest of it is almost stock standard Christian mythology.
jimmytucson
·قبل 5 أشهر·discuss
That “cyclopean” eye is described as a patch of light-sensitive cells.
jimmytucson
·قبل 6 أشهر·discuss
Fascinating idea. There was another "time-locked" LLM project that popped up on HN recently[1]. Their model output is really polished but the team is trying to figure out how to avoid abuse and misrepresentation of their goals. We think it would be cool to talk to someone from 100+ years ago but haven't seriously considered the many ways in which it would be uncool. Interesting times!

[1] https://news.ycombinator.com/item?id=46319826
jimmytucson
·قبل 6 أشهر·discuss
You can definitely protect from reassignment in those languages (e.g. `final` in Java) but they don't completely prevent you from changing the underlying data. Rust would be one that comes to mind that has true immutability. I guess the Go maintainers just didn't want to go down that road, which I get.
jimmytucson
·قبل 6 أشهر·discuss
Not shilling for Go here but there are a few misconceptions in this blog post. In addition to the others mentioned:

> All of these examples involve assigning to a constant a value known at compile time but none of them will work

Maps are not known at compile time. Hash functions are randomized based on a seed only known at execution time. The hashed value of "HELLO" is actually different each time the program runs. Even if the hash function weren't random, the runtime has to allocate buckets for map values on the heap, which involves calling the OS to get memory addresses for those buckets, etc.

In Go, `const` means "the compiler can completely evaluate this expression and store the final bytes in the executable," which has the effect of making them non-reassignable, but protection from reassignment is not an actual feature of the language the way it is in Java and C++ (goes back to the maintainers wanting to keep it simple).
jimmytucson
·قبل 6 أشهر·discuss
Hmm, so in a language that does automatic bounds checking, the compiler might translate a line of source code like:

    let val = arr[i]
to assembly code like:

    cmp     rdx, rsi        ; Compare i (rdx) with length (rsi)
    jae     .Lpanic_label   ; Jump if i >= length
    ; later...
    .Lpanic_label:
    call    core::panicking::panic_bounds_check

Are they saying with "correct code" the line of source code won't be covered? Because the assembly instruction to call panic isn't ever reached?
jimmytucson
·قبل 6 أشهر·discuss
> Safe languages insert additional machine branches to do things like verify that array accesses are in-bounds. In correct code, those branches are never taken. That means that the machine code cannot be 100% branch tested, which is an important component of SQLite's quality strategy.

Doesn't the language compiler write the code that checks if the array access is in-bounds? Why would you need to test the compiler's code?
jimmytucson
·قبل 8 أشهر·discuss
> [Learning Zig] is about fundamentally changing how you think about software.

Learning LISP, Fortran, APL, Perl, or really any language that is different from what you’re used to, will also do this for you.
jimmytucson
·قبل 9 أشهر·discuss
Just wanted to say, thanks for doing this! Now the old rant...

I started my career when on-prem was the norm and remember so much trouble. When you have long-lived hardware, eventually, no matter how hard you try, you just start to treat it as a pet and state naturally accumulates. Then, as the hardware starts to be not good enough, you need to upgrade. There's an internal team that presents the "commodity" interface, so you have to pick out your new hardware from their list and get the cost approved (it's a lot harder to just spend a little more and get a little more). Then your projects are delayed by them racking the new hardware and you properly "un-petting" your pets so they can respawn on the new devices, etc.

Anyways, when cloud came along, I was like, yeah we're switching and never going back. Buuut, come to find out that's part of the master plan: it's a no-brainer good deal until you and everyone in your org/company/industry forgets HTF to rack their own hardware, and then it starts to go from no-brainer to brainer. And basically unless you start to pull back and rebuild that muscle, it will go from brainer to no-brainer bad deal. So thanks for building this muscle!
jimmytucson
·قبل 11 شهرًا·discuss
It is just as "vibe-ish" as vector search and notably does require chunking (document chunks are fed to the indexer to build the table of contents). That said, I don't find vector search any less "vibey". While "mathematical similarity" is a structured operation, the "conversion to high-dimensional vectors" part is predicated on the encoder, which can be trained towards any objective.

    > scaling will become problematic as the doc structure approaches the context limit of the LLM doing the retrieval
IIUC, retrieval is based on traversing a tree structure, so only the root nodes have to fit in the context window. I find that kinda cool about this approach.

But yes, still "vibe retrieval".
jimmytucson
·قبل 11 شهرًا·discuss
That’s because every business is “scaled” to the point that the edge employees —- ie the people who interact with paying customers —- don’t own anything, and are 12 levels of management away from anyone who does.

My grandparents owned a grocery store. Their name was on the sign. If you brought home spoiled meat, that was their name and you as a member of their community that were put out.

When my mom brings home spoiled meat from Stop & Shop, she goes back there not just to exchange it, but to complain to someone about how it messed up her barbecue plans, etc. And I’m like seriously, why would anyone working at Stop & Shop give a rat’s ass about your family gathering? Stop & Shop is owned by a Dutch multinational “food retail” company.

But that’s not the capitalism she grew up with. She actually thinks capitalism is great because it allowed her parents to come over on a boat as teenagers and make lives for themselves, and have extra to send back home. But she hates it when she calls her cable company and ends up chatting with a girl in Singapore. Go figure.
jimmytucson
·قبل سنتين·discuss
In the data world I've worked with tons of folks whose responsibilities include getting questions from execs, knowing their way around the data warehouse enough to write SQL to answer those questions, and delivering the answers back (sometimes formatted nicely). Sometimes they have to predict what followup questions the exec will ask, like "why is that number so low, it obviously shouldn't be that low" so they can press the data engineers for bugs.

Like all things LLM, I don't know if this is about to make those responsibilities a lot easier, or just eliminate them altogether.
jimmytucson
·قبل 6 سنوات·discuss
Ironically, the word "architecture" comes from designing and constructing buildings. Likewise, someone who frames houses can become preoccupied with beams and rafter angles while not operating a saw or driving in nails.

I guess what I'm saying is, everyone - including construction workers - should take your advice.