JavaScript is at the forefront of our entire development approach. Not only do we use different JavaScript frameworks and management tools, but we also use pure vanilla JavaScript to solve simple problems throughout all of our client's builds. JavaScript is a general purpose programming language that can be blazing fast and fun to work with. There's not one project we are working on that doesn't involve it.

Telegram Messenger has frameworks for most known languages, which makes easier for anyone to integrate with them. I started with Golang and soon found that those frameworks are not up to date, not to mention my experience testing on Golang is also mixed due to how their testing tool works. The natural runner-up was JS, which I'm ditching in favor of TS to make a strongly typed code, proper tests and documentation for broader usage. TypeScript allows fast prototyping and can prevent problems during code phase, given that your IDE of choice has support for a language server, and build phase. Pairing it with lint tools also allows honing code before it even hits the repositories.

In 2015 as Xelex Digital was paving a new technology path, moving from ASP.NET web services and web applications, we knew that we wanted to move to a more modular decoupled base of applications centered around REST APIs.

To that end we spent several months studying API design patterns and decided to use our own adaptation of CRUD, specifically a SCRUD pattern that elevates query params to a more central role via the Search action.

Once we nailed down the API design pattern it was time to decide what language(s) our new APIs would be built upon. Our team has always been driven by the right tool for the job rather than what we know best. That said, in balancing practicality we chose to focus on 3 options that our team had deep experience with and knew the pros and cons of.

For us it came down to C#, JavaScript, and Ruby. At the time we owned our infrastructure, racks in cages, that were all loaded with Windows. We were also at a point that we were using that infrastructure to it's fullest and could not afford additional servers running Linux. That's a long way of saying we decided against Ruby as it doesn't play nice on Windows.

That left us with two options. We went a very unconventional route for deciding between the two. We built MVP APIs on both. The interfaces were identical and interchangeable. What we found was easily quantifiable differences.

We were able to iterate on our Node based APIs much more rapidly than we were our C# APIs. For us this was owed to the community coupled with the extremely dynamic nature of JS. There were tradeoffs we considered, latency was (acceptably) higher on requests to our Node APIs. No strong types to protect us from ourselves, but we've rarely found that to be an issue.

As such we decided to commit resources to our Node APIs and push it out as the core brain of our new system. We haven't looked back since. It has consistently met our needs, scaling with us, getting better with time as continually pour into and expand our capabilities.

When I started on this project as the sole developer, I was new to web development and I was looking at all of the web frameworks available for the job. I had some experience with Ruby on Rails and I had looked into .net for a bit, but when I found Laravel, it felt like the best framework for me to get the product to market. What made me choose Laravel was the easy to read documentation and active community. Rails had great documentation, but lacked some features built in that I wanted out of the box, while .net had a ton of video documentation tutorials, but nothing as straightforward as Laravels. So far, I am happy with the decision I made, and looking forward to the website release!

Comparing to ASP.NET Core MVC or ASP.NET Core Web API Simplify.Web allows you to easily build your web-site or REST API without any additional/complicated setup, covering cases like localization by default. It's projects structure very lightweight, just a minimum amount of what you need to setup ASP.NET Core request pipeline.

It is build on top of Simplify.DI IOC container abstraction, no dependency on Microsoft.Extensions.DependencyInjection and it's syntax. You can easily switch between DryIoc, SimpleInjector, CastleWindsor etc.

Any internal module of Simplify.Web can be easily replaced on extended by your custom module, covering your custom cases.

For HTML pages generation Simplify.Templates can be used allowing you to use just regular plain HTML without additional setup.

Can be easily integrated with Simplify.WindowsServices converting your web application not just to web-application, but a standalone windows service which can also do some background jobs via Simplify.WindowsServices.

And it is open source, of course :)

Optimize-js I will not describe this tool a lot here, because it's already good done by author on github

I just want to mention that this tool wrap up all immediately-invoked functions or likely-to-be-invoked functions in parentheses what is do a great optimization a JavaScript file for faster initial execution and parsing (based on my experience).

The performance of application where I've introduced optimize-js improved on 20% in a common (tested in Chrome and IE11).

• Clarification on Readme to the optimize-js
• Some of Nolan thoughts on the virtues of compile-time optimizations can be found in "Parens and Performance" – counterpost

Is it maintaining now? - Unfortunately, no (but feel free to send PR)

When I was evaluating languages to write this app in, I considered either Python or JavaScript at the time. I find Ruby very pleasant to read and write, and the Ruby community has built out a wide variety of test tools and approaches, helping e deliver better software faster. Along with Rails, and the Ruby-first Heroku support, this was an easy decision.

Here are all tools and skills you need to have for being among to world's top Full Stack Developers Reviews, critics and suggestions are most welcomed!

1. HTML and CSS
   • Semantic HTML5 elements
   • Basic CSS (Positioning, Box Models etc)
   • Flexbox & CSS Grid
   • CSS Variables (Custom Properties)
   • Browser Dev Tools
   • Responsive Layout • Set Viewpoint • Fluid Widths • Media Queries • rem over px • Mobile first, stacked columns
   • Saas
2. Deployment • Namecheap, google domains • FTP, secure FTP • Inmotion, netlify, github
3. Vanilla JavaScript
   • Basics
   • DOM manipulations and events
   • JSON
   • APIs
   • ES6+

1. Build Basic Sites
2. Build UI Layouts
3. Add dynamic functionality

4. Deploy and maintain websites

5. HTML and CSS frameworks - Bootstrap / Materialize / Bulma

6. Frontend JavaScript Frameworks - React, Vue and Angular

7. Basic Command Line

   • Git
   • NPM
   • Parcel
   • Gulp

8. State Management

   • Topics : Immutable State, Store, Reducers, Mutation, Getters, Actions, Observables
   • Tools : Redux, Apollo, VueX, NgRx

1. Build incredible front-end applications
2. Smooth and steady front-end workflow
3. Work well with team and fluent with git

4. Connect with background API and work with data

5. Server Side Language

   • Language :
     • Nodejs - Express, Koa
     • PHP - Laravel
     • C# - ASP.NET
     • Python - Django, Flask
     • Go
   • Topics : Basic syntax, structure and workflow, package management, HTTP and Routing

6. DataBase

   • Relational Database : MySQL, PostGreSQL
   • MongoDB
   • Cloud : Firebase, AWS, Azure
   • Lightweight - SQLite

7. Server Rendered Pages :

   • Next.js
   • Nuxt.js
   • Angular Universal

8. Content Management System

   • PHP : WordPress
   • JS : Ghost
   • Python : Mezzazine
   • .NET : Piranha

9. Misc.

   • Linux
   • Ngnix
   • Digital Ocean
   • Heroku
   • Docker

1. Setup Full Stack dev environments and workflows
2. Build back-end APIs & micro services
3. Work with databases
4. Construct full stack apps
5. Deploy to the cloud

Switching to Mobile Development : 1. React Native 2. NativeScript 3. Ionic 4. Flutter 5. Xamarin

Desktop Apps : 1. Electron 2. GraphQL 3. Apollo 4. TypeScript

Lastly, Serverless Architecture

Websocket is trending this year, but there is another technology similar with Websocket (WS) is Server Sent Event (SSE). Those method have used similar Content-type, SSE is used to text/event-stream and WS is used to binary or text/octet-stream.

The different both of those method is sent. WS is an undirectional sending data both of client and server and SSE is whatever data on server will be push to client.