philihp (u/philihp) - Readit News

philihp commented on ICE is using fake cell towers to spy on people's phones forbes.com/sites/the-wire... · Posted by u/coloneltcb

stephen_g · a day ago

It'd be a lot of trouble to interfere with the source, yes.

I think the release files is the place they could most easily tamper - generally they're stored on Github infra so the files could be changed, and the checksum on the download page also altered (or different files and different checksums provided to different people if targeted).

Unless the builds are totally reproducible it'd be tricky to catch.

philihp · 16 hours ago

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.

philihp commented on Getting rid of bed bugs: trickier than ever knowablemagazine.org/cont... · Posted by u/fortran77

sdwr · 2 years ago

I'd assume that works for local bedbugs, but is no defense against ones tracked in on clothing, furniture, etc.

philihp · 2 years ago

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.

philihp commented on PostgreSQL is enough gist.github.com/cpursley/... · Posted by u/cpursley

TheCapeGreek · 2 years ago

On top of that, a lot of discourse seems to happen with an assumption that you only make the tech/stack choice once.

For the majority of apps, just doing basic CRUD with a handful of data types, is it that hard to just move to another DB? Especially if you're in framework land with an ORM that abstracts some of the differences, since your app code will largely stay the same.

philihp · 2 years ago

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

philihp commented on After 34 years, someone beat Tetris [video] youtube.com/watch?v=GuJ5U... · Posted by u/gslin

philihp · 2 years ago

Alexander wept

philihp commented on Never Ship on Fridays octomind.dev/blog/on-deve... · Posted by u/thunderbong

popularonion · 2 years ago

> Sounds like your current/previous companies have heavier weight release processes that reduces how often releases go out?

Yes, that probably describes 98% of companies. So what?

philihp · 2 years ago

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.

philihp commented on Find Legal Moves in Brass Birmingham with Datalog blog.pzakrzewski.com/find... · Posted by u/gieksosz

philihp · 2 years ago

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

philihp commented on Unix Time reaches 1.7 billion epochconverter.com/countd... · Posted by u/AlwaysNewb23

philsnow · 2 years ago

not at all, I remember 1234567890

philihp · 2 years ago

I remember you remembering that when we celebrated 1500000000!

philihp commented on GitHub Actions Are a Problem felix-knorr.net/posts/202... · Posted by u/benrutter

twic · 2 years ago

GitHub actions are configured by version-controlled files too though. I have an actions-dev branch on my project, so I can iterate on actions config without having to clutter up master.

Would still be better if I could run locally to iterate. But the local run would have to have very high fidelity to what happens on GitHub to be useful.

philihp · 2 years ago

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.

philihp commented on HTML First html-first.com/... · Posted by u/tonyennis

codeptualize · 2 years ago

This is fun in to theory and in simple examples, but show me a big project that applies this and how it made a difference.

There are some bold objectives at the start that would be wonderful, but I’m a bit disappointed by the advice. I really don’t see how these would work in anything other than very basic scenarios, even less how they would achieve the objectives.

I’m all for using the web platform to the max, and I’m absolutely for reducing complexity as much as possible, but I’m highly skeptical these principles will achieve that and I would not be surprised if it increases complexity by having multiple ways to do something.

With peace and love but I can’t see from this list if you actually put these principles to the test or you just assumed it will do what you hope it will.

philihp · 2 years ago

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.