skysight-inc/HackerNews huggingface dataset:
As someone who went to public school in Texas, the textbooks in Texas are vetted by revisionists who still claim the Civil War was about states rights and not slavery, my civic teacher argued this repeatedly in the 1980s. A lot of kids are indoctrinated with the BS that downplay the slavery aspect, it's like the Big Lie of the south.
Things are so good medically for mice.
Just the fact you don't need liability insurance and a passage of traffic laws examination to ride a bicycle on any road except a freeway contradicts the core of your statement.
The framework for clinical trials it to go from “there doesn’t appear to be any harm” to “we have reasonable proof that no harm is expected”.

If this is as promising as it sounds it’ll surely process through the stages as it should and eventually reach human trials.
Insurance doesn’t cover them precisely because they don’t work.

https://www.science.org/content/blog-post/does-it-work-does-...
It's interesting because the EV was made fun of relentlessly when it came out, with Ford fans saying that it would be a flop.

Also, I'm biased, but I have to disagree with the "impractical vanity car" part. The current Mustang coupe is super fun to drive and affordable - the trunk is huge and it is quite comfortable for two people (even 3). The coyote v8 is a marvel of engineering - 460 HP with instant torque, but you can get 29 MPG with it on the highway (if you drive calmly). The turbo 4 is even more efficient.

To get anything comparable from European or Japanese coupes, you have to pay twice as much.

I apologize for the rambling.
I disagree, but I think once a project gets beyond a certain level of complexity you may need to move beyond make. For simple projects though I usually do something like:

CC=clang
MODULES=gtk+-3.0 json-glib-1.0
CFLAGS=-Wall -pedantic --std=gnu17 `pkg-config --cflags $(MODULES)`
LDLIBS=`pkg-config --libs $(MODULES)`
HEADERS=*.h
EXE=app

ALL: $(EXE)

$(EXE): application.o jsonstuff.o otherstuff.o

application.o: application.c $(HEADERS)

jsonstuff.o: jsonstuff.c $(HEADERS)

otherstuff.o: otherstuff.c $(HEADERS)

clean:
rm -f $(EXE) *.o

This isn't perfect as it causes a full project rebuild whenever a header is updated, but I've found it's easier to do this than to try to track header usage in files. Also, failing to rebuild something when a header updates is a quick way to drive yourself crazy in C, it's better to be conservative. It's easy enough that you can write it from memory in a minute or two and pretty flexible. There are no unit tests, no downloading and building of external resources, or anything fancy like that. Just basic make. It does parallelize if you pass -j to make.
Was UNIX open source?
that actually explains it well
In other words, the big story here is the decline of the mustang as a status symbol, not the rise of the Mach E (or electric vehicles in general).
There are a lot of cool museums if one happens to be in Houston IMHO. Also I dunno if they have the gigantic exhibits from the 1960s and 1970s still, but as a kid the Johnson Space Center impressed me.
Ah, we are at cross purposes here.

I stand by my statement that you have quoted. The “personally” bit was that I, personally, can no longer have full faith that his Wordpress commits are his work, given his recent conduct.

There is nothing accusatory about my statement that he has managed to closely associate Wordpress the product with Mullenweg the man. And it’s an undeniable fact that he’s managed to wring an enormous amount of profit from that relationship, and, indeed, boasts about it himself in the blogpost linked from this post!
That's entirely untrue, particularly at lower frequencies. This isn't audiophile cork-sniffing - the behaviour of a loudspeaker can be radically altered by the design of the enclosure. Entire textbooks have been written on the topic.

https://www.amazon.com/Introduction-Loudspeaker-Design-John-...
Good for image generation, inadequate for local llms (on its own).
Well, maybe when the next pandemic hits, there will be no more remote work. Since you do not believe it is an option, if it worked then, why wouldn’t it work now?
A trick I often use to get the most out of messagepack is using array encoding of structs. Most msgp libraries have support for this.

