I was able to fix my build issues by removing this from package.json

"eleventy-plugin-sass": "^1.2.0",

\> the day I decided to use eleventy

😑

🥲

I have a single json object and I can display the data just fine using mustache client-side-template. Now when I put two objects into a json array I cannot display neither object. Here is the single object: {"Date":"12/03/2021","Close":137.675,"Volume":8419,"Open":137.85,"High":138.525,"Low":136.85} and here is the array: [{"Date":"12/03/2021","Close":137.675,"Volume":8419,"Open":137.85,"High":138.525,"Low":136.85},{"Date":"12/02/2021","Close":137.65,"Volume":9136,"Open":136,"High":138.05,"Low":135.975}]

This works for the single object: {{Date}}Volume: {{Volume}}Open: {{Open}}High: {{High}}Low: {{Low}}Close: {{Close}}

How do I access the Date in the array?

The htmx way would be to generate your desired HTML markup on the server

I know, but in this example I'm pulling in json from a file that contains a json array. I just cannot access anything in the array...[0].Date doesn't work, [0][Date] doesn't work either....

on the server? You probably want to read the file and JSON.parse() it into an object

maybe try

[0]['Date']

I am not too familiar w/ mustache templates, but does this help? https://stackoverflow.com/questions/6516297/can-mustache-iterate-a-top-level-array#10014082

Yeah, this is the right answer. The JSON comes through as a map, not an object, so you can’t use dot notation to get at properties.

I read this when I went to bed yesterday, I could not agree more: https://eev.ee/blog/2016/03/06/maybe-we-could-tone-down-the-javascript/

one thing lead to the other, so I ended up here: https://gossipsweb.net/

It almost felt like a spiritual experience. Walking without any weight on my shoulders the very simple path to information.

Can't get it through with that syntax. Here are the files:

On a side note, I just discovered that my API tool can create custom endpoints which can render HTML rather than JSON. I need to do some deep diving this week regarding that feature. One step closer to a dream stack.

LOL @ the HTMX Twitter Banner...

https://birdwatching.zone/ and look at that back button and deep link support! very sophisticated!

There was one other point from this week's Twitter sturm und drang that has been bothering me: When did it become such a perceived sin to work in different languages in different contexts? I've had to work in a couple dozen languages over the course of my career. Switching contexts is hard but not that hard. HTML/CSS/JS(_hs) on the front, whatever on the back (I've been back to PHP lately, with the 8.x releases), and I'm one of those weirdos who writes PLPGSQL stored procedures in the DB tier rather than wrestle with ORMs or query builders in the web server tier. Use the proper (for you) tools for the proper contexts. JS full-stack seems like masochism to me.

It was a big selling point for node. I think it was an attempt to address the growing JS complexity by embracing JS even tighter. From a very high, abstract level, it sounds good -- learn one language well instead of two/three/four languages poorly.

But it turns out that different tools are better for different jobs. JS is great on browsers because it's ubiquitous. On a server, I'd much prefer something built for the job.

I do like the concept of WASM. Front end these days ends up with a "compile" analogue anyway, so may as well transpile whatever you want into a runtime for the browser. But JS would not be my choice of weapons pretty much anywhere for anything more than a sprinkling.

Yeah, WASM sounds cool, but it's let me down in practice. I think it's because different tools work differently (because they're made for different jobs). For example, Go is fantastic on servers. They've also made a WASM compiler. But to make Go work in WASM, they had to include a huge runtime component. So, any Go that I compile into WASM is already bloated by the compatibility layer they needed to make it work.

I used one of the Go->WASM projects. It let me down, too.

In tech, we forget that things just take time to grow. It'll probably just take another 10 years of someone optimizing the crap out of it, then our kids will use WASM everywhere.

And I'll still be converting htmx to Typescript v75

Remember in the 2000s, there was a lot of interest in DSLs. Maybe we’ll see a resurgence.