<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: Bluestrike2</title><link>https://news.ycombinator.com/user?id=Bluestrike2</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 01 Aug 2026 13:24:59 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=Bluestrike2" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by Bluestrike2 in "IMAX vs. IMAX 70mm: The difference between these two cinema formats"]]></title><description><![CDATA[
<p>Most of that discussion is less about any advantages inherent to either aspect ratio and more about just viewing the film as the director originally intended.<p>The cinematographer would have composed shots for the main 1.43:1 aspect ratio first while taking into consideration the other aspect ratios (the viewfinder will overlay the different framelines to help make those decisions). The DP then gets to go back in during post and recompose each shot for the different formats as needed, tweaking what was originally shot to do their best to maintain a cohesive feel and emphasis across each crop. With five different formats for The Odyssey[0], I'm sure that was a fun experience.<p>It's not that one format is inherently better. The frame is a storytelling tool, and you can use different aspect ratios to influence how audiences perceive the film.[1] It's when you start changing it afterwards with little regard for the director's original intentions that we see problems. The old pan-and-scan movie releases for VHS or cheap 16:9 conversions are frustrating examples.<p>0. <a href="https://www.odysseymovie.co.uk/explore-formats/" rel="nofollow">https://www.odysseymovie.co.uk/explore-formats/</a><p>1. <a href="https://www.cined.com/aspect-ratio-as-a-storytelling-tool-a-how-to-with-film-examples/" rel="nofollow">https://www.cined.com/aspect-ratio-as-a-storytelling-tool-a-...</a></p>
]]></description><pubDate>Fri, 31 Jul 2026 16:20:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=49125132</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=49125132</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49125132</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "Mercedes-Benz commits to bringing back physical buttons"]]></title><description><![CDATA[
<p>I for one am quite happy that Mercedes is committed to a physical button for hazard lights, parking assist overrides, and the other controls that are used so very...rarely. Perhaps they'll do something about the less commonly used buttons like climate control for the next model redesigns in five to seven years.<p>I really struggle to understand what's so damned difficult about this. They've admitted touchscreens annoy the hell out of drivers and capacitive touch buttons are even worse. Is it really going to take yet another lifecycle before they actually do something about it?</p>
]]></description><pubDate>Sun, 03 May 2026 15:26:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=47997887</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=47997887</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47997887</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "New Gas-Powered Data Centers Could Emit More Greenhouse Gases Than Whole Nations"]]></title><description><![CDATA[
<p>Even if modern renewables and batteries kill the need for future nuclear power plants, that doesn't excuse the consequences of decades of burning fossil fuels because environmental groups fought against nuclear power altogether.<p>We had better options back then, and we chose not to implement them while slowing down efforts to improve them: nuclear reactor designs could have been standardized to lower cost, even safer and more effective reactor designs could have been pursued years earlier, etc.<p>The costs--and opportunity costs--of inaction during that time were massive, and we're going to be paying them for generations. Renewables have a heavier lift ahead of them as a result, with less time to build out and upgrade the grid, transition to EVs, etc. The very least we can do is acknowledge the consequences.</p>
]]></description><pubDate>Tue, 28 Apr 2026 12:36:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=47933694</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=47933694</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47933694</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "The West forgot how to make things, now it’s forgetting how to code"]]></title><description><![CDATA[
<p>Try for too much impact, and you end up browbeating the reader until they're little more than metaphorical pulp. A human writer might like using those types of sentences--or any of the obvious LLM writing tropes--in specific contexts, but they'll usually recognize the need to avoid overusing them.<p>LLMs don't, and so the tropes get repeated ad nauseam. It doesn't help that social media posts are a huge part of their training data, and there's a large body of research on how Twitter and social media in general have altered grammar and sentence construction towards patterns more commonly found in oral-based traditions as users sought out ways to make their voices heard.<p>It's easy to imagine a more polished version of a line like <i>"It's not X. It's Y!"</i> being tossed out during a speech precisely because it <i>can</i> be dramatic and punchy. When it's done in every other paragraph, however, it can become rather disconcerting.</p>
]]></description><pubDate>Mon, 27 Apr 2026 13:34:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=47921374</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=47921374</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47921374</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "Tesla concealed fatal accidents to continue testing autonomous driving"]]></title><description><![CDATA[
<p>Disregarding the fact that NHTSA findings apparently contradict it (though that may just be a more recent change than the 2022 report), Tesla claims to use five seconds before a collision event as the threshold for their data reporting on their FSD marketing page:<p>> If FSD (Supervised) was active at any point within five seconds leading up to a collision event, Tesla considers the collision to have occurred with FSD (Supervised) engaged for purposes of calculating collision rates for the Vehicle Safety Report. This approach accounts for the time required for drivers to recognize potential hazards and take manual control of the vehicle. This calculation ensures that our reported collision rates for FSD (Supervised) capture not only collisions that occur while the system is actively controlling the vehicle, but also scenarios where a driver may disengage the system or where the system aborts on its own shortly before impact.[0]<p>In theory, that should more than cover the common perception-response times of around ~1 to 1.5 seconds used as a rule of thumb for most car accidents. But I'm quite curious what research has been done on the disengagement process as driver assistance systems return control to the driver and its impact on driver response times and their overall alertness.<p>If drivers trust the car to handle braking and steering for you, are we really going to see perception–response times that low, or have we changed the behavior being measured? Instead of timing a direct response to a stimulus, we’re now including the time required to re-engage their attention (even if they're nominally "paying attention"), transition to full control of the vehicle, and then react to the stimulus that they're now barreling down on.<p>For that matter, this approach is making the implicit assumption that pressing the brake pedal or turning the steering while is a sign of now-active control and awareness. Is it? Or could it just be a sort of instinctual reaction? I've been in the passenger seat when a driver has slammed on the brakes, only to find myself moving my right foot as if to hit an imaginary brake pedal even knowing I obviously wasn't the one driving. Hell, I remember my mom doing that back when I was learning to drive during normal braking.<p>0. <a href="https://www.tesla.com/fsd/safety#:~:text=within" rel="nofollow">https://www.tesla.com/fsd/safety#:~:text=within</a> five seconds</p>
]]></description><pubDate>Mon, 20 Apr 2026 13:39:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=47834165</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=47834165</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47834165</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "uBlock filter list to hide all YouTube Shorts"]]></title><description><![CDATA[
<p>Shorts are treated as a privileged feature; they aren't going to simply hide them just because a few of us have the unmitigated gall <i>not</i> to watch them. That's not to their benefit. Youtube and the other platforms want to manipulate users into getting on that particular hamster wheel, and the app's UX reflects that. In that, it's not dissimilar to how streaming services routinely prioritize engagement maximization over user experience. If it takes you a few more clicks to find your <i>continue watching</i> list, that's your problem.<p>I'd be surprised if the algorithms have much say on when and where shorts show up in your feed versus just inserting them into specific spots in your feed that were determined by a whole lot of user testing to see what's most effective. There might be some logic to tweak it, but overall placement is probably fairly uniform across users.</p>
]]></description><pubDate>Sun, 15 Feb 2026 21:50:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=47027968</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=47027968</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47027968</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "It's hard to justify Tahoe icons"]]></title><description><![CDATA[
<p>If it's a strategic play, it's a terrible one that douses usability in gasoline and sacrifices it at the altar of visual novelty for no real gain. Apple has spent literal decades working on and refining their Human Interface Guidelines for different devices. Between Tahoe and Liquid Glass, they seem to have just tossed them on the bonfire for no justifiable reason.<p>VisionPro was meant to literally overlay its interface over your field of vision. That's a <i>very</i> different context and interaction paradigm. Trying to shoehorn the adaptations they made for it into their other, far more popular interfaces for the sake of consistency? It's absurd.</p>
]]></description><pubDate>Mon, 05 Jan 2026 22:45:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=46506189</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=46506189</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46506189</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "The AI wildfire is coming. it's going to be painful and healthy"]]></title><description><![CDATA[
<p>Fair enough. I fully recognize just how easily it gets abused, and "used with purpose" is doing a lot of heavy lifting in my original comment. That said, if someone's going to engage in sentence sprawl, I'd much rather an em dash get abused in the process than some of the alternatives. Bad em dashes are at least less ambiguous than a chain of a commas mashing meaning into mush, and they provide an obvious visual break that jumps out at the reader.<p>Em dashes are strong; they can take the abuse. While I'm right there with you on dreaming of a renaissance in quality writing, that's likely more fantastical than my own hopes that we'd see a resurgence in quality em dash usage. At this point, I'd probably settle for outright stagnation in writing ability.</p>
]]></description><pubDate>Tue, 09 Dec 2025 14:18:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=46205150</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=46205150</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46205150</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "The AI wildfire is coming. it's going to be painful and healthy"]]></title><description><![CDATA[
<p>> it's not X (emdash) it's Y<p>No, no, no! Stop that! The em dash is an wonderful little punctuation mark that's damned useful when used with purpose. You can't turn it into some <i>scarlet glyph</i> just because normal people finally noticed they exist. LLMs use them because <i>we</i> used them, damn it.<p>For god's sake, are we supposed to go back to the dark ages of the double hyphen like typographic barbarians in the hopes that a future update won't ruin that, too? After all the work to get text editors to automatically substitute them in the first place?<p>What's funny is that, when people first started noticing that LLMs tended to like the em dash, I'd mentioned to a friend that I hoped—rather naively—it might lead to a resurgence and people would think to themselves "huh, that looks pretty useful." Needless to say, I got that one wrong. Are we really going to sacrifice the poor em dash just because people can't come up with a better signifier for LLM text?</p>
]]></description><pubDate>Sun, 07 Dec 2025 23:16:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=46186384</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=46186384</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46186384</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "Palisades Fire suspect's ChatGPT history to be used as evidence"]]></title><description><![CDATA[
<p>> If you dont believe even his mother, theres tons of other evidence. The anti fascism messaging on his bullets. The text messages to his partner saying a Kirk was full of hate.<p>Sigh. That's not what I claimed. I can accept his mother's limited statement from the charging document at face value, and still point out that we still know very little about his ideological leanings. <i>Why</i> did she consider him moving left? Was it just because of gay rights? Did his other views shift as well? Was the shooter's motivation more about the political side of things, or some misplaced idea that they were somehow protecting or helping their partner?<p>I have no clue, but I want answers to these questions if only because they can contribute to the effort of better understanding radicalization pathways and the process by which some random kid decided to commit an act of political violence.<p>We know that shooters rarely have cohesive, logical ideologies. The fact that a shooter decides to become a shooter in the first place is evidence that their personal ideology has shifted in some truly extreme ways that puts them--or should put them--outside the normal political discourse. Put another way, radicalization can take people to some truly unexpected places and it's entirely reasonable to want a nuanced view before jumping to affix labels because while labels can help us understand some things, they can also obscure other aspects and create entirely separate problems. Especially when those labels then get for partisan purposes and to undermine the political discourse.<p>As for the casings? We've got memes and video game references.[0] The most overtly political parts are "hey fascist, CATCH" with a video game code thrown in for good measure and an 19th century folksong that later became an anti-Mussolini resistance anthem. The others are memes. Do they all have meaning for the shooter? Obviously, since he went through the effort to engrave the casings. At the same time, their immaturity and oddness should be pointed out as well, as they undermine the idea that this was some sort of rational consequence of a cohesive political ideology.<p>> Straight cope and Im pretty sure I dont need to say why.<p>Perhaps you should re-read the sentence before trying to read something into it that wasn't present? My point was simple: even setting aside the ethical aspects of the question (simple answer: outside of baby Hitler hypotheticals, it's bad--and even with Baby Hitler, most people will acknowledge they're trying to leverage his future actions to make literal baby murder pencil out because they recognize that baby murder is a prima facie immoral act), political assassination is an <i>insanely</i> stupid means to shift public opinion and pretty much any politician, activist, or advisor--whether on the right or left--will tell you the same thing.  Feel free to substitute <i>right-leaning</i> for <i>left-leaning</i> in my original comment if "left-leaning" made the sentence read as something I hadn't intended. I certainly didn't intend to suggest that somehow only left-leaning folks are capable of recognizing that political assassination is a very bad idea with <i>tons</i> of unintended consequences. Anyone with even a basic grasp on history is more than capable of knowing how dumb it is.<p>Hell, we've got literal case studies showing how political assassinations tend to blow up in everyone's face. The CIA has a list of coups and political assassinations that pretty much all resulted in serious blowback that undermined their intended outcomes--and often resulted in the very thing they wanted to prevent.<p>So, yeah, I think that if the shooter shopped the idea that murdering Charlie Kirk would somehow magically make things better for gay or trans people to gay and trans advocacy groups--or influential figures on the left more broadly--they'd almost unanimously tell him he's a moron and notify the FBI even if they thought Kirk was a pox on American political discourse. It's an insane proposition, and only in the mind of someone who has serious problems would it somehow make sense.<p>I also think that the reverse situation--where the shooter wanted to benefit some conservative constituency or ideology by murdering a liberal political activist and shopped the idea around conservative politicians and activists--would likely result in the same call to the FBI.<p>0. <a href="https://www.cbc.ca/news/world/charlie-kirk-tyler-robinson-bullet-casings-messages-1.7632442" rel="nofollow">https://www.cbc.ca/news/world/charlie-kirk-tyler-robinson-bu...</a></p>
]]></description><pubDate>Wed, 15 Oct 2025 13:48:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=45592521</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=45592521</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45592521</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "Palisades Fire suspect's ChatGPT history to be used as evidence"]]></title><description><![CDATA[
<p>These questions are almost always more complex and nuanced than simply <i>left</i> or <i>right</i>.  I agree with you on the second part to a degree—insomuch as the modern media landscape pushes people to quickly label shooters and tends to disincentivize any sort of nuance—but might you be doing the same here?<p>The charging document[0] said that his mother claimed "that over the last year or so, Robinson had become more political and had started to lean more to the left – becoming more pro-gay and trans-rights oriented." There's also a text message he sent, which said "since trump got into office [my dad] has been pretty diehard maga." That's it. Acquaintances said "he wasn't too fond of Trump or Charlie [Kirk]," but we still haven't seen much that explains the specifics of <i>why</i> beyond the gay and trans rights angle. A former high school classmate said  "[w]hen I knew him and his family, they were like diehard Trump" and that he was politically conservative and supported Trump "ahead of the 2020 election."[1]<p>As for what changed and why, we don't know. Did he stop supporting Trump because of gay and trans rights? Did he still believe in other conservative ideas? Simply labeling him as a <i>leftist</i> implies a cohesive ideology, but ideology is rarely so simple or straightforward even for normal people who don't decide to commit political assassinations.<p>Beyond that, a lot of even ideologically-motivated shooters have some awfully peculiar and non-cohesive ideologies. If the suspect agrees with 80% of a particular tribe's most common views, but that last 20% consists of some truly batshit ideas that have very little if any support, are they still a member of that tribe? Would that tribe even want them? Would they themselves want to be part of that tribe? Plenty of conservatives who believed fully in the movement's ideas broke with Trump in 2016 solely on the basis of his personal character.<p>They can also grab onto ideas from other tribes, to the point where investigators wind up crawling through something that's less a cohesive political ideology and more a smorgasbord of ideas they pinned together. I mean, hell, you've got to have a screw or two loose to think a political assassination is going to somehow lessen--let alone stop--anti-gay and/or anti-trans sentiment. Run that idea past pretty much any left-leaning politician, activist, or political junkie, and they'll tell you you're a moron, likely right before giving the FBI a call.<p>0. <a href="https://static.foxnews.com/foxnews.com/content/uploads/2025/09/tyler-robinson-charging-document-assassination-charlie-kirk.pdf" rel="nofollow">https://static.foxnews.com/foxnews.com/content/uploads/2025/...</a><p>1. <a href="https://www.cnn.com/2025/09/12/us/tyler-robinson-charlie-kirk-shooting-suspect-invs" rel="nofollow">https://www.cnn.com/2025/09/12/us/tyler-robinson-charlie-kir...</a></p>
]]></description><pubDate>Tue, 14 Oct 2025 13:26:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=45579768</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=45579768</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45579768</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "I made a chair"]]></title><description><![CDATA[
<p>The problem with using modern pressure treated wood for outdoor furniture is less any cancer risks like with the old CCA treatments, and more that it's just a bad choice for a bunch of different reasons.<p>Modern copper-based treatments--e.g. ACQ or CA--still cause skin and eye irritation. If you try to sand it so that people sitting in your new chair don't get a nasty splinter somewhere best avoided, you can compromise the effectiveness of the treatment (even when the treatment gets full penetration, it's still most effective on the outer layers you're now sanding away). Plus, while the dust you create when working with it might not include arsenic, it's still nasty to breathe in and can cause respiratory problems. Staining P/T wood can be a whole ordeal in itself, and because interact much more closely with furniture than say a deck, any imperfections will be more noticeable.<p>Even then, it's not like P/T furniture isn't going to require ongoing maintenance in the future. At which point, you're better off with something like cedar or white oak. Hell, with a decent outdoor grade finish and proper care, even untreated pine is going to last for years without rotting away underneath you.</p>
]]></description><pubDate>Mon, 02 Jun 2025 12:11:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=44157991</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=44157991</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44157991</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "Trump announces 100% tariffs on movies ‘produced in foreign lands’"]]></title><description><![CDATA[
<p>I realize it's just another hair-brained scheme likely cooked up on the porcelain throne, but part of me is curious about how exactly they'd implement this train wreck.<p>Since Trump is relying on declarations of national emergencies for his tariffs, there's the question whether it's even <i>legal</i> given that Berman Amendments to the IEEPA[0] explicitly exempt "informational materials, including but not limited to, publications, *films*, posters, phonograph records, photographs, microfilms, microfiche, tapes, compact disks, CD ROMs, artworks, and news wire feeds" from the President's authority under IEEPA.[1]<p>Even if we set that aside and ignore the likely legal challenges, how would you actually implement them? It's not like a movie or TV episode "produced" overseas gets transmitted into the US each time somebody wants to watch it. It's a digital file, and you're really only sending it once. So when do you tariff the damn thing, how do you manage to actually do it since there's not exactly a literal port of entry for the internet, and what exactly do you value it at? The system isn't built to track and tariff info being uploaded to random servers, and making it work would require all sorts of new law.<p>Plus, what's the legal definition of "production" he wants to use? What constitutes <i>foreign</i> production? Can some of the <i>producing</i> just be done remotely? What if raw footage is uploaded instead and then it's edited here? Or a nearly finished copy that just needs something minor done to be considered ready? Hollywood accountants are in a league of their own. Put them in a room with lawyers and accountants whose focus is the creative eccentricities of tariff engineering--hello, chicken tax people[0]--and I shudder to imagine what they'd get up to.<p>We're only a few months in at this point, and I feel like I'm losing my mind.<p>0. <a href="https://en.wikipedia.org/wiki/International_Emergency_Economic_Powers_Act#Curtailment_of_emergency_executive_powers" rel="nofollow">https://en.wikipedia.org/wiki/International_Emergency_Econom...</a><p>1. <a href="https://www.congress.gov/bill/103rd-congress/house-bill/2333/text" rel="nofollow">https://www.congress.gov/bill/103rd-congress/house-bill/2333...</a><p>2. <a href="https://en.wikipedia.org/wiki/Chicken_tax" rel="nofollow">https://en.wikipedia.org/wiki/Chicken_tax</a></p>
]]></description><pubDate>Mon, 05 May 2025 12:51:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=43894559</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=43894559</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43894559</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "Judge rules Apple executive lied under oath, makes criminal contempt referral"]]></title><description><![CDATA[
<p>Ah, sorry about that. Any lack of clarity is on me; I had walked away for a bit before responding and ended up flattening the branch in my head by the time I started typing. You're fine :).</p>
]]></description><pubDate>Fri, 02 May 2025 12:40:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=43868978</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=43868978</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43868978</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "Judge rules Apple executive lied under oath, makes criminal contempt referral"]]></title><description><![CDATA[
<p>I think the issue is less the cost to developers and more the cost to users. Were there more users, no doubt a larger number of indie developers would be able to justify the expense. Without those users--or at least a reliable <i>promise</i> of those users in the near future--it's tough to justify even dipping your toes into it. It's a chicken and egg problem that's fundamentally tied to cost as well as hardware limitations. Discomfort from the bulk and weight was my biggest sticking point even before the price, for example.<p>Plus, the hardware is just the initial starting point. Your initial outlay will quickly be eclipsed by the dev hours spent working on Vision versions of your app(s), and that's when the opportunity costs become particularly noticeable. Time spent on a Vision app that may have no real market for years is time you could be spending adding features, testing changes, fixing bugs, marketing, etc. Skipping on Vision Pro is really a no-brainer for most indie developers, at least for the foreseeable future.</p>
]]></description><pubDate>Thu, 01 May 2025 16:22:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=43859833</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=43859833</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43859833</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "Adobe deletes Bluesky posts after backlash"]]></title><description><![CDATA[
<p>> I might be sympathetic to this reasoning if this was a $2 coffee or something, but $60/month is nothing to be sneezed at, and I'd expect buyers to read the very legible text under the price tag.<p>In some things, expectations are made to be disappointed. This is one of those.<p>We know that people use all sorts of cognitive shortcuts to make processing their environments easier. It doesn't matter if you're smart, dumb, foolish, or perfectly average. It's just how our brains have evolved to function, and companies have been consulting with industrial and organizational psychologists for decades to help them optimize their marketing and business strategies to maximize the chances that those shortcuts play out in a way that breaks in their favor. Before I/O psychologists, companies tried to do the same by guess and trial and error...and they stumbled upon lots of strategies that were later confirmed by psychological experiments.<p>Cereal boxes marketed to children have cartoon characters whose eyes are drawn looking down so as to appear as if they're making eye contact with kids walking down the cereal aisle.[0] There are all sorts of "tricks" commonly used by salespeople selling things to sophisticated buyers who are capable of recognize them for what they are. Why did pharma reps take doctors to dinner and give them cheap pens and swag? Or consider the success of psychological pricing[1] and how those strategies somehow manage to be successful despite it being commonly accepted wisdom that odd prices (i.e. $1.99 instead of $2) is a marketing gimmick. We know it's a gimmick, and yet, it still has an impact on our buying behavior.<p>Yes, the text is there below it, but the whole point of a dark pattern is to manipulate a large enough percentage of buyers/users in a way that generates more revenue than is lost due to any frustration or annoyance created by the same patterns. Most people skim through websites, pluck out key words, and continue on. We can bemoan people for not reading the fine print, but that's not going to change the behavior.<p>As for the beef metaphor, per unit pricing <i>can</i> absolutely be used to trip up would-be buyers into buying a bit more than they planned. Not because the foolish shoppers don't know any better, but because mixed units usually require a bit more cognitive engagement. Grocery stores absolutely recognize that and benefit from it. On the other hand, you can't really sell beef in a way other than by weight, so it's the opportunity for abuse is much more limited.<p>> Okay but if you read most complaints, it's clear that they're not even aware that such early termination fee even existed. There's approximately zero people who were aware the termination fee existed, found it too hard to figure out what it actually was, but somehow still went with the "Annual, billed monthly" option.<p>Sure, because Adobe purposely hides information about the fee. That's one of the dark pattern at play. In the absence of that information, users will insert their own expectations to create meaning. If there's a fee, we'd expect it's probably a reasonable one (even if we have <i>countless</i> examples in our lives of how fees can be anything but reasonable). Does half the annual cost of a subscription seem reasonable to most people? Would that be most people's first guess? Probably not. I might not have been clear about this in my original comment, but there are multiple dark patterns at work here.<p>> This feels like grasping at straws. If we're going to invoke "people might get two numbers confused with each other",[...]<p>That particular dark pattern is less about people confusing two different numbers with each other when they're directly in front of them, so much as it is about giving you two different numbers to remember two weeks after you've made your decision and gone on with your life. Literally nobody on the planet is going to keep the free trial or cancellation period as a mental priority over the course of two weeks, so it becomes little more than a random thought at the back of your mind. At best, you might jot it down or set aside the receipt until closer to the deadline. The pattern's purpose is that, if you think of the cancellation/trial periods at all, the numbers will be easily conflated. Think about the times in your life when you've asked yourself something like <i>did I see/do/hear [insert thing] last Monday or was it Tuesday?</i> and weren't quite confident in your answer.<p>Dark patterns doesn't have to trip up all subscribers or even most of them. But if it trips up a some of them, well, Adobe isn't going to complain about the opportunity. Multiple, more subtle dark patterns together can work just as effectively as one particularly vicious one. They can even be preferable, in that they won't piss off your customers nearly as much, either on their own or as a whole.<p>0. <a href="https://news.cornell.edu/stories/2014/04/food-psychologists-eyeball-cereal-characters" rel="nofollow">https://news.cornell.edu/stories/2014/04/food-psychologists-...</a><p>1. <a href="https://en.wikipedia.org/wiki/Psychological_pricing" rel="nofollow">https://en.wikipedia.org/wiki/Psychological_pricing</a></p>
]]></description><pubDate>Sun, 13 Apr 2025 03:54:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=43669963</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=43669963</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43669963</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "Adobe deletes Bluesky posts after backlash"]]></title><description><![CDATA[
<p><i>This is a bit longer than I would have wanted to spend writing about Adobe billing practices, but oh well.</i><p>Is it the most manipulative dark pattern in e-commerce? Hardly--there are plenty far more vicious--but it's still an attempt to prime a would-be subscriber to focus on the <i>annual, billed monthly</i> and play on their understanding of the word "monthly" by using it in both options.<p>"Annual, billed monthly" is set in smaller italicized type right under the actual price of <i>US$59.99/mo</i> on the main pricing page[0]. You've now been primed to focus on the $59.99 price. Only when you select a plan and a modal pops up do you see that there's a separate <i>monthly</i> option available from the <i>annual, billed monthly</i> option that's been helpfully pre-selected or a third <i>annual, prepaid</i> option.<p>The point is to quickly shepherd subscribers through the payment process. The user sees the $59.99 option they expected is pre-selected, so most hit continue and move on. If they look beyond the price in bold to the plan descriptions in smaller italics, well, there are literally decades of eye tracking studies showing users skim websites rather than carefully reading every single word. The price in bold draws in the eye, the word "monthly" <i>is</i> present so the user catches the word, and then they move on to the continue button.<p>Adobe could have easily labeled the plan <i>Annual, billed in 12 installments</i> or even <i>Annual, billed in monthly installments</i> to better differentiate the two options. They didn't for a reason. The word "monthly" comes with certain expectations. Using it for both the actual monthly plan and the default <i>annual, billed monthly</i> plan allows those expectations to bleed over to both.<p>While it mentions a fee for cancelling after 14 days, you'll find nary a mention of <i>what</i> that fee actually is until you track down a legal page[1] that isn't linked to any point during the payment process up until the sign-in prompt (I didn't bother creating a new account to look beyond that). At the very least, it's not present during the stage when you're still relatively uncommitted and somewhat more likely to notice any more onerous terms were they present.<p>Finally, there's an option for a 30-day free trial of Adobe Stock. I'd have sworn it was pre-selected a few years ago, but I may be mistaken on that. If it was, then at least that's a change for the better. Anyhow, did you notice how it's on a 30 day trial period whereas the normal plan has a 14 day cancellation window? Let those deadlines fall to the back of your mind for a week or two, and will you remember which is 14 days and which is 30? There was no reason why Adobe had to use 30 days for Stock or only 14 days for their other offerings. But it adds to the confusion, and that's the entire purpose of a dark pattern. Stock is also an "annual, billed monthly plan," but nowhere in the checkout process is it mentioned that Stock also has a large cancellation fee. That's hidden in a separate part of the Subscription Terms page.[1]<p>Adobe could easily just choose to settle for a straight-up monthly payment plan with no bullshit and completely sidestep recurring--but largely toothless, given the state of most alternatives to their software--criticism over their billing practices. They could eliminate the dark patterns and make their plan selection and payment process more transparent. They don't, presumably because those patterns generate more revenue than the lost goodwill they create is worth. That goodwill is diffused, and even if people grumble about it online, it generally doesn't rise to the level of leaving.<p>0. <a href="https://www.adobe.com/creativecloud/plans.html" rel="nofollow">https://www.adobe.com/creativecloud/plans.html</a><p>1. <a href="https://www.adobe.com/legal/subscription-terms.html" rel="nofollow">https://www.adobe.com/legal/subscription-terms.html</a></p>
]]></description><pubDate>Sat, 12 Apr 2025 14:41:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=43664788</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=43664788</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43664788</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "The Cult of the American Lawn"]]></title><description><![CDATA[
<p>A bit of common sense and understanding would go a long way to eliminating half the complaints you hear about HOAs.<p>If you know the tree is going to immediately start dying, you're just going to find the cheapest, least healthy sapling at the nursery.  Had they let you wait until the tree is more likely to survive, there's a better chance you'd be willing to spend a bit more to buy an older/larger sapling that'll look better and provide more shade from the start. Plus, the temporary tree slowly dying would probably be less visually appealing than an empty spot for a few months.<p>There are reasons why we plant street trees: improved aesthetics, increased home value, shade along the street and sidewalks, traffic calming effects, etc. By ignoring the reason behind them and just focusing on checking the box, your HOA was just begging for some malicious compliance that undermined the benefits of the replacement tree.</p>
]]></description><pubDate>Sat, 22 Mar 2025 15:23:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=43446389</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=43446389</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43446389</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "US Ends Support For Ukrainian F-16s"]]></title><description><![CDATA[
<p>I'd expect the original agreements that were put in place--both the ones with the subcontractors as well as the purchase agreements--are quite strict on what you can do with the plane. Trying to reverse engineer software (the policy was that no one gets access to the original source code for the F-35[0], at least back in 2009) is probably a no-go under those agreements.<p>The original article suggests that Ukraine may end up having to replace the electronic countermeasures hardware to get around this in the future, so I'd expect any attempts to "un-brick"/work around the lack of support will eventually be along those lines, even if it results in some performance degradation.<p>No matter how they approach this, it's going to be a horrifically difficult and expensive task.<p>0. <a href="https://www.reuters.com/article/world/exclusive-us-to-withhold-f-35-fighter-software-codes-idUSTRE5AN4JX/" rel="nofollow">https://www.reuters.com/article/world/exclusive-us-to-withho...</a></p>
]]></description><pubDate>Sun, 09 Mar 2025 14:54:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=43309536</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=43309536</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43309536</guid></item><item><title><![CDATA[New comment by Bluestrike2 in "NASA Shuts Off Voyager Science Instrument"]]></title><description><![CDATA[
<p>It's not really accurate to say that we <i>can't</i> go back to the moon. Setting aside the fact that there have been a number of successful unmanned lunar missions in recent years, whenever your point gets made, it usually glosses over <i>why</i> people make that claim.<p>The immediate answer is that we simply weren't interested in supporting major new manned missions. Manned spaceflight in general requires serious, ongoing political support across administrations. At the height of the space race, public support pretty much never rose above 50 percent in the United States.[1] The literal high mark  was 53% immediately after Apollo 11 successfully landed on the moon, which is honestly mind-boggling to think about. We've completely white-washed the existence of serious political opposition[1] to the Apollo program that plagued it from the beginning to the end because--looking back--it seems almost absurd, as if the very idea that half the country had no interest in going to the moon is an insult to the American psyche.<p>It's honestly amazing that we managed to follow up with the Space Shuttle at all. The STS program was shaped by a great many compromises NASA had to make in order to elicit political 
and military support. John Logsdon's <i>After Apollo</i> is a wonderful read on the subject.<p>Anyhow, it's not like we <i>can't</i> go back. It's not like orbital mechanics changed on us at some point and now we're all stuck in LEO. It's just a political choice, and we can make a new one whenever we want. It's just hard, in large part because we don't have the cold war and constant fear of imminent nuclear war to push the program through congress.<p>Beyond the political, to go back means redesigning everything that was done for Apollo. That's not a slight on American engineering or manufacturing capabilities. Everything--from the Saturn V, to the lunar module, and the countless pieces of equipment that helped get both where they needed to go--was designed for the manufacturing capabilities and techniques of the 1960s. You can't just grab the plans for the old Rocketdyne F-1 and start building them anew. The welds alone[2] represent a fundamental shift in capabilities and thinking. Common CAD design and analysis programs would have had Apollo engineers singing in the hallways in joy once they got over the shock.<p>They took what they had, and they made it work brilliantly. Change that context, and <i>they</i> would have designed a different engine, and the same goes for everything else.<p>0. <a href="https://www.space.com/10601-apollo-moon-program-public-support-myth.html" rel="nofollow">https://www.space.com/10601-apollo-moon-program-public-suppo...</a><p>1. <a href="https://www.theatlantic.com/technology/archive/2012/09/moondoggle-the-forgotten-opposition-to-the-apollo-program/262254/" rel="nofollow">https://www.theatlantic.com/technology/archive/2012/09/moond...</a><p>2. <a href="https://arstechnica.com/science/2013/04/how-nasa-brought-the-monstrous-f-1-moon-rocket-back-to-life/" rel="nofollow">https://arstechnica.com/science/2013/04/how-nasa-brought-the...</a></p>
]]></description><pubDate>Fri, 07 Mar 2025 00:25:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=43286436</link><dc:creator>Bluestrike2</dc:creator><comments>https://news.ycombinator.com/item?id=43286436</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43286436</guid></item></channel></rss>