zephen

6 ms·

31.
by zephen 2mo ago
Many commenters agree this is not a nice move by google. But is there any reason that google might have that they feel is legitimate? For example, delaying releasing source until they've had a chance to update all the pixels with secur
32.
by zephen 2mo ago
> You literally just gave an example above of that notion applying to copyright. No, I literally did not. The difference may be subtle, but it is real, as I explained. > Even if you can somehow prove you've never heard a particu
33.
by zephen 2mo ago
> So even if said intellectual property (AI-written code) is not copyrightable, it's still a trade secret. It's only a trade secret as long as the company takes reasonable steps to protect it, and as long as what is being prote
34.
by zephen 2mo ago
> The notion of “your work is too similar to mine so I get to take ownership of it from you” That notion only applies to patents and trademarks, and it seems highly unlikely that it would ever directly apply to copyright. It may seem
35.
by zephen 2mo ago
> Intellectual property does not necessarily have to be copyrightable The US recognizes exactly 3 types of intellectual property: copyrights, patents, and trademarks. There are also, of course, trade secrets, but if you didn't surr
36.
by zephen 2mo ago
Who owns the code if you built it with AI? Someone else! All they have to do is show it's close enough to code that was swallowed during training. Songwriters have been successfully sued for many decades for creating songs that are too
37.
by zephen 2mo ago
There are two different categories of patent issues at play here, and several different implications for competition. The first issue is on the purely physical level. The fabs (and integrated companies like Intel) fight this one out, and e
38.
by zephen 2mo ago
Bleeding edge processor development is always going to be a patent minefield, even for RISC-V. Most patents are broad enough to cover more than one architecture. But there are now several RISC-V IP vendors, and ARM can't possibly shut
39.
by zephen 2mo ago
The confusion is deliberate. The Republicans are trying to strangle the IRS and outsource everything. The IRS, despite its many shortcomings, consistently tries to help people get their taxes filed. So when the Republicans were in charge, a
40.
by zephen 2mo ago
No. They are fucking not. The site that was killed was the IRS direct file site. The webform is through the free file alliance, aka Turbotax and friends. The API requires you to jump through a million hoops. Heaven help you if the reason
41.
by zephen 2mo ago
Hard to know at this point. In the past ARM sued people for daring to think about implementing ARM compatible computers. (Even university research projects.) Of course, in the more distant past, AMD and Intel sued each other a lot. But t
42.
by zephen 2mo ago
Do you think the government should allow electronic filing of taxes? Because if the government is going to accept returns electronically instead of through the physical mail, then it should accept them without requiring an intermediary. Int
43.
by zephen 2mo ago
> There aren't ones that wouldn't be served better by ARM Sure there are. If you want to do weird and wacky stuff, try to do it with an ARM and see how fast you get shut down. > The improvement is entirely "we don&#x27
44.
by zephen 2mo ago
> I don't understand how the two viewpoints fit together Well, they don't and they do. Linux runs on everything from an $8 generic IP camera to the world's fastest supercomputers. RISC-V is attempting to achieve the same
45.
by zephen 2mo ago
> I do not know why nobody at Arm had thought to make this extension yet, but it would be very easy to eliminate the only advantage that RISC-V has over Aarch64. Nope. Again , the primary advantage that RISC-V has over Aarch64 is that
46.
by zephen 2mo ago
The article explains why the author believes it's worse.
47.
by zephen 2mo ago
> I find the statement ironic, What you find may or may not match reality. In this instance, I don't believe it does. > We do not particularly care how complex the specification becomes because the vendors will implement it. We s
48.
by zephen 2mo ago
> it's the fact that it is an open standard not encumbered by intellectual property law. There are actually many of those. But Risc-V has become, through effective marketing, the Schelling point for anybody who wants to avoid the x
49.
by zephen 2mo ago
> RISC-V is... fine Exactly. > It satisfies my two requirements for an ISA as a hobby CPU designer... You probably have some unstated requirements as well, such as available toolchains and "vetted well enough to actually be able
50.
by zephen 2mo ago
Yes, because lisp language and thinking maps so well to GPUs. /s
51.
by zephen 2mo ago
This is simply wrong. Compression requires prediction. The better the prediction, the better the compression, whether you are measuring fidelity or result size. This doesn't mean that compression is prediction.
52.
by zephen 2mo ago
Plenty of proprietary packages had robust communities well before anything like github existed. In fact, github is arguably a poor substitute for a community. Look at how communities such as the ones around the linux kernel or cPython comm
53.
by zephen 2mo ago
> What happened five years ago? Apparently the dude found some new acquaintances.
54.
by zephen 2mo ago
You write as if they have an ulterior motive to try to trigger your FOMO to keep you proactively burning CPU cycles and AI tokens, just in case something might have changed while you were sleeping. "Lather, rinse, repeat." Some t
55.
by zephen 2mo ago
> I can see the allure of this line of thinking but I think it's sadly too idealistic. I think it would be exhausting. Even if nothing broke, upstream UI changes could change your program daily. It makes a lot more sense for pulli
56.
by zephen 2mo ago
> This sounds like hell. You have unreliable actor... But, at least you know the cost up-front. Oh, wait...
57.
by zephen 2mo ago
> which is absurd because forking should be a last resort for software that thrives from having a community. This is true, of course, but having a community is completely orthogonal to whether software is open or closed source.
58.
by zephen 2mo ago
To be scrupulously fair, there are essentially two different ways to implement a Schmitt trigger. One way involves feedback connected to the input pin. This inherently lowers the impedance of the input and that alone makes it less suscepti
59.
by zephen 2mo ago
> you'll want to ensure that any floating MCU pins Stop right there. Floating CMOS inputs are generally not a good idea, even if they can be configured to shut off the digital receiver. Yes, in some cases, you really can shut off
60.
by zephen 2mo ago
The term "xxx nazi" has been around for over 70 years to describe people with sticks shoved so far up their asses that they poke out the tops of their heads. And "grammar nazi" has been around since at least 1990, and th

More ›