CodeBehind Framework
Ruby on Rails
CodeBehind Framework | Ruby on Rails | |
---|---|---|
39 | 471 | |
32 | 54,953 | |
- | 0.3% | |
9.7 | 10.0 | |
about 1 month ago | 3 days ago | |
C# | Ruby | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CodeBehind Framework
-
Elanat CMS 2.2 Gives New Meaning to Modularity.
Elanat CMS is a large and powerful content management system based on ASP.NET Core. Elanat CMS is a CMS-Framework that does not use any of the default ASP.NET Core frameworks (Razor Pages, MVC, Blazor). Elanat CMS is built under CodeBehind Framework. Elanat CMS and CodeBehind Framework both belong to Elanat team.
-
How to Load Controller Class From Another DLL?
When the modular name comes in ASP.NET Core, we have to use the CodeBehind framework. If you think the default MVC in ASP.NET Core has this modular feature, please leave a comment in the comments section.
-
Elanat Competes with Microsoft; CodeBehind 2.4 Released
About 8 months have passed since the birth of the CodeBehind framework. In these 8 months, we have released 29 new versions with revolutionary innovations, performance improvements and new features; we have now released version 2.4; CodeBehind framework version 2.4 is the 30th version of this framework.
-
How to Send Data to the Server
In this article, we want to teach you how to submit form data in the CodeBehind framework. To keep it simple, we just added a View page with a Controller class and didn't use a Model.
-
ASP.NET Core MVC vs Razor Pages, Which is Faster? CodeBehind!
CodeBehind Website
-
Disadvantages of MVC Architecture in ASP.NET Core
In this article, we discuss the disadvantages of MVC architecture in ASP.NET Core; at the same time, we compare the wonderful architecture of the CodeBehind framework with ASP.NET Core. For each disadvantage of MVC in ASP.NET Core, we will give an example and we will also add the corresponding example with the CodeBehind framework.
-
CodeBehind 2.1; aspx Back to ASP.NET Core
By studying the CodeBehind framework GitHub repository, you can get enough information about the structure of this framework and compare it with ASP.NET Core.
-
How to Use a Ready-Made Website in Back-End Framework
In this article, we want to teach you how to put these static templates into the powerful CodeBehind framework and make them dynamic.
- New Csharp Back-End Framework – Alternative to Asp.net Core
-
How to Build a Modular System Using ASP.NET Core?
We first explain the concept of a module, then teach how to create a module in a project built using the CodeBehind framework.
Ruby on Rails
-
Should You Use Ruby on Rails or Hanami?
Industry adoption - Without including the adoption of other popular and more established frameworks like Python, React, C#, and others, if we consider the adoption of Ruby frameworks, Rails easily eclipses Hanami. The Rails homepage lists some big-name organizations using the framework. On the other hand, as the new kid on the block, Hanami is not so widely adopted. We'll have to wait and see whether that will change in the future.
-
Rails Core Classes Method Lookup Changes: A Deep Dive into Include vs Prepend
on April 23, 2024, a PR #51640 was merged into main branch of Ruby On Rails. This PR title is Use Module#include rather than prepend for faster method lookup.
-
GitHub Incident with Issues, API Requests and Pull Requests
[0] is a my favorite demonstration of it.
[0]: https://github.com/rails/rails/commit/b83965785db1eec019edf1...
-
Client side Git hooks 101
Here's a real life example: Imagine a Ruby on Rails app on which a team of developers are working. The code is hosted on GitLab and all the work is coordinated using GitLab issues. In other words: For every commit, there's an associated issue and the issue number acts as a sort of primary key for documentation, time reporting and so forth. This convention has a few advantages, most notably the ability to easily learn more about how, when and by whom features were implemented as well as how this implementation came to be.
-
16 Best Ruby Frameworks For Web Development [2024]
Ruby on Rails is regarded as one of the best ruby frameworks. It was the primary language in developing big projects such as Twitter and helped the language boost the community. Often referred to as “Rails,” Ruby on Rails is a web development framework with an MVC control structure and currently running its 6.1 version. The 16-year-old language has dramatically influenced the web development structures and managing databases, web pages, and other components on a web application.
-
More control over enum in Rails 7.1
In Rails 7.1, a new option _instance_methods is introduced, allowing developers to opt-out of the automatic generation of instance methods for enums. When enum is defined with _instance_methods: false, Rails will no longer generate methods like pending?, processed?, etc.
-
Ruby on Rails load testing habits
Rails isn't super opinionated about database writes, its mostly left up to developers to discover that for relational DBs you do not want to be doing a bunch of small writes all at once.
That said it specifically has tools to address this that started appearing a few years ago https://github.com/rails/rails/pull/35077
The way my team handles it is to stick Kafka in between whats generating the records (for us, a bunch of web scraping workers) and and a consumer that pulls off the Kafka queue and runs an insert when its internal buffer reaches around 50k rows.
Rails is also looking to add some more direct background type work with https://github.com/basecamp/solid_queue but this is still very new - most larger Rails shops are going to be running a second system and a gem called Sidekiq that pulls jobs out of Redis.
-
DHH installing Campfire (37s ONCE #1) [video]
I'm looking forward to see what extractions from this will land on rails. For example: https://github.com/rails/rails/issues/50454
-
First commits in a Ruby on Rails app
Here is what strict_loading does (source):
-
Continuous Deployment with GitHub Actions and Kamal
Kamal is a wonderfully simple way to deploy your applications anywhere. It will also be included by default in Rails 8. Kamal is trivial, but I don’t recommend using it on your development machine.
What are some alternatives?
Elanat - Elanat is ASP.NET Core CMS. Elanat is add-on oriented framework. The Elanat kernel is designed to create an add-on for it as easily as possible; the Elanat kernel contains a variety of add-ons; the structure of Elanat allows the programmer to create a new web system containing different types of add-ons.
Roda - Routing Tree Web Toolkit
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
Hanami - The web, with simplicity.
SailsJS - Realtime MVC Framework for Node.js
Sinatra - Classy web-development dressed in a DSL (official / canonical repo)
Spring Boot - Spring Boot
Cuba - Rum based microframework for web development.
CakePHP - CakePHP: The Rapid Development Framework for PHP - Official Repository
Padrino - Padrino is a full-stack ruby framework built upon Sinatra.
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
yjit - Optimizing JIT compiler built inside CRuby