skysight-inc/HackerNews huggingface dataset:
Google sued by US artists over AI image generator
The Wikipedia article is correct in a pedantic way, but for all practical purposes, DNA -> RNA -> Protein is the place to start. Then you layer on the myriad complications that have evolved over four billion years.
"A patient whose heart has stopped could potentially live on the machine for months, awake, able to walk and read the newspaper. But he might never leave the I.C.U."

The only ethical problem I see is other people deciding what life is worth living.
> Should Apple be held accountable for that?

You could ask the same thing about gun manufacturers and shootings. This is a totally normative, political question.

And before you start moving the goalposts: an eye opening experience for me was considering that while you can dismiss an individual’s claims of “harms” as imaginary, what about a huge group of people? Specifically, if the authors unionized (they did) and they say that AI training on their work harms them (they do), does that not make in “real,” in a special way, the same special way that a law that comes into being via a popular vote is more “real” compared to a law that is made by fiat by a dictator? I am just trying to open your mind past these really basic sentiments and gotchas.

No matter what, AI developers must grapple with popular opinions about AI.
Nah, steady paycheck, health insurance, don't need roommates, can afford the nicer things in life. Gigging and touring is fun in your 20s, but starts to drain you. This is much better.
NixOS may be helping multiuser make a comeback, at least it is for me and my home servers. I no longer have to containerize my apps, i can have one baremetal server with a dozen+ services, all with their own users and permissions, and i don't have to actually think about any of the separation.

Plus there’s network shares. Multiple people in my home with linux PCs, each with their own slice of the NFS pie based on user perms. Sure, it’s not secure, but these are people I live with, not state-sponsored hackers.

All that said, I’d also love a simpler single-user perm setup. For VMs, containers, etc it would be amazing
Vote with your feet. Stop using Spotify. Dust off your carefully-curated collection of music files and your favorite player. Find music review blogs or internet radio stations that you like. Start buying files again. Start buying CDs again and ripping them yourself.

Spotify does what maximizes profit for Spotify, and after almost twenty years of expanding to dominate a lot of the online music space, this is not going to match up much with maximizing its likelyhood to surprise and delight your ears.
Most importantly: Null pointers still exist (yes I know they technically exist in unsafe Rust, to head off any pedants)

Also: No `?` operator
Snooping, or hijacking, the radio pathway between you and your network operator.
I disagree. Basically all Europe were in shambles 80 years ago, Communism was destroyed only 30 years ago. We still 4 wars in the last 30 years in Europe.

The accumulated wealth is long gone.
I've had these ERP struggles for the past 5 years as we've been going through our migration to Dynamics 365. The harsh reality is there are an insane amount of ERP solutions out there, and most of them are objectively terrible to work with.

You hit the nail on the head, though. We make the most progress in the migration when someone leaves the company or a new person is brought in.
I've gone into the office on Saturday more often than I care to admit.
> Isn’t that a lot of extra work? IME it’s a lot less work (and risk!) than resolving a massive merge conflict.
>
> The problems with long-lived branches all derive from the basic problem that eventually the complexity of maintaining two parallel implementations affects the work of everyone at the company.

This seems to imply that there's a choice between A) committing to the main branch, and B) long lived branches. I always work on branches, almost always with multiple commits, and then merge it into the main development branch once the feature is complete. I almost never have to deal with complicated merge conflicts.

That being said, you're talking about short lived branches. The article talked about committing directly in the main trunk/master branch; which is what horrified me.
Its super weird how america can make things half legal. In canada the responsibilities are divided up between different levels of government. None of this legal at one level but not another level bullshit.
Related:

Pyinfra automates infrastructure super fast at scale - https://news.ycombinator.com/item?id=33286972 - Oct 2022 (37 comments)

Show HN: pyinfra v2 - https://news.ycombinator.com/item?id=30999030 - April 2022 (2 comments)

