Robert Burnham
burnham.bsky.social
Robert Burnham
@burnham.bsky.social
Pragmatist & Principal Front-End Engineer. My hobbies include having lots of hobbies, losing interest in my hobbies, and pursuing old hobbies. Lifelong passion in software development and gaming. Recent interests include woodworking, astronomy, and cooking
Javascript isn't anything. It has none of the benefits of FP and obviously OO isn't even in the running for consideration.
October 4, 2025 at 9:57 PM
This is just the reality of the utility the two offer. Flexbox is going to be the primary tool you use. Grid will be mostly just for grid layouts (but not all, some are still better in Flexbox).
September 29, 2025 at 12:53 AM
I was on the fence about picking up BL4, given the issues surrounding its performance. I was willing to set those aside until I saw how Randy Pitchford (and indeed game's support team) are handling it....At least there's no shortage of good games to choose from besides Borderlands
September 15, 2025 at 6:41 PM
CSS's reputation can only go up. It's already universally hated by both web developers and designers alike.
September 14, 2025 at 5:48 PM
It would benefit the feed - regardless of anyone's individual political stance - to filter posts containing Gaza. Seems to be a bunch of bots posting the same handful of measures.
August 28, 2025 at 5:08 AM
The second paper describes the application of a combinations of skills to produce novel output, but not unrelated to either of the skills used. You're welcome to continue to cite and argue to your heart's content but it's not a very good use of my time if this is what you're bringing.
August 25, 2025 at 6:24 AM
Neither of those papers match the claims you're making... The first paper defines "emergent behavior" merely as the presence of capabilities not found in smaller models, it's a paper indicating that the capabilities of larger models can't be extrapolated from smaller ones.
August 25, 2025 at 6:24 AM
You should read thrugh the rest of this thread then... Lol, you are woefully mistaken.
August 25, 2025 at 3:32 AM
Just one difference though, is the fact that humans are not exclusively capable of generating output based on the input they've been given. That this conversation is littered with individuals who think an llm is comparable against human intelligence and creativity reeks of an echo chamber
August 25, 2025 at 3:31 AM
I'm aware, but the context here should be pretty obvious we're outside the realm of a technical discussion. I'm not going to conflate a coincidental usage of an appropriate term to be correct when it's surrounded by an attempt to make this tech seem like something it's not.
August 25, 2025 at 3:22 AM
But the reality is that it doesn't know what a question is. It doesn't know what an answer is. When I described it as a next-word prediction engine, that's not an analogy. That's quite close to the truth.
August 25, 2025 at 2:57 AM
I think you're approaching this with a preconception you're looking to have validated. It's not making inferences; there's no intelligence. It's not making connections that you've overlooked. Your phrasing suggests the notion that it has an answer to any given question, waiting to be "expressed"
August 25, 2025 at 2:57 AM
These large models are incredibly complex next-word prediction engines. Your prompt contributes to the input weights of millions of data points and the output is nothing more than the model using a weighting formula to determine an appropriate output. It's not creativity, it's complex heuristics
August 25, 2025 at 2:18 AM
I'm not saying they're not useful. As large data aggregation and parsing mechanisms they're phenomenal. They're especially useful in taking a description of a problem and finding the solution, which sounds like it might be what you're describing.
August 25, 2025 at 2:14 AM
The belief of originality doesn't make it original. It just makes you ignorant.
August 25, 2025 at 2:11 AM
Your assertion is fundamentally flawed. There is nothing being output by llms that is something that hasn't been done elsewhere. Use it on something outside of mainstream frameworks or architecture and it's output goes to shit rather quickly.
August 25, 2025 at 12:32 AM
Time to boot to a USB distro!
August 10, 2025 at 7:56 PM
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
July 13, 2025 at 12:23 AM
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.
July 8, 2025 at 2:39 PM
We've used leaflet pretty extensively in some of our stuff. What's your take on maplibre vs it?
July 8, 2025 at 12:41 PM
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.
July 8, 2025 at 12:40 PM
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.
July 7, 2025 at 12:02 PM
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.
July 7, 2025 at 2:16 AM
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
July 7, 2025 at 1:42 AM