#opensource framework

[gatethecat]

New powerup available!

Mario and Luigi can now get a new powerup on GME9. Might be from wonder but the first apparition of this powerup was in a SMW hack made looooooong ago.

I present to you... the bubble powerup.

Also made NPCs able to trigger events if you assign a timeline to them ;3

[adafruit]

ESP32-S3 moon phase clock test on 2.1" round TFT display 🌜🌚🖥️

Now that we have somewhat-kinda-sorta working support for RGB TFT displays on the ESP32-S3 - shout out to Jepler, who is doing the hard work over in this PR https://github.com/adafruit/circuitpython/pull/8351 - its time to test it with wifi too! That's right, the S3 can do wifi and these big displays at once, and CircuitPython is a beautiful framework for it since its so fast to iterate. This code snippet is based on PaintYourDragon's moon clock code here https://learn.adafruit.com/moon-phase-clock-for-adafruit-matrixportal but pared down for testing. We get the geolocation from IP, then look up the moon phase. Currently we just hardcoded it to display today's phase, but the next step is generating ~28 different phase images, and we'll display the one for the current evening as the API informs us.

[jasonseney]

It is great to see the team involved sharing this incredible work! 👏

StreamBuilder: our open-source framework for powering your dashboard.

Today, we’re abnormally jazzed to announce that we’re open-sourcing the custom framework we built to power your dashboard on Tumblr. We call it StreamBuilder, and we’ve been using it for many years.

First things first. What is open-sourcing? Open sourcing is a decentralized software development model that encourages open collaboration. In more accessible language, it is any program whose source code is made available for use or modification as users or other developers see fit.

What, then, is StreamBuilder? Well, every time you hit your Following feed, or For You, or search results, a blog’s posts, a list of tagged posts, or even check out blog recommendations, you’re using this framework under the hood. If you want to dive into the code, check it out here on GitHub!

StreamBuilder has a lot going on. The primary architecture centers around “streams” of content: whether posts from a blog, a list of blogs you’re following, posts using a specific tag, or posts relating to a search. These are separate kinds of streams, which can be mixed together, filtered based on certain criteria, ranked for relevancy or engagement likelihood, and more.

On your Tumblr dashboard today you can see how there are posts from blogs you follow, mixed with posts from tags you follow, mixed with blog recommendations. Each of those is a separate stream, with its own logic, but sharing this same framework. We inject those recommendations at certain intervals, filter posts based on who you’re blocking, and rank the posts for relevancy if you have “Best stuff first” enabled. Those are all examples of the functionality StreamBuilder affords for us.

So, what’s included in the box?

The full framework library of code that we use today, on Tumblr, to power almost every feed of content you see on the platform.

A YAML syntax for composing streams of content, and how to filter, inject, and rank them.

Abstractions for programmatically composing, filtering, ranking, injecting, and debugging streams.

Abstractions for composing streams together—such as with carousels, for streams-within-streams.

An abstraction for cursor-based pagination for complex stream templates.

Unit tests covering the public interface for the library and most of the underlying code.

What’s still to come

Documentation. We have a lot to migrate from our own internal tools and put in here!

More example stream templates and example implementations of different common streams.

If you have questions, please check out the code and file an issue there.

[digital-marketing-agency-delhi]

Symfony Development

Symfony, a comprehensive web application framework, is a valuable asset in PHP development, streamlining the creation and maintenance of web applications while minimizing repetitive coding tasks. Symfony furnishes developers with a framework, tools, and components that accelerate the development of web applications. Opting for this framework enables you to launch your applications earlier and without hassle.

[epistictechnology]

Top 8 Reasons ASP.NET Core is the Best Framework for Web Application Development

Are you looking for a strong framework that will enable you to construct web applications at a higher level? Consider ASP.NET Core first. In this post, we'll examine the top eight factors that make ASP.NET Core the greatest framework for creating online applications. ASP.NET Core offers a variety of features and advantages that make it a great choice for your next project, regardless of whether you are an experienced developer or are just beginning your coding adventure. So let's get started and learn why ASP.NET Core is the preferred framework for creating outstanding online apps.

Table of Contents

What is ASP.NET Core?

Difference Between .NET Core and .NET Framework

Reasons to Choose ASP.NET Core for Enterprise Web App Development

What Types of Projects are Best Suited for ASP.NET Core?

When should I choose ASP.NET Core?

Reasons to Learn .NET Core in 2023

Conclusion

FAQs

What is ASP.NET Core?

A cross-platform, open-source framework for creating cutting-edge, cloud-based online applications is called ASP.NET Core. The original ASP.NET framework has been completely redesigned with a focus on performance, modularity, and adaptability. Developers may construct high-performance web applications for Windows, macOS, and Linux with ASP.NET Core. For creating online APIs, web apps, microservices, and IoT (Internet of Things) applications, it offers a single programming model.

Difference Between .NET Core and .NET Framework

Let's define the differences between.NET Core and.NET platforms before going into further detail about why ASP.NET Core is the best platform for developing online applications. Despite the fact that both frameworks are a part of the.NET ecosystem, they have different qualities and applications.

A cross-platform, open-source framework with a focus on contemporary application development is called.NET Core. It offers a compact and versatile architecture for creating web applications with good performance. On the other hand, the Windows-only.NET Framework is better suited for developing conventional Windows programs and legacy software. Modern web application development favors.NET Core over.NET Framework because it delivers superior performance, flexibility, and scalability.

Reasons to Choose ASP.NET Core for Enterprise Web App Development

Outstanding Performance: Performance is a top priority in the design of ASP.NET Core. Applications can run more quickly and use fewer resources thanks to its lightweight and modular architecture. ASP.NET Core provides industry-leading performance for enterprise online applications with features like just-in-time compilation and native code generation.

Cross-platform Compatibility: The fact that ASP.NET Core may be used on a variety of platforms is one of its main benefits. No matter whatever operating system you are aiming for—Windows, macOS, or Linux—ASP.NET Core offers a consistent development environment. Because of this cross-platform compatibility, developers may distribute their applications on the platform of their choosing and reach a larger audience.

Scalability and High Throughput: ASP.NET Core is designed to scale horizontally and handle heavy traffic volumes. It features load balancing, message queuing, and distributed caching, allowing applications to easily handle a lot of concurrent requests. ASP.NET Core can scale to meet your needs whether you are creating a low-traffic enterprise solution or a small-scale application.

Security and Reliability: For web application developers, security is of utmost importance, especially when working with sensitive user data. To safeguard your application from common security threats, ASP.NET Core comes with built-in security capabilities including request validation, data encryption, and authentication procedures. Regular updates and patches for ASP.NET Core also help to maintain the framework's dependability and security.

Modularity and Extensibility: The modular architecture of ASP.NET Core enables developers to pick and select the components they require for their application. This modular design encourages code reuse, maintenance, and testability. Additionally, ASP.NET Core easily interacts with well-liked front-end frameworks and tools, offering developers the freedom to design dynamic user experiences.

Developer Productivity: A wide range of frameworks, libraries, and development tools are included with ASP.NET Core to increase developer productivity. Web application developers can construct and iterate on their projects more quickly thanks to capabilities like scaffolding, code generators, and built-in testing frameworks. The rich community support and copious documentation further enhance the overall developer experience.

Cloud Readiness: As a cloud-ready framework in the age of cloud computing, ASP.NET Core shines. Popular cloud computing systems including Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP) are all smoothly integrated with it. Developers may deploy their apps as Docker containers and take advantage of the scalability and flexibility of cloud environments thanks to ASP.NET Core's native support for containerization.

Cost-Effectiveness: Last but not least, ASP.NET Core provides enterprise web app development with cost-effectiveness. As an open-source framework, it does not require high licensing fees. Additionally, the performance enhancements and scalability capabilities of ASP.NET Core can lead to cost savings by lowering infrastructure needs and enhancing overall effectiveness.

What Types of Projects are Best Suited for ASP.NET Core?

ASP.NET Core is a versatile framework that can be used for various types of web application projects. Here are some examples of projects that are best suited for ASP.NET Core:

Enterprise Web Applications: ASP.NET Core excels in building enterprise-grade web applications that require high performance, scalability, and security. Whether it's a customer-facing e-commerce platform, a content management system, or a business intelligence dashboard, ASP.NET Core provides the necessary tools and features to deliver robust and scalable solutions.

Microservices Architecture: Microservices architecture has gained popularity due to its scalability and flexibility. ASP.NET Core is well-suited for developing microservices-based applications, where each microservices can be built and deployed independently. The lightweight nature of ASP.NET Core and its support for containerization makes it an ideal choice for building microservices.

API Development: ASP.NET Core offers excellent support for building web APIs. Whether you are creating a RESTful API or implementing a GraphQL endpoint, ASP.NET Core provides a powerful framework for designing and implementing your API. The built-in support for content negotiation, model binding, and authentication simplifies the development process and enables rapid API development.

Real-time Applications: If you're working on a real-time application that requires bi-directional communication between clients and servers, ASP.NET Core has you covered. With SignalR, a real-time web framework built on top of ASP.NET Core, you can create interactive and responsive applications like chat apps, collaborative tools, and live dashboards.

Cloud-Native Applications: ASP.NET Core embraces cloud-native development principles and seamlessly integrates with cloud platforms. Whether you are building serverless functions, deploying to Kubernetes clusters, or leveraging the scalability of cloud providers, ASP.NET Core offers the necessary tools and integrations for building cloud-native applications.

When should I choose ASP.NET Core?

Choosing the right framework for your web application development is crucial. Here are some scenarios where ASP.NET Core shines and is the ideal choice:

Cross-platform Requirements: If you need your application to run on multiple platforms, including Windows, macOS, and Linux, ASP.NET Core is the perfect fit. Its cross-platform compatibility ensures that your application can reach a wider audience and cater to different user preferences.

High Performance and Scalability: When performance and scalability are critical factors for your application, ASP.NET Core delivers exceptional results. Its lightweight architecture, native code generation, and support for horizontal scaling make it well-suited for high-traffic and resource-intensive applications.

Modern Development Practices: If you embrace modern development practices like microservices, containerization, and cloud deployment, ASP.NET Core provides the necessary features and integrations. It allows you to adopt industry best practices and leverage the benefits of cloud computing for your applications.

Security and Reliability: When dealing with sensitive data or security-sensitive applications, ASP.NET Core's built-in security features and regular updates ensure that your application remains secure and reliable. The framework's focus on security and its proactive approach to patching vulnerabilities make it a trustworthy choice.

Cost-Effectiveness: ASP.NET Core's open-source nature and its ability to reduce infrastructure costs through performance optimizations make it a cost-effective solution for web application development. If you are looking to maximize your development budget without compromising on quality, ASP.NET Core is an excellent option.

Reasons to Learn .NET Core in 2023

As we step into 2023, learning .NET Core can offer significant benefits for developers. Here are some reasons why you should consider learning .NET Core this year:

Growing Demand: The demand for skilled .NET Core developers is on the rise. Many organizations are adopting .NET Core for their web application projects, creating ample job opportunities for developers with .NET Core expertise. By learning .NET Core, you can position yourself for career growth and job security.

Modern Development Stack: .NET Core provides a modern development stack with support for the latest technologies and frameworks. By learning .NET Core, you gain access to a powerful ecosystem that includes popular frameworks like ASP.NET Core, Entity Framework Core, and Blazor. This empowers you to build cutting-edge web applications using industry-standard tools and practices.

Cross-platform Development: .NET Core's cross-platform compatibility allows you to build applications that can run on multiple operating systems. This versatility gives you the freedom to develop applications for various platforms, expanding your reach and opening doors to new opportunities.

Cloud-Native Development: .NET Core is designed to embrace cloud-native development practices. By learning .NET Core, you can leverage its integrations with cloud platforms like Microsoft Azure and AWS to build scalable, resilient, and cloud-native applications. This knowledge is invaluable in today's cloud-centric landscape.

