philihp

See also: Recursion

Can we settle for Factorio and 2028?

Possible, yes, but pretty damming to Microsoft's reputation if proof that their infrastructure has been compromised and anyone realizes it's happening. This sort of thing killed Sourceforge when they started shipping adware bundled into installers of the programs they distributed.

Not much can stop a lone bedbug carried in. What you're trying to do is prevent your mattress from becoming a nest.

The problem with DE is it's so inexpensive and effective, and that makes it difficult to sell as a product. I got a 2kg bag of it for $10, and it's enough to last decades.

The way you've trivialized a database vendor swap makes me curious how often you do this.

Alexander wept

When you control the devices to which you're deploying to, there is little reason why you wouldn't deploy as often as you can. It helps a great deal in isolating bugs to keep your changesets small, and you can either do that by slowing down the product iterations (and getting poor feedback from each), or releasing more often. This is ubiquitous with web development.

Weekly releases (or slower) is appropriate when you rely on users to update their software or firmware. Most mobile app development does this.

I implemented the rules of Ora et Labora. Every card's ability is some fun puzzle of enumerating all the legal ways to play it. Some are simple like "go here and you get an amount of sheep", others are "you can convert an amount peat to coal here" so if you have 5 coal, you can offer 0, 1, 2, 3, 4, or 5 peat as input. The more fun problems are like "convert 3 different resources into 6 of any one type of basic resource" or "convert four to bread for 0.5 energy each" and wood is worth 1 energy, peat 2, and coal 3 energy. Lots of fun combinatorics.

It's all open source and playable at https://ora.kennerspiel.com

I remember you remembering that when we celebrated 1500000000!

Running actions triggered from a non-main branch does it for me, either on pushes to the branch, or 'workflow_dispatch'. You'll otherwise never get that level of fidelity to what happens in production.

Keep the logic in your YAML "dumb". Avoid variables and subroutines in the file, if you want to DRY something, create your own custom action. You can have unit tests on an action, you can't have unit tests on a GHA workflow.

For a frontend developer who is younger than jQuery, starting a project following this advice would be a good opportunity to learn why we do the things we do like build steps, and remember how much development sucked before HMR.

I suspect the author hasn't actually done this on a project with more than one person, supporting 99% of browsers in the wild. I also suspect they didn't run their own code, because either my screen is not as tasty, or "onlick" is not an handler of div.

I still have the music for egatrek in my head!

Sounds like you have a bigger problem if your browser isn't properly sandboxed.

The design of Quora is awful. It's like Yahoo Answers, but instead of an inane unqualified answer, you get a dubious answer surrounded and camouflaged by answers to sponsored questions you didn't ask.

Imagine knowing this, and still using the imperial system

I'm hopeful as well, although pessimistic. The demographic of people who would pay money to escape advertising are also quite profitable if you can successfully target in your advertising campaigns.

"Nobody plays Halo on PlayStation"

I've never understood the appeal of guestbooks and commenting on Wordpress. Static HTML is a wonderful medium for getting your message out, do we need the validation of visitors commenting?

An almond tax would probably balance it out.

There's a lot of irony in this.

Healthcare could also do it. Ultimately you need people to be incentivized to both have an UID in the system, and also not want more than one.

Obsession is somebody liking that which you find unnecessary.

There, I made it point-free. Isn't it much simpler?

Passwordstore (pass) databases are just a git repo which makes great audit trails, but also gives it syncing for free rather than reinventing the wheel.

It uses PGP rather than rolling its own encryption, which also makes it compatible with hardware tokens, for free.

It's not some complicated project... it's just a thousand or so line shell script.

Yeah pretty much. A lightning channel is a bit like putting money down as a retainer for a lawyer, or putting a deposit down in a hotel.

The real transaction happens at the beginning, and another transaction happens at the end when the channel closes and we settle out who gets the remainder.

It's pretty easy to advocate for another Vietnam/Afghanistan when you don't have any skin in the game, and you have the means to go out into the country and bury your head in the sand.

The scientists said they were sorry.

Must be driving really fast.

AWS understands lifetime value of the user, not just the account. I've had mistakes ON MY PERSONAL ACCOUNT that were in no way connected to my work. Times when I was just experimenting. They refunded it in full. I've also heard from STUDENTS who may not ever get into infra work that they're still reasonable and lenient.

You would be absolute mad to use any other platform. AWS gets it right on the customer service front. Amazon, perhaps deeply less so... but AWS? amazing.

I volunteer as tribute.

Passwordstore is probably the most secure, being that it's a short (1500-line) shell script offloads the actual encryption to GPG and network sync to git. There's just not a lot of surface area to attack there... and it also works for teams.