Pyinfra v2.0 Released - https://news.ycombinator.com/item?id=30973976 - April 2022 (3 comments)

Show HN: Pyinfra v1.4 - https://news.ycombinator.com/item?id=26983266 - April 2021 (3 comments)

Pyinfra – automate infrastructure super fast at scale - https://news.ycombinator.com/item?id=23487178 - June 2020 (64 comments)

Pyinfra v0.3 - https://news.ycombinator.com/item?id=13862942 - March 2017 (1 comment)

Pyinfra v0.2 - https://news.ycombinator.com/item?id=12956784 - Nov 2016 (2 comments)
Out of the 15+ SWIM has been to in WA state, SWIM has never seen a dispensary take anything but physical cash (bills and coins).
I predict the rate in progress in LLMS will diminish over time, whereas the difficulty of an LLM writing an accurate computer program will go up exponentially with complexity and size. Is an LLM ever going to be able to do what say, Linus Torvalds did? Heck I've seen much less sophisticated software projects than that which it's hard to imagine an LLM doing.

On the lower end, while Joe Average is going to be able to solve a lot of problems with an LLM, I expect more bugs will exist than ever before because more software will be written, and that might end up not being all that terrible for software developers.
If you’re referring to Android, the answer is no. Android is a mobile OS. It does not run Mac or Windows desktop apps.
You obviously haven’t been paying attention as these rule making processes started literally years ago that’s how much red tape there is to get through.

And even if what you are saying was true (it isn’t) isn’t that the entire argument for democracy in the first place? “Politicians make good policy because they want to get re-elected” is how we should hope things work.
The important thing for me at least isn't he `-u apache` but rather knowing that `apache` exists as one of the installed services on this box.

In the old ways, that was apparent because of the presence of the log file.

Granted, this isn't the problem it used to be for us, however, it would come up because we'd have our services named things like `foo-ws` and knowing that `foo-ws` existed on a given box might be tricky were it not for the log files.
The last three words of the title are a clear indication of the context of the discussion. It's perfectly legitimate to discuss tech as it applies to a specific (and popular) use.
ReplyGuy was posted here six months back under a different name...

https://news.ycombinator.com/item?id=38070502
Wait, the only GPU supporting PCIe 5.0 is the NVIDIA H100 and it doesn't have RT-cores IIRC. Right?
It exists :-)

For zip archives, there are fuse-zip and mount-zip which are FUSE filesystem.

As an intermediate between OS level and application-level, there are desktop environment level: gvfs for GNOME and KIO for KDE, but they are compatible only in their own ecosystems.
> An accountant could then use a computer in service of them embezzling a serious amount of money from their employer. Should Apple be held accountable for that?

You joke, as if we didn't do exactly this -- regulate accountants and accounting software. (GAAP, DFARS, SOX, PCI DSS, etc)

And we did the same thing with say, Auto Manufacturers and automobiles (FMVSS and CAFE via NHTSA)
Is that even a problem? Any program can shell out to sudo, hence why you shouldn't set NOPASSWD in sudoers. Polkit takes in a request on an unprivileged interface, that request is evaluated in privileged code against the set of privilege rules, and then passed the proper capabilities if the rules allow. This includes a mechanism where it can, if desired, prompt a user to enter a password etc to prevent a rogue program silently acquiring root. But even in the worst case, the rogue program is not going to acquire any capabilities that you would not otherwise have as with sudo, and the breakpoint between privileged and unprivileged code is (in theory) more tightly defined and controlled.
That, and inadequate sensor diversity and coverage.
I made a career out of it and made it to regional status. If you want to pay your bills, you need to hit national level or teach music. It's a fucking grind and you naturally age out.
The entire point is that crash recovery fails because you rarely test it. By making it the one and only code path, by definition, you will be testing it all the time, so it is much more likely to work in the first place.