Community Support: The .NET Core community is vibrant and supportive. Learning .NET Core connects you with a vast network of developers, forums, and resources. You can collaborate, seek guidance, and contribute to the community while enhancing your skills and staying up to date with the latest trends in web application development.

Conclusion

ASP.NET Core is undeniably the best framework for web application development. Its exceptional performance, cross-platform compatibility, scalability, security, and extensive ecosystem make it the top choice for developers. Whether you are working on enterprise web applications, microservices, APIs, real-time apps, or cloud-native solutions, ASP.NET Core empowers you to build robust, high-performance applications that meet the demands of the modern web.

So, if you're ready to take your web application development to new heights, embrace ASP.NET Core and unlock its full potential.

FAQs

1. Can I migrate my existing ASP.NET applications to ASP.NET Core?

Yes, you can migrate your existing ASP.NET applications to ASP.NET Core. Microsoft provides migration guides and tools to assist in the migration process. However, keep in mind that there might be some changes and adjustments required in your codebase to ensure compatibility with ASP.NET Core.

2. Does ASP.NET Core support database integration?

Yes, ASP.NET Core provides robust support for database integration. It includes Entity Framework Core, a powerful object-relational mapper (ORM) that simplifies database operations and supports a wide range of database providers.

3. Can I host ASP.NET Core applications on Linux servers?

Absolutely! ASP.NET Core is cross-platform and can be hosted on Linux servers along with Windows and macOS. This flexibility allows you to choose the hosting environment that best suits your requirements.

4. Is ASP.NET Core suitable for small-scale projects?

Yes, ASP.NET Core is suitable for both small-scale and large-scale projects. Its modular architecture and flexibility make it adaptable to projects of varying sizes. You can start with a small-scale project and scale it up as your needs grow.

5. Does ASP.NET Core support modern front-end frameworks like React or Angular?

Yes, ASP.NET Core seamlessly integrates with modern front-end frameworks like React, Angular, and Vue.js. You can use these frameworks alongside ASP.NET Core to create rich and interactive user interfaces.

Remember, choosing the right framework depends on your specific project requirements and goals. ASP.NET Core offers a robust and versatile foundation for web application development, empowering you to create exceptional applications that meet the needs of the modern digital landscape.

[this-week-in-rust]

This Week in Rust 572

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on X (formerly Twitter) or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.

Want TWIR in your inbox? Subscribe here.

Updates from Rust Community

Official

October project goals update

Next Steps on the Rust Trademark Policy

This Development-cycle in Cargo: 1.83

Re-organising the compiler team and recognising our team members

This Month in Our Test Infra: October 2024

Call for proposals: Rust 2025h1 project goals

Foundation

Q3 2024 Recap from Rebecca Rumbul

Rust Foundation Member Announcement: CodeDay, OpenSource Science(OS-Sci), & PROMOTIC

Newsletters

The Embedded Rustacean Issue #31

Project/Tooling Updates

Announcing Intentrace, an alternative strace for everyone

Ractor Quickstart

Announcing Sycamore v0.9.0

CXX-Qt 0.7 Release

An 'Educational' Platformer for Kids to Learn Math and Reading—and Bevy for the Devs

[ZH][EN] Select HTML Components in Declarative Rust

Observations/Thoughts

Safety in an unsafe world

MinPin: yet another pin proposal

Reached the recursion limit... at build time?

Building Trustworthy Software: The Power of Testing in Rust

Async Rust is not safe with io_uring

Macros, Safety, and SOA

how big is your future?

A comparison of Rust’s borrow checker to the one in C#

Streaming Audio APIs in Rust pt. 3: Audio Decoding

[audio] InfinyOn with Deb Roy Chowdhury

Rust Walkthroughs

Difference Between iter() and into_iter() in Rust

Rust's Sneaky Deadlock With if let Blocks

Why I love Rust for tokenising and parsing

"German string" optimizations in Spellbook

Rust's Most Subtle Syntax

Parsing arguments in Rust with no dependencies

Simple way to make i18n support in Rust with with examples and tests

How to shallow clone a Cow

Beginner Rust ESP32 development - Snake

[video] Rust Collections & Iterators Demystified 🪄

Research

Charon: An Analysis Framework for Rust

Crux, a Precise Verifier for Rust and Other Languages

Miscellaneous

Feds: Critical Software Must Drop C/C++ by 2026 or Face Risk

[audio] Let's talk about Rust with John Arundel

[audio] Exploring Rust for Embedded Systems with Philip Markgraf

Crate of the Week

This week's crate is wtransport, an implementation of the WebTransport specification, a successor to WebSockets with many additional features.

Thanks to Josh Triplett for the suggestion!

Please submit your suggestions and votes for next week!

Calls for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

RFCs

No calls for testing were issued this week.

Rust

No calls for testing were issued this week.

Rustup

No calls for testing were issued this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Call for Participation; projects and speakers

CFP - Projects

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

If you are a Rust project owner and are looking for contributors, please submit tasks here or through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!

CFP - Events

Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.

If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!

Updates from the Rust Project

473 pull requests were merged in the last week

account for late-bound depth when capturing all opaque lifetimes

add --print host-tuple to print host target tuple

add f16 and f128 to invalid_nan_comparison

add lp64e RISC-V ABI

also treat impl definition parent as transparent regarding modules

cleanup attributes around unchecked shifts and unchecked negation in const

cleanup op lookup in HIR typeck

collect item bounds for RPITITs from trait where clauses just like associated types

do not enforce ~const constness effects in typeck if rustc_do_not_const_check

don't lint irrefutable_let_patterns on leading patterns if else if let-chains

double-check conditional constness in MIR

ensure that resume arg outlives region bound for coroutines

find the generic container rather than simply looking up for the assoc with const arg

fix compiler panic with a large number of threads

fix suggestion for diagnostic error E0027

fix validation when lowering ? trait bounds

implement suggestion for never type fallback lints

improve missing_abi lint

improve duplicate derive Copy/Clone diagnostics

llvm: match new LLVM 128-bit integer alignment on sparc

