Programming

cross-posted from: https://gregtech.eu/post/21117342

Elixir v1.19 released: type checking of protocols and anonymous functions, broader type inference, improved compile times, and more

cross-posted from: https://lemmy.dbzer0.com/post/55628224

I’ve been thinking about discovering underappreciated Lemmy instances. GitHub’s awesome-lemmy-instances used to serve a similar purpose, but it hasn’t been updated in a long time, and I haven’t found anything else like it.

I got the idea from this post about finding decentralized communities in the Fediverse. I’m thinking of a Lemmy bot that tracks Lemmy instances, calculates the average number of active users and standard deviation, and identifies instances with activity below the average plus two standard deviations. It would then rank these underutilized instances by performance metrics like uptime and response time, and periodically update a curated list on Lemmy to guide users toward instances that could use more participation.

I'd love feedback on how you would go about doing something like this. And specifically how to rank by performance.

Hey,

I’m exploring the idea of a webpage where you can paste a function (or a block of code) in any programming language, and it outputs a list of specific, actionable refactoring suggestions - things like:

• Unnecessary complexity
• Poor naming conventions
• Duplicated logic
• Violations of language-specific best practices
• Readability issues

The goal is to help developers quickly spot areas for improvement and make their code cleaner, more maintainable, and easier to understand.

Questions for you:

• Would you use such a tool? Why or why not?
• What features would make it important for you? (e.g., integration with GitHub, support for obscure languages, explanations for each suggestion, etc.)
• Are you ready to pay for a tool like this (for example, paying for access to advanced checks or being able to tune checks for your programming style)?
• Are there existing tools you love (or hate) that do something similar?

It’s been 60 days since I started building Brahma-Firelight JS, a Rust-based Node.js framework.

In its initial release, v1.0, it came out with massive performance — but without async support. People were genuinely surprised by the benchmarks, but many asked for Express-like ergonomics and full async support.

That feedback led to v1.5, which introduces some groundbreaking changes:

1. Async Support: Even if the JS event loop gets stuck, the Tokio runtime gracefully handles the response with a gateway timeout. This ensures high-level safety — combining the power of two different runtime worlds.

2. Native Server Timeout and Body-Limit Configuration: Configure request timeouts and body size limits directly — no extra dependencies needed.

3. True Multi-Threaded Server: Runs across multiple threads without requiring clusters or PM2 — thanks to Rust’s Tokio and Hyper.

4. Express + Hono-Style Ergonomics: Brahma-Firelight keeps developer experience simple and intuitive — no need to learn Rust to write production-grade JS apps.

After dozens of suggestions and refinements, we’ve finally stabilized the framework for production use.

Try it out: https://shyam20001.github.io/rsjs/ If you find it helpful, drop your suggestions or PRs — every contribution counts.

Qt 6.10 is now available, with new features and improvements for application developers and device creators!

Highlights for UI builders include a new flex-box layout system for Qt Quick, and support for more vector animations in SVG and Lottie format. And we have listened to your feedback and made it easier to exchange data between C++ code and a Qt Quick UI developed in QML. Such data can then be used with the new SearchField control, or with a new FilledSurface graph from the Qt Graphs module.

If you prefer to maintain your existing codebase, upgrading to Qt 6.10 ensures your application automatically aligns with high-contrast system settings on both desktop and mobile platforms. This and other improvements in our accessibility implementation directly benefits users reliant on assistive technologies, improving usability and inclusivity without requiring any additional development effort.

In addition to these highlights, new APIs across the Qt modules bring increased flexibility and productivity for both QML and C++ developers, and for users of Qt Widgets and Qt Quick.

Cross-posted from https://sh.itjust.works/post/47610810