demesisx

joined 1 year ago
[–] demesisx@programming.dev 2 points 1 month ago

Edited. Good call.

[–] demesisx@programming.dev 13 points 1 month ago (1 children)

I got you, fam(ily). It has a real smooth, simple ring to it. ;)

[–] demesisx@programming.dev 142 points 1 month ago* (last edited 1 month ago) (10 children)

Temu: contribute to the irreversible heat death of your own planet just to save some money on useless, piss poor quality trinkets created out of cancer-causing, hazardous materials using slave labor coupled with unfair market practices that are then shipped thousands of miles over the oceans using the world's worst polluting container ships.... like a billionaire.

That should be their slogan.

edit: added slave labor, unfair market practices edit: added hazmat

[–] demesisx@programming.dev 16 points 7 months ago* (last edited 7 months ago) (1 children)

Trains are awesome and I fully support them but let's not be idealistic here and pretend that true self driving cars will never happen.

Edit: jokes on you! I made a grammatical correction that makes your reply IRRELEVANT. 😉

[–] demesisx@programming.dev 127 points 7 months ago (13 children)

SELF-DRIVING TECHNOLOGY SHOULD BE STANDARDIZED AND OPEN SOURCE.

Any other implementation puts profits over human lives.

 
- url: /c/formal_methods

- name: Formal Methods

Formal methods are intended to systematize and introduce rigor into all the phases of software development. Formal methods are generally used in the development of most critical software in which security, safety is prime objective and cost of failure is high. This style of rigorous development is a crucial yet underrepresented aspect of our software engineering toolkit. This is a place to aggregate interesting topics and discussions of specific uses and ideas in formal methods.

A community for discussions on formal methods here on programming.dev could draw in more academics and mathematicians. These discussions would inevitably cross-pollinate into more pragmatic languages when discussed in such close proximity.

Subjects/Languages discussed here: formal methods and specifications, dependently-typed languages, categories, totality, correctness, Agda, Coq, Idris, Isabelle proof assistant, etc.

This potential community would be distinct from /c/functional programming and /c/Haskell because it would focus on correctness, totality, and formality above all.

Though I don't have the time nor the expertise, it would probably be exceptionally easy to moderate this community due to the level of discussion expected.

[–] demesisx@programming.dev 1 points 1 year ago

It shows. I dream of how cool this would look on a pro camera. There’s something off about the sharpness and contrast that is sort of jarring. I can, however, see what your eyes saw that made you want a photo of it. I just wish your camera represented it better.

Any suggestions for a person that may travel to Kyoto next year?

[–] demesisx@programming.dev 1 points 1 year ago

Nothing at all. Maybe my suggestion is ignorant (but I don't think it is).

What I am suggesting is a template configuration for instance operators to make getting up and running fool-proof. From what I hear, the nixpkgs module is great but it doesn't help with the more complex parts of spinning up an instance regarding DNS and other aspects of a typical instance's tech stack. If we could share a github repo with a FULL minimum viable product for all of the parts needed to run a real, solid lemmy instance, it would allow instance operators to gain all of the advantages that we currently enjoy using flakes. For example, an instance operator might be able to safely upgrade their entire instance with one command while, from what I observe, it currently takes instance operators a week or more to test and install things in that old, painful non-Nixy way.

 
 

I was looking into the prospect of deploying an instance of Lemmy myself. Being an ULTRA nix fanboi (and a Docker-hater), I was immediately struck by how much the process still depends on (and, IMO, is being held hostage by) Docker containers.

Can we (or at least someone more capable and with more free time than I) help the Lemmy community by harnessing the power of nix and flakes to create declarative, reproducible Lemmy scratch-built instance deployment?

I suspect it would be exceptionally easy for some of you out there. If you are a flakes power-user, just think of how much this could help the community (and perhaps awaken a few people to the power of flakes).

ps. if this already exists, please point me in the right direction.

view more: next ›