This gives you a key benefit of protobuf, without needing external schema files: you don't have to pay the space of the keys of your data.

This is simply not something you can do with JSON, and depending on your data can yield substantial space savings.
I think it’s just a way to stop the reporting of an event turning the event into an opportunity for people to gain media coverage and propel their careers, or their interests that may not be related to the discussion at hand.

Public debates are swamped with characters who want to make a name for themselves by holding views, having a particular style, or catering to certain demographics. At this point, the debate ceases to ne a way of discussing ideas and opinions. It’s just a way to sell the participants. Likewise, there are many people who want the opposite. They hold opinions but really don’t want to be part of the wider social debate . They don’t want to be public figures defending a particular point. They just want to contribute in some way.
Beat me to it. Relevant Derek Lowe quote from a different article.

But as I did when I wrote about the lecanemab data, let’s get some of the disclaimers out of the way at the beginning. I mentioned there that no Alzheimer’s drug candidate has ever stopped the progression of disease, and that of course means that no such candidate has ever reversed any of the damage, either. See below for more on that as it relates to donanemab, but what we’re looking for in all these cases is essentially slowing down the rate at which these patients deteriorate.
…
But here goes: lecanemab slowed decline by 27% on the CDR-SB scale, and donanemab slowed it by 29%. As you will can see from my earlier writeup on the former drug, opinion was very much divided on whether the lecanemab numbers would even be noticeable in real-world use (there is no standard for clinically meaningful efficacy in CDR-SB changes). So I would have to think that the same objections apply here. We cannot be sure that this drug will actually make a difference in the real-world care of patients with Alzheimer’s - not yet, anyway. This point is completely avoided in the Lilly press release, but it is nonetheless real and we will be hearing more about it from clinicians - well, if you listen closely above all the noise, that is.

https://www.science.org/content/blog-post/lilly-s-new-donane...
> Pony cars have been dying for decades

only if your definition of "decades" is ~5 years? Otherwise the resurgence of the pony car was only like 20 years ago in the first place (5th gen mustang & charger 2005, Challenger 2008, camero zeta 2010).
Doesn’t this raise more questions though? If ultrasound impacts chemicals in the body, what about other forms of waves? Do we still have to find out how the body reacts to different frequencies and wavelengths?
Small and fast
Do you think greedy people would sell off a companies' assets for parts if that company was profitable?

They don't buy healthy companies, the people that do that are looking for failing companies that they can buy for pess than their assets are worth.
Oh yeah, support staff aren't always aware of everything. For example, with one of our latest features, we didn’t have time to add a UI option to disable the feature. The expectation was that support staff could disable it via their special admin panel upon user request. However, I accidentally discovered that when users asked to hide the feature, tech support told them it wasn’t possible! It turned out the tech support lead forgot to share that information with the team.

As for the OP, they should have conducted load testing and implemented rate limits on their end, rather than blindly relying on someone’s word that GitHub was ready to handle all their product's load for free.
Continual growth is possible in at least two ways:

1) standard sigmoids, which never stop growing yet are also finite

2) standard ecological growth, where growth is never ending but so is death. This is much more typical of systems like capitalism than sigmoids growth. New upstarts experience exponential growth for a whole, then peak, and then die.

Of course be careful of mentioning these standard scientific observations around those in the degrowth cult, as the cognitive dissonance may cause an unpleasant explosion.
I think there's two kinds of "knows how to drive."

- There's the people you're talking about, who treat public roads like their own playgrounds with little regard for public safety or road laws.

- There's also people who will keep an eye on their surroundings, understand how weather affects driving performance (acceleration, braking, cornering) and when to use or not use automation like adaptive cruise

As long as we've got a car-centric society in North America I'm more than fine with more drivers falling into that second bucket but having to deal with roads in Toronto, Ottawa, and Montreal very regularly, most people just don't pay attention on the road.
If anyone has an M1 binary…
According to linked article on this submission RTO is confirmed to be from early March https://news.ycombinator.com/item?id=42659215
Yes that is the major potential problem with this type of mouse model in general. Mice are modified to have a condition that resembles something like alzheimer's disease and then treatments are tested, but there's no guarantee that the underlying disease is actually the same, so if the condition that is induced in the mice is just a symptom rather than the underlying cause of the human disease, or just superficially resembles it, the treatment may not actually be effective in humans.
Contemplative LLMs
Cayennes aren't exactly cheap, either.
Why were they applying patches? And what were they patching? What were the consequences when you busted them?
No, you're missing the point. This discussion isn't about my comfort level with autocracy, it's about how, in a democracy, you want corporations to be aligned with the policies of the currently fashionable governmental leadership.

> You don't seem to have a problem with autocracy, but I do.

I hadn't expressed my own views in autocracy myself. I had argued how the democratic will of the people as expressed for elections can actually be for the (future) society they live in to be autocratic; I gave examples, and you just gave Hitler as an example. So I don't think you have argued against this point. You should revise your last paragraph to read:

(The voting US majority) doesn't seem to have a problem with autocracy, but I do. I've lived in countries with those leaders - and Trump is cut from the same cloth. Enjoy it while it lasts.

I had hoped that you would be able to express that you understand that the current system is somewhat democratic, and that the current will is for the democratic system to extinguish itself. With this distinction being understood, I would have liked to discuss what institutions it would take for a society to not only be democratic, but also sustain that democracy into the future.

I would have liked to explore more nuanced notions; for example,

- you talked about companies "doing the autocratic government's bidding in controlling the population (by controlling information)", but I wanted to discuss what it means

- to shape the information environment of a voting citizen, so that they have certain beliefs so strongly autocratic that even in a democratic process their democratic will is to have an autocratic government.

- to examine the reality of the information and mass communication environment already present that is quite necessary for nationhood, that convinces someone to vote for a person that they have never spoken to personally and pretty much never heard of directly with their eyes and ears, to protect and advocate for their personal interests and rights, over someone they know from experience they can trust with for that like a family member or close friend. It is clear to a 4 y.o. that their parents are the only person they can trust for that, but as we grow up and learn about society through our information diet, we learn that we should be trusting people we never meet for it.
> I don’t know how standard harmful treatments get retired from active use.

So naturally, you've assumed they don't get retired? I assure you, they do: sometimes it takes longer than it should, but if there's evidence that a treatment is harmful, it eventually does fall out of practice. Very few leeches are used in medicine today, in case you haven't noticed.

The ProPublica story you linked was published in 2017, so I'm not hearing that this problem of treatment 8 years ago is still a problem today. It also doesn't make clear what evidence it has against stents. I found some studies from 2003/2004 that say they found insufficient evidence for stents preventing "mortality, acute myocardial infarction, or coronary artery bypass surgery". However, there was evidence for "substantial reductions in angiographic restenosis rates and the subsequent need for repeated PTCA".

Now setting aside the pause for a second. Don't look this up: do you even know what "angiographic restenosis" is? If not, why would you think you're qualified to have an opinion on this? Because you read an article in ProPublica, you think you're a cardiologist now?

And here's my big picture point: yes, you can find problems with the medical field. Doctors are humans, and they make mistakes. But the track record of doctors as compared to random quackery off the internet, is absolutely stellar. You're criticizing medicine without comparing it to anything. Some of your criticisms are valid areas we could improve on, but the alternative you're offering is much, much worse. People die from under-studied treatments all the time.
Well, they did just spend an enormous amount on building a new tower on Park Ave.
>Trump threatened economic retaliation against Denmark, should the Scandinavian country — a NATO member — stand in the way of his territorial ambitions.

It's all a bit nuts. Has any other US president gone territorial expansionist like this?
Hmm, I wonder what's the best way™ to, er "locally backup" those files, in such a way that no git-clean invocation will remove them without promoting.

All I can think of are things like periodically copying them to another folder, or give them a different ownership needed for edit/delete, etc.

Unless there's some kind of .gitpreserve feature...
Pretty sure that doesn't handle the 'Z' timezone offset, as I saw the same with various PHP built-ins. Some ignore offsets, some don't...but handle only specific formats and not others, including the Z. So you still need some kind of wrapper.
Curious. I don't have an account, and I can read it.
> if you're working within a translation unit, thats much simplified, but then you're much more limited in what you can do without repeating a lot of code. I wonder how the author solves this.

You are correct in that the source code to the function being evaluated must be available to the compiler. This can be done with #include. I do it in D with importing the modules with the needed code.

> This is already somewhat possible if you can express your test as a macro, which if you add in the first point, then this becomes trivial.

Expressing the test as a macro doesn't work when you want to test the function. The example I gave was trivial to make it easy to understand. Actual use can be far more complex.

> Performance

D is faster at compiling than C compilers, mainly because:

1. the C preprocessor is a hopeless pig with its required multiple passes. I know, I implemented it from scratch multiple times. The C preprocessor was an excellent design choice when it was invented. Today it is a fossil. I'm still in awe of why C++ has never gotten around to deprecating it.

2. D uses import rather than #include. This is just way, way faster, as the .h files don't need to be compiled over and over and over and over and over ...

D's strategy is to separate the parse from the semantic analysis. I suppose it is a hair slower, but it also doesn't have to recompile the duplicate declarations and fold them into one.

Compile time function execution can be a bottleneck, sure, but that (of course) depends on how heavily it is used. I tend to use it with a light touch and the performance is fine. If you implement a compiler using it (as people have done!) it can be slow.

> one of the ways I have kind of implemented templating in C is by defining a variable and importing a c file, changing the variable, and then reimporting the same c file. Another thing I've done is define a bunch of things and then import the SQLite C Amalgamation and then add another function (I do this to expose a SQLite internal which isnt exposed via its headers). All of these use cases would break with this change.

I am not suggesting removing #include for C. The import thing would be additive.

> Are there any thoughts about these issues?

If you're using hacks to do templating in C, you've outgrown the language and need a more powerful one. D has top shelf metaprogramming - and as usual, other template languages are following in D's path.
You can't expect 62.5% for 5/8 hours, you have other costs to them for benefits etc.
also https://lwn.net/Articles/993895/
Has not kink become mainstream? Especially for software devs (HN crowd).
> What do all these intervals add up to? Four thirds.

I'm not sure what I was thinking of; 3.3333... is obviously ten thirds.
You might not feel it yourself but you get assigned it by others anyway.
Great visuals! I loved to use fatmap to look at ski resorts and mountains in 3d to identify slope/terrain etc. Having ski resorts as 3d models I can check out would be an awesome use case!
When I read about this I immediately thought about Aaron Swartz. He was persecuted for downloading copyrighted stuff, while Meta and other Corps will get a slap on a wrist. Such a sad story. And it's his death's anniversary today... RIP
I assumed that growth was in relation to revenue. Isn't that the case?
I've been following the whole story and from what it looks Matt thinks that WordPress is his own property.
When something goes open source even the creator needs to be wise enough to understand that it's not his property anymore. I've seen this in many "hybrid" startups that plan to solve the marketing/distribution/ecosystem problem with "partial open source". But the history shows where these frequently end up.

You can't have full ownership of something that you've released to the world, but it takes balls to admit it to yourself.
> end remote work and require more than 300,000 employees to work from the office five days a week.

Ending remote work is one thing. Requiring workers to come to the office five days a week is a whole other thing! There is a wide spectrum between the two. The two are not the same.

Whenever this happens, the reason is the same. They want to lay off people without having to pay severance and unemployment benefits.
The question is not profitable. The question is can they be MORE PROFITABLE than they currently are. Some companies are unprofitable and easy targets. Others are mildly profitable, but PE can lever up their investments to goose MORE out of them, resilience and survivability be damned.
They never claimed to be starting a fork (at least not yet)[0]. They only called for reform to the existing governance structures.[1]

Matt Mullenweg painted it as a fork to suit his narrative and pre-emptively poison the well (by implying they are incompetent) of a potential future fork.[2]

He's done that a couple times now. He claims to support forks and says "I'll even promote them on WordPress.org" (paraphrase) but what he does is post before a fork is even ready or properly organized. Thereby sabotaging the effort and making everyone involved look bad. [3]

It's truly evil.

[0] https://x.com/jdevalk/status/1878210129914409063

[1] https://joost.blog/wordpress-leadership/

[2] https://wordpress.org/news/2025/01/jkpress/

[3] https://wordpress.org/news/2024/10/spoon/

EDIT: Matt just posted another childish taunt in response to Joost's clarification. See https://x.com/photomatt/status/1878227222927933815
Let's not sugarcoat it, it's just a way to fire a large number of employees, it's never been a debate about remote work.

The issue for them is that usually it's the best employees leaving when done this way and the company is then stagnating.
BTW, important that Sevastopol is not random choice, but it is strategical point to control Crimea.

Control Crimea and coast of azov sea is important, because Russia have powerful internal water routes via azov sea. For example, when Russian black sea warship need some deep maintenance, they use rivers network to reach service facilities in deep country.

It is luck for Ukraine, that we have huge part of azov sea coasts, with Mariupol, one of largest steel enterprise of the world and also big port (sure, I mean we control them before war).

For Russians, Mariupol was hidden threat, they constantly fear that Ukraine will use power to block Russians from enter sea from Don.
What if you alias ssh on the local machine to open a tmux with the top pane being a red warning, and then the whole thing could automatically close when ssh ends so the experience is just like normal ssh?

I've never actually used tmux, but maybe I will try it out!
Eventually plus 10 years, as this article is 10 years old.
Right, yes, exactly this. Using a tool or process without full understanding of its operation, or how to use it in different ways, is not _ideal_ - but it's a different thing (similar! but different) from "doing something just because everyone else is doing it". A Makefile-copier might not know the full stack of concepts that undergird their working configuration - but they do know (in the "true justifiable knowledge" sense) that it _is_ a working configuration, and they know why they're adopting it.
They are also extremely limited. Timestamp-based freshness is often broken by modern VCSes. Git doesn’t record timestamps internally, so files can (and often do) have their mtime updated even when their contents are the same, causing unnecessary rebuilds.

They also are utterly unable to handle many modern tools whose inputs and/or outputs are entire directories or whose output names are not knowable in advance of running the tool.

I love make. I have put it to good use in spite of its shortcomings and know all the workarounds for them, and the workarounds for the workarounds, and the workarounds for those workarounds. Making a correct Makefile when you end up with tools that don’t perfectly fit into its expectations escalates rapidly in difficulty and complexity.
If we haven't seen positive results in humans I'm gonna guess it being a lot harder to push ultrasound through a human skull than a mouse skull is part of the reason.
> where we only pretend to have the rule of law and equal application of it.

We have definitely stopped pretending.
The impact of ultrasound on dissolving and breaking things in liquid is well studied in general engineering. I don't understand your open ended question about this raising questions. How so? We don't use microwaves for dissolving or breaking crystals anyway like we already do for ultrasound.
I appreciate the insight. What would you say works? Also do you have a blog? I would like to read more about this from an insider's perspective.
I see. Well the button works for my wife and I, and we've been playing it (on Pixel and Samsung phones). I wonder why it doesn't work on yours.
I personally don’t like forward referencing because it makes code harder to read. You can no longer rely on the dependency graph being in topological order.