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

Said human would likely not be able to create a clean-room implementation of any of the codebases they worked on.


That's exactly the problem. Digital natives have, by and large, grown up with computing devices which try their best to be the opposite of general-purpose: their skills are siloed to the few apps they rely on, and e.g. files, keyboard shortcuts, the command prompt are not part of the "API" they learned.


> They know what a file is, they use & manage files more than any other generation prior.

Unfortunately, they don't.

They might have had a computer in their hand for hours each day, but they barely know anything about it. The ones who do tend to be those who grew up playing on PC, as opposed to console or mobile, because the latter - despite falling under the "digital natives" aegis - are really shockingly ignorant of even basic concepts.


> The timing is also suspicious, shortly after publication of this report: https://www.reuters.com/business/media-telecom/smartphone-ma... which forecasts declining smartphone sales meaning less devices for this OS to run on.

Why would declining sales of new smartphones have anything to do with PostMarketOS, which only supports phones more than half a decade old?


PostmarketOS doesn't exist in a vacuum. It’s the final stage of a device's life cycle. If the initial sales of new devices decline, the pool of available hardware for enthusiasts to tinker with in five years will be significantly smaller.


Yes. In five years, once the PMOS devs manage to get a 2025 device in working state, they might have less devices to play around with, so there could be an indirect effect on the project.

What I struggle to believe - what I don't believe - is that there any sort of connection between the report about likely declining sales and PMOS' announcement.


pmOS does support recent phones, provided that they can be bootloader-unlocked - and that's only a few brands these days.


Right now, their wiki page on device support [0] lists zero actual devices as "fully supported":

> These are the most supported devices, maintained by at least 2 people and have the functions you expect from the device running its normal OS, such as calling on a phone, working audio, and a functional UI.

> Besides QEMU devices, this is currently empty. The ports we had here earlier weren't as reliable as we would have liked. We plan to add new devices here with a higher standard.

The most recent smartphone in the Community section of that page is the Fairphone 4, released half a decade ago, in 2021. Pixel devices can trivially be bootloader unlocked, but that doesn't make the work that goes into supporting them much easier: the latest device in Testing is the 6a/6 Pro, from 2022, and its device page lists all the features but the most basic (touchscreen, flash, internal storage) as "Untested".

[0] https://wiki.postmarketos.org/wiki/Devices


It refers to evaporative cooling of group belief - https://www.lesswrong.com/posts/ZQG9cwKbct2LtmL3p/evaporativ...


Not quite - the chip the article refers to is the 47L04 [0], which is "just" NVSRAM built out of a RAM + EEPROM. I do agree on FeRAM being cool, though - I have a few I2C chips en route, and I can't wait to get my hands on them.

[0] https://www.microchip.com/en-us/product/47L04


You could also consider MRAM. Which is available in larger sizes - up to 4 Mbit on SPI bus in the MR20H40, and 128 Mbit in EM128LXQ (but it gets unreasonably expensive when this big).

https://www.everspin.com/family/mr20h40?npath=259


Thanks to both of you for bringing FRAM onto my radar!


People who do not want to read and trust the slop that whatever LLM du jour is regurgitating after calling out to said search engines.

Humans are already unfortunately prone to bullshitting and bloviating, but they are also used to dealing with other humans: there's no need to add an additional layer of both from a black box which does not behave like one.


Setting aside general-purpose LLMs, there exist a handful of models geared towards translation between hundred of language pairs: Meta's NLLB-200 [0] and M2M-100 [1] can be run using HuggingFace's transformers (plus numpy and sentencepieces), while Google's MADLAD-400 [2], in GGUF format [3], is also supported by llama.cpp.

You could also look into Argos Translate, or just use the same models as Firefox through kotki [4].

[0] https://huggingface.co/facebook/nllb-200-distilled-600M [1] https://huggingface.co/facebook/m2m100_418M [2] https://huggingface.co/google/madlad400-3b-mt [3] https://huggingface.co/models?other=base_model:quantized:goo... [4] https://github.com/kroketio/kotki


You can't say "$TRAIT is binary" when you follow that up with "$TRAIT can only be true, false, or sometimes something else". That's not a binary trait by definition.


They would just move to calling the procedure a violation of the "natural order" - "Lovecraftian horror", "Frankenstein arrangement", "something Mengele would do" - argue that it is akin to rape, create conspiracy theories about uteri being stolen, and/or invoke "Think of the children!"

I saw all of that already. Some of it in this very thread, some of it on the defunct /r/GenderCritical: I remember someone proposing committing suicide by volcano to keep her uterus out of "male [sic] hands".


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

Search: