Hacker Newsnew | past | comments | ask | show | jobs | submit | vbarrielle's commentslogin

I don't think old publications will become open access, only new ones.


They made most of their archive open access a few years ago.


No, they did not. They made it free to download, but open-access† licensing would permit third parties to legally mirror it on servers that don't block access from Algeria or Switzerland or privacy-focused browsers, and so far that licensing hadn't happened. I'm happy to see that apparently it's happening today.

______

† As defined in the Berlin Declaration 22 years ago: https://openaccess.mpg.de/Berlin-Declaration


So that's what this wording means:

> Making the first 50 years of its publications and related content freely available expresses ACM’s commitment to open access publication and represents another milestone in our transition to full open access within the next five years.

( from https://www.acm.org/articles/bulletins/2022/april/50-years-b... )

I wouldn't have understood that nuance without the context given by your comment, but in my developer mind I analogize "freely available" to a "source available" license that they took on, as a step towards going open access ("free and open source") over time. I'm also happy to see that that transition seems on track as planned.


Only up to 2000. It’s unclear if the catalog from 2000 to 2025 will be fully made open. There may be legal obstacles if the originating authors and institutions don’t consent.

I haven’t been able to find anything that states otherwise. What changes in January is the policy for new publications.


Everything is going to be open, they have been saying this for ages. The issue isnt rights, they have those, its been funding this.


What's different legally about the publications prior to 2000?


I don’t know, but they only opened the backfile up to 2000: https://www.acm.org/articles/bulletins/2022/april/50-years-b...

Or at least they haven’t explicitly announced anything in that vein for post-2000.


No, there appears to be archives of past journals on the site.


But the approach here is "write new code in rust", not rewrite.


Google rewrote Android's Bluetooth stack in Rust.


Also mentioned:

  Chromium: Parsers for PNG, JSON, and web fonts have been replaced with memory-safe implementations in Rust


Eh, I don't think it's actually one or the other. Google has taken on rewriting some more problematic components in rust. See for example:

Binder kernel driver: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

Media codecs: https://www.androidauthority.com/android-16-in-process-softw...


This is also happening at Microsoft:

> Rewriting SymCrypt in Rust to modernize Microsoft’s cryptographic library

https://www.microsoft.com/en-us/research/blog/rewriting-symc...


Yeah, there's also a freetype replacement https://github.com/googlefonts/fontations

I think they're trying to avoid rewriting things for no reason though. The things being rewritten tend to have a history of security problems or other issues that would be cause for a rewrite even if it wasn't in Rust.


That ends up being "rewrite it in Rust" because new code includes changes to existing code. A nice thing about Rust is that you can generally rewrite things piecewise there's no need to switch everything at once.


Sure, but at a macro level the approach is still to "rewrite" Android subsystems in Rust. Just slowly.


Automated theorem provers are also built around backtracking, which is absent in LLMs.


There is some long term planning going on, but bad luck when sampling the next token can take the process out of rails, so it's not just an implementation detail.


Bad counter-example, because FSD has nothing in common with LLMs.


A paper that says: "our approach is simpler than the state of the art". But also does not loudly say "our approach is significantly behind the state of the art on all metrics". Not easy to get published, but I guess putting it as a preprint with a big company's name will help...


There are places in France where the house numbers are based on the distance to the beginning of the block, but it's not that common.


Your parent post meant that a few centuries ago, the american continent was not known, so the known world could be split between east and west.


It's cute that you think your high-school level cypher is probably not seen in the training set of one of the biggest LLMs in the world. Surely no one could have thought of such a cypher, let alone create exercises around it!

No one should ever make claims such as "X is not in <LLM>'s training set". You don't know. Even if your idea is indeed original, nothing prevents someone from having though of it before, and published it. The history of science is full of simultaneous discoveries, and we're talking cutting-edge research.


The point is not that the cypher is hard, the point is that the randomish string it needs to answer the question can’t possibly be computed just from correlations from the training data. Rather, it learned an emergent, generalizable skill that it used to solve it.


I'm not sure it's very well aligned with the spirit of copyleft licenses.


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

Search: