3,081 karma · joined October 22, 2025
(That said, on the scale of blame for it being bad, I would say the GUI framework accounts for 0% of that and the programming methodology accounts for 100% of that)
It's not that difficult. If your security is bad, somebody finds and tells you. Then you have five options: (a) attempt to prosecute them, (b) thank them for their volunteer work and tell them to fuck off, (c) give them some loose pocket change for their help, (d) actually pay them a real bounty, (e) offer to hire them. ~0% pick E, ~10% pick D. The people who can help them literally come to their door with hard proof of their ability to help, voluntarily, and 90% of the industry snubs their nose at the very people who can take advantage of bad security. This problem is entirely self-inflicted.
Okay, you've added a requirement. Poll the current cursor position after the first hit-test sets the dragging state and call a function to render your object with X% opacity at a higher Z level than anything else. Your 30 minute job has become a 60 minute job.
> As is deciding whether the ghost should affirmatively snap out of and into the source and target containers (that is, whether the destination container should appear to “make room” for the ghost at some point), whether there’s a transition on that,
Most applications don't go this far, including your operating system like Windows that sets baseline UX expectations, so you're well beyond the default expectation for drag-and-drop. If someone asks you to implement drag-and-drop without specifying they want all the bells and whistles, and you respond it's going to take you a week because you're planning to go all-out beyond necessary business requirements, they'd have a valid reason to be like "WTF mate?". Also this is still pretty paltry and not a week's worth of work.
[1]https://www.sfgate.com/business/article/shanghai-to-s-f-flig...
[2]https://www.macrumors.com/2019/01/11/apple-united-airline-pu...
> If anyone can dig up an ancient library on GitHub for drag-and-drop back in those days, I'd imagine it would be several thousand lines long,
I bet, the JS devs who do write code overcompensate for the ones who can only stitch together libraries. I suppose because the expectation is that the library consumer is incapable of writing their own code extending it, so the library itself must support every possible combination of use cases for a million different users, even though the code any individual consumer actually needs is more like 100 loc.
MLK Jr. was being monitored by the FBI and CIA, who believed he was a Communist.
...just economics that benefit him. The economics of rental for consumers are horrific. It doesn't even have to be about an abstract sense of ownership and freedom, even if it's "just economics" this is still an insanely self-serving to say because he's talking about economics that benefit 00.01% at the expense of the other 99.99%.
I've seen the video where he says those words out loud, on mic.
We are literally talking about a situation where this is not happening! And the problem is that it's not just this. Once you give them a license to police e-mail, they start policing e-mail for all kinds of arbitrary and inscrutable reasons. If this were going to be done, it should really be formalized as an industry standard by an independent consortium, not up to the whims of Microsoogle.
Yes. In the first place, this should not even be a thing. Two corporations should not be in control of who can send e-mail. If they want to mark not having DMARC as spam, mark it as spam, or better yet flag it with a specific warning about the domain, but these games with refusing to deliver are just bullshit and essentially force a monopoly where other e-mail providers cannot compete because their e-mails aren't delivered.
> you're expecting to use it without steering
If I have to manually "steer" every mistake it makes on every trivial task, instead of being able to deterministically eliminate classes of failures so that fixing the task one time ensures that failure never happens again on similar future tasks, it is in fact faster to just type the fucking code myself.
> there is nothing deterministic about using llm's for codegen
And if you're okay with that, you're more like a farmer eating the slop meant for his pigs than an engineer. Using Sol Max, you can get near-deterministic output for a much wider range of tasks and specifications. Not all specifications; at a certain degree of sufficiently detailed specification it will begin failing again. But some, which is better than none.
Wrong. What I want Luna to be able to do is ~deterministically make small edits or generations of 1~10 LoC according to a specification, and it literally cannot even do that. It violates specifications no matter how small you aim.
This is the same stupid argument trotted out repeatedly in the thread, and it doesn't hold up to reality. Would you care to explain how adding specifications helps a model that demonstrably ignores specifications? A model that cannot even handle the trivial specification of "the filename must be lowercase" is not going to get better when you add more specifications it ignores. I would guess that you're actually significantly underspecifying relative to me. Perhaps you're happy with whatever slop you get and don't notice Luna's overwhelming incapability to actually provide what one requires, because you don't have requirements.
[0] https://news.ycombinator.com/item?id=50373961 [1] https://news.ycombinator.com/item?id=50374111
I am not one of those people, as I do not do cars, but I would hazard a guess that most car people over a certain age do in fact feel very strongly about what modern cars have become. The ones who grew up without knowing what ownership feels like less so, which reflects the exact same dynamic with younger generations who are growing up without ever knowing what it feels like to own the hardware they use.
LLM-generated blogpost. The stench is all over it.
I know AI bros are allergic to reading, but at least feed my reply to a clanker and get it to summarise for you before ignoring what I wrote. This lying con artist went on a media hype tour claiming, with no qualifications, that he would have "100% parity" with the entire Adobe suite in a month (this was a month ago, by the way). He then admitted here on HN that he was lying in other places to build hype and that that claimed goal of 100% parity in a month would not be accomplished[1][2]. His own clankers have revised their own made-up estimate from 82% parity down to 45%:
> These numbers replace the 2026-10-03 estimate (82% "of the way", 140–220 agent-hours to 95%, kept below for the record). That estimate counted feature surface and was far too optimistic"[3]
[1]https://news.ycombinator.com/item?id=49962334
[2]https://news.ycombinator.com/item?id=49961661
[3]https://github.com/storytold/photocraft/blob/main/docs/targe...
You people, really this entire industry, are completely bereft of a single intelligent thought, the only thing you all can do is lie, lie, lie. The multi-trillion dollar scam, the entire US economy centered around how long three of the world's most notorious liars and their army of MLM artists can keep the charade going and get rubes like you to unironically shill their scamware as though any professional in the world is using it over Photoshop.