sreekotay

I always liked: is it like shaving, getting a haircut, or getting a tatoo?

Exactly this.

This is the real answer (amongst other goodness) - this one is well executed and differentiated

Every language at scale needs a preprocessor (look at the “use server” and “use gpu” silliness happening in TS) - why is it not the the same as the language you use?

Most of that you can get with diligence in high school and a smattering of College classes as HS junior/senior IMHO.

Nailed it in one. Or (similarly) never makes the priority/cut-off list because "what metric does it move?"

Are... are you comparing quicksort to... Quickdraw?

Lol - ok that's genuinely funny :). slow clap

do you have any examples of this online to play with? I see the samples in the arvix doc and some documenation at github but not examples I can see live.

This is realtime capture/display? Presumable (at this stage) for local viewing? Is that right?

hunh - THAT's cool. Learn something new every day.

That said - it does appear encapsulated, much like an iframe - css doesn't take, etc. so though more "pure" HTML I'd argue doesn't fulfill the spirit of "include"?

( •_•) ( •_•)>⌐■-■ (⌐■_■) Deal with it.

:)

you need a server for HTML to work, as practical matter. But yes. There IS a workaround to that too, if you're REALLY determined, but you have to format your HTML a giant JS comment block (lol really :))

[edit: I'm sure there are still some file:// workflows for docs - and yes this doesn't address that]

While you do need a server i think this is the functional equivalent? The fetch JS and insert outlined (linked to) in the article is async. This blocks execution like you'd expect an HTML include to do. It's WAY easier to reason about - which is why the initial ask, I think...

This has always worked for me. Pretty much the ask? https://gist.github.com/sreekotay/08f9dfcd7553abb8f1bb17375d...

Depends on your definition of robust (e.g. how are you handling T-junctions) but in general I would agree with this, in that that some things that are NOT trivial should rightly be pushed up the art pipeline.

Good pipelines shouldn't rely on clever parser behaviour (as a general rule)

The core problem with pure text as an interface tends to be discoverability. Where to go from where I am is often unclear.

Under rated reply.

(Though I think here the author means "free algebra" in the colloquial sense)

But .... it sounds like it was was? The original MIT SLIP version (yes SLIP not LISP) had a framework for embedding dynamic modules - so could do an early version of "learning." It feels like it was indeed more a framework for testing out different kinds of chatbot logic - maybe a meta-chatbot?

The famous DOCTOR script was just one example to demonstrate the tools's capabilities, and not the main point of ELIZA.

[Edit: the paper suggests the DOCTOR script is "ELIZA" not ELIZA, i.e. the limited version that became popular, not the full version that was built)

Can't wait for OpenSSL and LibreSSL...

Yep OS X wasnt til 2000/2001 and absolutely NOT smooth even on relatively new high end Macs at the time.

OS 8 and 9 were winXP like in terms of desktop effects - no soft anything.

Was a graphics and lead app engineer on many of the Kai line of products at the time.

So much fun. And polarizing for sure - but more fans than detractors, and the business didn't fail because of lack of interest. Way more sordid/gossip-y and sad unfortunately.

What OS do you think you were running in 1996?

Can you say more on recipes? I had always heard that it had to with copyright - that one needed the copy above to create a copyrightable work.

Genuinely lol'ed! This is such a perfect child + 1 argument - well played :)

My contribution: http://sree.kotay.com/2007/04/shift-registers-and-de-bruijn-...

Is that right?

So if a set is infinite but a provably strict subset of another - would we not say that set/infinity is smaller?

For sake of argument, not Apple because they are too close to the HW (specifically their own), and not Google because they are too far away from the HW (completely fractured).

Amazon is an interesting underdog here...

This seems odd. You can absolutely draw triangles with shared edges without touching the same pixel twice.

I mean tbf, they were released around the same time (so i agree one did not plagiarize the other) but DVD CSS was likely more widely known first - albeit due to DeCSS

The project you linked to is erlang, not elang as referenced above.

No concern for security helps a lot...