HN user

musicnarcoman

58 karma
Posts0
Comments24
View on HN
No posts found.

As someone who made the mistake of printing keys only in human-readable format: ocr software is only so accurate.

So if you have more than a handfull of bytes you may have to actually read it "by hand" to fix errors.

These days I keep the really important keys both as a qr codes and also hex. But the hex is not pleasant to work with.

The git history is useful to find out: * The why, who and when of some change to the code or configuration. * Looking at older variants of code to see previous attempts to know what has already been tried. * git blame and git bisect for automated troubleshooting.

While I do not build LFS regularly or for production use, the security improvement typically comes from the fact that the end system is _super_small_ and focused. Less software means less attack surface.

Sure, compromised binaries are nasty but personally I do place quite a lot of trust with the distribution repos.

(PS, if you are reading this and contribute packages to distribution repos: Thank you!)

Ah yes, the dreaded page limit! I look for examples of working synthesis so I will still read it.

The question of fixed vs. infinite integers and observable sizes of datastructures is a dilemma that I do not know of any good solution to. Selecting fixed and observable sizes leads to efficient execution but risks making programs unportable (after they have been compiled and are distributed as object code).

Selecting arbitrary precision integers and no observable sizes instead requires a smart runtime/jit/compiler to get efficient execution.

Nice work, I will have to read the research paper later ("Tacit Programming Code Synthesis and Optimization with Genetic Algorithms").

One question, why did you decide to make the size of cells visible to programs (pointer arithetic)? Will that not lead to the same portability challenges that we have already had with C and C++?

(3b) you could also build an ARCHIVE FILE (a statically linked library, libmylib.a) from one or more .o files. If you link with a static library, its code is copied into the a.out file at runtime.

Huh? There is no copying at runtime when using a static library. Or have I misunderstood this all these years?

It is definitely possible, me and a few other students did it in a university course. Assuming the FPGA at least has a media access controller (translates bits to analogue signals) it is not to hard to encode/decode ethernet frames. Sadly, on the top of my head I do not know of any open IP. We wrote our own, but it is closed.

So, what alternatives are you suggesting?

I have tried and used Mercurial, SVN, RCS, CVS, Bitkeeper, TFS, Bazaar, Perforce, Darcs and of course Git. Granted, Git may not be great, but it is still my first choice.