bevr1337

I'm quite certain the author is a Starfleet captain. So few things make me as excited to be human.

I wish I lived in this reality. It sounds like a utopia over there.

I did sweat localization with this approach. We use a workflow to ensure some peer review but it's an added challenge. Seemingly all good.

The first answer reinvents tagged templates and the second suggests them. I thought it was a good example to show the complexity of hacking in this approach. I'll add more context in the future.

I'm agreed that the average developer would hate working with an an AST -- JSX covers 99.9% use-case and React codebases are full of functional programming escape hatches -- but it is the foundation. An HAST is an interoperable, extendable representation we can move between any framework or tooling.

I'm likely projecting too much on the proposal. Templating is the top priority but it's the ancillary bits you mention that excite me most.

> Markup-based templates look like the output

I made the mistake of drinking functional programming laced koolaid, so in my mind they really do translate well, but I respect that you have a broader perspective.

Thanks for taking the time to reply. I'm a smidge honored that you'd even review my feedback!

What is "enough" here? It is good enough for the unified community. I know npmtrends.com isn't the best metric, but unified is popular. Unified has made it trivial to move between HTML, MDX, MD, JSX and even combinations of the above. I'm learning it's an opinion, but hyperscript and hast are HTML enough being that they're models of HTML

Hooking into a tagged template is a challenge. Functions will receive a list of unparsed html strings and already evaluated expressions to zipper up themselves before forwarding to the downstream template API.

https://stackoverflow.com/questions/39971088/evaluating-temp...

Unlike an expression or tag, a developer can hack on any AST or hyper script provided by a library. Im not sure proxies or reflection are useful working with string primitive and they're unergonomic.

This was something I mentioned on the other post so I appreciate seeing it called out clearly in the reply. (Not to assume I inspired the mention.) Thank you for sharing.

> Just don't use it as a form of giving up on fundamental human needs, you're more resourceful than that.

This glib advice is what lands you in an uncomfortable HR meeting or is the reason you won't get invited back for game nights. This will be deeply hurtful to families struggling with fertility or adoption and to individuals who experienced the foster system.

Neither apathy nor ignorance affect adoption or pregnancy. Families will be excluded by the staggering costs, marital status, employment history, disability, and gender and sexual identity.

Ive written a few versions of this reply. Some included my personal background having been moved by protective services, or some emotional stories about my siblings in the foster system, some with swears, and one was simply "check yourself." The issue is deeply personal. More advocacy is always appreciated, but I implore you to tune in.

SSH ate its lunch in shell contexts, and then those new fangled computer graphics and browsers pecked away at the crumbs.

From one Telnet lover to another, I'm still resentful folks blamed Telnet. Other application protocols built on TCP sockets are encouraged to use SSL/TLS e.g. HTTPS, SFTP, WSS (which is possibly HTTPS in a trenchcoat).

My speculation is that it raised the barrier for entry. Artists and writers wanted to quickly build and share worlds. Most computers supported raw TCP sockets and most shells handled ANSI, so players could join without installing software.

Today, people assume Telnet can't be secured and so they don't bother. Regrettably, I maintain some.

There's a recent push for MUD hosts to deploy a WSS proxy. An example: The IRE MUDs have a login telnet subnegotiation which the web client performs over WSS. Credentials are no longer sent in plaintext nor stored in the application's command history. (Telnet does specify when inputs shouldn't be stored in hisotry, but it's on the client to respect.) IRE is a bit of a pooper here, they consider the WSS service private. Because the subnegotiation is nonstandard and WSS is discouraged, MUD clients are obligated to make bad choices.

Other MUDs and engines are more forward. Evannia games support WS and Telnet and both can use SSL.

So what MUDs are we playing?

Edit to add: the tintin author, Scandum, is still at it. There's a nice group of folks in the Discord where Scandum and others helped me write my first terminal emulator. Come join us!

There are similarities, I agree, but there are huge differences too. Both should be analyzed. For ex, Wikipedia requires humans in the loop, has accountability processes, has been rigorously tested and used for many years by a vast audience, and has a public, vetted agenda. I think it's much harder for Wikipedia to present bias than pre-digital encyclopedias or a non-deterministic LLM especially because Wikipedia has culture and tooling.

"Large" is almost meaningless in this context. Douglas Adams put it best

> Space is big. Really big. You just won't believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it's a long way down the road to the chemist, but that's just peanuts to space.

From an education site:

> Everything with mass is able to bend space and the more massive an object is, the more it bends

They start with an explanation of a marble compared to a bowling ball. Both have a gravity well, but one exerts far more influence

https://www.howitworksdaily.com/the-solar-system-what-is-a-g...

Great choice of words. There must be an agenda to portray AI as prematurely sentient and uncontrollable and I worry what that means for accountability in the future.

Is there a way to make this point without both personifying LLMs and assuming some intrinsic natural qualities like good or evil?

An AI in in the present lacks the capacity for good and evil, morals, ethics, whatever. Why aren't developers, companies, integrators directly accountable? We haven't approached full Ghost in the Shell yet.

We can nitpick this point because react has had a ref API for at least 5 years now. Given a ref, all DOM API are available. For events, SyntheticEvent will refer to a native event if it exists.

The SyntheticEvent abstracts vendor discrepancy. Under the hood, react can apply some optimization too.

https://legacy.reactjs.org/docs/events.html https://react.dev/reference/react-dom/components/common#reac...

I'd love to see something that builds on the work of hyperscript and HAST. They are great models of the DOM. It would be exciting if a template language were syntax sugar.

JSX is easy to reason about because its elements are 1:1 with a single, uniform function call. That feature means JSX is always optional. Sometimes it is even more verbose or less-performant to use JSX than a hyperscript API like specifying optional properties. I think errors and call stacks are clearer than during string interpolation, but that's possibly BS.

Web components offer limited data binding and the hyperscript approach has clear control flow. The templates seem to be a source of confusion in the GH discussions.

There is still something special and pleasant about jquery because its API was a reflection of the domain. As a developer, I want to query for a node (CSS selector, xpath, etc.) to affect change and traverse to other nodes. After a beer or two I'm convinced emacs and org mode approaches are worth emulating in the web.

Great article and linked discussions. Thanks for sharing.

Why? Why are we sure that the population will not settle? Or that our increased productivity won't offset a change in labor?

I do worry societies will fail to handle side effects like the temporary increased demand for elder care, but no real fear of total societal collapse.

Are they? Compounding pharmacies are common and boring. If someone hasn't yet used a compounding pharmacy then it's likely they're in very good health -- yay for them!

What's being described doesn't feel like an issue with compounding rather folks setting up shop to peddle questionable drugs.

> Implementing Lisp onto WebAssembly is so obvious that you may wonder why somebody did not have this idea long ago.

I did find this on the Femto GitHub and got a chuckle. Yes, dear author, that is exactly the piece of information I want explained. Too funny.

Thermals and energy consumption are almost always improving between generations. It's hard for me to think of 13th generation as old. Maybe I'm getting old!

Do users still need to obtain (an obviously legal, Nintendo approved) ROM of classic OOT to use the randomizer?

Then it's clear your didn't read my comments. Scroll up and you can see that I am replying to a mischaracterization of Luddites.

Here is the original comment that I addressed:

> or to become complete Luddites living on subsistence farming?

Sure, +10 points for semantics, but it's missing the point. Maybe my fault for invoking a false liberal/conservative binary.

Intriguing to try and reify labor rights as conservative. Definitely a novel argument.

I found it to be a very fun read. Some neat connections being made.

Yeah CF still carries some annoying startup energy and it's fine to hate them, but this didn't move my needle.