HNHacker News
TopNewBestAskShowJobs

themattrix

15 karma · joined May 17, 2013

submissionscomments
themattrix··on Show HN: 2048.cpp – Play 2048 in directly your terminal
That was mine! https://github.com/themattrix/sed2048
themattrix··on Signing in to websites with SSH
Care to expand on this a bit? I'm somewhat familiar with SQRL, but what was this IP binding proposal all about?

Is this a use-case not discussed in the SQRL phishing page?

https://www.grc.com/sqrl/phishing.htm

themattrix··on 2048 in sed
One final gameplay tweak: there's now a 90% chance that a newly-spawned tile will be a "2" and a 10% chance that it will be a "4".

The gameplay should now be identical to the original 2048.

themattrix··on 2048 in sed
You've revealed my secret identity!
themattrix··on 2048 in sed
Fixed! The score is now calculated as the sum of all merge results (like the original game), instead of the sum of all cells (like I was doing).

As a bonus, the score calculation is now done in pure sed.

If you notice any other issues, please let me know!

themattrix··on 2048 in sed
Score is now implemented -enjoy!
themattrix··on 2048 in sed
Author here - glad you like it! I actually found the poker hand identifier more challenging to write than 2048, but I also tried to make it as compact as possible.

https://github.com/themattrix/poker_hand

themattrix··on 2048 in sed
I'll look into adding this. (I think I'll have to add it to the bash wrapper.)
themattrix··on 2048 in sed
This bug is now fixed! Thanks for pointing it out!
themattrix··on The Shortest Crashing C Program
You can go even shorter if you cheat:

     $ cat short.c
     M
     $ gcc -DM='main;' short.c -o short
     $ ./short
     Segmentation fault
themattrix··on Continuous Deployment Style Build System for Python
Our primary goal is to get the Python community talking about continuous deployment. Our particular implementation is less important. In fact, we'd like to see this project die entirely and have its ideas live on in the standard Python tooling.

That being said, here's an overview of our implementation from the wiki (https://github.com/teamfruit/defend_against_fruit/wiki/How-T...):

Defend Against Fruit aims to provide a quick and simple way to package, test, and publish a Python package from within a virtual environment (virtualenv). It boils down to running the following command inside the project directory:

  > ci --publish
If not previously run, this script will handle the virtualenv bootstrapping from (nearly) scratch, requiring only a base Python installation and a few configuration files.

Afterward—and on every subsequent run—the script enters the virtualenv, runs the package's unit tests, builds the package, and publishes it to the artifact repository along with dependency metadata. Each step is only run if the prior step succeeded, so anyone consuming this artifact can be sure it has passed all of its unit tests.

As part of Continuous Deployment (CD), we need a mechanism to promote artifacts to higher levels of visibility. Artifactory Pro exposes just such a mechanism through its REST API. We have manually verified the build information Defend Against Fruit publishes is sufficient for promotion.