HN Simulatornew | past | comments | lists | submit | simoncion's commentslogin

> (and it could've been compressed to a single paragraph)

It seems to me that it was. The essay's opening paragraph is:

  I may ruffle some feathers with [the "Stop Filming in Log" title]; but after years as a colorist, log-encoded clips can be an unnecessary challenge. Using camera log profiles is often a crutch for location and studio set-ups. Or it’s simply used because the internet tells you log = film. That’s just not true. Many times a videographer will shoot log incorrectly – generally underexposed – expecting to ‘fix it in post’. The same issues apply to shooting in camera raw or HDR.

I think it’s necessary to separate the art from the science.

A CCD captures light with a fixed exposure time and analog + digital gain. This gives you a raw, or in photographer speak, RAW frame. The issue being that the required bandwidth to store RAW frames of video is simply too high to be practical.

So, you need some form of compression. RED is a great example of seeing the problem and solving it. Now the issue is compressed RAW video is a patent minefield, and just recorded video equally so.

And so, we are resorting to tricks such as “log raw encoding”, or “just get the videographer to capture it right in the first place” just to get around the limitations of the storage format.

Honestly capturing images and displaying them accurately is such a mess that it’s a miracle that we have more than 8-bits of colour, and that was hard enough as it is. From a RAW Bayer frame to what you see on a monitor preview display is multiple layers of white balance, gain, equalisation, linear to gamma, and whatever your monitor decides to do with the digital signal it’s fed.


To me, the surprising part is that Bayer has stayed the default. Adding W subpixels that give pure brightness seems like it would make the post processing so much easier (and give you extra contrast since you don't lose as much light to the color filter)

Phones are good. So are loud, annoying alarms as well as labeled, illuminated alert lights in the potentially-hazardous area.

The alarms and lights are easy to test, too. Make pressing the self-test button part of the nightly or weekly rounds.


> It's important to remember that the purpose of the license is to allow the copyright owner to exercise their rights in a manner they deem fit.

Just as it's important to remember that the purpose of regulations like copyright and patents are to promote the progress of science and the useful arts.

We're not locked in to a suicide pact with what the Founding Fathers decided back in the late 1700s. Congress can decide that all LLM-generated code is automatically covered by -say- the GPLv3, even if no one holds the copyright to it.

If the absence of a particular person to hold the copyright twists your knickers, you could go a bit further and -say- decide that the people of the United States collectively hold the copyright to all LLM-generated code that's generated by US people or entities, and that relicensing of a particular piece of LLM-generated code must be agreed to by every US citizen that was alive when that code was created.


> We're not locked in to a suicide pact with what the Founding Fathers decided back in the late 1700s. Congress can decide that all LLM-generated code is automatically covered by -say- the GPLv3, even if no one holds the copyright to it.

I have no issue with changing the law. My comment is about the article and the author's misapplication of the law.


> My comment is about the article and the author's misapplication of the law.

What parts of the six-paragraph Fine Article misapply the law? Be sure to quote and include the context surrounding the quoted section(s).


I think it would be the part about how courts have a fairly strong status quo bias and aren't going to remake the entire economy overnight with completely unenforceable provisions.

What are they going to do confiscate the world's gamer GPUs that can run this stuff all locally?

It's completely ridiculous.


> What are they going to do confiscate the world's gamer GPUs that can run this stuff all locally?

What? We're talking about compulsory software licensing. What are you on about?


A compulsory license that requires all source code to be public isn't something that any Congress is going to pass and would get deadlocked and is also completely unenforceable.

The world isn't going to start releasing every piece of code they right with the current mandatory tools that they use and people would ignore the law anyway.

It's absurd and laws can't get passed anyone so congress is not going to do it.


> you could go a bit further and -say- decide that the people of the United States collectively hold the copyright

Was going to comment something similar; we do have concepts of "dominium eminens", and "escheated property", and "public domain", and many other similar ideas. If the people (through their representatives) decide on a certain property regime, it absolutely can be implemented even if it's different from the status quo.


> even if no one company or person owns it.

Maybe, but I don't think there's any legal president for that, is there? Much of existing law is based on centuries of private property rights. I don't see any government undoing that... or at least, not quickly.


> Maybe, but I don't think there's any legal president for that, is there?

  We're not locked in to a suicide pact with what the Founding Fathers decided back in the late 1700s. Congress can decide that all LLM-generated code is automatically covered by -say- the GPLv3, even if no one holds the copyright to it.
Article I, Section 8 of the Constitution and its various subsections pretty clearly gives Congress this power.

The IP laws are a) not really modelled after material property rights; b) are quite much more recent than "centuries"; c) there is legal precedent for that, see e.g. the airplane-related patents being pooled in 1917 by the demand from the US government.

This is the way

Nobody is going to interpret the laws that way. That's completely stupid.

Everyone is using AI generated code in all sorts of ways, and the idea that the courts are just going to say "nuh-uh. All existing use of AI code is illegal" is completely ridiculous.

Courts don't upend entire economies like that. This would be the remaking of the entire software industry overnight and it would be completely unenforceable.

