Perfect-Stack

The Perfect Tech-guide & Awesome-list đź› i

A developer’s info-guide on: tech - tools - Libs - Frameworks


Decisions: have long-term impact. Dev-stack/toolchain + working method/strategy impacts your progress.
Making right choices: early on, increase success and progress chances, self-respecting your skills.
Nothing’s perfect, yet… better options/methods improves DX, workflow, structure, progress, efficiency.

To Contribute » add links to items, reason/prove an obvious better option, improve doc.

* target users - keywords: developers, designers, researchers, students, startups, decision makers

Shortcuts

### Starter intro
### Awesome list
### Programming Languages
### Frameworks - more info/details
### Extra information and discussion


Starter intro

To beginners and startups

Don’t make technical decisions just based on what others do, market hype, popular trends…
…instead, decide based on multiple factors, such as:

Pros/Cons - Review Comparison - Requirements- Best fit / Integration,
Problem solves - Feasable / Accessible - High Rated - Popularity,
Focus / Goals - Priority / Importance - Stable Eco-system
and finalize your decision considering:

...Why? >> press to expand this topic ↴ Majority of developers adopted older popular tech/methods by the circumstances in past, by workplace/education requirements job offers, senior advice, or the 1st option encountered, or just due to common hype, in the past, but not the best choice now. This cycle repeats and non optimal tech get stuck in social, market, and job/edu systems, then if you adopt it, by the time you build your work on it, the tech might be near end of life, or bad/slow pace, as it holds to legacy patterns, and compatibility patches to make it work with ongoing needs of the users. Therefore instead of market hype, make decisions based on facts, use whatever is best for the job, mostly if you're doing your own business or planning a `startup`, deciding better tech/methods, results in productivity, efficiency and saves time/cost. Therefore If you're not forced or bound by a legacy eco-system or specific rules/conditions, do your research, compare options, and make decisions you benefit. [*...extra pointers on this topic...>>*](#new-developer-or-decision-maker)

` Wish you good luck! `
***

Target Platforms

Native SDK Android, iOS, embeded runtimes... if targeting specific device abilities or inclusive native functions of an embeded device, phones or a VR headset.

Web if the development target is general, multi-platform, web/communication based, and not limited by vendor lock-in, then use the web platform, which has most use cases, most open and is cross-platform. It covers all platforms client, server, browser, mobile devices, cloud and desktop.

System in case lower level control/privacy/system access is required, or direct Hardware/OS access and high performance at scale, then a server/workstation system/s plus a custom software stack (low/mid level programming languages, SDK, runtimes...) is more suitable.

Cloud A complete or custom system solution on web/network. You subscribe to a managed virtual system, in different levels from VPS, API, Host... much features, managed/maintained. All pros, only cons: no physical control/access/privacy(unless self hosted)

Learning tips

` Go to beginner guideline details `-> Web-Dev guideline
***

Awesome list


AI

General

AGI - LLM models

* AGI(Artificial General Intelligence) …. MoE(Mixture of Experts)

Tools, Audio, Video…

Best youtube AI Channels: bycloud - Ai Jason - Matthew Berman

InkedAI-Srvc11

About Different AI generations »
Check AI Awesome list for more AI info/tools/applications, more details. » (…needs update)

^


Frameworks  »

^

UI »

Standard CSS:

UI Lib / Kit - main advantages »

UI categories

### UI Recommendations + reason:

^

Cloud platforms:

^

Database:

^

API / Communication patterns:

Programming Languages:

Low level

High level

(Type Safety / Typescript):

</details>

^

Other stuff

^
***

Frameworks information


Frameworks Architecture

Frontend:

Backend:

JavaScript Runtimes:

Python eco-system: jobs, popularity, AI libs/community, resources, ease of usage, +beginners.

^

Fullstack:

Sveltekit: complete yet custom scalable solution, flexible use of frontend + backend.

Best web/app framework + DX, combined best practices and innovations in web ecosystem.
Phoenix: Live view generative FE + Elixir BE. Best for server oriented web development.
Astro: your frontend of choice + a unified good set of predefined patterns, tools, DB!
Custom Build: Vite(bundler/dev-server) + Nitro(Server) + Vinxi(Router) + FE UI/interface

Node.js cloudish frameworks: Next(Vercel/React), Nuxt(VUE), Astro(multi platform).

Svelte framework pros:

Developer Experience: write less code, concentrate on your ideas, not development complexity.
Standard: the code is compiled to standard JS. Fast/optimized, can be used anywhere, reusable.
Less complexity: easier to read code, compiled, no v-dom overhead, no framework caused issues at runtime.

less Testing/Dependency issues: unexpected reactions, conflicts, misunderstanding source of issues.
less Errors: due to not having runtime dependencies, or external factors except your own code.

Less Cost: easier to read code of other devs => continue their work + less bugs + less testing + faster development.
Smaller bundle size (Compiled), without virtual-dom and framework overhead…

^
***

Extra Information


Web Development - about definitions

^
***

Web development guideline:

1. Learn the base web standards -> (HTML, CSS, Javascript) follow/practice tutorials. Make few apps.(ex: Todo)
2. New web standards -> ES6/next, new HTML, new CSS (grid,…) practice/try what you learn.
3. Update the previous apps you made, using new things you learned. make a game and a blog site.
4. Deploy: learn how to host/deploy your site. Host on cloudflare pages, deno deploy, begin, netlify, github pages,…
5. Learning decision: learn extra stuff once is required(predict it). (Ex: DB, AI, specific tools/libs…)
6. Learn a Framework: better Dev-eXp & scoping. composable, reusable components, structure and configuration.
7. Learn Design: Patterns, tools, UI/UX(user interface/experience). Concepts: visual clarity, visual effects, utility 1st.
8. Responsive design: native looks, any device, clear focus, usability/accessibility. CSS flex, grid…
9. Backend: 1. Sveltekit(if using svelte) ___ 2. Deno: new js-runtime replacement for Node.js by its creator.
10.Personal various experiences, use GIT, github, Make a portfolio site (show case). a social profile: Linkedin + twitter.
11.Testing/Typing: only if neccessary and: in large teams on complex projects with security risk or much new/junior/outsourced devs.
12.Summary: Be an expert in one field, pro on few more, know about the rest. Fullstack: Frontend + Backend + Eco-system + Experience.

^

About AI - Generations

Past AI: Machine Learning + Data/algorithms.
Output results such as detection/decision/states… are made from a defined input processed by Machine Learning + Data science tools/patterns to extract meaningful data/states, using specific algorithms and models.

Pre/Current: Generative AI, builds result from input data.

Present: Generative AGI. Is the same as above, but more accurate, matured and efficient.

Future Ai: is a systemic AGI. It creates custom composed advanced solutions, adding real-time autonomuos abilities.
The past generation recognise, detect, compose a result, This new generation understands (input + general concept + you).

^

### Work Tips:


The Web - status summary

The web was originally made to communicate with text and data, it later evolved to present simple graphics and images.

...press to expand. Hardware advancements in performance and capacity, plus emerging smartphones and social networks caused web based online services go mainstream in network communications, it progressed fast and competes with native platforms. The sudden progress pace in contrast with the concept of keeping it backward compatible with legacy standards, caused some complexity and confusion in the last decade due to workarounds to support new features by vendor prefixes, various 3rd party libs, tools and frameworks to achieve demands of dev/user/market. The slow adoption of new trends was caused by issues with backward compatibility of existing sites and old systems while native mobile and desktop platforms had all breaking changes at once to support new hardware. By then 3rd party libs, prefixes and frameworks... were made to solve/patch the issue and provide features that didn't exist in web standards yet. Good news, the new web standards and innovations, improved the situation, furthermore Frameworks evolved and matured including new Web APIs to provide functionality and access to new technologies. Therefore with much flexibility, compatibility and openness, Web eco-system can now compete with native desktop and mobile platforms. Whenever learning something, learn latest stable standards and best practices, some of the old prefixes, 3rd party libs,... are not required anymore...(as explained above) unless is justified, mandatory or no alternatives. The recommended trends mentioned here were handpicked by checking reviews comparison, personal experiments, and by looking into new trends top professionals adopt.

^
***

New developer or decision maker?

...Details - Reasons and Pointers on choosing tech stack/methods... (press to expand) - Avoid learning 6 ~ 10+ years old stuff if a better alternative is available. old tech was made for past era ecosystem, development model and HW/SW/issues. - Is still popular due to seniors who learned it in past when it was a valid option and using it at work for years, later new developers are forced to follow them. This process might repeat multiple times... - The old popular tech nature: ___ it works, is popular and has big community and resources, yet in time it becomes more complex, due to extensions, compatibility patches and conflict solving layers to make both the original and new syntax/tools/requirements work together... Aside of that each time a new feature is added, this process might repeat, and the platform gets large, complex, multiple different revisions.(Ex: MS SDKs, .net framework,...) - Breaking changes and migration: ___ when a new feature that contradicts something in the system which can't be solved, the devs will decide to either give up on the feature, add extra flags/configs or make a breaking change, thus you must stay on old branch or learn + update your previous codes or totally migrate if is hopeless. - Each time a breaking change shows up, you might need to repeat this process. this makes multiple dev branches in a company if the team can't / won't follow. - Prevent Issues: an old legacy target which depends on layers of other legacy tech, will encounter conflicts, compatibility, deprecated dependencies, which will cost time + resources + man power to solve them. - Low level coding is not affected much by the mentioned issues. they rarely change, and if so, is about new features, compatibility and stability. - Unnessecary overhead: as old devs retire, new ones might add extra layers of abstraction instead of updating the original code, these issues cause: extra complexity, overhead, extra cost in long-term, Large number/size of files, large developer teams, or slow working pace,...

^
***

This site is open source. Improve this page.