HN user

thelazydogsback

689 karma
Posts0
Comments375
View on HN
No posts found.

I think it was from the movie industry - just something in the background shot with lots of blinking lights and occasional beeps was known as an EBG, or "electronic bullshit grinder". They do tend to impress investors as well as audiences.

I remember walking into the Computer Factory in Grand Central station in NYC and playing with the Lisa. (Later I did some Smalltalk on the Lisa and the Techtronix.)

I still remember the layout ca. 1979-83 like it was yesterday - on the right side when you walked in was a separate room with some kind of P-Code machine which was the "business mini". The Lisa and later the Mac were set up on a table on the right, and the Apple][ in the back. In the center were the Kaypro, and some other CP/M machines, and the Commodore Pets (the OG chicket keyboard version and the green-screen one w/the real keyboard) (incl. some IEE-488? accessories), the Sol II, and then the gfx show-offs (making my TRS-80 jealous), the CompuColor II and Exidy Sorcerer. The other wall had the printers - the Anderson-Jacobson daisywheel printer, an adapter w/solenoids to turn your Selectric typewriter into a printer, a few 9-pin matrix printes like the IDS Paper Tiger (right before the Epson MX-80 took over)

Good times. Sigh...

Some of this reminds of me a combination Icon and Mozart. (And happened to just come across my old Icon book a few days ago.)

Maybe the backtracking concepts are "too built in?" - e.g., (1|2) is not a first-class/reified "amb" object, right? - so if I want to introduce a different search than depth-first backtracking (breadth, dependency-directed), etc., I couldn't directly.

Seems like there could be some confusion between multiple, backtracked values and actual sequences -- this often leads to sub-optimal/confusing Prolog code as well, deciding when you have an explicit control structure vs. backtrack, when to "harden" results using setOf/bagOf/findAll, etc.

Well, if we all ate meat alternatives most of the time and treated ourselves to real meat much less often, we could reduce the density of animals raised for food so that they could be raised humanely. I love meat and especially bacon, but I'll have sea-crunch (or whatever) most of the time if it means we don't have to torture animals all their lives.

Related: this Future Perfect podcast https://pca.st/ngofo0ll

Thanks for the pointer -- looks like (OCaml/F#)++ with an effect system and some other niceties. I guess I'd rather go that way then enter the Scala effects mire. There are some obvious issues I didn't see up front (unless I missed them) - - How do content addressable fns and their codedabase integrate w/git (seems like it really has to for the time-being) - The usual: What's the execution model & perf characteristics? - I see it's written in Haskell, but don't know if it's interpreted or further transpiled, etc. - Debugger? Interop? - Type and efficiency of GC - Impl. of collection types - simple conses vs. HMAT or r/b trees, etc.

A strongly-typed pluggable effect system like this should really replace in a more structured and powerful way what Python does today, which is really just to proxy out to efficient external libs (often written in native code, like Numpy or various AI engines, etc.) If Python is used for actual compute, you're adding several 0's to your runtime.

So I'm curious if Unison is of that ilk, or can be used dependency-free for CPU-intensive (and in my case, non-numeric) workloads.

AM Stereo 4 years ago

Got to watch those 100ft full-wave whip antennas when going under the bridge ;)

Parinfer hits the sweet-spot for me -- you still get the benefits of the parens, but the indentation is still enforced to match, and changing either one causes the other to be updated accordingly

Most things that increase normal cellular growth by stimulating the mtor pathway and IGF production, etc., will also increase abnormal cellular growth - including things like, well, eating - esp. carbs/sugar and protein. It's certainly possible that a marked increase in NAD _could_ increase the growth of certain types of cancers, but I'd think this effect would be swamped by other factors.

As for "medical doctors" -- unless the MD in question is a (sports) nutrition specialist, perhaps oncologist, _and_ has graduated in the last few years or spends many hours a week keeping up with research that is accelerating every week, there's a good chance an intelligent consumer of podcasts/blogs/reddit/books is a better source of info on this topic. (Which is why I had to tell my MD why I wanted to take Metforin.) Not knocking MD's - but most simply don't have the time for this sort of thing the way practices are set up now.

Sure - you can find many NR and NMN supplements on AMZN for example. NMN has gained popularity over NR, I believe mostly due to longer shelf life. Elysium and TruNiagen are two famous brands, that IIR were sueing each other at some point? I take another/cheaper NMN supplement. Caveat emptor - there's really no way to tell what you're getting from many of these - and even if you're getting pure ingredients, the jury is still out.

Note that this study shows that supplements increase _blood serum_ levels of NAD, not concentrations inside the cell and mitochondria where it counts. So I'd say that without further qualification, this study shows safety more than efficacy. The role (if any) of exogenous NAD precursor supplementation is still a topic of debate, and there's a lot of money in selling these formulations. FWIW, I personally take NAD precursors because they likely do no damage (other than to the wallet), and they possibly do some small amount of good. There are plenty of other supplements I'd spend my money before NAD precursors. (And of course diet and exercise outweigh them all for most...)

I'm tired about hearing about the lack of "explainability in AI" when the issue is with deep-learning & non-symbolic AI, the very allure of which to date has been its black-box, just-train-it nature, leading to all kinds of neat-o scary (truly) high-dimensional text and image trickery without the foresight of actually bothering to try to actually understand anything. We've had some pretty incredible explainable AI, planning & NLP processing, etc., in the past (1970's to early 2000's for the most part) that needs to act as the "prime motivator" to drive the DNN methods that really excel at processing at the periphery.

I think it's much simpler -- it's about the focus on design over usefulness. I really don't care if the u/x looks like someone's weekend VB project as long as it does what I want in an obvious, discoverable way. Some of the worst things in web (and desktop) u/x seem to come from the design-side of the house and are more about some 1950's design ethic of what would look good in a magazine layout, rather than treating the computer as a tool that gets shit done. (Of course, some sites _are_ magazines, and they get a pass...)

I feel the same about iOS apps -- they are all adventure games.

And in-place editing on a phone? Just fill the whole freaking screen with a big editor window in a giant font where I can target the cursor with my fingers, and let me submit it to the field when I'm done.

And get off my lawn! :)

I have an old tribal rug (Turkish/Afghan?) that has a "evil eye" (but a good evil eye...) weaved into it in order to break the otherwise perfect symmetry of the design.

Yeah. I couldn't find the other articles I was looking for. His US bioweapon theory is pretty silly.

As for "anti-vaxers", though I don't count myself as one or probably agree politically with most of them, I'm going withhold complete judgment there - vaccines are obviously effective, but until there are actually epidemiologically valid multi-generational meta-studies with as many confounding factors as as possible removed (probably requiring placebos be given to a percentage of people) I'm not sure we can separate vaccines from other relatively novel environmental or behavioral factors that may lead to certain diseases, esp. developmental/neurological conditions. I now have a bit less knee-jerk anti-anti-vax attitude after sitting at a table with several doctors who admitted they didn't/wouldn't follow all vaccine protocols with their own children - but I know this is certainly not scientific evidence. But I'll certainly be getting the COVID vaccine when I'm eligible...

Most code is not CPU-bound, and for code that is, a hot spot is all the usually needs to be optimized. Today .Net Core is remarkably performant, and the fact that just by writing code carefully, or using Span<> etc., you can get close to bare-metal perf with w/o resorting to FFI to unsafe code is a good thing. This is much easier than trying to keep your friendly Rust borrow-checker happy even for moderately complex data-structures with varying lifetimes.