you can't claim an invention is invalid because there are no "studies" that show such an invention has already existed and succeeded, you'd by definition never invent anything!
12,368 karma · joined April 5, 2007
http://techspot.zzzeek.org
you can't claim an invention is invalid because there are no "studies" that show such an invention has already existed and succeeded, you'd by definition never invent anything!
"but it's a real typewritten letter! you dont understand!"
yeah but you didn't snail mail it to all of us, you or someone put it on the internet on a webpage. if you can scan a letter as a JPG and scp it to a server, you can run an OCR and put alt text in.
If you don't like my posts, the downmod button is right there. I can otherwise do without the moralizing lecture which is definitely something nobody wants here. Did you just search for "AI" posts that needed policing to even find this totally dead thread ? Talk about HN being a "job"
after he literally single-handedly ruined the product by personally censoring the editorial team and/or firing large numbers of journalists on multiple, extremely high-profile PR-disastering occasions [1] [2]
from that perspective, Bezos seems perfectly content to weather PR disasters from his companies and drape them in bizarre rationalizations.
[1] https://www.theguardian.com/media/2024/oct/29/washington-pos...
[2] https://finance.yahoo.com/news/more-60-000-washington-post-2...
a gemini query is like a google search with natural language embedded. ill do my "google search" and just rewrite the text next time, ta
unless google searches are also illegal for hacker news commenting
> If rekabis cared about what an LLM had to say they could have done that themselves.
I post stories here hoping for just that human interaction you speak of, plenty of scientists here who could have added to the topic, but none did. Doomerists are not typically interested in researching their claims, it would make for much less sensationalistic claims. From my own human perspective, the best I could offer without research is "that looks like a really ridiculous claim". I think a researched claim is a lot more valuable here.
oh heck here's it's response to the Venus part:
"Climate scientists and astrophysicists have looked into this extensively. The definitive scientific consensus is that a Venus scenario is physically impossible on Earth from burning fossil fuels. To trigger a runaway greenhouse effect that vaporizes the oceans (like Venus), Earth would need to receive much more solar radiation than it currently does. Even if we burned every single ounce of fossil fuel on the planet and triggered all feedback loops, the Earth would become devastatingly hot and hostile to human civilization, but it would eventually stabilize. It would not turn into Venus."
I've no reason to doubt this is absolutely true.
that's not what they're gonna do though....
> The region has “crossed the point of no return,” the paper’s authors wrote, adding New Orleans “may well be surrounded by the Gulf of Mexico before the end of this century.”
sorry, Gulf of what ? /s
I followed the advice on this site and actually got very bad news. But the good news would be, that I'm on a strict medication regimen now and maybe I'll live to see my son's graduation.
RFK is killing people. it's what he does.
thanks for listening
> In July 2025, the Administration published an Executive Order to accelerate federal permitting of data center infrastructure. On May 11th, 2026, Administrator Lee Zeldin proposed a rule to allow data center developers to engage in “pre-construction” activities before they receive their final environmental permits. The EPA claims this has “no impact to human health or the environment.”
she wants to ban this apparent practice of companies beginning excavation for their new datacenter before they even get their permits, which I entirely support.
Well your other options are Marxism or Star Trek replicators. I'd choose the latter.
why not use hooks to automatically reject issue comments / PRs etc. from users that didnt go through onboarding, rather than repurposing GH features that aren't really designed for that use (and are hence in danger of being changed someday)?
[1] https://www.newyorker.com/culture/the-new-yorker-documentary...
Never overestimate the billionaire class....
the value of the junior dev is the hopes that they'd be a senior dev someday, I dont have a solution to that problem. But in my current capacity where the only devs I'm "managing" these days are via open source contributions, they're already gone - 100% of what I get is through their own work with LLMs (which I have to spend more time correcting than if I used the LLM myself).
my post is more about how we really need to be seeking energy sources from all possible corners, and we have a government that is literally paying billions to contractors to cancel wind projects.
the "growing demand" is the AI datacenters (the linked story goes into detail). it's the direct result, so while it might feel soothing that this other story doesnt actually mention "AI" it's mostly just an omission.
(edit) the issue is that there's a sudden tight timeline and yes as other comments mention it's too bad the issue wasn't addressed sooner, but that's not very unusual when there's no major impetus to force a change. and that whether or not AI/LLM is a net good for society (I literally have Claude writing code for me as I type this), the energy issue is one that seems to be a real one (unlike the water issue which mostly seems to be not so real).
the town^H^H^H^H region (edit) is already in the process of expanding their infrastructure to get power from elsewhere so things will be "fine", but this is a terrible time to have a government that is rabidly cancelling non-fossil energy projects as fast as possible.
are we just trying to say, "use AI for prototyping and customer demos that aren't important to be mature, use senior devs to develop and maintain the real products" ? You could just say that then...? Which I also disagree with as how AI should be used, AI is valid to include as a tool across all forms of development - it just should never be put in charge for production-level software (e.g. no vibe coding of mission critical components).
Hence the Onion
When you have junior people come in with PRs and you do the whole hand-holding thing so they learn and grow and all that, they're there because my project is famous, they want to get credit (which I give them), then they're off to get jobs whereever and they are working with completely different technologies, and you never hear from them again either, because, of course, they're now busy!
Really, outside of my core group of hangers-on, Claude is the only contributor we have that doesn't leave us.
> This makes a lot of sense to me. It relates to an idea I've seen circulating elsewhere: if a PR was mostly written by an LLM, why should a project maintainer spend time reviewing and discussing that PR as opposed to firing up their own LLM to solve the same problem?
well yeah. I almost use PRs now just as a lazy means of issue prioritization. I'd love if github had more fine-grained controls to disable PRs but allow occasional contributors in (they don't).