Ahmet Dadak Repository Research

Next.js

In React projects, there are a couple of problems related to rendering all the content on the client-side. First, the page takes longer to become visible to the user, because before the content loads. Second, if you are building a publicly available website, you have a content SEO issue. The solution to both of those problems is server rendering, also called static pre-rendering.

Next.js is a React framework that makes server rendering React applications easier. It provides a common structure that allows you to easily build a frontend React application, and transparently handles server-side rendering for you.

The thing I like most with Next.js is that under the pages folder in the root directory of the project, the files can be reached by the filenames with not considering the route issue. In other words, Next.js serves each file in /pages under a pathname matching the filename. For example, /pages/about.js is served at site.com/about.

Here you can find details about Next.js

Flask

Since I use python for my ML projects and I try to concretize the ML projects as tiny applications, I discovered flask to make python web applications.

Flask is a micro web framework written in Python. It is regarded as micro-framework because a micro-framework is normally a framework with little to no dependencies on external libraries. In the case of Flask, its dependencies are:

• Werkzeug a WSGI utility library
• Jinja which is its template engine

I really liked Flask because it allowed me to make a simple application in a few days. I used the first-time flask framework while I was implementing a digit recognizer web application. Since I created my model on python, I was able to use that model on a python running application. It allowed me to make a web application and I was be able to use that model in my application.

Here you can find details about Flask