Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Porting a library to a different language with a sentence

randomlabs.ai

Post reply on HN
Print view View original

11–20 of 21 posts

Re: Porting a library to a different language with a sentence

#11

Post by pcthrowaway »

deng wrote: post #6

I cannot find any link to a repository with that ported library. I can't imagine why you wouldn't share this exciting port, unless of course the code is not that great? And as a sidenote, why would you ever hijack the up/down cursor keys on a web page? There are still people out there on actual computers which use them for scrolling.

> And as a sidenote, why would you ever hijack the up/down cursor keys on a web page? There are still people out there on actual computers which use them for scrolling.

There are also people who will give up on the article when they realize they can't scroll with the arrow keys.

Re: Porting a library to a different language with a sentence

#12

Post by JaggerJo »

JonChesterfield wrote: post #8
JaggerJo wrote: post #7

Earlier quoted context omitted.

> .. excluding all tests and examples, .. How would you verify that the ported code actually works if you don't port the tests and examples? I see tremendous use in a tool that could be used to port "any" library to any language. I'm very skeptical if this works if the library itself depends on other language specific libraries, ... but we'll see. If you'd seriously want to use that port in production it only makes s…

It's much more convincing evidence that the port worked if you run the same tests and examples as before. If you've let the llm change the tests too it's very hard to tell whether the new codebase does the same thing as the original.

Yes, that would be even better - but also way harder for unit tests as you’d need to interop between the langauges.

Re: Porting a library to a different language with a sentence

#14

Post by Anonbrit »

frumplestlatz wrote: post #10
JonChesterfield wrote: post #8

Earlier quoted context omitted.

It's much more convincing evidence that the port worked if you run the same tests and examples as before. If you've let the llm change the tests too it's very hard to tell whether the new codebase does the same thing as the original.

Claude Sonnet has a funny habit of fixing test failures by deleting the failing tests.

It really is like an over enthusiastic college intern!

Re: Porting a library to a different language with a sentence

#15

Post by Archit3ch »

FearNotDaniel wrote: post #2

> If you're reading this you probably have some idea of what slate is. Tip for anyone writing technical/product blogs: never assume readers know what your product is. They probably came in for the first time from a random link on some site like HN and this is your first (and maybe only) opportunity to get that elevator pitch in. I think this particular example is a good one, in that they immediately provide a one-sen…

> If you're reading this you probably have some idea of what slate is.

Yeah, they make audio plugins. :)

Re: Porting a library to a different language with a sentence

#16

Post by reycharles »

Archit3ch wrote: post #15
FearNotDaniel wrote: post #2

> If you're reading this you probably have some idea of what slate is. Tip for anyone writing technical/product blogs: never assume readers know what your product is. They probably came in for the first time from a random link on some site like HN and this is your first (and maybe only) opportunity to get that elevator pitch in. I think this particular example is a good one, in that they immediately provide a one-sen…

> If you're reading this you probably have some idea of what slate is. Yeah, they make audio plugins. :)

It's a type of rock

Re: Porting a library to a different language with a sentence

#18

Post by hn8726 »

JaggerJo wrote: post #7
JonChesterfield wrote: post #3

I was looking for signs that the tests and examples worked afterwards. Those are missing. Its javascript to typescript, which unless I'm missing something, can be done with `mv foo.js foo.ts`. No examples of any transforms done by the tool. And it wasn't one sentence, it was a sequence of questions and answers. I guess they started with the title for the blog post and didn't really worry about showing whether it did…

> .. excluding all tests and examples, .. How would you verify that the ported code actually works if you don't port the tests and examples? I see tremendous use in a tool that could be used to port "any" library to any language. I'm very skeptical if this works if the library itself depends on other language specific libraries, ... but we'll see. If you'd seriously want to use that port in production it only makes s…

> How would you verify that the ported code actually works if you don't port the tests and examples?

Port tests, run them against unported code. Port code, run it against unported tests? That way you also verify that the public api hasn't changed

Post reply on HN