Robert Burnham

Time to boot to a USB distro!

If you have access to a std out you can always console.log, and if you're in a runtime environment (such as a browser) you can put in `debugger` to halt during runtime in order to inspect or use the console to explore all variables in scope

I'm not sure I'd say configuring a bundler (nowadays) is all that complex, but you can just use fetch then. You either fetch your data and write your js for the browser like it's 2012 (which is fine for websites) or use transpilation and more easily write a complex application.

We've used leaflet pretty extensively in some of our stuff. What's your take on maplibre vs it?

It may seem like you're fighting tangled-up sheets in the middle of the night but take a few minutes and try to figure out why it's doing what it's doing. It is (almost always) deterministic.

If it's part of the codebase you don't need to do any of that. Just import it in your client side code and it'll be part of the js bundle generated. You only need fetch if you don't want it to be part of your bundle, intentionally.

Not trying to fix anything. There's just nothing complex or difficult about working with json in Javascript. Certainly not if you're working client side in an environment that facilitates es modules syntax.

If this is a transpiled app and the json file is part of the bundle, you shouldn't need to assert at all. If you do (and I'm understanding you correctly) something is odd with your bundling configuration

From the server, I presume? You're going to need to obtain it on the client side via fetch and then parse it using JSON.parse. If server side, then yeah you're going to have to use either common js (require) or import with asserts. Or just use the fs api and load the file as a string and JSON.parse

For websites? Sure. For web applications, we use more complex Javascript frameworks, libraries, and supplemental languages like sass and typescript and transpile that down to regular Javascript and css that you're browser can run.

Not meaning to dig on you, but what I really need is fewer blog posts 😅

It works perfectly well for the 1 use case it was designed for, whether you're having to use a bundler or not. If npm is giving you trouble though, I'm not sure what anyone is going to be able to do to help you out.

(provided you're in a browser context, that is, though I'd be surprised if node didn't have the JSON api implemented natively)

No imports required, just Json.parse(). The mdn docs are your friend, just search json.

Show me an understanding of flexbox, stacking context, css (no, not tailwind), and something unique built with React, Vue, Svelte, or Angular. That's all I want to see.

It would still be sad. A backend without a front end has a very low ux ceiling. We're well past the age of users tolerating bad ux regardless of functionality.

Nope, this behavior is on by default. Its opt-out

I actually love this functionality, that and turning `a =>` into `(a, b) =>` just by adding a comma after `a`. At least, once I got used to it.

Well, assuming my experience is representative of the broader software development landscape. But yeah especially if that difference is used in extrapolating other insights, it's a likely factor.

It's not always the case, but the more complex the work is, the more likely the position will be - again, only in my experience - to be listed as an engineering position.

I would describe them as different jobs, based on my experience over the years, but I'm sure perspectives would vary. Positions in for-hire software development shops and small businesses seem almost exclusively to use the developer nomenclature.

Because some front end developer, somewhere, didn't test print View

With those using "engineer" *

One big assumption it seems you're making is that positions labeled with developer are synonymous with using engineer. That's not been my experience at all.

It is remarkably easy with the right library. Building it all yourself might be a more informative experience? That being said I don't know if having low level canvas api experience is all that useful.

@duneawakening.com I - for one - am enjoying the game immensely as a solo player. Aside from all the other great things, the resource gathering, tech pacing, progression, etc all feel great for soloers and the DD doesn't feel like as big of a gamble. Keep up the great work!

Late last night I stumbled upon pinning recipes in @duneawakening.com by pressing `y` while hovering over a schematic in a fabricator. Looks like the feature isn't quite done, or was put on hold? I imagine it might've been conceived as providing a resource overlay?

Ah well that's unfamiliar territory. Honestly the best resource is probably the existing official rendering libraries, especially those closest to the new framework in question.

Gotcha. Is there a specific need to avoid the mainstream renderers? I guess I'm confused what the need is. Or are you just trying to build your own renderer for the hell of it? (in which case I would strongly recommend you to go in blind)

Are you referring to just getting storybook rendering for some component (a typical use case) or are you needing to do something nuanced and unsupported by the typical patterns recommended by the documentation? Your initial phrasing suggests the latter, but your follow up suggests the former.