Skipping React hydration… so, only rendering on the server? BBC just re-invented server-side rendering, bravo 👏😆

I say this as an 8-year React developer. Damn, our industry really drank the kool-aid on on this one. Of course, plenty of people have been saying that React for static content like this has always been a misapplication of the tool, I’ve been reading opinions like that the entire time I’ve been working with it.

I’m glad BBC is doing this, though. Legitimate kudos to them for recognizing the issue and working towards fixing it. I actually think there are some great benefits that React has given us:

• A universal component interface for all JavaScript-targeting languages
• An enormous ecosystem of components
• Popularization of the “component model”, which has spread to basically every other language that is used to render user interfaces (the mental model is just that much better)
• A quickly-evolving (React is arguably on its third major paradigm shift) testbed for what works best for UI development

I would be happy if React was supplanted in the near future, but I also have some fondness for it. I know I’m way off topic on this post, just felt like talking about React.

Tracking scripts degrade gracefully, so you can disable JS, and the page should still work just fine.

This is why I come to Lemmy, for bean recipes nested 6 comment levels down.

I tried Warp back when it first came out, but haven’t really considered switching to it since then. What do you really love about it?

This was a really good talk! I’ve been using git for about a decade, but I learned several new things. Here’s a few:

• Sorting git log by committer date
• Speeding up common operations on bigger repos with git maintenance
• More useful file blame with the -C flag on git blame

Mmm, gimme that salty sodium light.

Same. I only got through day 3 last year since I didn’t have time to do both the learning and the solving. I think I need a longer term project to give me more focus when learning a new language. This year I’m just sticking with my usual language Elixir, which I always enjoy.

While I agree that a lot of the hype around AI goes overboard, you should probably read this recent paper about AI classification: https://arxiv.org/abs/2311.02462

Systems like DeepMind are narrow AI, whereas LLMs are general AI.

As a JetBrains Mono user for the past couple of years, I used Monaspace all day this past Friday to try it out, and it was not for me. The oval shape of JetBrains Mono glyphs is so aesthetically pleasing to me, and I don’t think I’d be able to switch to another font that doesn’t have similar styling.

That motherboard’s M.2 slot has its own heatsink, so you shouldn’t buy an M.2 SSD with a heatsink if you plan on installing it in that slot. Instead, get the model without one: https://www.newegg.com/western-digital-2tb-black-sn850x-nvme/p/N82E16820250247?item=N82E16820250247

I actually bought the exact same one you have listed and ended up having to pry the heatsink off. My fingers were very sore afterwards.

I’ve gotta go with Elixir. I’ve been using it professionally for about 7 years now, and it’s been amazing to see it grow in the way it has. It’s very well-designed, based on a rock-solid foundation (Erlang/OTP), has an amazing standard library with fantastic documentation, and has a strong culture of pragmatism and developer friendliness.

I personally work in web dev, and Phoenix has consistently shown itself to be an extremely capable web framework. LiveView has kicked off a new paradigm for making web applications that most major languages are copying.

There’s a solid embedded story with Nerves, and serious foray into ML/AI with Nx. It’s obviously not suited for the lower level stuff, but that’s when Rust integration with Rustler comes in. Many wouldn’t be interested in Elixir because of it’s dynamic typing, but there’s serious effort by the creator and a research team into developing a gradual type system for the language.

Just an overall solid language that’s extremely pleasant to use with a really healthy and (slowly but surely) growing community.

I really love Elm, and it challenges the common notion of what it means to be a “healthy” language/ecosystem. It’s a beautiful passion project that can really only be used if you adhere to the vision of its creator, but it’s a really admirable and utopian vision.

The reasons for it not being very popular are pretty clear (slow language evolution, “one way to do anything”, perfectionist design), but it’s an extremely cohesive and friendly language. I’ve never used it for anything serious, but I hope it stays around. Clearly the creator isn’t aiming for widespread adoption, but I hope that the niche it’s created grows nonetheless, because it’s a lovely ecosystem and community.

I don’t know exactly what environment you’re working, but Postgres has a reputation as the best DBMS to work with from a developer’s perspective. I definitely feel that way, at least.

What type of lab are you working in, and what other technologies do you work with?

I changed my VS Code theme to Dracula around Halloween 2016 for fun. I never changed it back.

Looking at your posts, it seems like you’re really into ecology/farming/wildlife. I think Lemmy is currently seeing the biggest growth with its tech and tech-adjacent communities. Whether it’s because it’s a little more complex to use or because that’s just the demographic that knows about it more, I can’t say for sure.

It reminds me of the earlier days of Reddit (which I didn’t even participate in), when it was almost solely a programming/tech community. As it grew in users, so did the variety of communities. I think Lemmy is going to be similar.

I applaud you for building up the communities you’re a part of. I hope that you can look back in a few years and realize that you sowed the seeds for something that grew much bigger.

Keybindings really can make a huge difference, whether they’re existing ones you discover or ones that you create.

I remember discovering VS Code’s default key binding for “going back” to the previous cursor position (going across files), which is Ctrl±. That really reduced the mental load of keeping track of which functions/files I was visiting and made me feel more at ease jumping around, knowing I could easily get back to where I was. If you need more context on some code you’re writing/reading, you can more easily go off on little tangents to gather whatever context you need, and that speeds the whole process up.