Font-Awesome VS Ruby on Rails

Website: https://fontawesome.com

the i element is the icon of the button, I'm using fontawesome.com for the icon, the class fa-apple retrives Apple icon for us.

Icons: Fontawesome Development: HTML, SCSS, JavaScript Deployment: Github + Netlify

1. Font Awesome

For generic icons (i.e. you just need a d6 and not a system-specific d6 option), Foundry has Font Awesome which are easy to search, then copy and insert, and always look good inline.

The following is an example of defining Font Awesome:

Of course, we have many different ways of solving this problem. Some of the most common include pre-existing third-party icon libraries (such as Font Awesome), icons bundled into a third-party component library (like the Kendo UI Icons), or a completely custom set of icons designed and maintained by your design team. Obviously, going 100% custom will require more work (on both the design and dev side), but might be worth it to achieve a truly unique look – or if the UI will require icons for uncommon symbols or concepts.

The featured GitHub projects are dynamically retrieved through the power of the GitHub GraphQL API. The blog posts are seamlessly pulled in using the Dev.to API. Additionally, Redis is used to cache the GitHub and Dev.to API responses for 1 hour to reduce the number of API calls. Icons are provided by Font Awesome through their kit from the CDN. I've also implemented the new View Transition API feature to enhance the user experience.

For those who are unfamiliar with Laravel, it is a very popular monolithic PHP web framework similar to others like Ruby on Rails. It is known for its ease of use, rapid development and making PHP development far more enjoyable haha!

🛤️ Ruby on Rails:rubyonrails.org

On the back end, we worked to migrate data from Spark (a data processing engine) to a custom, in-house RETS (real estate transaction standard) aggregator, which helped dramatically grow the customer base. We also moved Agent Inbox to a hybrid solution using React.js and Ruby on Rails, replacing their single-page-application solution with server-side rendering to improve project stability and speed. (This move came from our experience knowing that small teams working on various platforms simultaneously often end up inadvertently wasting time and money.)

How to start using React components written in TypeScript using Ruby on Rails as a server with only built-in Rails features? There are a couple of ways we can achieve it with.

We rewrote and redesigned the entire user interface, contending with a very tight timeline, and we upgraded the existing code within Ruby on Rails, including all dependencies that were previously unsupported and thus creating security risks for the product.

And if you’re not familiar with tools like Laravel and Ruby-on-Rails, they are opinionated full-stack frameworks (for PHP and Ruby) with lots of built-in features that follow established conventions so that developers can write less boilerplate and more business logic, while getting the industry best practices baked into their app.

I don't think it is superfluous to clarify to folks who might not be familiar with Rails how migrations work. In Rails, we create classes for migrations in the db/migrate folder that inherit from ActiveRecord::Migration[:rails_version]. This is a good example of metaprogramming in Ruby. Instead of directly inheriting from the ActiveRecord::Migration class, ActiveRecord::Migration has redefined the [] (square brackets) method to dynamically create a class with features available for the specified Rails version and return it, so we can inherit from it. This allows us to use migrations created in previous versions of Rails even after updating Rails. The newly created class typically has two methods, up and down, which apply and revert the changes to the database, respectively. Alternatively, it might have a single change method if the changes can be automatically reversed by Rails. The name of the file containing the class starts with a 14-digit timestamp, and Rails maintains a table with one column containing these timestamps for executed migrations. This ensures that migrations are run only once and in the order they were created when you type rails db:migrate. This system ensures smooth database schema changes and consistency across different environments. It's important to mention that the SQL code we will write in the next section will be compiled and executed by the database engine, so if we need to make changes, we need to revert the migration, change the code, and execute it again. You can read more about migrations here: Rails Migrations Guide.

Ruby on Rails, in my opinion, is the most productive full-stack web framework to-date.

The Rails core team wanted to make it easy for today's and future Rails developers by providing a simple API for model attributes. All developers need to do is pass the attribute's name. Here is how they demonstrated their solution. Pow 💥

You may notice in the new_framework_defaults_7_0.rb file mentioning the impact of this change, which is cache invalidation. In order to gather some more information I looked at the ActiveSupport::Digest which basically has just 3 class methods, a setter & getter for hash_digest_class and the hexdigest method. Furthermore, I searched across the rails/rails repo to find the usage of ActiveSupport#hex_digest_class (if interested this link leads to the search results) to find most of its usage only around code that deals with caching. This included caching of views, active_record queries, http ETAGs and also cache keys for the cache store you have set e.g. redis, filestore etc.