make codegen help output more consistent

make sure type_param_predicates resolves correctly for RPITIT

pass RUSTC_HOST_FLAGS at once without the for loop

port most of --print=target-cpus to Rust

register ~const preds for Deref adjustments in HIR typeck

reject generic self types

remap impl-trait lifetimes on HIR instead of AST lowering

remove "" case from RISC-V llvm_abiname match statement

remove do_not_const_check from Iterator methods

remove region from adjustments

remove support for -Zprofile (gcov-style coverage instrumentation)

replace manual time convertions with std ones, comptime time format parsing

suggest creating unary tuples when types don't match a trait

support clobber_abi and vector registers (clobber-only) in PowerPC inline assembly

try to point out when edition 2024 lifetime capture rules cause borrowck issues

typingMode: merge intercrate, reveal, and defining_opaque_types

miri: change futex_wait errno from Scalar to IoError

stabilize const_arguments_as_str

stabilize if_let_rescope

mark str::is_char_boundary and str::split_at* unstably const

remove const-support for align_offset and is_aligned

unstably add ptr::byte_sub_ptr

implement From<&mut {slice}> for Box/Rc/Arc<{slice}>

rc/Arc: don't leak the allocation if drop panics

add LowerExp and UpperExp implementations to NonZero

use Hacker's Delight impl in i64::midpoint instead of wide i128 impl

xous: sync: remove rustc_const_stable attribute on Condvar and Mutex new()

add const_panic macro to make it easier to fall back to non-formatting panic in const

cargo: downgrade version-exists error to warning on dry-run

cargo: add more metadata to rustc_fingerprint

cargo: add transactional semantics to rustfix

cargo: add unstable -Zroot-dir flag to configure the path from which rustc should be invoked

cargo: allow build scripts to report error messages through cargo::error

cargo: change config paths to only check CARGO_HOME for cargo-script

cargo: download targeted transitive deps of with artifact deps' target platform

cargo fix: track version in fingerprint dep-info files

cargo: remove requirement for --target when invoking Cargo with -Zbuild-std

rustdoc: Fix --show-coverage when JSON output format is used

rustdoc: Unify variant struct fields margins with struct fields

rustdoc: make doctest span tweak a 2024 edition change

rustdoc: skip stability inheritance for some item kinds

mdbook: improve theme support when JS is disabled

mdbook: load the sidebar toc from a shared JS file or iframe

clippy: infinite_loops: fix incorrect suggestions on async functions/closures

clippy: needless_continue: check labels consistency before warning

clippy: no_mangle attribute requires unsafe in Rust 2024

clippy: add new trivial_map_over_range lint

clippy: cleanup code suggestion for into_iter_without_iter

clippy: do not use gen as a variable name

clippy: don't lint unnamed consts and nested items within functions in missing_docs_in_private_items

clippy: extend large_include_file lint to also work on attributes

clippy: fix allow_attributes when expanded from some macros

clippy: improve display of clippy lints page when JS is disabled

clippy: new lint map_all_any_identity

clippy: new lint needless_as_bytes

clippy: new lint source_item_ordering

clippy: return iterator must not capture lifetimes in Rust 2024

clippy: use match ergonomics compatible with editions 2021 and 2024

rust-analyzer: allow interpreting consts and statics with interpret function command

rust-analyzer: avoid interior mutability in TyLoweringContext

rust-analyzer: do not render meta info when hovering usages

rust-analyzer: add assist to generate a type alias for a function

rust-analyzer: render extern blocks in file_structure

rust-analyzer: show static values on hover

rust-analyzer: auto-complete import for aliased function and module

rust-analyzer: fix the server not honoring diagnostic refresh support

rust-analyzer: only parse safe as contextual kw in extern blocks

rust-analyzer: parse patterns with leading pipe properly in all places

rust-analyzer: support new #[rustc_intrinsic] attribute and fallback bodies

Rust Compiler Performance Triage

A week dominated by one large improvement and one large regression where luckily the improvement had a larger impact. The regression seems to have been caused by a newly introduced lint that might have performance issues. The improvement was in building rustc with protected visibility which reduces the number of dynamic relocations needed leading to some nice performance gains. Across a large swath of the perf suit, the compiler is on average 1% faster after this week compared to last week.

Triage done by @rylev. Revision range: c8a8c820..27e38f8f

Summary:

(instructions:u) mean range count Regressions ❌ (primary) 0.8% [0.1%, 2.0%] 80 Regressions ❌ (secondary) 1.9% [0.2%, 3.4%] 45 Improvements ✅ (primary) -1.9% [-31.6%, -0.1%] 148 Improvements ✅ (secondary) -5.1% [-27.8%, -0.1%] 180 All ❌✅ (primary) -1.0% [-31.6%, 2.0%] 228

1 Regression, 1 Improvement, 5 Mixed; 3 of them in rollups 46 artifact comparisons made in total

Full report here

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

[RFC] Default field values

RFC: Give users control over feature unification

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

[disposition: merge] Add support for use Trait::func

Tracking Issues & PRs

Rust

[disposition: merge] Stabilize Arm64EC inline assembly

[disposition: merge] Stabilize s390x inline assembly

[disposition: merge] rustdoc-search: simplify rules for generics and type params

[disposition: merge] Fix ICE when passing DefId-creating args to legacy_const_generics.

[disposition: merge] Tracking Issue for const_option_ext

[disposition: merge] Tracking Issue for const_unicode_case_lookup

[disposition: merge] Reject raw lifetime followed by ', like regular lifetimes do

[disposition: merge] Enforce that raw lifetimes must be valid raw identifiers

[disposition: merge] Stabilize WebAssembly multivalue, reference-types, and tail-call target features

Cargo

No Cargo Tracking Issues or PRs entered Final Comment Period this week.

Language Team

No Language Team Proposals entered Final Comment Period this week.

Language Reference

No Language Reference RFCs entered Final Comment Period this week.

Unsafe Code Guidelines

No Unsafe Code Guideline Tracking Issues or PRs entered Final Comment Period this week.

New and Updated RFCs

