charles_parnot
charles_parnot on Hacker News
Posted by
charles_parnot on Monday January 08, 2018 @07:15PM
from the scripting.com dept.
The Mac app is still a paid app, but given the iOS ecosystem, it seems they decided it was not worth trying to charge for it. It's a bit sad but a great deal!
Posted by
charles_parnot on Wednesday September 16, 2015 @02:46PM
from the blog.papersapp.com dept.
Right, it was tongue in cheek. There is of course some data in there :-)
I suppose what I meant is that it is lossy: you cannot get back what you "INSERT". That violates a pretty basic assumption about what a database is supposed to do ;-)
An interesting consequence of contentless tables is that you end up with a database that does not have data. Should we still call it a database? :)
I actually did consider this when writing the "parser" but it was complicated enough that it was just getting in the way of my goal of having the simplest code and specs that got the job done. Also using 1-2-3-4 is simple enough that I decided it was not worth the extra rule.
I added a link to it on asciimage.org
Be my guest :-)
I added the js port on asciimage.org. There is a Go version as well I will link to.
I know SVG very well, even have used it a few times for automatic generation of various graphics for bioinformatic projects. I use a lot of different graphic editors, and I am very familiar with them, e.g. Illustrator, Sketch, Acorn, Photoshop, Omnigraffle. I am also very familiar with e.g. Bezier paths manipulations, linear transforms, linear algebra, etc. I love maths.
Pixel alignment, asset management and being a one-man shop allowed more excentricities is what justifies this, for small icons with simple features (a few straight lines or rects).
Nice to see the actual comparison of the binary size (and there is the 2x and 3x png). On the other hand, to be fair, the memory footprint will be more with the ASCII version (text + final NSImage loaded as bitmap in memory) compared to png (only the bitmap in memory, directly loaded from disk). The size of the bitmap is big anyway: there is no compression.
No worry, and no offense taken!
Nice way to think about it. I agree.
Yes, PNG is probably using less memory. For a few small icons, though, it's negligible either way.
Fair enough. I certainly did not mean to pretend anything like this.
Exactly, could not have said it better.
I only use it for very simple icons (square, couple of lines, etc)
You are totally right, and I actually also considered doing just that initially in my code.
When you skip a character, you move on to next shape.
So, 1-2-3 5-6-7 = 2 triangles
But 1 3 5 = 3 points
TBH, the bug is an example of where this hack should not be used :D
I will write the promised README, btw :)
You could actually have quite a lot of data generated in a lab, depending on what you do. By only storing the signatures, you can have a much cheaper service that what would be needed to store GB of data, and really focus on other aspects that are critical for this: security, backup, user interface, speed,... Having only to worry about backup of a bunch of signatures is a much easier task than having to worry about backing up the actual data.
We do plan to allow syncing to a local network drive, if that can work. The idea is that it will be file-based, and can leverage Dropbox, Google Drive or... a local networked drive. Still working on it, though! See PARStore on github for some of the basic ideas, as this is what we use for document storage.
Thanks for the feedback! Nice idea about printing. The export will be here very soon, it simply did not make the cut for 1.0 because it needs more testing.
Yes, the 'first to file' thing is still new enough that many scientists still think it is useful to sign their notebooks for that purpose. There are still subtleties to those rules, though, that we need to investigate a bit.
The problem evoked here is for your institution at which you work, to know that their researchers are not changing the data afterwards and following best practices. In this scheme, the user would submit the hashes to a central server controlled by the institution. Then, the user have no way of changing the content without them knowing.
And yes, you would need to add some authentication to know it's always the same user, but that's a different, orthogonal issue.
For actual proof e.g. in court, you'd need a third party with a private key used to sign the content. A little more involved... But the main point of that would be patent litigation, and with the new 'first to file' rule in the US, it is much less relevant.