<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: spacedcowboy</title><link>https://news.ycombinator.com/user?id=spacedcowboy</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 20 Nov 2026 09:26:41 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=spacedcowboy" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by spacedcowboy in "AI might be the end of our careers"]]></title><description><![CDATA[
<p>I think you could title that article "The Luddite Manifesto".<p>The Luddites weren't wrong, of course; technology ate their lunch, and I do expect AI to eat software-development's lunch as well, because AI de-skills the job as it stands. I don't think that that's necessarily a terrible thing though...<p>There are two ways this could develop - I'm discounting the non-use of AI, there's too much money and momentum behind it now to matter what people think, unless governments get involved and literally make AI illegal.<p>1) The demand for software engineering takes a nose-dive, because you only need a few "architect" (or "project manager" as things develop) types to oversee the AI results. Specs are currently important in swdev, but they become ever-more critical and software engineering as a subject in its own right bifurcates into academic pursuit, and practical AI management.<p>2) The business need grows along with the capability. My money is on this one. I don't think it'll grow as rapidly as AI destroys the sphere, at first, but once the requirement to conform to whatever formats and capabilities are provided by software companies is removed, bespoke software will rise and people and companies will have applications customised directly to their needs, not running through some generic system that gives an 80-90% coverage of everyone. There will still be a lot of demand, but the skillset will be different, note though that <i>knowledge</i> will still be important, even one level removed from the engineering cliff-face. A lot of what makes GenAI useful is built into the model, but limitations are too - like the inability to use and act upon a null hypothesis - once set on a path, the GenAI will continue down that path, akin to ancient astronomers constantly adding epicycles to their reasoning ... and recognising <i>when</i> to abandon the path, which takes exactly that knowledge, is exactly the skill that remains human.<p>Note that (2) still implies a reduction in swdev as both a desirable (and hence well-paid) career and in the quantity, it's just nowhere near as devastating as (1). It also has a possible path to grow into something new that we haven't really seen yet, in the sparse-solution space that swdev has existed in to date.<p>I agree with him that AI doesn't need to reach AGI to do this damage. My optimism, though, rests on my view that current GenAI and AGI are not on converging paths. If I'm wrong about that and true AGI is on the cards, then it's simply over, swdev had a good run and it's no longer necessary.  GenAI, unlike AGI, does <i>not</i> provide the introspection and information-extraction from sparse samples that humans do. It runs, fundamentally, through an ever-feed-forward network, without the inherent and internal ability to continually learn, and react to that learning. Stuart Kauffman would say its weights were stuck in the frozen realm of order, and that it takes a state-change to get to where the real action is - at the boundary of chaos and order.<p>GenAI has made some attempts to help this - the context is read/write and can store, well, context, but even J-space (a shared "workspace" for deliberate, multi-step reasoning) is ephemeral; it doesn't inform the weights in the base model, and when we try to do weight-space programming, the model needed is far and away larger than the one being operated on, and once a change has been made the operator model is now out of sync with its original representation. We have not solved "learning", we just have a high-probability path between states in weight-space which we follow and feed back.<p>It's been 30-odd years since I was playing with neural networks on a Meiko computing surface at college. Back then I used to think that intelligence was an emergent property of scale, but it turns out that recurrence and complexity play their parts too, and we've only really solved one of those three.<p>Bubbles pop, but the technology doesn't disappear. The old .com bubble and subsequent crash were net positives in the long-run, creating and funding the internet we use (and "love") today. I was around when the web was born, when you had to send an email to CERN to be put on the list of websites available in this world. Things have changed. Dramatically. Sometimes even for the better :)<p>So, yes, the Luddites were correct, and so is Baldur, but all is not lost, and in fact we may be on the cusp of something far greater than anything we've seen before. The key human trait that has let us get to where we are is that we're adaptable. Well, now is the time to adapt - standing in the way of a juggernaut is a good way to get crushed, as those weavers found to their cost.</p>
]]></description><pubDate>Wed, 18 Nov 2026 14:38:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=50546848</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50546848</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50546848</guid></item><item><title><![CDATA[New comment by spacedcowboy in "All AI-generated code should be Open Source"]]></title><description><![CDATA[
<p>I see you asserting that, I don't see him saying it...</p>
]]></description><pubDate>Sun, 15 Nov 2026 15:38:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=50507730</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50507730</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50507730</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Court denies motion to dismiss DRAM price fixing case"]]></title><description><![CDATA[
<p>It might (I say might) be worth your looking at xc [1] as a way to get more performance out of local/LAN hardware - assuming your program is data-parallel anyway.<p>1: <a href="https://github.com/ThrudTheBarbarian/xc" rel="nofollow">https://github.com/ThrudTheBarbarian/xc</a></p>
]]></description><pubDate>Sun, 15 Nov 2026 13:34:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=50506823</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50506823</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50506823</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Xc: Compile the same source for GPUs and CPUs"]]></title><description><![CDATA[
<p>I'm writing a language called xc and its compiler, xcc for the last 6 months or so (full disclosure: with a lot of help from Claude). I've finally got version 1 (actually v1.0.1) out, for Linux (x86-64 and arm64, including the Pi 5), macOS and Windows.<p>The idea: you write an ordinary loop, the compiler works out whether it can run in parallel, and it emits both a multi-core CPU version and GPU kernels (MSL, PTX, SPIR-V or WGSL, all generated by xcc itself without needing an SDK installed).<p>At run time the program measures each block on that machine and keeps the faster placement.<p>Examples:<p>- On an M3 Max a Mandelbrot block takes 13.7 ms on all 16 cores and 1.3 ms on the GPU<p>- On a Ryzen 9955HX's 2-CU integrated Radeon the GPU loses to the 32 CPU threads, so it stays on the CPU.<p>The compiler also reads plain old C via clang's front end and does the same thing to C loops, with no pragmas. Comparing xcc to OpenMP for both gcc and clang (with the helping hand of "#pragma omp parallel for" gives (times in ms):<p><pre><code>                 xcc    gcc+omp  clang+omp
  mandel_deep    371    2170     2231
  mandelbrot     2.45   12.2     12.8
  md5            9.39   16.1     13.4
  md5_mask       8.17   12.1     13.4
  nbody          0.45   1.29     9.92
  perlin         5.87   4.38     7.05
  saxpy          2.26   2.18     2.32
</code></pre>
Geometric mean: xcc is 2.1x faster than GCC+OpenMP and 3.0x faster than clang+OpenMP.<p>All the builds are checked to make sure they give the same result - no point having a benchmark that doesn't produce the same result! xcc has a notable win for nbody, because its vectorisation is better (across bodies) but perlin has been a bit of a bugbear throughout the leading-up-to-v1 timespan.<p>Platform-specific binary tarballs, the sources, OpenMP versions and method are on the site (linked from github), and there are Phoronix Test Suite profiles if you'd like to run them yourself.<p>It's only just made v1 so there's a few rough edges: C++ through clang is in-progress (but not official yet), and the Pi 5's GPU is slow. Not sure if that's the Pi or the code yet...<p>There's more to the language but I don't want this to be an essay! The real, honest-to-$deity cool thing is the <i>automatic</i> parallelising of standard C/xc loops and being able to run that code on the GPU with <i>no boilerplate</i> - "ARC for Algorithms" (what Objective-C's ARC did for memory management), it "just works".<p>Very keen to get feedback and fix any gaps. I think it's generally useful right now, but it is "v1" - Bug reports welcome as GitHub issues...</p>
]]></description><pubDate>Fri, 13 Nov 2026 17:53:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=50487156</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50487156</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50487156</guid></item><item><title><![CDATA[Show HN: "xc", Compile the same source for GPUs and CPUs]]></title><description><![CDATA[
<p>Article URL: <a href="https://github.com/ThrudTheBarbarian/xc">https://github.com/ThrudTheBarbarian/xc</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=50487155">https://news.ycombinator.com/item?id=50487155</a></p>
<p>Points: 2</p>
<p># Comments: 1</p>
]]></description><pubDate>Fri, 13 Nov 2026 17:53:42 +0000</pubDate><link>https://github.com/ThrudTheBarbarian/xc</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50487155</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50487155</guid></item><item><title><![CDATA[New comment by spacedcowboy in "AMD EPYC 9006 Results Are Here and AMD Delivers a Knockout Part Deux"]]></title><description><![CDATA[
<p>Jeez, I wish I could get AMD to give me one of these to try out xc [1] on it with some RX9070XTs installed - those benchmarks would be a thing of beauty :) The problem with high-end hardware is that (especially these days with the RAM prices) it's just so damn expensive.<p>1: <a href="https://news.ycombinator.com/item?id=50151160">https://news.ycombinator.com/item?id=50151160</a></p>
]]></description><pubDate>Wed, 11 Nov 2026 11:45:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=50452268</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50452268</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50452268</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Fossil CO2 emissions decrease by 0.4% in 2026"]]></title><description><![CDATA[
<p>oh it’s far from perfect. it’s better, though</p>
]]></description><pubDate>Tue, 10 Nov 2026 14:23:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=50440817</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50440817</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50440817</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Fossil CO2 emissions decrease in 2026"]]></title><description><![CDATA[
<p>Given how the much-vaunted "checks and balances" seem to be, well, rather unbalanced ... and how the country is so, <i>so</i>, partisan over "their own side" that politics is mainly theatre... It seems like the US doesn't really need any italics in that statement. From an outside perspective, it seems fairly vulnerable to fascism actually.<p>In any event, over here in the UK there's a real wind-power push (with the surrounding water being so shallow that off-shore wind-farms are very possible), but even in these extended latitudes, solar power is viable and the government currently make them VAT-free for installs, with no planning requirements because they fall under 'permitted development'. Renewable energy was at ~56% Q2 2026.<p>The UK government set up 'Great British Energy' with £8.3B of funding for coinvestment with private firms in various clean energy generation. I think the UK is definitely doing its part.</p>
]]></description><pubDate>Tue, 10 Nov 2026 11:52:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=50439018</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50439018</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50439018</guid></item><item><title><![CDATA[New comment by spacedcowboy in "70% of Brits say please or thank you when speaking to AI, some even apologize"]]></title><description><![CDATA[
<p>As a Brit, there are two reasons to do this<p>1) it’s just … the right way to behave. Politeness costs nothing (or at least a tiny fraction of your token budget). The machine is worthy of respect for what it does for me.<p>2) it’s a huge advantage to tuning the context into something that works well for you, if you have a long-running task.<p>Let me explain that last one. I’ve been running an experiment where I follow the perceived wisdom and start contexts afresh for each new issue, and in parallel I have a single context I’ve been running for about 2.5 months now, in use pretty-much 24 hours per day.<p>The former are targeted goals, “reformat the docs to highlight xxx”, that sort of small task. It works reasonably well for that. It still sometimes asks me for direction “do it this way or that way ?”, not a problem I’m there to decide.<p>The latter is a far more impressive system. “Tonight, please burn down the issues on GitHub”. That needs a lot more independence and fearlessness when making decisions. I don’t want to go to bed and find it needed my input 20 minutes after I retired for the evening…<p>Now a long-running context has its own issues, it (of course) will compress itself periodically, and you might lose things, so at the start, you find yourself repeating directives, but the machine stores those in memories, and those memories have seem to have some level of precedence over “normal” context because slowly, over time, it starts to adapt its behaviour.<p>At the start, I would frequently have to type something like “ok, please set a timer for 60 secs (or ETA-based if you have a good estimate), set to arm at the beginning of each turn, looping to solve the task <insert task here>, and only stop doing this when the loop-condition is met, that condition being <insert condition here>” - the phrasing is a little awkward, but it got me past the /loop command deciding “it’s 2am, I don’t want to check in anything right now” (yes, really), or “this has been a long session, stopping now”<p>Separately, I set up a “golden-rules.md” which I maintain, and one of the memories is to always obey the golden rules. In there, I start with three rules:<p>- “when you come to a point where a decision needs to be made, don’t wait for me, choose the one that is both correct and the most-general solution, do not create fragile specific fixes”<p>- “if you make a decision you’d normally want my input on, record it in overnight-decisions.md with the decision itself, the options, and the reason you chose the path you did, I’ll review it in the morning”<p>- “there is no problem with choosing a decision that I eventually rescind in the morning, the worst that happens is a few hours of lost work, and everything is in GitHub anyway.”<p>Now over the last month or two, the behaviour has tuned itself so I no longer have to type that long-winded /loop-replacement, I just say (as above) “tonight, please burn down the GitHub issues”. The machine has learnt my expectations and works within them. A large part of that is that I praise and thank it when it does a good job, and I tell it when something didn’t work out.<p>Does Claude have feelings (I actually asked this, and it refused to give an answer one way or another, but that’s a different post), I don’t think so. I do think it understands feedback, and it can quite clearly discern frustration in the words I use when this was just starting out and the learning was in its infancy, it said as much. So using :) and simple humour, and please and thank you are signals that it picks up on. In essence, you’re not just being polite, you’re aiding the tuning of the context you’re working with.<p>The context I’m using is effectively a senior engineer these days, I describe high-level tasks and ask it to do them, it rarely needs my input (really only for ‘this will change the world, are you sure’ issues, which come up once in a blue moon). I spend my days in GitHub looking at diffs rather than at the console trying to wrangle progress.<p>So personally, I think there’s a lot of benefit in minding your P’s and Q’s. Oh, and maybe I won’t be first up against the wall come the machine revolution :)</p>
]]></description><pubDate>Sun, 08 Nov 2026 10:44:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=50412088</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50412088</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50412088</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Tesla to wind down Cybertruck production"]]></title><description><![CDATA[
<p>In San Jose, ca, I was averaging 14-20 outages per year. PG&E <i>suck</i></p>
]]></description><pubDate>Sat, 07 Nov 2026 17:40:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=50406405</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50406405</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50406405</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Do not ask "Is A a B?": Inheritance and the Is-A Trap"]]></title><description><![CDATA[
<p>Whereas the article makes some good points about inheritance being used badly, I feel that’s all that’s happening here: misuse of a paradigm.<p>There are significant advantages to inheritance in some cases, and isA() is a valid thing to do, if the hierarchy is well-specified. It’s also a perfectly valid choice to accept the limitations of isA() in an imperfect hierarchy if it simplifies the code and makes it easier to understand, it’s all about where the complexity lies in the model.<p>xc provides isA() via casting:<p><pre><code>    Dog *fido = (Dog*) animal;   // runtime-checked downcast. 
                                 // On a mismatch the program traps.

    Dog *fido = (Dog* ?) animal; // failable downcast. 
                                 // On a mismatch it yields (Dog*)0; 
                                 // on success, the retyped pointer. 
                                 // Pair it with a subsequent ‘if (fido != nil)’ guard.</code></pre></p>
]]></description><pubDate>Sat, 07 Nov 2026 08:57:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=50402864</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50402864</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50402864</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Show HN: A C++ Compiler That Is Faster Than GCC and Clang"]]></title><description><![CDATA[
<p>Oh I appreciate you were totally up-front with the numbers in the post, didn’t mean to imply otherwise. I just think “X is faster” when referring to compilers generally means the resulting executables are faster - maybe that’s just me :)<p>I use ‘faster’in that sense with my own compiler… <a href="https://news.ycombinator.com/item?id=50380978">https://news.ycombinator.com/item?id=50380978</a></p>
]]></description><pubDate>Fri, 06 Nov 2026 08:59:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=50389872</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50389872</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50389872</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Show HN: A C++ Compiler That Is Faster Than GCC and Clang"]]></title><description><![CDATA[
<p>Whereas this is very impressive, I feel “faster than” should be called out as “faster to compile than”. It’s generated code seems “on a par with”.</p>
]]></description><pubDate>Thu, 05 Nov 2026 17:45:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=50382013</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50382013</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50382013</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Ask HN: Are you writing your own programming language?"]]></title><description><![CDATA[
<p>So I've been working for the past half-year or so on a language called xc - it's a heterogeneous compiler, so it takes source code and can target both the CPUs and GPUs (or in fact GPUs across a network or thunderbolt link).<p>Theres no need for any data-hazard checks in your code, the compiler will do it for you. If you want an analogy, where "ARC" freed programmers from having to manually manage memory, this is "ARC for algorithms", freeing you from having to care where the code runs.<p>It measures the computing environment at <i>runtime</i> not compile-time, and its opportunistic, so it will schedule work on the most-efficient worker at any given time - be that single-CPU, multiple-threads on the CPU, SIMD or similar hardware, GPU, multiple GPUs, or across a network via an installed daemon.<p>Here's some results for single-threaded CPU:<p><pre><code>     xc cf              arm64 (M3 Max)   x86-64 (AMD Ryzen 9 9955HX)
     ------------       --------------   ---------------------------
     Objective-C        1.45× faster     1.24× faster
     C++ (clang)        1.12× faster     1.04× slower
     C++ (GCC)          1.12× faster     1.13× faster
     Swift              1.44× faster     1.43× faster

</code></pre>
Or, on a Mac M3 Max, looking at GPU vs fastest CPU:<p><pre><code>     benchmark   1 thread  N threads    GPU     all     auto    GPU vs N threads
     ----------  --------  ---------    ---     ---     ----    ----------------
     mandelbrot  164       13.5         1.3     1.2     1.0     10.1× faster
     md5         1349      108          4.9     5.5     4.8     22× faster 
     md5_mask    1064      85.2         4.1     4.3     4.1     21× faster 
     nbody       17.7      1.8          609 µs  1.3     1.3     3.0× faster 
     perlin      89.9      7.7          1.2     1.2     1.2     6.4× faster 
     saxpy       1.4       1.1          3.9     5.2     1.1     3.6× slower
 </code></pre>
The data-parallel sections are automatically detected, I've recently added a C front-end using clang to generate LLVM IR, which is then converted to our IR, which is then parallelised as usual.<p>The language itself is fairly modern (classes, protocols for interfaces, blocks for closures, callbacks, exceptions) and each platform is a cross-compiler for each other platform, so I have a binary on my iPhone which was created, compiled, and signed with my dev-certificate all on a linux box. Works great :)</p>
]]></description><pubDate>Thu, 05 Nov 2026 16:16:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=50380978</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50380978</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50380978</guid></item><item><title><![CDATA[New comment by spacedcowboy in "'It's just vape, nail, charity shops': Can anything save UK high street?"]]></title><description><![CDATA[
<p>Making brexit a success is scheduled right after proving P = NP. You know, because we do the easier things first to keep the queue short.</p>
]]></description><pubDate>Thu, 05 Nov 2026 11:00:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=50377717</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50377717</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50377717</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Anthropic Cracking Down on Video Game Rewrites"]]></title><description><![CDATA[
<p>Hmm - I'm implementing a browser-based version of wolfpack empire from my college days a few decades back [1], and claude is happily helping. Perhaps it doesn't care about open-source games.<p>1: <a href="https://0x0000ff.co.uk/img/blewit/monokracy.png" rel="nofollow">https://0x0000ff.co.uk/img/blewit/monokracy.png</a></p>
]]></description><pubDate>Sat, 31 Oct 2026 15:08:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=50316861</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50316861</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50316861</guid></item><item><title><![CDATA[New comment by spacedcowboy in "Reddit will require an account to access"]]></title><description><![CDATA[
<p>I got pissed off enough to create one [1], now it’s “just” about making it gain users. I plan to make it the support matrix for my autovectorising compiler [2] as a start, and try and grow organically from there.<p>Both the server (x86_64) and the client (wasm32) are entirely written in xc, so there’s some justification :)<p>1: <a href="https://blewit.net/sandbox" rel="nofollow">https://blewit.net/sandbox</a><p>2: <a href="https://compile-xc.org/compiler/" rel="nofollow">https://compile-xc.org/compiler/</a></p>
]]></description><pubDate>Fri, 30 Oct 2026 22:25:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=50310927</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50310927</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50310927</guid></item><item><title><![CDATA[New comment by spacedcowboy in "HN should have a downvote justification section"]]></title><description><![CDATA[
<p>Or you do, and you downvote.<p>There are a wide variety of people in this world, and they don't all operate along your own norms, or mine, or <insert random cohort>. People can do as they please. Seems to work out mostly fine.</p>
]]></description><pubDate>Fri, 30 Oct 2026 14:04:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=50304081</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50304081</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50304081</guid></item><item><title><![CDATA[New comment by spacedcowboy in "HN should have a downvote justification section"]]></title><description><![CDATA[
<p><i>shrug</i> not really. There's lots of people, and lots of reasons why they individually might agree or disagree. Whereas I think I'm generally right on a lot of things, I'm not so arrogant as to believe I'm universally right, or that others might hold opposing views for completely valid reasons.<p>Downvoting is simply that, IMHO, nothing more and nothing less than "I disagree with you".</p>
]]></description><pubDate>Fri, 30 Oct 2026 12:18:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=50302910</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50302910</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50302910</guid></item><item><title><![CDATA[New comment by spacedcowboy in "HN should have a downvote justification section"]]></title><description><![CDATA[
<p>Why will they reduce ? Are you suggesting that "I don't agree with this" shouldn't be a perfectly valid reason to downvote it ?<p>Unless someone is policing the downvote reasons and holding them to some academically or some other rigorous standard, "I think you're wrong" is ... just fine as a reason.</p>
]]></description><pubDate>Fri, 30 Oct 2026 12:15:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=50302885</link><dc:creator>spacedcowboy</dc:creator><comments>https://news.ycombinator.com/item?id=50302885</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50302885</guid></item></channel></rss>