[new] Implement The Update Framework for Project Signing

[new] [RFC] Static Function Argument Unpacking

[new] [RFC] Explicit ABI in extern

[new] Add homogeneous_try_blocks RFC

Upcoming Events

Rusty Events between 2024-11-06 - 2024-12-04 🦀

Virtual

2024-11-06 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

2024-11-07 | Virtual (Berlin, DE) | OpenTechSchool Berlin + Rust Berlin

Rust Hack and Learn | Mirror: Rust Hack n Learn Meetup

2024-11-08 | Virtual (Jersey City, NJ, US) | Jersey City Classy and Curious Coders Club Cooperative

Rust Coding / Game Dev Fridays Open Mob Session!

2024-11-12 | Virtual (Dallas, TX, US) | Dallas Rust

Second Tuesday

2024-11-14 | Virtual (Charlottesville, NC, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2024-11-14 | Virtual and In-Person (Lehi, UT, US) | Utah Rust

Green Thumb: Building a Bluetooth-Enabled Plant Waterer with Rust and Microbit

2024-11-14 | Virtual and In-Person (Seattle, WA, US) | Seattle Rust User Group

November Meetup

2024-11-15 | Virtual (Jersey City, NJ, US) | Jersey City Classy and Curious Coders Club Cooperative

Rust Coding / Game Dev Fridays Open Mob Session!

2024-11-19 | Virtual (Los Angeles, CA, US) | DevTalk LA

Discussion - Topic: Rust for UI

2024-11-19 | Virtual (Washington, DC, US) | Rust DC

Mid-month Rustful

2024-11-20 | Virtual and In-Person (Vancouver, BC, CA) | Vancouver Rust

Embedded Rust Workshop

2024-11-21 | Virtual (Berlin, DE) | OpenTechSchool Berlin + Rust Berlin

Rust Hack and Learn | Mirror: Rust Hack n Learn Meetup

2024-11-21 | Virtual (Charlottesville, NC, US) | Charlottesville Rust Meetup

Trustworthy IoT with Rust--and passwords!

2024-11-21 | Virtual (Rotterdam, NL) | Bevy Game Development

Bevy Meetup #7

2024-11-25 | Bratislava, SK | Bratislava Rust Meetup Group

ONLINE Talk, sponsored by Sonalake - Bratislava Rust Meetup

2024-11-26 | Virtual (Dallas, TX, US) | Dallas Rust

Last Tuesday

2024-11-28 | Virtual (Charlottesville, NC, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2024-12-03 | Virtual (Buffalo, NY, US) | Buffalo Rust Meetup

Buffalo Rust User Group

Asia

2024-11-28 | Bangalore/Bengaluru, IN | Rust Bangalore

RustTechX Summit 2024 BOSCH

2024-11-30 | Tokyo, JP | Rust Tokyo

Rust.Tokyo 2024

Europe

2024-11-06 | Oxford, UK | Oxford Rust Meetup Group

Oxford Rust and C++ social

2024-11-06 | Paris, FR | Paris Rustaceans

Rust Meetup in Paris

2024-11-09 - 2024-11-11 | Florence, IT | Rust Lab

Rust Lab 2024: The International Conference on Rust in Florence

2024-11-12 | Zurich, CH | Rust Zurich

Encrypted/distributed filesystems, wasm-bindgen

2024-11-13 | Reading, UK | Reading Rust Workshop

Reading Rust Meetup

2024-11-14 | Stockholm, SE | Stockholm Rust

Rust Meetup @UXStream

2024-11-19 | Leipzig, DE | Rust - Modern Systems Programming in Leipzig

Daten sichern mit ZFS (und Rust)

2024-11-21 | Edinburgh, UK | Rust and Friends

Rust and Friends (pub)

2024-11-21 | Oslo, NO | Rust Oslo

Rust Hack'n'Learn at Kampen Bistro

2024-11-23 | Basel, CH | Rust Basel

Rust + HTMX - Workshop #3

2024-11-27 | Dortmund, DE | Rust Dortmund

Rust Dortmund

2024-11-28 | Aarhus, DK | Rust Aarhus

Talk Night at Lind Capital

2024-11-28 | Augsburg, DE | Rust Meetup Augsburg

Augsburg Rust Meetup #10

2024-11-28 | Berlin, DE | OpenTechSchool Berlin + Rust Berlin

Rust and Tell - Title

North America

2024-11-07 | Chicago, IL, US | Chicago Rust Meetup

Chicago Rust Meetup

2024-11-07 | Montréal, QC, CA | Rust Montréal

November Monthly Social

2024-11-07 | St. Louis, MO, US | STL Rust

Game development with Rust and the Bevy engine

2024-11-12 | Ann Arbor, MI, US | Detroit Rust

Rust Community Meetup - Ann Arbor

2024-11-14 | Mountain View, CA, US | Hacker Dojo

Rust Meetup at Hacker Dojo

2024-11-15 | Mexico City, DF, MX | Rust MX

Multi threading y Async en Rust parte 2 - Smart Pointes y Closures

2024-11-15 | Somerville, MA, US | Boston Rust Meetup

Ball Square Rust Lunch, Nov 15

2024-11-19 | San Francisco, CA, US | San Francisco Rust Study Group

Rust Hacking in Person

2024-11-23 | Boston, MA, US | Boston Rust Meetup

Boston Common Rust Lunch, Nov 23

2024-11-25 | Ferndale, MI, US | Detroit Rust

Rust Community Meetup - Ferndale

2024-11-27 | Austin, TX, US | Rust ATX

Rust Lunch - Fareground

Oceania

2024-11-12 | Christchurch, NZ | Christchurch Rust Meetup Group

Christchurch Rust Meetup

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

Any sufficiently complicated C project contains an adhoc, informally specified, bug ridden, slow implementation of half of cargo.

– Folkert de Vries at RustNL 2024 (youtube recording)

Thanks to Collin Richards for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

[playstationvii]

#Playstation7 #framework #BasicArchitecture #RawCode #RawScript #Opensource #DigitalConsole

To build a new gaming console’s digital framework from the ground up, you would need to integrate several programming languages and technologies to manage different aspects of the system. Below is an outline of the code and language choices required for various parts of the framework, focusing on languages like C++, Python, JavaScript, CSS, MySQL, and Perl for different functionalities.

1. System Architecture Design (Low-level)

• Language: C/C++, Assembly

• Purpose: To program the low-level system components such as CPU, GPU, and memory management.

• Example Code (C++) – Low-Level Hardware Interaction:

#include <iostream>

int main() {

// Initialize hardware (simplified example)

std::cout << "Initializing CPU...\n";

// Set up memory management

std::cout << "Allocating memory for GPU...\n";

// Example: Allocating memory for gaming graphics

int* graphicsMemory = new int[1024]; // Allocate 1KB for demo purposes

std::cout << "Memory allocated for GPU graphics rendering.\n";

// Simulate starting the game engine

std::cout << "Starting game engine...\n";

delete[] graphicsMemory; // Clean up

return 0;

}

2. Operating System Development

• Languages: C, C++, Python (for utilities)

• Purpose: Developing the kernel and OS for hardware abstraction and user-space processes.

• Kernel Code Example (C) – Implementing a simple syscall:

#include <stdio.h>

#include <unistd.h>

int main() {

// Example of invoking a custom system call

syscall(0); // System call 0 - usually reserved for read in UNIX-like systems

printf("System call executed\n");

return 0;

}

3. Software Development Kit (SDK)

• Languages: C++, Python (for tooling), Vulkan or DirectX (for graphics APIs)

• Purpose: Provide libraries and tools for developers to create games.

• Example SDK Code (Vulkan API with C++):

#include <vulkan/vulkan.h>

VkInstance instance;

void initVulkan() {

VkApplicationInfo appInfo = {};

appInfo.sType = VK_STRUCTURE_TYPE_APPLICATION_INFO;

appInfo.pApplicationName = "GameApp";

appInfo.applicationVersion = VK_MAKE_VERSION(1, 0, 0);

appInfo.pEngineName = "GameEngine";

appInfo.engineVersion = VK_MAKE_VERSION(1, 0, 0);

appInfo.apiVersion = VK_API_VERSION_1_0;

VkInstanceCreateInfo createInfo = {};

createInfo.sType = VK_STRUCTURE_TYPE_INSTANCE_CREATE_INFO;

createInfo.pApplicationInfo = &appInfo;

vkCreateInstance(&createInfo, nullptr, &instance);

std::cout << "Vulkan SDK Initialized\n";

}

4. User Interface (UI) Development

• Languages: JavaScript, HTML, CSS (for UI), Python (backend)

• Purpose: Front-end interface design for the user experience and dashboard.

• Example UI Code (HTML/CSS/JavaScript):

<!DOCTYPE html>

<html>

<head>

<title>Console Dashboard</title>

<style>

body { font-family: Arial, sans-serif; background-color: #282c34; color: white; }

.menu { display: flex; justify-content: center; margin-top: 50px; }

.menu button { padding: 15px 30px; margin: 10px; background-color: #61dafb; border: none; cursor: pointer; }

</style>

</head>

<body>

<div class="menu">

<button onclick="startGame()">Start Game</button>

<button onclick="openStore()">Store</button>

</div>

<script>

function startGame() {

alert("Starting Game...");

}

function openStore() {

alert("Opening Store...");

}

</script>

</body>

</html>

5. Digital Store Integration

• Languages: Python (backend), MySQL (database), JavaScript (frontend)

• Purpose: A backend system for purchasing and managing digital game licenses.

• Example Backend Code (Python with MySQL):

import mysql.connector

def connect_db():

db = mysql.connector.connect(

host="localhost",

user="admin",

password="password",

database="game_store"

)

return db

def fetch_games():

db = connect_db()

cursor = db.cursor()

cursor.execute("SELECT * FROM games")

games = cursor.fetchall()

for game in games:

print(f"Game ID: {game[0]}, Name: {game[1]}, Price: {game[2]}")

db.close()

fetch_games()

6. Security Framework Implementation

• Languages: C++, Python, Perl (for system scripts)

• Purpose: Ensure data integrity, authentication, and encryption.

• Example Code (Python – Encrypting User Data):

from cryptography.fernet import Fernet

# Generate a key for encryption

key = Fernet.generate_key()

cipher_suite = Fernet(key)

# Encrypt sensitive user information (e.g., account password)

password = b"SuperSecretPassword"

encrypted_password = cipher_suite.encrypt(password)

print(f"Encrypted Password: {encrypted_password}")

# Decrypting the password

decrypted_password = cipher_suite.decrypt(encrypted_password)

print(f"Decrypted Password: {decrypted_password}")

7. Testing and Quality Assurance

• Languages: Python (for automated tests), Jest (for JavaScript testing)

• Purpose: Unit testing, integration testing, and debugging.

• Example Unit Test (Python using unittest):

import unittest

def add(a, b):

return a + b

class TestGameFramework(unittest.TestCase):

def test_add(self):

self.assertEqual(add(10, 20), 30)

if __name__ == '__main__':

unittest.main()

8. Order of Implementation

• Phase 1: Focus on core system architecture (low-level C/C++) and OS development.

• Phase 2: Develop SDK and start building the basic framework for UI and input management.

• Phase 3: Work on backend systems like the digital store and integrate with front-end UI.

• Phase 4: Begin rigorous testing and debugging using automated test suites.

This comprehensive approach gives you a detailed idea of how each component can be built using a combination of these languages and technologies. Each section is modular, allowing teams to work on different aspects of the console simultaneously.

[Pixel Art/Sprites/Buildinodels/VictoriaSecretPixelArtKit #Playstation7 #DearDearestBrands]

[allineedistostudy]

Free resources!!

Learn to Code — For Free — Coding Courses for Busy People (freecodecamp.org) -> Free code camp

https://roadmap.sh/ -> Road map: so many roadmaps for high level overviews to guide you for tech roles

Big-O Algorithm Complexity Cheat Sheet (Know Thy Complexities!) @ericdrowell (bigocheatsheet.com) -> Big old cheat sheet: Visual display of big O

GitHub - prakhar1989/awesome-courses: :books: List of awesome university courses for learning Computer Science! -> GitHub: FREE courses on everything by universities compiled by Prakhar1989

https://visualgo.net/en -> 𝐕𝐢𝐬𝐮𝐚𝐥𝐀𝐥𝐠𝐨:Visual display of algorithms

https://devdocs.io/ -> 𝐃𝐞𝐯𝐃𝐨𝐜𝐬: Documentation of popular libraries and frameworks

Technical Interview Guide for Busy Engineers | Tech Interview Handbook -> 𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐇𝐚𝐧𝐝𝐛𝐨𝐨𝐤: all you need for technical and behaviour interviews

Grind 75 - A better Blind 75 you can customize, by the author of Blind 75 (techinterviewhandbook.org) ->𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐇𝐚𝐧𝐝𝐛𝐨𝐨𝐤: useful for technical cause you can set a guide on how much time you have

https://caniuse.com/ --> 𝐂𝐚𝐧𝐈𝐔𝐬𝐞:what web browser support for CSS

Leetcode Patterns (seanprashad.com) -> 𝐒𝐞𝐚𝐧 𝐏𝐫𝐚𝐬𝐡𝐚𝐝: Leetcode patterns with what companies ask it

14 Patterns to Ace Any Coding Interview Question | HackerNoon -> 𝐇𝐚𝐜𝐤𝐞𝐫𝐍𝐨𝐨𝐧: helpful article to pass coding interviews

GitHub - EbookFoundation/free-programming-books: :books: Freely available programming books -> 𝐆𝐢𝐭𝐡𝐮𝐛: FREE BOOKS by EbookFoundation

Your Career in Web Development Starts Here | The Odin Project -> 𝐎𝐝𝐢𝐧 𝐏𝐫𝐨𝐣𝐞𝐜𝐭: road map for full stack JS or ruby on rails

Jake's Resume - Overleaf, Online LaTeX Editor -> 𝐎𝐯𝐞𝐫𝐥𝐞𝐚𝐟: Jake's Resume Template

Get Started Contributing to Open Source Projects | CodeTriage -> 𝐂𝐨𝐝𝐞 𝐓𝐫𝐢𝐚𝐠𝐞: opensource issues

First Timers Only - Get involved in Open Source and commit code to your first project! -> 𝐅𝐨𝐫 𝐅𝐢𝐫𝐬𝐭 𝐓𝐢𝐦𝐞𝐫𝐬: open source issues for first timers

#100Devs - leonnoel.com -> 𝟏𝟎𝟎𝐃𝐞𝐯𝐬: Fullstack bootcamp\

I found this on Linkedin somewhere and wanted to share :)

[llewelynpritch]

Anti-racism and being an ally to Indigenous Peoples https://youtu.be/RpfWuhU6feI https://lnkd.in/ememKHbC  https://lnkd.in/ekBVQPeH  XR HUMANITY’S EMERGENCY SERVICES SOCIAL, CLIMATE JUSTICE LOCAL, STOP THE ROT - FREE RESOURCES UPDATED 30 June 2023

https://lnkd.in/eKDneFBN  https://lnkd.in/eTKsnhzP A human-centric, holistic, rights-based, advocating regenerative culture educational framework for justice, about the root causes of our cost-of-living-climate-crisis on planet earth. #AI #OpenSource GPT Chat Llewelyn Pritchard MA 28 June 2023 

[medewerkers]

StreamBuilder: ons opensource framework dat je dashboard mogelijk maakt.

We kunnen vol trots aankondigen dat ons eigen framework dat je dashboard op Tumblr mogelijk maakt, sinds 6 juli opensource is. We noemen dit framework StreamBuilder en we gebruiken het al jaren.

Eerst de basics. Wat betekent 'opensource'? Opensource is een model voor decentrale softwareontwikkeling die de samenwerking stimuleert. In begrijpelijke taal is het beschikbaar stellen van de broncode van softwareprogramma's zodat gebruikers of andere ontwikkelaars hem kunnen gebruiken of aanpassen. Wat is Streambuilder? Nou, elke keer dat je je feed Volgend of Voor Jou bezoekt, of een zoekopdracht invoert, een blogbericht of lijst met getagde posts bekijkt of zelfs als je naar de blogaanbevelingen kijkt, gebruik je dit framework. Als je de code zelf wilt bekijken, kijk dan hier op GitHub!

StreamBuilder doet een hoop. De primaire architectuur is gericht op contentstromen ('streams'): berichten van een blog, een lijst van blogs die je volgt, berichten met specifieke tags, of berichten aangaande een zoekopdracht. Dit zijn verschillende soorten streams die kunnen worden gecombineerd, gefilterd op basis van bepaalde criteria, gerangschikt op relevantie en kans op engagement, en meer. Op je Tumblr-dashboard zie je berichten van blogs en met tags die je volgt gecombineerd met blogaanbevelingen. Elk van deze types is een aparte stroom met een eigen logica, maar ze delen wel allemaal hetzelfde framework. We injecteren de aanbevelingen op bepaalde intervallen, filteren berichten op basis van je blokkeringslijst en rangschikken berichten op relevantie als je "Het beste eerst" hebt ingeschakeld. Dit zijn voorbeelden van de functionaliteit die StreamBuilder ons biedt. Wat zit er in de doos?

De volledige codebibliotheek voor het framework dat we gebruiken om zo goed als elke contentfeed op het platform weer te geven.

Een YAML-syntax voor het opstellen van contentstromen en het filteren, injecteren en rangschikken ervan.

Abstracties voor het programmatisch opstellen, filteren, rangschikken, injecteren en debuggen van stromen.

Abstracties voor stromen samen op te stellen, bijvoorbeeld in carroussels, voor stromen-in-stromen.

Een abstractie voor paginering op basis van de cursorpositie voor complexe stroomsjablonen.

Unittests voor de openbare interface voor de bibliotheek en het grootste deel van de onderliggende code.

Wat we nog in petto hebben

Documentatie. We moeten nog veel van onze eigen interne tools migreren!

Meer voorbeelden van stroomsjablonen en voorbeeldimplementaties voor verschillende veel voorkomende stromen.

Als je vragen hebt, kun je de code zelf bekijken en daar een ticket indienen.

[ty-bayonet-betteridge]

"anything other than google chrome" is accurate but keep in mind that most browsers are google chrome and lying about it. 99% of browsers on the modern market are built on the Chromium framework which is just Chrome but open-source (still maintained by Google.) this includes Brave and OperaGX and all those other trendy browsers you see advertised these days. fight against Googles monopolizing by switching to Firefox SPECIFICALLY, its opensource and run by a nonprofit that respects your data privacy and as others have said can import your settings from whatever previous browser in literally seconds.

Reddit • YouTube

[opensourceais]

Unpacking the power of Aurora’s AI Explainability Module a core component of the G.O.D. (Generalized Omni-dimensional Development) Framework. It doesn’t just interpret black box models it illuminates them.

Gain real-time debugging, uncover hidden biases, and ensure full auditability across your AI pipelines. Whether you're building for compliance, trust, or clarity, this module puts transparency at the core of your system.

Welcome to explainable AI not just as a feature, but as a foundation.

https://t.co/VVT4i3hEvP #AI #ExplainableAI #EthicalAI #AIDevelopment #TechForGood #AuroraAI #TransparencyInAI

— AuroraAI (@OpenSourceAl) May 13, 2025

[hawkstack]

OpenShift vs Kubernetes: What's the Difference and Which One Should You Choose?

In the world of modern application development, containers have become the go-to method for deploying and managing software. At the heart of this revolution are Kubernetes and OpenShift—two of the most popular container orchestration solutions available today. But what sets them apart, and which one is the right fit for your organization?

Let’s break it down. 👇

1. Platform vs Orchestration

OpenShift is a container platform, built around Kubernetes but enhanced with developer and operational tools to streamline deployment, scaling, and management of containerized applications.

Kubernetes is a container orchestration engine, offering the core functionality to manage containerized workloads and services.

While Kubernetes is the foundation, OpenShift is the fortified house built upon it—with tools, policies, and automation to ease the operational burden.

2. Installation

OpenShift offers an automated installation process with its own installer, making cluster setup much simpler for enterprise environments.

Kubernetes often requires a manual setup or reliance on third-party tools, which can introduce complexity—especially for large-scale deployments.

3. Networking

OpenShift comes bundled with networking components like Open vSwitch and uses Operators for streamlined configuration.

Kubernetes needs you to configure networking manually with CNI plugins, which adds to the learning curve and operational overhead.

4. Updates & Lifecycle Management

OpenShift handles updates and patching through a centralized Operator framework, reducing risks and downtime.

Kubernetes updates are manual and fragmented, often requiring significant planning and operational involvement.

So, Which One Should You Use?

Choose Kubernetes if you’re looking for a flexible, open-source base to build and customize your own platform—and you have the engineering muscle to support it.

Choose OpenShift if you want an enterprise-ready, secure, and fully-integrated platform with automation, compliance, and scalability baked in.

For enterprises seeking speed, security, and support, OpenShift is often the smarter choice. At HawkStack Technologies, we specialize in helping businesses adopt and scale OpenShift with real-world training, architecture design, and implementation support.

🔗 Looking to upskill your team in Kubernetes or OpenShift? Connect with us at HawkStack Technologies for hands-on, expert-led training programs.

🔖 Tags:

#OpenShift #Kubernetes #ContainerPlatform #DevOps #CloudNative #RedHat #Containers #Microservices #EnterpriseIT #PlatformEngineering #Automation #HybridCloud #InfrastructureAsCode #CI_CD #SRE #CloudComputing #K8s #OpenSource #HawkStackTechnologies #TechBlog

[buzzleaktv]

Llama-3 405B Coming Next Week

Today’s top AI Highlights: Train AI models globally using peer-to-peer network with this opensource framework Build RAG apps that can process 10 Million words Meta is releasing Llama-3 405B on July 23 OpenAI is reportedly working on an AI project codenamed Strawberry & so much more! Read time: 3 mins Training LLMs is a resource-intensive process, often requiring access to massive,…

[itlabour]

How Mantine UI Can Help You Build Apps 5X Faster | 2025

Looking for the fastest way to build stunning web apps? Mantine UI can help you build apps 5X faster with its powerful, customizable, and developer-friendly components. In this video, we explore why Mantine UI is gaining massive popularity among React developers and how you can use it to speed up your projects.

From ready-to-use components to advanced theming options, Mantine UI is designed for both beginners and pros. Whether you’re creating dashboards, landing pages, or full-scale applications, Mantine UI gives you the flexibility and performance you need.

🔥 Key Highlights: ✔️ What makes Mantine UI unique? ✔️ Hands-on demo of Mantine components. ✔️ How Mantine UI compares to other UI libraries. ✔️ Best practices for seamless UI design.

Don’t miss out—watch now and start building faster with Mantine UI! 🚀

🔔 Subscribe for more web development tips & tricks!

🔥 Hashtags

#MantineUI #ReactJS #WebDevelopment #UIDesign #Frontend #ReactComponents #OpenSource #JavaScript #NextJS #TechTrends

🔑 SEO Tags

Mantine UI, Mantine UI tutorial, Mantine UI React, best React UI library, React UI components, how to use Mantine UI, Mantine UI vs Material UI, Mantine UI vs Chakra UI, best UI library for React, React component library, React UI framework, UI design in React, front-end development, build React apps faster, React UI templates, React theming, responsive UI with Mantine, web development 2025, modern UI frameworks, free React UI components, open-source UI library, Mantine UI review, best UI kit for React, Mantine UI examples, Mantine UI customization, UI/UX with Mantine, front-end tools for developers, how to style React apps, developer productivity tools, speed up UI development, React UI best practices, Mantine UI pros and cons