Hacker Newsnew | past | comments | ask | show | jobs | submit | xenophonf's commentslogin

I stopped using this when the dev did their rugpull and won't go back.

Yes.

It's nice to get an easy question every once in a while.


"Require actions to be pinned to a full-length commit SHA" applies to composite actions, too. I had to replace pre-commit/action as a result.

That "inadvertently" desperately needs scare quotes.


I only found out about them via word of mouth, but who knows. At least they're good stuff!


> [Qwen coder 0,5B] can output decent functions given the right context instructions

Can you share a working example?


So… a prompt? I’m not on my laptop but I hooked it to cmp.nvim, gave it a short situational prompt, +- 10 lines, and started typing. Not anywhere near usable but with a little effort you can get something ok for repetitive tasks. Maybe something like spotting one specific code smell pattern. The advantage is the ridiculous T/s you get


LM Studio isn't free/libre/open source software, which misses the point of using open weights and open source LLMs in the first place.


Disagree, there are a lot of reasons to use open source local LLMs that aren't related to free/libre/oss principles. Privacy being a major one.


If you care about privacy making sure the closed source software does not call home is a concern...


I run Little Snitch[1] on my Mac, and I haven't seen LM Studio make any calls that I feel like it shouldn't be making.

Point it to a local models folder, and you can firewall the entire app if you feel like it.

Digressing, but the issue with open source software is that most OSS software don't understand UX. UX requires a strong hand and opinionated decision making on whether or not something belongs front-and-center and it's something that developers struggle with. The only counterexample I can think of is Blender and it's a rare exception and sadly not the norm.

LM Studio manages the backend well, hides its complexities and serves as a good front-end for downloading/managing models. Since I download the models to a shared common location, If I don't want to deal with the LM Studio UX, I then easily use the downloaded models with direct llama.cpp, llama-swap and mlx_lm calls.

[1]: https://obdev.at


This looks like an LLM's hallucinations. I don't see any evidence supporting the conclusions made, and some of the conclusions are overblown, like that bit about DKIM keymat leaks being the "most dangerous". The whole thing is written in this breathless, overwrought style that seems to be favored by bots fed a strict diet of ad copy and marketing white papers—"not X. Y!" (That's a thin gruel and probably ought to be treated by our future AI overlords as child abuse.)


> This looks like an LLM...

The word "masterclass" in the title is another clue in that direction. In the past 20 years i have only ever heard it used (frequently/habitually) by LLMs and many recent (LLM-era) articles.

Edit: or maybe i live an ultra-secluded life and don't see people using that word all the time. Gemini, in any cases, loves using that word and humans (in my experience) rarely use it.


Where in the pnpm documentation does it say that it ignores scripts by default?

From https://pnpm.io/cli/install#--ignore-scripts:

> Default: *false*


Weird. The config also appears to default to `false`

https://pnpm.io/settings#ignorescripts


This page describes the behavior, "disables the automatic execution of postinstall scripts in dependencies":

https://pnpm.io/supply-chain-security

While this explicitly calls out "postinstall", I'm pretty sure it affects other such lifecycle scripts like preinstall in dependencies.

The --ignore-scripts option will ignore lifecycle scripts in the project itself, not just dependencies. And it will ignore scripts that you have previously allowed (using the "allowBuilds" feature).


PyPI enforces immutable releases.

https://pypi.org/help/#file-name-reuse

> PyPI does not allow for a filename to be reused, even once a project has been deleted and recreated...

> This ensures that a given distribution for a given release for a given project will always resolve to the same file, and cannot be surreptitiously changed one day by the projects maintainer or a malicious party (it can only be removed).


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: