Live data from Hacker News

Quake 1 port for Apple Watch

github.com

61–70 of 96 posts

Re: Quake 1 port for Apple Watch

#61
post #22

Earlier quoted context omitted.

Even if they don't have the claimed sleep-related benefits, surely they can't cause any harm (except for slightly orange screenshots!)

True. We can tolerate orange screenshots if it makes some people feel better. Even if it’s a placebo effect. One study found out that people using such blue light filters tend to have more screen exposure at night. Perhaps they think the filter allow them to watch more the screen, which may not be good. https://pubmed.ncbi.nlm.nih.gov/32197951/

Or do people use blue light filters to try and remedy their preexisting extra screen time?

(I don't have access to the article text and the abstract just seems to point the correlation)

Re: Quake 1 port for Apple Watch

#63
post #14

Earlier quoted context omitted.

I have some experience with ML and I have no idea what you're talking about. It kinda sounds like neural architecture search and sparse models created using weight pruning. Lots of people are working on both of those things, but IMO the latter (if that's what you mean by "Can you add weights non uniformly?") is a dead end for most use cases where you have some sort of accelerator or deep learning instructions availab…

I’m unfortunately the sickest I’ve been in years, so this will have to wait. Maybe it’s part of why my comment sounded strange. There is an idea here, and it’s a mistake to dismiss it out of hand. Adding weights non uniformly during training (not after) is the key to smaller models that outperform present day GPT3. A sketch of the algorithm is to start with a 2x2 block of weights, sum the gradients across 10 training…

You mention this technique has been shown to outperform GPT3, do you have a citation for that? Would love to read more details about this interesting concept.

Re: Quake 1 port for Apple Watch

#64

For those that prefer not to leave a mess on their file system, nor have default permissions changed and security degraded, nor have Google Analytics snooping on them, would prefer access to upwards of six times as many packages, would prefer an easy choice between binary install and full source build including dependencies built from source, and would prefer a more recent version (1.6 [1] https://www.macports.org/in…

> For those that prefer not to leave a mess on their file system ... innoextract has been available on MacPorts[1] since January 2019. Speaking of making a mess, instead of somewhat vague sniping, you could have made it clear that your beef is with Homebrew, rather than risking the impression that it's with this neat Quake 1 port. Because at the moment you have the top rated comment and it looks like you're slagging…

> it looks like you're slagging off this project rather than making a potentially valid argument for Macports over Homebrew.

It looks like you're personally attacking me rather than speaking to any argument I may have made.

> The project author probably chose Homebrew because they already knew how to use it, it works, and they were more interested in making their Quake port than with evaluating different package managers. People make these kinds of choices all the time, particularly with side projects where they only have limited time to work on them.

As I made no mention of the author nor the project, and no one but the author knows the reasons for their choices, this is a mind-reading fallacy wrapped in a straw man.

Re: Quake 1 port for Apple Watch

#65
post #13
post #11

Earlier quoted context omitted.

The first gen watch was very much like the first gen iPhone - a cool tech demo on underpowered hardware. It was supported far too long, and with its final updates it was barely suitable as a timepiece. It couldn’t handle the most basic of tasks, like receiving messages or playing MP3s on your AirPods.

That is quite surprising given that a Pentium 166MHz had zero issues playing mp3s in winamp, 1998 hardware.

Did it have a five gram battery?

Re: Quake 1 port for Apple Watch

#66
post #63

Earlier quoted context omitted.

I’m unfortunately the sickest I’ve been in years, so this will have to wait. Maybe it’s part of why my comment sounded strange. There is an idea here, and it’s a mistake to dismiss it out of hand. Adding weights non uniformly during training (not after) is the key to smaller models that outperform present day GPT3. A sketch of the algorithm is to start with a 2x2 block of weights, sum the gradients across 10 training…

You mention this technique has been shown to outperform GPT3, do you have a citation for that? Would love to read more details about this interesting concept.

they didn't say it was shown, he stated that those to be developed models would do that.

Re: Quake 1 port for Apple Watch

#67
post #48

This is so cute and cool! While I don't know, whether I want to play long Quake sessions on my watch, it shows that the Apple watch is a quite powerful compute device. Actually, it should be more powerful than most workstations of the 90ies, as it has a dual-core 64bit Processor. It also shows, how much the watch and some other Apple devices are held back by the software restrictions. Basically any software released…

Who is stopping you from doing what exactly? What would be true if you were not stopped? Who is not free to experiment and distribute? What does the huge field consist of?

Re: Quake 1 port for Apple Watch

#68
post #66
post #63

Earlier quoted context omitted.

You mention this technique has been shown to outperform GPT3, do you have a citation for that? Would love to read more details about this interesting concept.

they didn't say it was shown, he stated that those to be developed models would do that.

"Adding weights non uniformly during training (not after) is the key to smaller models that outperform present day GPT3." seems to greatly imply a certainty of result that has already been discovered. Though this commenter is familiar to me, and I know he has made silly claims in other threads throughout the years here.

Re: Quake 1 port for Apple Watch

#69

For those that prefer not to leave a mess on their file system, nor have default permissions changed and security degraded, nor have Google Analytics snooping on them, would prefer access to upwards of six times as many packages, would prefer an easy choice between binary install and full source build including dependencies built from source, and would prefer a more recent version (1.6 [1] https://www.macports.org/in…

    brew analytics off
And in general it does everything as user not su for a few years now. (Actually a good idea if using it before M1 to brew dump, remove installs and brew, then reinstall from the dumped brew file.)

https://sparanoid.blog/749577

Re: Quake 1 port for Apple Watch

#70
post #13

Earlier quoted context omitted.

That is quite surprising given that a Pentium 166MHz had zero issues playing mp3s in winamp, 1998 hardware.

Did it have a five gram battery?

How do you think it would keep BIOS settings stored in RAM between power cycles?
Post reply on HN