Plus in Nov or 2026, get out and vote, no matter how hard it is to get to the polls. This happened because people sat on their behinds and did nothing in Nov 2024,
And, try to talk to people who don't agree with you. Have an open mind, listen, avoid being judgmental and critical. It's not easy, but you can change minds.
Won't matter. Donny put the epstein files out, redacted, to remind every single influential person in the blast radius that unless he keeps holding the redaction pen, all their lives will be over.
One thing to consider: it’s clear he was very widely connected in American elite circles. It’s likely that almost all prominent people (in finance, business, the arts, science, government, etc) all came across him. We know he worked pretty hard to get intertwined with everyone he could.
And yet, although the list of his connections is large, it’s very far from most of these people. It seems plenty of people saw him for who he was and steered clear.
Not sure what that means. Mostly ordinary citizens go to protests. Not aware of any group paying felons to protest. Speaking of, is Trump allowed to vote?
Attending public (peaceful) protest is valuable. It shows that people with that view point (whatever it is) are not alone. It encourages more people to get involved.
I hope that this is hyperbolic satire and not a genuine viewpoint because it is incredibly unrealistic to the point of being almost fantastical. The US government aren't going to "go after" or interfere with Hacker News at any time in the future unless it suddenly, inexplicably becomes a popular hotbed of political activism (which it shouldn't become anyway).
Wrong. They are kidnapping American citizens and exiling them. They’re imprisoning people that criticize the government.
It’s a totalitarian regime. With enough time, will come after all dissenters.
> popular hotbed of political activism
First, it is unbelievably illegal for the government to do this.
Second, pain is their objective. Republicans have had no principles since they elected Trump in 2016. Their only objective is to hurt whomever they consider the enemy.
And everyone that isn’t screaming “I love the orange dictator!” is an enemy.
unless it suddenly, inexplicably becomes a popular hotbed of political activism
That's the thing about AI and scale. You don't have to only target the big fish. You can cast a wide net and scoop up data on people in every nook and cranny of the internet.
The concentration camps were loaded with people who thought their town was too small for the Nazis to bother with.
I want the government to know how i feel. I want them to see my posts and comments. If this anonymous surveilance without warrants is the only way to be acknowledged then thats a form of protest to me and it has made me want to be more outspoken knowing we are all being watched. Fuck ice.
I swear many years ago you could delete old posts but not any longer. About all you can do now is do something so egregious that they delete your account.
There's likely many iterations of HN comment datasets out there from "show hn: I scraped everyone's comments for my comp sci/big data class" over the years.
That’s actually how I got my Facebook deleted in 2015, and it appears I am still banned. I posted a picture, from behind, of a cowboy wearing only chaps. I tried to join again around 2022 to sell some stuff and they rejected me.
Probably the best move I made for my mental health tbh.
Have they stated the justification for this anywhere? You'd think a site that brands itself as being for hackers would value its users having control over their comments/privacy.
There's value in editing for clarity within a window of a live discussion. After the live discussion is less active, it's important to be able to reference things or see a coherent view of the discussion and what people were responding to.
Yes, it's because the comments create a discussion thread that then becomes impossible to follow (or worse, misleading) if certain comments within it are either deleted or edited to say something different. The idea is that what you write becomes communal property once it's been responded to, because it's part of a community discussion that loses meaning if people start deleting individual comments.
Pretty sure they only change the username to something anonymous though, and remove any PII in comments you've written, right? They won't delete the comments themselves AFAIK.
Let them come for us. If it comes to that, trolling social media to arrest american citizens en masse, people are going to be forming militias and I'll join up the local outfit. I don't care anymore. I'm ready to take a stand if it comes to it and take back our country and I'm sure I'm not alone on that either.
They have a limited amount of power to suppress opinion even with their powerful tools and thugs. Their method is to go after big platforms and prominent individuals. If you keep speaking up anyway, it will overwhelm them.
Fearing the consequences doesn't make you a complicit but a victim. Sure there will be people who will take a more brave/difficult stance, but can't blame others for not doing so, we don't know they'd put at stake.
If Trump's going to throw me in his El Salvador gulag for being a deep state Soros-backed neoliberal globalist shill on HN, I'm going to make sure somebody in his regime at least has to read my bullshit first.
3,500,000 pages[1] have been released, including 2,000 videos and 180,000 images.
If this was only "2%" of the files, you're alleging there's 175,000,000 pages of documents. Absolute nonsense. That's not even realistic. Not to mention nobody but the government knows how many pages are in "the files" - anything else you see is just made up.
> Im not a conspiracy theorist at all... murder of hundreds or thousands of girls and 1 year old babies
this is one example mentioning babies. There are hundreds of other pictures and emails re young girls. If you bother to look into this, you will see. you would rather feel superior nitpicking a minor detail while missing the fucking point. Good job. Heres another crumb, a tiny sliver of evidence:
You're interpreting that email to mean they've killed thousands of one year old babies? Or perhaps it was a joke about a party that had a bunch of babies at it... I dare say, you're so deep down the conspiracy rabbit hole you don't know which way is up.
Some of these claims don't have bulletproof video evidence and DNA, and i suspect you would call those fake too even if they did but they are not unbelievable when considered in the context of everything that's been shown. I can't do that for you.
Anyways, if that's not enough for you to even spend some time reading the news, then I don't know what is. Enjoy being stupid and smug.
This guy gets it, and isn't falling for the distractions.
Also, what is going on with this thread? Everyone here sounds like they're from Reddit, which has one of the most hysterical and heavily-propagandized userbases in existence.
One person here even said that Reddit is "free from MAGA influences". Like lol, Reddit is nothing but bot accounts and activist moderators who will insta-ban you for wrong-think. The whole site is nothing but astroturfing, and you have to be an NPC to believe any political post on its frontpage.
HN's has been one of my fav sites to lurk on for at least a decade, but I can't tell it apart from Reddit sometimes.
HN has taken a very sharp turn over the past 2-3 years. Putting aside politics, they are reflexively cynical, misinformed and confident in their ignorance even about technology. Missing the boat on AI as well for years as its evolved from cool chatbot that hallucinates to can write serious code with few errors and solve unsolved research problems with some assistance.
It's the smugness and complete lack of curiosity that gets me, which I am seeing even in this thread.
Any idea why the culture's been shifting here? I've always loved the deep & insightful back-and-fourths we've had on HN, but now a lot of that nuance is lost, and it's mostly just kneejerk reactions ("thing is the way it is because GREED, simple as that") and the endless nit-picking of unimportant details.
One day redhat is going to grease Trump's pole with enough cash, and King Donald is going to send a member of his tribal-tattooed, part-time MAGA influencer burgerwaffen to pull-up the black van and take you under cover of night for posting wrongthink about wayland & systemd.
This is a somewhat simplistic view of ownership and borrowing for modern programming languages.
Pointers are not the only 'pointer's to resources. You can have handles specific to your codebase or system, you can have indices to objects in some flat array that the rest of your codebase uses, even temporary file names.
An object oriented (or 'multi paradigm') language has to account for these and not just literal pointers.
This is handled reasonably well both in Rust and C++. (In the spirit of avoiding yet another C++ vs Rust flamewar here, yes the semantics are different, no it doesn not make sense for C++ to adopt Rust semantics)
struct resource {
resource(ctx *c, ...) {index = c->store(...); ...;}
size_t index;
ctx *c;
~resource() {c->free(index);}
// copy constructor+op creates new handle
// move constructor+op copies the handle, maybe zeroes the current one
};
With this you can rely on RAII, smart pointers, upcoming lifetime checks and annotations, etc. The core idea is that you treat objects of classes like this as values and everything works out seamlessly. Even if they are 'pointers' in all but name. You can also overload the dereference operator for it to have pointer-like syntax, but that is discouraged.
When you have just once resource this might be overkill but for large projects with tangled webs of resources, this sort of setup really makes the code simpler and easier to design.
That's C++ for you, simple things look complex but once you get into big hairy projects things stay at the same level of complexity instead of becoming an unmanageable mess.
D almost supports RAII, and the compiler seems to do some automated copy to move conversion, but this is the sort of thing that really, really needs a large number of users and compiler implementers to iron out issues and corner cases. Nothing against D, the language is pretty neat!
But if I'm not mistaken, this is just handling index allocation, release and avoiding dangling manually. The programmer is still responsible, right? And I don't think Rust can do better for indices, since indices are normal, "eternal" values.
> this is just handling index allocation, release and avoiding dangling manually
No, it is abstracted away. You just have to follow best practices when writing a library.
resource foo(...); // This gets freed at the end of scope. See RAII.
auto x = make_unique<resource>(...); // can be moved, freed when owner is.
auto y = make_shared<resource>(...); // freed on zero reference count
I don't know D so I'm probably missing some basic syntax. If pointers cannot be copied how do you have multiple objects referencing the same shared object?
OOP and ownership are two concepts that mix poorly - ownership in the presence of OOP-like constructs is never simple.
The reason for that is OOP tends to favor constructs where each objects holds references to other objects, creating whole graphs, its not uncommon that from a single object, hundreds of others can be traversed.
Even something so simple as calling a member function from a member function becomes incredibly difficult to handle.
Tbh - this is with good reason, one of the biggest flaws of OOP is that if x.foo() calls x.bar() in the middle, x.bar() can clobber a lot of local state, and result in code that's very difficult to reason about, both for the compiler and the programmer.
And it's a simple case, OOP offers tons of tools to make the programmers job even more difficult - virtual methods, object chains with callbacks, etc. It's just not a clean programming style.
Edit: Just to make it clear, I am not pointing out these problems, to sell you or even imply that I have the solution. I'm not saying programming style X is better.
I work at a D company. We tend to use OOP only for state owners with strict dependencies, so it's rare to even get cycles. It is extremely useful for modeling application state. However, all the domain data is described by immutable values and objects are accessed via parameters as much as fields.
When commandline apps were everywhere, people dreamed of graphical interfaces. Burdened by having to also do jobs that it was bad at, the commandline got a bad reputation. It took the dominance of the desktop for commandline apps to find their niche.
In a similar way, OOP is cursed by its popularity. It has to become part of a mixed diet so that people can put it where it has advantages, and it does have advantages.
On the flipside, with OOP is usually quite easy to put a debugger breakpoint on a particular line and see the full picture of what the program is doing.
In diehard FP (e.g. Haskell) it's hard to even place a breakpoint, let alone see the complete state. In many cases, where implementing a piece of logic without carrying a lot of state is impossible, functional programming can also become very confusing. This is especially true when introducing certain theoretical concepts that facilitate working with IO and state, such as Monad Transformers.
That is true, but on the flip-flip side, while procedural or FP programs are usually easy to run piecewise, with OOP, you have to run the entire app, and navigate to the statement in question to be even able to debug it.
Imho, most FP languages have very serious human-interface issues.
It's no accident that C likes statements (and not too complex ones at that). You can read and parse a statement atomically, which makes the code much easier to read.
In contrast, FP tends to be very, very dense, or even worse, have a density that's super inconsistent.
> In contrast, FP tends to be very, very dense, or even worse, have a density that's super inconsistent.
Depends on the FP. Pipes make things fairly legible. Example from Elixir:
def some_function(thing, doodad, doohickey) do
thing
|> foo(doodad)
|> bar()
|> baz(doohickey)
|> quux()
end
Also easy to debug -- break on any of those lines, or insert `|> IO.inspect()` at any point for good old fashioned print debugging.
Conversely, the non-FP non-pipe version of this would:
(a) be monstrous and difficult to segment: `quux(baz(bar(foo(thing, doodad)), doohickey))`,
(b) needlessly require OOP: `thing.swizzle(doodad).razzle().blorple(doohickey).dazzle()`, where the functions are methods defined on the preceding construct (or some parent construct, to god-knows-what generation), or
(c) require a lot of throw away variables (you get the picture).
I wish more languages had a pipe construct. It's very handy.
Interestingly, D is one of the few languages to have uniform function call syntax,[0] which makes the dot syntax effectively act as a pipe operator, requiring no OOP coupling for its use. Very neat!
>one of the biggest flaws of OOP is that if x.foo() calls x.bar() in the middle, x.bar() can clobber a lot of local state, and result in code that's very difficult to reason about
That's more a problem of having mutable references, you'd have the same problem in a procedural language.
Very few OO languages track reference mutability with any level of rigor. In C/C++ most devs don't even know what restrict is or how to write code using it correctly (which is very difficult an bug prone), const is unfortunately not enough.
In fact I don't even know of any production language that handles variable mutability with any rigor other than Rust.
It worked alright for Rust, and yes Rust does support OOP, there are many meanings to what is OOP from CS point of view.
I have ported Ray Tracing in One Weekend into Rust, while keeping the same OOP design from the tutorial, and affine types were not an impediment to interfaces, polymorphism and dynamic dispatch.
I don't think it worked well for Rust - in fact one of the core issues of Rust imo, is that it somewhat encourages this OOP style which can cause major headaches when you design an app in a traditional OO way - object compostion, complex and stateful, non-copyable objects full of 'smart' behavior, necessitating clones, and state that needs to be reconciled.
The whole concept of OOP is a major conceptual regression in how it treats aliasing, which is a major headache for compiler writers, necessitating either whole program analysis or JIT like techniques.
I agree with the sentiment, I really like D and find a missing opportunity that it wasn't taken off regarding adoption.
Most of what made D special in D is nowadays partially available in mainstream languages, making the adoption speech even harder, and lack of LLM training data doesn't help either.
> that is why carpenters are still around and no one buys Ikea
The irony in this statement is hilarious, and perfectly sums up the reality of the situation IMO.
For anyone who doesn't understand the irony: a carpenter is someone who makes things like houses, out of wood. They absolutely still fucking exist.
Industrialised furniture such as IKEA sells has reduced the reliance on a workforce of cabinet makers - people who make furniture using joinery.
Now if you want to go ask a carpenter to make you a table he can probably make one, but it's going to look like construction lumber nailed together. Which is also quite a coincidence when you consider the results of asking spicy autocomplete to do anything more complex than auto-complete a half-written line of code.
> I think you have misunderstood what a carpenter is. A carpenter is someone who makes wooden furniture (among other things).
I think _you_ have misunderstood what a carpenter is. At least where I live, you might get a carpenter to erect the wood framing for a house. Or build a wooden staircase. Or erect a drywall. I'm sure most carpenters worth their salt could plausibly also make wooden furniture, at an exorbitant cost, but it's not at all what they do.
I sanity checked with Wiktionary, and it agrees: "A person skilled at carpentry, the trade of cutting and joining timber in order to construct buildings or other structures."
These guys made one of the most amazing tables for someone I know: https://rustictradesfurniture.com/. If you said "you're not a carpenter because you aren't slapping 2x4s together", you'd get a wry chuckle that means 'who is this idiot'.
> Yeah, that is why carpenters are still around and no one buys Ikea.
I'm sorry, what? Are you suggesting that Ikea made carpenters obsolete? It's been less than 6 months since last I had a professional carpenter do work in my house. He seemed very real. And charged very real prices. This despite the fact that I've got lots of Ikea stuff.
> Compared to before, not a lot of carpenters/furniture makers are left.
Which is it? Carpenters or furniture makers? Because the two have nothing in common beyond the fact that both professions primarily work with wood. The former has been unaffected by automation – or even might plausibly have more demand due to the overall economic activity caused by automation! The latter certainly has been greatly affected.
The fact that people all over the thread are mixing up the two is mindboggling. Is there a language issue or something?
There is a language issue: carpenter is used as synonym of woodworker. It's like someone who doesn't know anything about computers using the term 'memory' to mean storage rather than working memory (i.e. RAM).
Nah, IKEA has replaced moving furniture with throwing it away and rebuying it. Prior to IKEA hiring a carpenter was also something that is done a few times in a lifetime/century. If anything it has commodized creating new furniture.
Eventually yes, when incapable becomes a synonymous with finding a job in an AI dominated software factory industry.
Enterprise CMS deployment projects have already dropped amount of assets teams, translators, integration teams, backend devs, replaced by a mix of AI, SaaS and iPaaS tools.
Now the teams are a fraction of the size they used to be like five years ago.
Fear not, there will be always a place for the few ones that can invert a tree, calculate how many golf balls fit into a plane, and are elected to work at the AI dungeons as the new druids.
While I don't share this cynical worldview, I am mildly amused by the concept of a future where, Warhammer 40,000 style, us code monkeys get replaced by tech priests who appease the machine gods by burning incense and invoking hymns.
Same for ERP/CRM/HRM and some financial systems ; all systems that were heavy 'no-code' (or a lot of configuration with knobs and switches rather than code) before AI are now just going to lose their programmers (and the other roles); the business logic / financial calcs etc were already done by other people upfront in excel, visio etc ; now you can just throw that into Claude Code. These systems have decades of rigid code practices so there is not a lot of architecting/design to be done in the first place.
Nick Offerman wants to have a word with you. Given the choice of building my own furniture and things or IKEA and I had the skills I’d go the build it myself route. It’s doable. It was before. And it still is. All we got now is super duper capable auto correct and text completion. Use it for what it is. Don’t let it replace you.
My experience is that all LLMs that I have tested so far did a very good job producing D code.
I actually think that the average D code produced has been superior to the code produced for the C++ problems I tested. This may be an outlier (the problems are quite different), but the quality issues I saw on the C++ side came partially from the ease in which the language enables incompatible use of different features to achieve similar goals (e.g. smart_ptr s new/delete).
I work with D and LLMs do very well with it. I don't know if it could be better but it does D well enough. The problem is only working on a complex system that cannot all be held in context at once.
The complaints are against the open-weight LLMs, I didn't try them much. I do use mostly Claude as that's what the company is paying for. They don't pay for laptops with GPUs or locally hosted LLMs to test those.
It's not like it knows perfect D, it does make mistakes and I don't work on a C++ or Rust project to compare its behavior. Generating templates from scratch is a bit of a challenge but given we have plenty of examples in our code with some prodding it manages to write well enough.
They taught us that Geography is old fashioned so the geography classes and history were all replaced with "Social Studies" at some time in the 80s. Most of that class was just about reading holocaust books, I think we had a week or two where they taught us what islands and fjords are, but the only time putting names to countries and capitals on a map came up was an optional extra credit quiz in 8th grade. Most people skipped it.
We had to take Geography, Social Studies, World History, American History, Civics, etc. as separate classes.
Islands/fjords etc were covered in Geology/Earth Science, and we also took separate courses for those as well.
Geography was reserved for understanding where things are in the Earth, how borders are defined, a little bit of world history as far as borders changing, etc. And also Apartheid for some reason because I guess they didn't know where else to stick that lesson in.
Rote memorization has never been my strong suit and so I suffered a lot in geography as it was taught to me. I got a D in that class. Now that I'm out of school and can actually properly learn, it all sticks a lot better because I've learned to contextualize everything and link together facts.
reply