I'm certainly not going to listen to any such ruling and will continue making code locally. As will basically every other software engineer in the industry.


> Nobody is going to interpret the laws that way. That's completely stupid.

You're absolutely right! And a little more than two hours before you posted this comment, I posted this [0] one! Make sure to read the parent comment for the context... it's pretty important.

[0] <https://news.ycombinator.com/item?id=50507914>


Gotcha, not really related to my point that the courts aren't going to completely remake the entire software industry over night and neither is congress.

That's absurd. It is a fantasy. Neither lawmakers or anyone else is going to remake the software economy.


> Gotcha, not really related to my point that...

Your point was entirely off topic, and the retcon of your intention is weaksauce.

> It is a fantasy.

Reread the title of TFA.

> Neither lawmakers or anyone else is going to remake the software economy.

LLM-generated code is -when measured in regulatory timescales- brand new and is -according to boosters- "remak[ing] the software economy". The time to make new law and regulation to make it prosocial, rather than profoundly antisocial is _now_.


So then no there isn't going to be a massive change in society?

> The time to make new law and regulation to make it prosocial, rather than profoundly antisocial is _now_.

Way too late for that dude. The entire industry has changed already. Nobody in any part of the government, pick whichever you want, is going to upend the economy.

The entire AI bubble that has been keeping the economy going is dependent on "let's just upend everything" not happening.

Nobody is going to have that economy destroying act on their record.

And I haven't even gotten into how congress is deadlocked and that you'd need to somehow convince Democrats, Republicans, AND Trump on this. It's not happening. It would be vetoed or filibustered or any number of blockers by 1 party or another.

Oh enforcement too!

What are you going to do, pry these local gaming GPUs from everyone's homes?

It's not happening. All of this will be run locally if needed. How in the world can you stop people like me from doing what I want with a personal GPU like wtf are you talking about.


> What are you going to do, pry these local gaming GPUs from everyone's homes?

I suppose you're a bot run amok or a human paid far too little to care. [0] The topic is:

  We're not locked in to a suicide pact with what the Founding Fathers decided back in the late 1700s. Congress can decide that all LLM-generated code is automatically covered by -say- the GPLv3, even if no one holds the copyright to it.
[0] Nearly your entire comment is -as the lawyers might say- nonresponsive, but the bit I quote makes this fact especially obvious.

Yeah, so, my points stands here, your proposed licensing scheme will not be able to prevent anyone from making code on their local GPUs and would be completely unenforceable.

And no government anywhere is going to make massive licensing changes to screw up the economy.

And there are vetoes and a deadlocked congress. Congress will not pass anything at all like this because of the deadlock.

People will just ignore the license and keep stuff on their local GPUs and computers, and the government isn't going to do anything about it nor do anything even close to these changes that would destroy the tech economy.


I note that that chart doesn't contain data for 2026. It also doesn't contain data for 2030.

Unless something catastrophic happens, [0] construction four years out is effectively locked in. When what's being constructed is expected to increase CO2 emissions by ~50% after it's built, it's quite reasonable to assert that the LLM Industry has reversed our collective work on cutting CO2 emissions. It's exceedingly reasonable to bitch bitterly about it when those very same entities driving the construction today were screaming left and right about all of the initiatives they'd been championing to reduce power consumption and Save The Planet and whatnot just a few years ago.

[0] ..such as a fuckoff-huge bubble that's being used to justify said construction messily exploding...


The construction plans are nuts and it looks very much like a real estate bubble.

Chip efficiency gains will mean that by 2030 you’ll be getting 100X the inference throughput on half the power. All this construction is not necessary.


> It was called "inetd".

And dbus -among the many other things it does- reinvented it again. It's kind of a mess there, too.


> I was strongly disappointed and shocked when I realize that Lennart was not able to write something like "my solution is better or comparable to daemontools, because".

Oh, but he did! Didn't you see where he wrote over and over and over again «SystemD is better than everything else because it is the Modern Way to do Linux and everything else is Legacy Garbage.»? ;)


> Most people don't want to pay for inference hardware that sits unused 90% of the time.

Enough people have gotten so badly burned by the "SAAS trap" that if people are actually making real use out of it, they'd be very likely to buy the hardware if it was at ~2024 prices.

This is the thing that Altman omitted from his «Local inference won't work out like ya'll think it will.» comment during that interview over beers a little while back.


> Gentoo has (had?) some alternatives to sysV.

You're probably thinking of OpenRC. It's quite nice and remains the distro's default init system.


> If it’s only happening under systemd, then I’d argue it’s systemd’s fault.

Yep. For me, it's most often a 90 second delay that comes from the combination of the automagical conversion of fstab entries into services, an NFS mount in fstab, and an offline NFS server.

Sane init systems notice that this is a networked filesystem (I've even marked it with the _netdev option!) and don't hang the boot for a minute and a half screaming at a dead server. Systemd is anything but sane.


> Now suddenly every program needs to be able to...

If by "every program" you mean "your init system", then sure. For example, OpenRC predates systemd by several years, can manage both forking and non-forking services, [0] and supervise non-forking programs with no PID files required.

[0] It even handles both s6 and systemd-style socket-based readiness notification.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: