Hacker News new | past | comments | ask | show | jobs | submit | a-french-anon's comments login

I use Macports on my work Macbook, but I'd love for Portage prefix to be fully functional on ARM Mac, personally. The tool interface is just so much better.


on contrast, I have a 32bit macbook pro on snow leopard, so none of these shiny tools can be even remotely useful to me (sapphire being arm only? yeah, that)



I wasn't aware the Klippel scanner can do low-frequency measurements - any idea how?


Complicated maths, from what I (don't) understand. Note that it's only the NFS that can do so.

https://www.audiosciencereview.com/forum/index.php?threads/u... is a good resource to get a high-level explanation.


Maybe I'm wrong, but when reading the first article, it seems like the entire thing exists mainly (not completely) because Go's GC isn't generational.


Maybe somewhat, but it's not hard to get pathologically bad GC behavior out of generational GCs either. Pools / manual memory management will always have some reasonable use cases.


More than two is a bit painful, in my experience, as I don't think Emacs has directional focus like the usual X11 WMs (e.g. i3, bspwm) and C-o works well with only two.

Magit and sly/SLIME work much better with a second window, I'd say.


> I don't think Emacs has directional focus

It does, but I don't think they have default bindings. The commands are windmove-{left,down,up,right}. I've had them bound to C-S-{h,j,k,l} for years and it makes moving around much more fluid and predictable than C-x o.


If you need to manage multiple windows in emacs I find ace-window perfect.

Pops up a number in the top left of the window and you hit it to jump to it. If only two, C-o works as before.

https://github.com/abo-abo/ace-window

I have never used more than like 5 windows and only for a short time. I guess it doesn't work past 10 but that's gotta be enough for anyone...


Ref counting is garbage collection (cf https://courses.cs.washington.edu/courses/cse590p/05au/p50-b...). It's just not tracing garbage collection.

I'm a decent fan of both Tcl and CL, but Tcl has the big problem of being "almost" homoiconic and lacking good meta-programming tools like quasi-quoting. I say almost because comments break homoiconicity, whereas in CL they are discarded at read-time, never appearing in the parsed tree.


Quasiquoting is only necessary in Lisp because Lisp evaluates its arguments by default. Tcl does not do that.


Quasiquoting allows us to specify a mostly fixed template of code where we would like to indicate variable parts that are to be substituted (note: not evaluated).

The stuff here sure looks like quasiquoting to me:

https://wiki.tcl-lang.org/page/Macro+Facility+for+Tcl

  mac  mloop {idx cnt cmd} {
     return "for {set $idx 0} {\$[set $idx] < $cnt} {incr $idx} {$cmd}"
  }
The "..." with embedded $... reference is is a kind of quasiquote.


I don't see what crusty implementation details have to do with a philosophy. In fact, UNIX itself is a poor implementation of the "UNIX" philosophy, which is why Plan 9 exists.

The idea of small composable tools doing one thing and doing it well may have been mostly an ideal (and now pretty niche), but I don't think it was purely invented after the fact. Just crippled by the "worse is better".


So, how (in truth, "when") do you recognize that the emperor is missing his clothes?


Never seen any of those, I'd have mentioned Heat instead.


https://kommandostore.com/products/the-heat-rig

note: Would definitely not recommend wearing this loaded outside of a LARP environment at a range, with friends that have a sense of humor


Why would Lispers feel at home with its (whitespace delimited) syntax? Quite the strange claim.

I know this isn't a common rant, but I hate so-called functional language still bowing to the "infix mathematical operator special case" dogma, when those are just binary (variadic in Lisp) functions.

Always found it pretty appealing, otherwise. And no ";;"!


It's certainly an incredible gem, but I do find it quite bloated in features. Which is why I plan on trying https://github.com/baskerville/plato one of these days, to see if it does everything I need.


Is it not easy enough to just ignore the features you don't need?


Those mean a pretty cluttered UI, in my eyes.


And what's wrong with a UI being "cluttered", especially if the alternative is that it fails to expose the software's full functionality?


Consider applying for YC's Summer 2025 batch! Applications are open till May 13

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

Search: