floxy

I used to use a full Slackware Linux distribution with X-Windows on a 486 clone with 4 Megabytes of RAM.

Apple can create a clone for their wall-garden when they want to catch up to the times.

>wildly underestimate how many engineers work on Chrome.

It is completely insane how many people work on Chrome. It seems like it is time to deprecate web browsers and do something different. Like you get a frame-buffer to draw on with something like a wasm vm. Web pages get replaced by programs (which they essentially are anyway). Get rid of 99.9% of the cruft that has accumulated over the decades in browsers. If you want to have some of that cruft, that is a library you have to send.

Anyone care to guesstimate how much effort there would be in creating an actually-secure curl and openssl? Using something like Common Lisp or Lean, instead of C.

I as skeptical as the next guy when it comes to the claim that ambient audio modulates the fluorescent light. But I could sure use more details on what analysis was done to the photos. Sounds like there were several photos taken, say 100ms(?) apart. Then the photos were subtracted pixel-by-pixel to look at the variations in time (between photos) or spatially (neighboring pixels)? I still think a photo-diode AC-coupled to a high gain amplifier fed into an oscilloscope would be the more conclusive test. Do a audio frequency sweep from 100-10kHz. Both with the fluorescent light on, and then again with the light off (as a control, in case something else in the setup is sensitive to the audio).

I distinctly remember paying $40 per megabyte at Costco to upgrade my Cyrix 486-40 from 4MB to 8MB (maybe 1994 or so).

>Where may I see the advantage in the long run, in any dimension?

The advantage of what?

I suppose I could envision a scenario like: Service A has a "reset your password" option. Someone with a "[email protected]" tries to use this option. Normally this fails when mangled-popular-unicode-domain-plus-garbage.com can't be found. Enterprising malicious actor registers mangled-popular-unicode-domain-plus-garbage.com, and now gets a hold of user password reset requests.

I don't think that is a reasonable request for a response to a comment post, but in my experience, many lisp macro advocates come from other procedural / OO languages and aren't well acquainted with other programming paradigms, so they don't generally know what the don't know about other styles, say functional programming, and how to solve problems using higher order functions, etc. instead of reaching for macros. Which is OK. Not everyone has to become a programming language dilettante.

Or you could wrap arguments in lambdas (anonymous functions) for eagerly-evaluted languages. Lisp unfortunately has a bulky syntax for lambdas, compared to something like Smalltalk. Of course, you can fix this with reader macros in Common Lisp (but no one does). Clojure has a shorter syntax I believe as well: #().

I'm interested in reading more about how reader macros make `eval` better/useful.

Looking forward to reading the results of your benchmarking Hurd vs. Linux.