(The obvious counterargument being that if there are different ways in which the software can crash, this is still not an adequate defense.)
Eh, I could. But I'm quite sure that the method of switching to systemd-networkd also requires the same if not much more maintenance as simply changing the ifconfig template every few years...

I really don't care about interface configurations that much. It's an annoyance, but one that's quite easy to fix. I think introducing yet another network configuration here isn't the answer, but my linux fleet just run k8s anyway and network config on the linux level is quite simple before we get into cillium/istio/etc :}
NixOS at it again :)
Really what you'd like to see is a way to write the mount command for each file type (do one thing well) and another command to detect the file type and dispatch accordingly (probably similar to the `file` command), all in user space.

The only thing standing in the way of this today is that MacOS doesn't expose a user space file system API. You can do this on Linux, Windows, and BSDs today.

(No, file provider extensions don't cut it, Apple devs who read this, please give us a FUSE equivalent, we know it exists).
CZ also came to the US willingly as opposed to Do Kwon who went on the run.
All these are great but I was lacking more advanced features from them.

So I created openpanel.dev which is a combo of Plausible and Mixpanel.

Privacy focused as well!

Check it out https://openpanel.dev
Treating the Rust implementation of memory safety as a magic silver bullet is obviously the wrong approach. Not all classes of vulnerabilities are not built on buffer overflows or memory related issues, and in my opinion those where the low hanging fruits and this is why so many exploits were based on them.

There is no such thing as a "safe" programming language.
Some even omit the second hand which is the most technically correct version of "without complications". Also the most traditional/formal for a men's dress watch or women's watch.
Poll: Your startup made a time machine. Go back in time or forward, and how far?
OK, your startup has succeeded in creating a time machine.

You can make a single time journey from which you will not return.

Which way do you go, and how far, and tell us why....
200 years forward
200 years back
1 million years forward
1 million years back
500 million years forward
500 million years back
Yes. The first recipient of an artificial heart was tethered to a sizable amount of hardware and confined to an ICU. Now, implanted artificial hearts are regularly used.
At plastic treaty talks, sharp disagreements on whether to limit production
A Review of Upscaling Hydrothermal Carbonization
the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237

PS: https://pwnies.com/systemd-bugs/

edit, this one went on for more than a year: https://github.com/systemd/systemd/issues/6632
I really don't think this is a positive in any way, unless you oppose recreational marijuana usage.

Making it a schedule III puts it back in "Doctor prescription" territory, and since there's now a legal route to getting it, a lot of these businesses that have operated with impunity are breaking a different set of laws if it's schedule III. No doubt that laws and decriminalization statutes would need to be updated to comply federally. Banks may be able to be used, but only if you're a registered pharmacy. It's really just a lot more questions and a lot more people to profit on the chain to selling it.

Most of the world still treats it as an illegal substance. In the US we have definitely allowed popular sentiment to make it appear much less harmful than it is. I'm not sure it belongs in schedule I, but it certainly doesn't belong OTC.
I mean "systemctl status" shows all services and their hierarchy, there's also "systemctl list-unit-files" if you want to see things that aren't part of the current target (runlevel).

It's much easier in the systemd world to see the state of the system, the state of the service, and the logs of a service because it enforces this consistency.
It's not just about running as root though, but as being in a SUID binary.
The funniest thing about that stereotype is how can they simultaneously be lazy, yet also be taking all our jobs?

Stereotypes are just stupid and lazy thinking.
> the "transpiler" term is trying to draw a line where there isn't even a seam in the landscape.

I don't think you have proven that it is a seamless landscape. In fact, I think that people's definitions have been remarkably consistent in spite of their fuzziness. The heart of what I have read is that most people understand a transpiler to be an intermediate text to text translation whose output is input to another tool. The common colloquial definition of a compiler is a text to machine code (for some definition of machine code) translation whose output is an executable program on a host platform. You can make an argument that every compiler is a transpiler or every transpiler is a compiler, but I think it requires a level of willful obtuseness or excessive pedantry to deny that there is something behind the concept of a transpiler. This discussion wouldn't even be happening if transpiler were a completely meaningless term.
Superfest Glass
The Brazilian CPF (our equivalent to the SSN) goes up to eleven (literally) by including not one, but two check digits; IIRC, the first one (the tenth digit) is computed over the first nine digits, and the second one (the eleventh digit) is computed over the first ten digits.
In that statement, it doesn't really add anything.

In the statement "XYZ is a compiler/transpiler", it does. It doesn't hurt to have a word that is more specific than others. Otherwise we should just refer to compilers as an "app" :)
> Do US laws allow companies to use any random chemical without any review? Is it a whitelist or blacklist approach and should it be changed?

Yeah, pretty much. It's a blacklist unless it's a food additive in which case it needs to be generally recognized as safe [1]. Unfortunately herbicides like paraquat don't fall under that regulatory umbrella.

It's also a relatively weak blacklist so when something gets banned companies frequently switch to an close analog like when plastics manufacturers went from BPA to BPS/BPF.

[1] https://en.wikipedia.org/wiki/Generally_recognized_as_safe
To be fair that pretty much describes all patient visits to the ICU. You're not there because things are fine and you'll be going home soon, you're there because you're on death's door and the hospital folks want to keep you on this side of it.
"The overarching problem here is that we have this fear of letting people die"

This feels like a crazy thing to hear a physician say. Our acceptance of death as inevitable is a learned helplessness. Modern medicine is not even 100 years old by some accounts, and every new decade brings new "miraculous" treatments that naysayers called completely unrealistic before. There's no reason to believe that humanity will need to accept death as inevitable forever. Any theory of medicine that is based on accepting that people die is dooming itself to a primitive, barbaric existence.

The ethical dilemma goes away if these machines become more portable and 100x cheaper, a transformation we've seen many times. From keeping a cat alive for 30 minutes in 1934 to humans in 1952 to days in 1971 to months/years in the 2010s-2020s to ... what, decades? Centuries? These people are having conversations and we're saying "well we should let them die because death is a part of life" -- no, it clearly doesn't have to be. Yes, there are cost concerns, triage concerns and quality of life concerns, but those are engineering problems that we know we could dramatically improve if we actually invested significantly in this technology. I do not accept that we should not be afraid of "letting people die" -- let's be fucking terrified of it and do everything we can to stop it, please. Because everything we've seen from medicine over the last 100 years indicates that we can.

And to those who say that death must be a part of life or (insert societal problem with shaky justification here) will happen, I ask: what if the situation were reversed? What if everyone lived forever and we were facing overcrowding or whatever -- would your solution be to kill everyone nearing 100 years of age?
Sounds familiar... https://en.wikipedia.org/wiki/Authors_Guild%2C_Inc._v._Googl....
That's not what he's describing. In this case there actually is no cash or traditional ATM involved on-site. It's connected to the dispensary POS, not a physical ATM. (They often have a regular ATM like you describe also, though.)

So you do an ATM transaction, but the money goes to the dispensary somehow. I do not know how it works on the back end, but I've used it as a customer. It's lovely and can even be done over your phone.
This feels a bit like using the Rust name as clickbait. You could replace "Rust" with any other programming language and write the same article. Yes, supply chain attacks are a major issue these days. Yes, crusty old OS interfaces require a lot of attention to safely integrate with. None of these are new or specific to Rust, and no reasonable person would expect the borrow checker to address these issues.

I'm not exactly sure what this article was even about if I am honest.
It's hard to argue against the fact that access to opportunities is not evenly distributed across different states.
the wording of the questions aren't good, but the states that have recently banned it certainly seem to be catering to the 13% who say illegal under all circumstances, due to the extremeness of the actual laws passed

before Roe was overturned I would have considered myself pro life because I don't believe in late term abortions, but with the new legal landscape I've become effectively pro choice because the new laws are so extreme that they ban life saving health care that has little to do with the life of the unborn

I wonder how many are like me
In fact, if factotum were implemented on Unix along with an analogue to the Plan 9 capability device, venerable programs like su and login would no longer need to be installed ‘‘setuid root.’’ — https://plan9.io/sys/doc/auth.html
I wonder if qemu with cpu=host counts...
So far, sort of. Continuous does have the advantage of having both C# and F# (although it’s a bit crashy these days on modern iOS). I can take the code I test there and build it on a desktop system as well, but haven’t figured out how easy it is to round-trip stuff in this yet (should be as easy, if not easier, but re-using libraries might be trickier).
Yeah, it seems strange to reference the borrow checker at all... is there some notion out there that the borrow checker is a general purpose security tool that is supposed to prevent all vulnerabilities?

The article would make sense if the vulns were memory related, but this seems like an article stating that seat belts won't protect pedestrians from being struck by a car.
It has very little to do with the size and expense of the machine itself. ECMO requires 24/7 human maintenance because humans are messy dynamic meatbags, and tubes clog with clots, blood changes pH, people have an annoying tendency to move, etc. Every hospital with ECMO literally has "an ECMO team" to support the thing. It's mind-bogglingly expensive in terms of human capital.

Other people on this thread are trying to imply that these things are like artificial hearts. That is true only in that the heart is one of the things that an ECMO machine attempts to replace. We don't have anything like an implantable artificial lung.
I found myself nodding at the first 2 paragraphs, then got serious whiplash on paragraph 3. That was wild.
I only wish the technology were better ten years ago when my father in law passed away. He was on one of these types of machines, but only after he had surgery and his heart and lungs were already failing for days and his body was weak. If they could have put him on the best and newest machine of today right away, then his body could have recovered a bit before they had to operate to fix his heart valve, which was faulty.

I do have to say, at the end when we visited him before they turned the machine off, it was absolutely a horror scene with huge clear tubes with blood flowing through them and the machine was fully clear as well, I assume to let staff catch any clotting early. When they turned off the machine I almost couldn’t help but look at the machine and the blood filled tubing, knowing that my father in law was given a second chance by it even though it failed. I used to have nightmares about the scene I saw there, but now I think of how great it is that we can replace some of the most important organs with machines, even if it’s still limited to hospitals.

Morally, we should advance this tech as fast as possible so maybe next people can use these in their homes, or as a backpack or something, then on to artificial organs inside the body. The people going on these machines today are pioneers and the things we learn today will help other down the line even better.
To add, this is a part if the legal process that isn't well understood by the public, and often misrepresented in the media. It's not even well-understood by experts, frankly, but it's important to note that this is a stage in the legal appeal process where SCOTUS can choose to kind of temporarily pre-rule on a law being challenged, based on very brief arguments. It's often used in cases where failing to act on one side or another presents a serious risk of something happening before the court can rule. For example: an execution. SCOTUS can "stay" an execution, that is, prevent the execution from happening, because, well, if the guy gets killed before the trial, and then they find in his favor, they can't undo the execution.

In a case like this, it's not surprising that they found no significant irreparable harm to Texans if the law remains until the courts can rule.
Age verification vendors do this. Sites can do this discreetly and securely. Therefore, I agree it's a state commerce issue, not an amendment issue.
It's pretty tiring to pretend two different things are the same without explaining yourself.
Submission URL goes to their Fourth Quarter 2023 results. This is the first quarter 2024: https://ir.aboutamazon.com/news-release/news-release-details...
not once ever have I made that mistake. I might have woken up on a Saturday and thought it was a weekday, but well before appearing at work was that confusion cleared up. How does one do that more than once?

Even work from home is immediately cleared up once I look at my computer screen.
Oh wow I ended up reading it at millions as well. Likely because 55 billion wasn’t within the real of belief.