Hacker Newsnew | past | comments | ask | show | jobs | submit | code_code's commentslogin

I've had the thought that programmers should note assumptions in flagged comments, and those comments should be automatically collected, and then reviewed occasionally. Assumptions might be sustainable, so to speak, but they can also create one kind of technical debt.


I've generally wondered about extensions for RTOS support. Special kinds of priority-encoders off registers for flags; shared-memory locks; -- that sort of thing.


I forget the name of the other famous physicist (not Dyson) who said it, but the quote was: "I've seen more [persons] destroyed by Physics than by drugs".

I don't regret my Ph.D., but I still remember the monotone voice in which I defended my dissertation. Listen to advice here. Powerlessness is quite something to experience when one is (has been) locked in for years.


I first read the title as Waterfail Process. I need new glasses and less confirmation bias.


i'm stealing that


Tab will be a printable shape.


There will be different skintone, multi-gender, tab emoji.


Even decades ago I gave such reported concern with photographs more credence than the typical western account of it. I also wondered if the translation was precise enough -- could it (in some cases) have reflected a concern with "essence" more generally? Even without reference to a soul the concern can be a bit immaterial.


Likewise "nuclear plant phenomenology".


I have a recent note that says (from HN id=21495338), try makepad.github.io/makepad . My recollection is that this is such an example.


Nice! though confusingly its an editor that run JavaScript pages. https://makepad.github.io/makepad.html


I've only looked at web components casually, but the examples I saw seemed a greater mess than this. Interact DOM components, CSS, slots, JS, private DOM, ... AND plan for late-loading code and resources. ?!


Thanks for your work. I've been re-reading Knuth's _The TeXbook_ as a reminder of fine points in typography. So much can be covered in just provisioning for floating blocks, top-floating blocks, widows and orphans, a few counters, some flexibilty in headers and footers, and such. It seems like you and/or CSS are hitting those high-points.

I hear you emphasizing this might just be for print, but something like a Kindle in-browser reader (hidden nav; spacebar or < or > to turn a page) can also provide a nice experience (different to scrolling) in reading longer works.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: