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

It’s two sides of the same coin. The reason those sites see scrapers as a problem is it still costs money to serve page requests to then but they are no good fit generating ad revenue.

I don’t think they were trying to make a statement about the law. Just pointing out that it really shouldn’t be a surprise to anyone that site operators would take a dim view of this sort of thing.

Half the time, if not more, its a self caused problem.

> I don’t think they were trying to make a statement about the law

Me neither; GP says: "it definitely does take mental gymnastics to think you're entitled to read a NYT article without paying", and [in my perception at least] such a statement doesn't make any sense unless the GP assumed that people who can't afford paid access to media don't deserve to know what's poppin', which doesn't seem particularly noble of a belief.


No one deserves anything created by someone else.

There are plenty news medias that are free, or ad-supported. If you can't afford an NYT sub, find out "what's poppin'" elsewhere.


> doesn't make any sense unless the GP assumed that people who can't afford paid access to media don't deserve to know what's poppin' which doesn't seem particularly noble of a belief.

Yup. There's the mental gymnastics.

I deserve to have access to the roads, but I don't deserve a free car, bus fare, free bike or free taxis.

I deserve to have access to foods, but I don't deserve simply walking in to a store and walking out with food without paying.


Well those aren’t my gymnastics, I don’t believe anything should be gated behind a payment or any other form of expectation of a favor being returned. It sure takes too much mental gymnastics to be okay with that.

Agreed. And it made a much stronger case for Rust than I’m used to seeing. For most of us non C/C++ programmers memory safety is a problem that’s more easily (not necessarily better) handled with a garbage collector.

But there are times when I really want to come to Rust from the other direction, and almost think of it as a Haskell alternative that doesn’t bring all the headaches that come from being lazy. The examples the author chose beautifully illustrate some of Rust’s virtues that lend themselves to that perspective.

(But no, we are not going to talk about higher programming. I did say “almost”.)


As someone who speaks multiple languages and uses multiple programming languages, I would say it’s much more true of programming languages than it is of natural languages.

Spoken languages have the odd idiom that doesn’t translate well, and certain languages express certain ideas more or less succinctly. But it’s not like Chinese’s lack of verb tense makes it harder to think about how things are happening in time. The concept still exists, it’s just expressed differently. But not so differently that I can’t translate decently well on the fly.

Programming languages have much more variability in what kinds of concepts they can easily express. In Smalltalk I’m going to use dynamic dispatch to express damn near everything because it’s just about the only sane way to do domain modeling. In Standard ML I’m going to lean instead on algebraic data types and pattern matching. Those tend to lead to very different ways of breaking down a problem. In Scheme I don’t have either built in but both are easy enough to implement as a library, so I’ll freely choose whichever option seems most appropriate to the problem at hand. In assembly language I’ll avoid any such abstraction altogether because, while I could probably implement versions of both, it would be a total PITA and probably result in incomprehensible code. And translating among any of them is likely to be the work of multiple hours or even days.


Things have changed so much since then. In the 80s compilers didn’t optimize as well, and generally couldn’t because of resource constraints on the computer. The limited power of 1970s and 1980s computers is all over the design of C. Header files are meant to reduce the memory needed to compile programs, for example.

The last time I needed C’s power to fit something into memory and compute limitations, it was code running on a microcontroller and better systems languages like Zig and Rust weren’t a thing yet.


> Header files are meant to reduce the memory needed to compile programs, for example.

That is not very accurate. Back then, C was compiled file by file and the outputs from those separate compilations were linked into the final binary (each C file is a translation unit, a term still used today). Header files were reprocessed for each new translation unit that included them, they did not save memory for compilation. They saved some memory on disk storage because shared bits of programs were extracted to a common file, but that savings was also not their purpose.

The purpose was to extract the shared bits and reuse them to prevent errors and reduce duplication. Imagine having to recreate the contents of some or all of stdio.h at the top of all your C files that import it. Now you have hundreds of places to update if that library changed, or hundreds of places to make an error in one of the function specs.

Saving memory was not a benefit, nor an intended benefit of header files. The header still has to be read for each translation unit and processed so there are no memory savings in compilation (back then) from using them. Now, today there can be some with precompiled headers, that come much later than the invention of headers for C, though.


That explains a lot. Why do we still have header files? I suppose the C people wouldn’t let us change it at this point, but it does seem quite pointless now that we have computers with 10,000x more memory.

It would be a very disruptive change. For example, you can’t do away with header files without also rethinking how shared libraries work, too. Which then leads to hairy questions like, “Where do you put a library’s preprocessor macros if not in the .h file?” Any such changes you make would need to be coordinated with operating system vendors, since it would touch bits of how shared libraries work that are OS-specific.

And we already have header-only libraries, which are often close enough.


Empty string is not a valid alternative to null because the empty string is still a string. There are valid cases where “this value is not set” and “this value is set to an empty string” mean two different things.

There are even more valid cases where “this integer is not set” and “this integer is set to 0” are different things.

It’s also a type safety concern. Using sentinel values is comparable to the “billion dollar mistake” version of nulls because it creates a special value that implicitly exists and is not part of the variable’s type definition. This means the compiler can’t help you remember to check it. You have to just remember, and forgetting is a bug. With optionals (including opt-in nullability like in Kotlin), on the other hand, the compiler knows when you do and do not have to worry about a value not being present, and can raise a compile time type error when you forget.


I have always had a love/hate relationship with unit tests. I love them for all the obvious reasons. I hate them for all the times I read a test suite where 80% of the tests could have been eliminated by just improving the design of the system under test so that error condition wasn’t possible in the first place.

It also speaks to why I remain skeptical of relying too much on coding agents for code review. They are still pretty iffy on implementing the right thing, and even worse at detecting when a PR didn’t implement the right thing. Ignoring that reality is how you do like Anthropic did and increase your rate of merging changes from 2500/day to 30,000/day without a corresponding increase in the rate at which you deliver useful work product.

OpenAI did a data dump of work in progress, leaving it to the mathematics community to make sense of it. I don’t think they claimed that there were Lean proofs for everything? Did they warn that some Lean proofs were incomplete?

Why did they stop in the middle anyway? Was there a justification given for that?

The cynical answer is that their primary goal was never to meaningfully contribute to mathematics. It was to pick some low-hanging fruit for the marketing department. So they did the 10% of the work that generates 90% of the buzz.

It’s more likely that their goal was internal research, to test a new LLM before releasing it. But, then they had something that mathematicians would be interested in, so they threw a data dump over the wall. It’s a rather rude way to do it, but this isn’t a company that particularly cares about the things that mathematicians care about.

OpenAI no longer needs to do anything to get publicity. There are some organizations that are so famous that everything they do is newsworthy and anything they do will be covered whether they like it or not. Remaining low-profile is no longer an option.

The people claiming that everything is marketing haven’t come to grips with the inequality of fame.


This would be plausible except for the fact that there was a press release.

There was a blog post. It's the bare minimum when announcing something to the public, not a sign that they're going to use it to promote themselves in a significant way.

There's no "low profile" for a company like OpenAI. Either you let the public (including the press) know or you don't, and keeping the results secret would be bad.

If they just told a few people, it would leak eventually and then you'd have articles based on rumors, along with accusations of a coverup. For an example of the difficulty, look at what happens when people try to do coordinated disclosure of a security bug.


The more likely answer is because that is what the agent decided to do given inconsistent instructions. No one read what it said about what it was doing before releasing the presser.

Worth pointing out, though, that that was hardly a disinterested assessment.

It’s selection bias. It’s always been selection bias.

The “10x” developers I’ve known (and been) were all incredibly effective at snagging the work that they personally were most able to do quickly, and shirking the rest.

That’s not necessarily all the difference. But I’d estimate they would maybe be at most 2x developers if you remove their ability to avoid the proverbial 10% of the work that takes 90% of the effort.

AI coding intensifies this effect. And it also helps explain why people’s amazing success stories for personal projects don’t seem to translate to business ROI. For a side project I am in complete control over design and scope, have no customers or stakeholders to keep happy, etc. So I easily - and mostly unconsciously - tailor what I’m doing to what the coding agent can do well, and quietly drop the rest. I don’t have that luxury at work.


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

Search: