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

Fable Converted Pylint to Rust

pypi.org

Post reply on HN
Print view View original

41–50 of 122 posts

Re: Fable Converted Pylint to Rust

#41

Post by rpunkfu »

bravetraveler wrote: post #11
TheChaplain wrote: post #8

IMHO there is little point of these conversion projects. It screams of "look at me, see what I made" and when the attention goes down a little nothing was ever pushed to the repo ever again. Perhaps I am out of touch, but a project with author/s that have passion for every line, function and purpose, feels more real and worth my trust to spend time using it.

I'd go even further: 'look at me, see what was paid for.' This isn't much different than the 'builder brained' coworker who is obsessed with creating technical debt, not owning it. Throwing shit at the wall and seeing what sticks, passing it off as sage wisdom. It'd be interesting to see the math behind offsetting the GPU crunching with more power efficient linting. Assuming every person or CI job switched (and the m…

Essentially pay-to-win for coding.

Re: Fable Converted Pylint to Rust

#42

Post by flyingbeaver09 »

voidUpdate wrote: post #15

Do you generally pylint an entire codebase at once though? Why not just the file you are actually working on? Based on the homeassistant results (10.3 hours to lint 17.5k files), it only takes about 2 seconds to pylint a file, which doesn't really feel like enough of a wait to need an entirely new linter

hopefully I never have to work with you if you think 2 seconds for libting is fine

Re: Fable Converted Pylint to Rust

#43

Post by NonHyloMorph »

short_sells_poo wrote: post #18
Hamuko wrote: post #5

So basically `ruff check --select=PL` but worse in every single way, maintained by a system that's not even available anymore? It even uses Ruff's code under the surface.

> It even uses Ruff's code under the surface. This is the modus operandi for a lot of vibe coded stuff. Absorb the code of entire projects wholesale and then repackage it as something new. Some of them have the decency to at least give credits to the original.

Speculative hyothesis: It might not be compatible with a capitalist social order, but also I get the impression that it' something that will staylike something that will stay. The involved means of production and their control are the critical point here. (Also - highly speculative - potentially the question if they should be >>owned<< at all even by some abstract commons)

Re: Fable Converted Pylint to Rust

#44

Post by lelanthran »

baq wrote: post #38
lelanthran wrote: post #27

Earlier quoted context omitted.

In an open source tool, there is no value without community of contributors. The value of the discussed project is exactly zero right now in the best-case scenario . It's more likely to be negative: because there has been no contact with reality (no users have used it in production), the risk is higher than using the existing one. IOW, 1. Only after some brave souls use this in production, will the value of this proj…

category error. surely you aren't calling binary releases of binutils 'projects'? why would you call this thing a 'project' in the sense you're using?

> surely you aren't calling binary releases of binutils 'projects'? why would you call this thing a 'project' in the sense you're using?

Because you called it a good thing using my definition of project:

>>> It improves the dev-ex of people contributing to these projects

If this is supposed to be a "Product of the compilation process only", then sure, but if so, what devex of the contributors exist?

If you want to shift to regarding this as analogous to the binary releases of binutils, then the devex of contributors doesn't matter, because the contributors to binutils aren't binary-patching files.

Re: Fable Converted Pylint to Rust

#45

Post by the_duke »

TheChaplain wrote: post #8

IMHO there is little point of these conversion projects. It screams of "look at me, see what I made" and when the attention goes down a little nothing was ever pushed to the repo ever again. Perhaps I am out of touch, but a project with author/s that have passion for every line, function and purpose, feels more real and worth my trust to spend time using it.

Making something 50-2000x faster is pointless?

Besides that, Rust code is actually much easier to maintain , thanks to type system guarantees.

Re: Fable Converted Pylint to Rust

#48

Post by voidUpdate »

flyingbeaver09 wrote: post #42
voidUpdate wrote: post #15

Do you generally pylint an entire codebase at once though? Why not just the file you are actually working on? Based on the homeassistant results (10.3 hours to lint 17.5k files), it only takes about 2 seconds to pylint a file, which doesn't really feel like enough of a wait to need an entirely new linter

hopefully I never have to work with you if you think 2 seconds for libting is fine

and hopefully I never have to work with you if you think that every single second must be spent coding, no seconds allowed for stuff to process in the background when you save a file

Re: Fable Converted Pylint to Rust

#49

Post by odiroot »

TheChaplain wrote: post #8

IMHO there is little point of these conversion projects. It screams of "look at me, see what I made" and when the attention goes down a little nothing was ever pushed to the repo ever again. Perhaps I am out of touch, but a project with author/s that have passion for every line, function and purpose, feels more real and worth my trust to spend time using it.

The ~~beatings~~ rewriting to Rust will continue until morale improves.

Re: Fable Converted Pylint to Rust

#50

Post by bravetraveler »

rpunkfu wrote: post #41
bravetraveler wrote: post #11

Earlier quoted context omitted.

I'd go even further: 'look at me, see what was paid for.' This isn't much different than the 'builder brained' coworker who is obsessed with creating technical debt, not owning it. Throwing shit at the wall and seeing what sticks, passing it off as sage wisdom. It'd be interesting to see the math behind offsetting the GPU crunching with more power efficient linting. Assuming every person or CI job switched (and the m…

Essentially pay-to-win for coding.

With moves like this, I'm not so sure victory is assured... but yes. Pay to play.

I, like most, beat linting delay by running it in the background; asynchronous.

Having been negative, so far, I want to say something positive. I appreciate that LLMs weren't used for license washing in this case.

Post reply on HN