News for hackers. Stuff that matters.

samsepi01

Re:Europe is scaling back its landmark privacy and AI laws on Thursday November 20, 2025 @10:51AM (#45993923)
Maybe so. In the meantime, Europe will continue to fall behind economically.
Re:The Grug Brained Developer (2022) on Wednesday June 18, 2025 @03:08AM (#44307364)
But can't you instead just set a breakpoint next to wherever you are gonna put that print stmt and inspect value once code hits? print stmt seems like extra overhead
Re:My AI skeptic friends are all nuts on Sunday June 08, 2025 @04:35AM (#44215602)
> "The loop of prompt->study->prompt->study... is disruptive to my inner loop for several reasons, but a big one is that the machine doesn't "think" like i do. So the solutions it scaffolds commonly make me say "huh?" and i have to change my thought process to interpet them and then study them for mistakes. My intution and iteration is, for the time being, more effective than this machine assisted loop..."

My thoughts exactly as an ADHD dev.

Was having trouble describing my main issue with LLM-assisted development...

Thank you for giving me the words!

If Peru gets to claim this pope, then the US gets to claim Tesla, Einstein, etc. lol
Re:Playwright Tools for MCP on Wednesday March 26, 2025 @07:40PM (#43488806)
Please share results!
Re:Grok3 Launch on Tuesday February 18, 2025 @04:34PM (#43095386)
I guess when it comes to LLM's what is considered the "source" - the weights or the code used to build the weights?
Re:Show HN: Former – Open-source Cursor for SQL on Friday February 07, 2025 @06:05AM (#42971338)
Oh dope, I'll try again later, then!
Re:Show HN: Former – Open-source Cursor for SQL on Thursday February 06, 2025 @02:34AM (#42960017)
Love the idea, folks! Congrats on open-sourcing.

Just tried your macOS desktop app download link, but only see an x64 option - do you have a version for ARM (i.e. Apple Silicon) ?

Re:Legalizing Sports Gambling Was a Mistake on Saturday September 28, 2024 @01:06AM (#41678025)
We definitely need to pump the brakes on this...

Sports gambling ads have become so pervasive that it’s hard to watch a game without being bombarded by manipulative promotions that say stuff like "BET $5, GET $200 INSTANTLY"...

I became a recreational sports bettor in college through offshore books. I always felt like I was doing something extremely dangerous and so was very careful - probably in large part because of the societal stigma surrounding sports betting. I feel like I benefited from having instilled in me a greater fear of gambling dangers that I wouldn't have now if I just started gambling after seeing all these prominent sports talking heads discussions, social media influencer promotions, and constant TV advertisements.

Trying stricter regulations feels like a no-brainer before totally reverting to a federal ban.

At a minimum, we should match the intensity of regulations for other legal vices: - National min. age of 21 for any state that legalizes sports betting, matching drinking regulations that were set 40 years ago. - Restrict advertising to audiences where you can confidently report that >70% of which are adults >= 21 years old, similar to recreational marijuana advertisement regulations in states like CA. - More intense warnings should follow each ad, clearly emphasizing the risks of addiction and the likelihood of financial loss, similar to the mandatory disclosures in prescription drug ads.

Additionally, for the unique vice of sports gambling and it's associated societal dangers, there should be: 1. More intense restrictions on ads: a. Clearly disclose all stipulations. For example, language like ‘BET $5, GET $200’ should be accompanied by fine print explaining that the bonus bet can’t be withdrawn, and any winnings must be wagered multiple times before withdrawal. b. Transparent statistics of users' outcomes at specific sports book. Something like: "Y% of our customers who have accepted a bonus bet have successfully turned it into real cash in their bank account. The remaining (100-Y)% lose it all." 2. Regulations on sports book's social media accounts promoting individual bettors' winnings - i.e. Sports books shouldn't be able to promote a story about someone winning $100k on a $1 20-team parlay. 3. Roadblocks, at a minimum, on betting losses for vulnerable groups -- e.g. after a bettor has lost X% of their initial deposit/yearly salary/net worth/etc, the bettor's account should be restricted in some way unless they say to a real person on the phone: "YES, I AM AWARE OF HOW MUCH MONEY I'VE LOST. I WISH TO RISK LOSING MORE MONEY." 4. A requirement that all bets be placed with money deposited via debit card/check/cash. A ban on taking on any kind of debt (like using a credit card to deposit funds into betting account) to place a bet seems reasonable.

I think most of these projects are bit overkill, OG poster's repo is about what I'd do myself.
I found this tool (repo2file) helpful for my workflows - quickly giving context for questions to my local LLM about my working (small) repo in the terminal. Until I saw this post, I wasn't aware of any of those.

What makes his better? Since you're asking, I tried these and here's my verdict:

- [files-to-prompt](https://github.com/simonw/files-to-prompt) (from the GOAT simonw) --> There's no option to specify files to include, must work backwards with ignore option

- [code2prompt](https://github.com/mufeedvh/code2prompt) --> It always puts the output to the paste buffer even if you specify output file

- https://gh-repo-dl.cottonash.com/ --> There's no CLI

- [1filellm](https://github.com/jimmc414/1filellm) --> Many dependencies and complicated setup(have to setup GitHub access token which I've never done)

- [repopack](https://github.com/yamadashy/repopack) - [ingest](https://github.com/sammcj/ingest) --> haven't tried these yet, but they actually look promising...