sloum

While he only did it, to my knowledge, for one book: Stephen King is the only major writer I have heard of to write a full novel with pen and paper (the novel in question was _Dreamcatcher_), which is really interesting to me.

Agreed, it seems writers that also code have all kinds of different workflows. I end up using (x)html and doing print stylesheets and rendering pdf for print using weasyprint (works really well, and they have sample stylesheets on their website that are a good starting point).

I like Erewhon. Nice font.

I definitely get it not being everyone's thing. But I really really love Moby Dick. It is so funny! My wife kind of prepped me for viewing a lot of it as comedy or humor, especially toward the beginning, and viewing it through that lens absolutely helped. The language is old enough that you sometimes have to realize that the author is being funny, but it is there. I really loved all of the information about whales... that is just not true. Wasn't even thought to be true at the time.

Out of curiosity: why use Gitea for personal projects when you can put up raw git repos and run the git-daemon that comes with git? Super lightweight, really functional. Add _cgit_ if you need to be able to view the repos online. Simple and does not require upkeep like gitea (which seems to break with every update and is really heavy).

I have had the same $5 VPS for many years (10-ish?). I mostly use it for websites. As of last night I have 13 websites running on it (down from 18). Most of them probably don't _need_ to have the uptime that the server gives them. I have also done some git hosting on the server, but not so much lately. It is nice to have the server and be able to putt stuff up/take stuff down, self host, write my own tools (I run a pastebin and a kanban board for organizing aspects of my life and remembering things). It works well for me and my use cases. I don't run anyone else's software and I don't use JavaScript for anything, so maintenance is minimal. Occasional Debian updates. It has stayed solid.

Congrats to the team! There is some great stuff in this release. A few of the items have been things preventing me from daily driving Haiku (I have it on a thinkpad for fun sometimes), so I'm excited to spin this up.

Meh. The project died for me when they started using LLMs for development in the first place.

You could add features to make it a PWA and explain to users how to save it t their desktop. I used ProtonMail for years that way (I do not have a smartphone anymore, so no longer do so).

Yes!! This!! I wrote a shell awhile back and was pretty happy with it... but could _not_ get job control to work quite right. It was a big pain.

Found it:

> “Covered application store” means a publicly available internet website, software application, online service, or platform that distributes and facilitates the download of applications from third-party developers to users of a computer, a mobile device, or any other general purpose computing that can access a covered application store or can download an application.

To whittle down the the important part:

> “Covered application store” means > any [...] general purpose computing that can access a covered application store or can download an application

If you have a network stack, you can 100% connect to a "covered application store" and thus the OS falls under the scope of the law.

I believe that if you have a network stack and can download files from the internet--which would include software--that it counts. I don't want to re-read to find the part, but they seemed to imply that any system where you could download software from the internet and then run it.

From the bill:

> "Covered application store” does not mean an online service or platform that distributes extensions, plug-ins, add-ons, or other software applications that run exclusively within a separate host application

There is a reasonable argument that a linux distribution is, itself, a host application. This is clearly an argument against their intention... but makes perfect sense to me. With this argument, the law does not apply to pretty much any environment where the applications are scheduled and run by a supervising process, at least by my reading.

> "vile machines raping the planet" is obviously vitriol

Well, I still think you are giving an opinion and I am giving mine. I disagree with your opinion. Mr. Pike is making a statement of fact. I do not consider it particularly vitriolic. You may consider it hyperbolic and I could understand that (even if I do not agree with it).

> Abolish it rather than continuing the current path, strict prohibition on any creative endeavor, and being extremely skeptical about anything other than direct language translation

...is not extreme in the slightest. If something is wrong (either morally or as a good and viable path forward) it only makes sense to cease following that path. I posit that it is not possible to creatively use this technology. It can only serve to steal the creativity of others. Prompting a machine to make something out of misc. parts for you does not make you creative. Nor does it make the machine creative. But for us to agree on that we would have to better define either creativity or art (spoiler: my view is that only sentient beings can be creative or make art). I suppose I could agree that the developers of an AI system are being creative, but certainly not the users. Being skeptical is always a good position with something new until shown reasons to not be skeptical. Positions are allowed to grown and change, s tarting skeptical about something is absolutely a reasonable position to start from. I see none of your statement as being evidence of extremism at all. Sounds like exercising sound, reasonable judgement.

Well, I couldn't disagree more with you: being anti-AI is absolutely not an extreme position. You are living in a bubble if you think it is. "Fervent anti-AI territory" is a good position, not hate speech.