skysight-inc/HackerNews huggingface dataset:
Yes. Wasm does to my knowledge not have an answer for this, even if some projects patch in their bridge logics. Networking and file systems, and the permission model, is "the rest of the fucking owl". Linux isn't standardized, but at least it's Linux. Without consensus on the fundamental APIs I don't see how we can get to a platform agnostic experience. Even an https call isn't simple: you need TCP and you need to pull root certs from the env, at the very least. Where's the API for that?

I hope for a much more near term bright future for WASM: language interop. The lowest common denominator today is C, and doing FFI manually is stone age. If you can leverage WASM for the FFI boundary, perhaps we can build cross language applications that can enjoy the strengths of all libraries, not just those outside of our language silos.
20a outlets are also expensive compared to 15A ones. When redoing the electrical in the house I inherited I put a dedicated circuit in the living room for the TV/game consoles/etc since my daughter's gaming rig would be going in the living room as well; since I hadn't decided to put the recessed panel for the TV wiring in at the time it was the only outlet on the circuit and code dictates that a 20A circuit with a single outlet must use a 20A receptacle.

I can buy a 10-pack of nice 15A Leviton Decora Edge outlets (that use lever lock connectors instead of screw terminals) for $26 ($2.60 each), but basic 20A tamper resistant outlets (which newer editions of the NEC require anywhere a small child can access them) are $6+ a pop.

When nothing outside of my electrical room (where the servers live) has need of a 20A receptacle it's kind of pointless to spend the extra money on them, but the extra couple bucks on 12 gauge copper is always wise.
On a side note, there are no 5090's on amazon.com, except as part of a system. I suppose this is because any that become available are purchased and amazon doesn't display out of stock items in their search results? There are 5080's.

https://www.amazon.com/s?k=nvidia+rtx+5090+32gb+ddr7&i=elect...
> In the year 2030, no one will remember Kubernetes.

That's 5 years from now.

Which is a pretty good time frame for getting enterprisey things on to kubernetes.

And maybe a bit short for getting vendors to add a new sandboxed VM type to their supported platforms.
If there is no corresponding tax cut, there will be a recession or depression. Even if there is a tax cut, there is no guarantee that money won’t be used for other things (to buy assets, save, or pay down debt).
Why would you not extend that idea to paying for gps access directly?

Simply stated, the idea is that it is a public good for businesses to know the weather as well as they can. For somewhat self evident reasons.
You come across as fairly confrontational.

But I don’t understand the point. Satellites already fly indefinitely and can drop payloads of kinetic energy weapons. Why all the complexity of VLEO and drones? What could you that’s impossible with other, simpler, already-extant weapons systems?
Agree on the performance, unfortunately. Even C+P operations in RustRover are "too complex".
Yes, the CPI includes rent (and owner's imputed rent).
This was true of svn and git; both had command named the same as VCSs that were popular when they were introduced, but had semantics that were subtly (or not so subtly) different.
You would think that at the very least our military would not tolerate having to build its machinery with parts from abroad. Can anyone speak to this?
The closest way to visualize it is probably how cloudflare offers something kind of like a container (if you squint) via it's workers product.

https://blog.cloudflare.com/announcing-wasi-on-workers/

I assume the merit for cloudflare is lower overhead cost per worker than if they had done something more like AWS lambda. Explained better than I can, here: https://developers.cloudflare.com/workers/reference/how-work...

It does currently present a lot of restrictions as compared to what you could do in a container. But it's good enough to run lots of real world stuff today.
With `jj undo`, it's not a huge deal. I'm (mostly) kidding.

jj has to weigh trying to be the best VCS it can be alongside factors like "how much will this confuse someone who's used to git." Both things are important, and balancing them is a tricky process.

Take `jj commit` for example. This "does what git commit does," sorta. But also, not really? But if you're five minutes into `jj`, coming from `git`, then yeah, `jj commit` is exactly what you think it is. And that lets you be comfortable. Even though, from the `jj` perspective, it's a very bad name.
> Bun

Nit: bun uses javascriptcore
Who says they're suddenly mad now? The voters have thrown out two incumbent Presidents in a row and switched political parties three Presidential elections in a row.

Unfortunately for them, there's a political duopoly.
The biggest blocker for me to switch to using jj currently is https://github.com/jj-vcs/jj/issues/3949 which is that it doesn't have a `core.fileMode` option equivalent. What this means in practice is that it's unusable from WSL when your repo is on an NTFS filesystem. It gets confused by NTFS's lack of executable permission bit and makes spurious changes/commits.

It's a small thing, but while jj adds some convenience, it doesn't add enough (for me) to offset the inconvenience of changing my workflow to not use WSL. (Another relatively minor inconvenience is its inability to use your SSH configs. So if you have multiple key pairs and need to use specific ones that aren't jj's default pick, an ssh-agent is the only way.)

That said, I would 100% recommend jj over git for any new programmer who hasn't yet had to contort their brain already into the git ways. All the things that git's UI does a great job of obscuring and presenting in a confusing way, jj presents in a straightforward way that makes sense and is easy to remember.
> we rely on the government as a safety net

This is the issue though. They think the safety net is the problem.
Long ago, I sometimes pointed at the fact that China installs a "party-approver" on every committee they have as a stark contrast to the democratic, meritocratic US and one of the reasons why the West had been ahead in innovations.

I never thought I would live to see the day the US itself is having one of these. Wtf is this "DOGE team lead"? They will have power over newhires and policies at every federal agency?

I literally can't believe it. It is almost unreal. Sometimes I fantasize about what would happen if the world turn upside down tomorrow. I guess I now know how it actually feels...
I had a NDE two years ago. I had a lucid experience, saw someone (looking like a pastor) telling me "Do not be afraid, the same way you had to be born to experience this world, we need to die to experience the other world", I then woke up. I am not religious. It did leave a strong impression on me and think about it often.
One benefit of being an old engineer is watching how excited people get when they rediscover something that has gone around the bend over and over again. I swear if you fuckers reinvent DCOM I will shit in your hats.
Not really. 15A receptacles are required by code to be able to handle 20A of current at their terminals, so the larger wire and breaker allows for more loads to be run instead of one big load to draw it all (and if you need that, then a 20A circuit with a single receptacle does actually require it to be a 20A receptacle).
The wipers are certainly better than when I got the car 5 years ago, but they still seem to go too slow or too fast in some conditions. I don't have much to compare them against, as my previous cars have all been from the early 1990s or cheap rentals.

I don't remember a setting for auto defogging. My car just does it sometimes.
> Many of my colleagues try them out for an hour or two and then jump ship back to VSCode just because the initial "wtf is going on" factor is so high

People who get hung up on the aesthetics of their IDEs are going to have other problems with programming generally.
What we're seeing here is the dismantling of necessary and useful government functions by people who have no idea about the consequences of what they're doing.

I can't wait for them to come for GPS (run by DoD). All these people want to do is replace these government functions with a worse and more expensive private alternative but hey, someone gets to rent-seek massive profits, so that's OK. It's also a lesson in how for many things, them being run by a government entity is the best alternative.

If you want to see actual waste, how about a current sitting Senator and former Florida governor who, at the time, run a company that got the largest fine in history for defrauding Medicare to the tune of $1.7 billion [1], something for which nobody faced criminal prosecution.

[1]: https://www.factcheck.org/2014/06/floridas-medicare-fraud-fl...
Definitely a dead take. WASM has its merits but it’s not a panacea.
What a relief to know that, since AGI isn't possible, none of these things will be happening.

Despite sci-fi stories to the contrary, everything humans do with AI is just humans executing their own volition with tools. There is no desire, aim, or behavior of a computer that is separate from its operator or programmer. The machine is not coming for you unless someone tells it to.
True, but I suspect it'll be a lot easier to virtualise all those APIs through WASM than it is for a regular native binary. I mean, half the point of docker is that all syscalls are routed into an LXD container with its own filesystem and network. It should be pretty easy to do the same thing in userland with a wasm runtime.

And the nice thing about that is you can pick which environment a wasm bundle runs in. Want to run it on the browser? Sure! Want to give it r/w access to some particular path? Fine! Or you want to run it "natively", with full access to the host operating system? That can work too!

We just ("just") need wasi, and a good set of implementations which support all the different kinds of sandboxing that people want, and allow wasm containers to talk to each other in all the desirable ways. Make no mistake - this is a serious amount of work. But it looks like a very solvable problem.

I think the bigger adoption problem will be all the performance you leave on the table by using wasm instead of native code. For all its flaws, docker on linux runs native binaries at native speed. I suspect big companies running big cloud deployments will stick with docker because it runs code faster.
Institutions, Technology and Prosperity
WASM solves a different problem to containers. Where WASM does well is in running sandboxed code efficiently, because that's where it started out. I think WASM will likely take over as the standard for shipping things like Functions-as-a-Service implementations, and other forms of plugins, where one host application/server of some kind wants to efficiently run pieces of untrusted logic.

Containers don't solve that problem. They aren't a particularly good security boundary, and they are much heavier weight, in terms of bytes and startup costs, than WASM binaries, because they are deeply integrated into the OS for networking, etc. However, when what you need to do is ship a binary with a bunch of accoutrements, dependencies, files, etc, and then run multiple processes, multiple threads, and use more of the OS primitives, containers are an ergonomic way to do that, and that suits Infrastructure-as-a-Service much more closely.
Show HN: Considering building a tool to automate changelog/blog/social/and so on
Hi friends,

I love building things, but I hate dealing with the repetitive stuff. You know, writing the terms of service, a privacy policy, setting up a contact form, writing changelogs when there's an update, and even thinking up tweets for promotion. It's all important, but it really pulls me away from the fun part: building the actual app.

That's why I'm thinking of a tool to help set up those content with one command and automate all that tedious work when you create your pull requests.

I build the waitlist site over weekend and put more info there: https://footer-three-puce.vercel.app/

For example, the package will include terms of service, privacy policy, contact form, changelings and so on. You'd be able to manage the content in the SaaS app. When you create a pull request, it would scan and understand the code to create changelogs, blog posts, or social media posts.

I'm looking for feedback on whether this is something other developers would find useful.
NOAA is a crown jewel of the American experiment. Agencies like this don't exist to turn a profit — they are there to serve the public interest.
Capabilities based Operating Systems will replace containers. WASM is a stepping stone to help the world better impedance match them conceptually.

If someone tacks on file system access to WASM, the whole system becomes worthless.
I can’t believe it’s happening after 17 years…
Why does anything need to replace anything?

Containers, VM's, physical servers, WASM programs, Kubernetes, and countless other technologies fill niches. They will become mature, boring technologies, but they'll be around, powering all the services we use. We take mature technologies, like SQL or HTTP for granted, but once upon a time, they were the new hotness and people argued about their suitability.

It sounds like another way to distribute software has entered the chat, and it'll be useful for some people, and not for others.
I have been finding the workflow I described to be quite helpful, because it also provides me a scratchpad that I associate to the branch. And since the tip is never the git head so when I have to fallback to git I'm "sure" I'm not operating on that.

I'm still experimenting with things, but I think my overall takeaway is that in jj my working copy is "on branch", so I should lean into that rather than try to emulate my older workflows too much. And this new workflow... I just find it better!
> Many Chinese cities implement driving restrictions based on the last digit of a car's license plate, but EVs are typically exempt from this rule.

I didn't know that, good point! You would already want to get an EV in Beijing since the license lottery has a separate allotment for them, but even then you might not win a license (not sure what the odds are right now, it depends on what they are selling). I assume SH is the same.
I don't think so. I have a P16 Gen2 and this thing sucks power like nobody's business. 13950hk and 128gb of RAM. I barely get 1 hour of light programming work. I mostly use it as a desktop though, and I have a separate M2 Mac for traveling.
WASM does not run on real hardware. At best, WASM can be considered a virtual machine (in the way that the JVM and the .NET CLR are virtual machines). I guess we can call that a "runtime".

Containers package applications that run directly on real hardware (well, directly on a real kernel that is running on real hardware). There is no runtime. I am talking OCI containers here (Docker and Kubernetes). At least they can. Most containers are probably running on a Linux kernel that is running in a virtual machine (in the way that KVM, EC2, and VirtualBox are virtual machines).

WASM needs a runtime. That is, it is going to run inside an application. That application needs to run on a kernel. So, WASM will always be further from the hardware than a container is.

WASM solves the same "portability" problem that the JVM and .NET do. So, maybe WASM wins against those environments.

That is not the problem that containers solve though. Containers bundle applications with their dependencies. They replace "installation and configuration" with instantiation (deployment). WASM does not magically eliminate dependencies or the differences between environments (not even the difference between V8 implementations).

If anything, the technologies are complementary. Maybe, in the future, all our containers will be runing WASM applications.

Or maybe we will run a different kind of container that ONLY runs WASM applications and then WASM can replace the Linux kernel running in a VM that hosts all our OCI containers today. Perhaps that is what the author really envisions. Even then, it sounds like more of a complement than a true alternative.
That would only stymie the smallest-time players. Things like sideways text in margins or rotated table column headers are common enough that these have been solved problems for decades. Breaking the text down into specific elements and handling it differently or ignoring it altogether based on context and content is trivial.
I know it wasn't the intention of the author in the slightest, but I feel so small and incapable after reading that piece. Good luck bess.
> > if I'm understanding it right, turns r --[edit3]--> q --[edit2]--> p into r --[edit3]--> p.

> You are right with the outcome but wrong about why. `jj abandon -r q` would turn `r --> q --> p` into `r --> p`

Well, it can do two things. Given:
`r(f3) --[e3]--> q(f2) --[e2]--> p(f1)`

`jj abandon -r q` makes `r(f1+e3) --[e3]--> p(f1)`, as if you had rebased `r` onto `p`.

`jj abandon -r q --restore-descendants` makes `r(f3) --[e2+e3]--> p(f1)`, as if you had squashed `r` into `q`.
Miniature Hard Drives
All that is needed are knobs or buttons or switches to directly access as many functions as possible without the driver looking. For things in the screen, there should be a clicking knob that can navigate the screen without touch.
That's due to the translation. The original term 天神 comes from the polytheistic Chinese folk religion so it doesn't have the same connotation.
In the same way as a 911 driver's behaviour is influenced by porsche's design of certain systems, etc
Very sad. In case you didn't open the link yet, this is from the widow of Jake Seliger, who was very active on HN: https://news.ycombinator.com/threads?id=jseliger. He died a few months ago.

Grieving while being a new mom must be brutal.
Trump supports Black History Month so I'm not sure removing it would be an effective way to curry favor. Below is a proclamation he issued at the end of January.

------------------------------------

January 31st, 2025

BY THE PRESIDENT OF THE UNITED STATES OF AMERICA
A PROCLAMATION

Today, I am very honored to recognize February 2025 as National Black History Month.

Every year, National Black History Month is an occasion to celebrate the contributions of so many black American patriots who have indelibly shaped our Nation’s history.

Throughout our history, black Americans have been among our country’s most consequential leaders, shaping the cultural and political destiny of our Nation in profound ways. American heroes such as Frederick Douglass, Harriet Tubman, Thomas Sowell, Justice Clarence Thomas, and countless others represent what is best in America and her citizens. Their achievements, which have monumentally advanced the tradition of equality under the law in our great country, continue to serve as an inspiration for all Americans. We will also never forget the achievements of American greats like Tiger Woods, who have pushed the boundaries of excellence in their respective fields, paving the way for others to follow.

This National Black History Month, as America prepares to enter a historic Golden Age, I want to extend my tremendous gratitude to black Americans for all they have done to bring us to this moment, and for the many future contributions they will make as we advance into a future of limitless possibility under my Administration.

NOW, THEREFORE, I, DONALD J. TRUMP, President of the United States of America, by virtue of the authority vested in me by the Constitution and the laws of the United States, do hereby proclaim February 2025 as National Black History Month. I call upon public officials, educators, librarians, and all the people of the United States to observe this month with appropriate programs, ceremonies, and activities.

IN WITNESS WHEREOF, I have hereunto set my hand this thirty-first day of January, in the year of our Lord two thousand twenty-five, and of the Independence of the United States of America the two hundred and forty-ninth.
This assumes that everyone implements the same set of APIs that work in the same way.

More likely, the browser will implement some that make sense there, some browsers will implement more than others, Cloudflare workers will implement a different set, AWS Lambda will implement a different set or have some that don't work the same way... and now you need to write your WASM code to deal with these differing implementations.

Unless the API layer is, essentially, a Linux OS or maybe POSIX(?) for Docker, which I doubt it would be as that's a completely different level of abstraction to WASM, I don't have a lot of faith in this being a utopian ideal common API, given that as an industry we've so far failed almost every opportunity to make those common APIs.
War Robot Puts on Thirty Minute DJ Set in SF Nightclub
Oh yeah, I don't think your workflow is bad, you're not the first person who I've heard of give it a try. Just wanting to make sure you knew it was possible!
Side note, I really wish software would stop using EE terminology to name things. Ohm, Capacitor, Electron, etc. It muddies up search results for no good reason. Is there a reason this has become a trend lately?
Unfortunately my merging experience has been mixed. I find the idiosyncratic merge markers to be overtly futzy (why are you indenting everything by a single character?), and the conflict resolution still is quite hand-hold-y.

It's never been wrong, but I am slightly unconvinced at how well merge conflict resolution works relative to git + rerere.
"Hallucination" is just a strange scientific word that seems to stigmatize experiences that are probably far more common than anyone admits.

As a child it was understood to me that certain drugs (only the illegal ones) precipitated hallucinations and this was quite undesirable.

After a lifetime of listening to disembodied music on radio, shows on TV, and sailing through Cyberspace, how can we not question reality as moderated through pixels or remote broadcasts... even just your printed paperbacks?

Religions speak of voices/visions all the time and perhaps it's perceived as bunk when an oracle, a psychic, a shaman or a seer receives messages. But generally Western Medicine is concerned with dull-witted people hallucinating detrimental and dangerous things for them. Not people who are guided by encouraging voices or just hearing music in their head at a snap of fingers. One time after college, my mom just goes "don't you think listening to all that awful music is hurting you?" and I was like "welp, vicious cycle."

For myself, I don't remember/experience dreaming and my visual "powers" are limited to watching the world go by, but my inner voices are myriad and a rich tapestry. Unfortunately they're overwhelmingly bad and evil and pessimistic, [they had eventually come to parity with the way people treated me in meatspace,]

so I went through a series of physicians and medications as they attempted to exorcise those daemons by means of human chemistry experiment. Strangely I rarely had the experience as auditory or any sort of "sound in my head" so it's difficult to explain how they're there, and it was harder for me to accept that they were, and my intellect questioned the proposition that a pill could be a voice-killer like heroin is a pain-killer?

And just like antimicrobials or pesticides, it's not easy to find drugs that quell only the bad voices, lol.
An interesting Near Death Experience report
Be careful with essential oils. In most cases the lethal dose for an adult human is about 5 grams.
Preach it, because document/literal SOAP and WSDL are The Way, The Truth, and The Light!
"Our" models are not inferior. There is plenty of data, and the next frontier is prediction-time compute and data synthesis. Shouldn't the Chinese worry that they are depressing the publication of commercial IP?
I am reminded of this comment made only two days ago about the deficiencies of the similar Kotlin Native project:

https://news.ycombinator.com/item?id=42989406