1,743 karma · joined October 28, 2021
For example, the all-zeros file is a member of the set of all random 3 megabyte files, and it would certainly be possible to compress that, if by great good fortune you were lucky enough to receive it - albeit something that is unlikely to ever happen in the possible lifetime of the universe, given current physical theories.
Is it possible to quantify this idea of a 'weak' file more accurately?
Basing it on an open protocol, so it doesn't become a single point of failure, was a clever idea that allows the idea to survive the demise of any single organization.
May there be many more such anniversaries.
You could, of course, run a local wireless IP layer and use this to route, but peer-to-peer wireless has well-known scaling problems.
Still, it looks like a very interesting and reasonably well thoughout out idea.
Implementation diversity is absolutely essential to an open-standards based Web, and right now the Web is pretty much the only open channel for pretty much all of human discourse.
Having said which, Mozilla is in real trouble, and desparately need to sort out their business model.
None of which is to discount the furture potential of LLMs, or the amazing ability they have right now - I've solved other simpler problems almost entirely with LLMs. But they are not a panacea.
Yet.
But what Marcus seems to be assuming is the impossibility of any fundamental theoretical improvements in the field. I see the reverse; the insights being gained from brute-force models have resulted in a lot of promising research.
Transformers are not the be-all and end-all of models, nor are current training methods the best that can ever be achieved. Discounting any possibility of further theoretical developments seems a bold position to take.
Surely the referees must have raised this at the review stage?
https://www.nationalarchives.gov.uk/
or get in touch with the enthusiast community, people like
https://www.nathanmediaservices.co.uk/ceefax/
You should ensure whoever you give them to can give you a binding commitment to use for legitimate archival purposes, and not just acquire them and sit on them for copyright reasons.
A better system would enable true constraint-based parametric design, but I think doing so would involve an order of magnitude more complexity in the implementation, and quite probably infeasable compute times.
Software development, on the other hand, took merely decades, and would be much faster to reboot, as computer language and compiler technology can be easily reinvented given information in printed books. If anything, I'd suggest an emphasis on having paper copies of books on classic programming languages and computer history widely distributed in paper libraries, and making sure that paper libraries are not displaced entirely by electronic ones.
I'd consider archiving full documentation of pre-existing basic technology, rather than rolling your own; a widely distributed complete set of printed books, circuit diagrams, manuals, source code and assembly code listings capable of reproducing something like BCPL on PDP-11 might be a better choice; creating something like a PDP-11 class computer with valves or relays would be eminently feasible.
Missiles, bombs and artillery are one thing, but personalized silent assassination out of nowhere, at any time, without a traceable attacker you can pin down or counterattack, is quite a different threat.
Alas, doing this with quadcopters and winged drones is really not difficult to do, for anyone with a reasonable computer science education - or come to that, a particularly bright teenager somewhere in the world. NVIDIA even market their Jetson boards as being suitable for "smart drones": https://developer.nvidia.com/buy-jetson
Of course, there's a difference between a DIY demo and a fieldable weapon, but it's one of productization, not the Manhattan Project.
I'm quite surprised that at least one of the participants in the various current wars haven't done this already. They've certainly got sufficient incentive to do it.
I'm not as worried about the Black Mirror robot dogs, current robot dogs seem far less practical to weaponize compared to suicide/surveillance drones, which are already cheap and being used as weapons already sans the autonomy.
Perhaps one reason is that OSS system programmers are washing their dirty linen in public; not a matter of "many eyes make bugs shallow", but that "any eyes make bad code embarassing".
Just for example, I'm planning to make one of my commercial projects open source, and I am going to have to do a lot of fixing up before I'm willing to show the source code in public. It's not terrible code, and it works perfectly well, but it's not the sort of code I'd be willing to show to the world in general. Better documentation, TODO and FIXME fixing, checking comments still reflect the code, etc. etc.
But for all my sense of shame for this (perfectly good and working) software, I've seen the insides of several closed-source commercial code bases and seen far, far worse. I would imagine most "enterprise" software is written to a similar standard.