Maybe certain projects need a specialty tool in your toolbelt— but for your typical work, if you were to start a new project today, what would you reach for in order to deliver on time and on budget?
Maybe certain projects need a specialty tool in your toolbelt— but for your typical work, if you were to start a new project today, what would you reach for in order to deliver on time and on budget?
For further actions, you may consider blocking this person and/or reporting abuse
Rust + Typescript.
probably also worth mentioning, that Rust bindgen will generate ts typings so its perfect for some blazing wasm code if you so wish.
I am intrigued what you love about that combo?
At first it was because I wanted to try all the new hotness, but this is all quite old now so I guess I liked what both languages did for their respective areas. I like rusts no nonsense approach in that it's pretty hard to write bad code and it's pretty hard to write code from a beginners stand point, you really have to keep trying and failing and being repeatedly beaten over the head from the compiler until you end up with idomatic rust. On the other hand we have typescript, this is as flexible as you want, obviously I aspire to write strongly typed strict JavaScript but I tend to get a little lapse in my discipline over on this side, I get that freedom of prototyping speed that I don't in rust and I guess that's a nice pairing, now if I where a 10x I know this combination would lead to some incredibly resilient software.
That's fascinating. What do you mean by "now if I where a 10x I know this..."?
What a quote! Because it's true, I'm a lazy developer, I like my computer to help me to code at every stage. A 10x developer is a joke about the mythical inhuman skills of a developer that is superior to all other developers. I suppose I'm saying, if I weren't the human behind the machine this stack would meet the perfect criteria for excellent software, Microsoft seem to agree with me, for their software is being reengineered in rust, and the invented typescript and this new language which we don't know a lot about yet other than it's likely typescript like but will be used in the same space as rust, zig, d and other c alternatives.
I love that
Any library recommendations?
I read Actix was good, but now has maintainer problems.
It did have maintainer issues in the past, but has a new maintainer. You can also try Rocket which is about on par, but I dont know if its as fast.
Results of StackOverFlow's survey on most loved languages in 2020 might agree with you :)
9 out of 10 DEV devs might agree with me haha 😂
What's your Rust library/framework set look like?
So on the Rust side.
Actix Web although I tried Rocket which was also great, I wanted to use http2 on what is reportedly the fastest web server around. the reason being the stack I am developing is ESModule based so I am trying to move away from a bundler and get as many small requests as I can. the experience feels like 2005 but with Typescript powers, Its liberating!
For the front end, it has to be XState and lit-hml / lit-element. so enjoyable.
The intro to this project can be found here. Rust has been decided after this post was created. I am working hard on a full shop to showdev, its going really well and probably will be done next month.
🌌 A modern FE stack in a parallel universe 🦓
Adam Crockett ・ May 11 ・ 4 min read
This sounds really interesting!
This is really cool, I've been chewing at rust for web development, but I'm wondering how/where you can host a rust web server?
I'm likely to spin up a AWS lightsail or something small to install rust. I think that'll do for early days.
Lambda also has a Rust runtime.
🔬 On my list of stuff to tinker with! 🔬
I'm a big fan of what folks have dubbed the GoLD stack:
Who doesn't love a little bit of serverless :D
It almost feels like they purposely picked Lambda and DynamoDB for working with Go, just so the stack would sound that well xddd
Lol yeah
Step one is always have a kick-ass name! :D
Hahah, I'm currently working on a MERN stack, I'm thinking to switch out React to Vue just so I could be the mighty VENoM dev xddd
I don't, I guess ;) We used lambda since quite early days but in almost every case we regretted it in the end. It always turned out that Kubernetes with some application processing (eg. Sidekiq) scales better, performs better and we have better insight into what's going on if something goes wrong.
Hahah yes, definitely there are draw backs when it comes to serverless, I think it's all about the project at the end of the day.
Your final point is the most important to me, transparency is actually key for when (not if) something goes wrong :)
What's your experience with Dynamo DB? As far as I've heard it it's great for record based transactions, but tricky for aggregate analytics work. (Disclaimer: I've barely even read the docs :p)
Dynamo DB is great nowadays....a year ago was the worst thing I could have used ....I've never written so much code for such a small project (extremely high traffic) to handle just throttling strategies. Then one day we turned on "on demand" and never cared for that service ever again
I have never used it personally for analytics, but I have heard using it in tandem with Amazon Athena is great for that kind of stuff!
I like DynamoDB a lot, though I have heard it's not great if you have a data set which is growing rapidly.
I have used Athena with an S3 data store. That worked well for that particular job :)
This is my current go-to stack:
Full disclosure I'm working on an internal app for Prisma, but it's sooo nice to have VS Code write half of my code for me thanks to type-safety and intellisense. Types defined in the database schema flow all the way to React components on the frontend. 💯💯💯
Wrote an intro to this stack last week :D
Complete Introduction to Fullstack, Type-Safe GraphQL (feat. Next.js, Nexus, Prisma)
Xiaoru Li 🇨🇳🇩🇪 ・ Jun 9 ・ 13 min read
It really depends what I am doing, but for quick prototyping (which is a common thing I do):
Generally Laravel on the back end, with React on the front end.
I'd prefer to use Postgres rather than MySQL or MariaDB, but it tends not to be possible because the PHP community is very MySQL-focused. I also tend to use Redis as my cache and queue backend.
I have been really interested in getting deeper into Laravel. I heard that it meshes really well with Vue (which I already know) so it intrigued me more. I am also about to learn React. Have you tried using Laravel with both Vue and React and if so, what is your reasoning for your preference being React?
The default front-end toolset for Laravel uses Vue, so it's quicker to get working with Vue in Laravel than any other front end framework.
I have tried Vue a couple of times, and the issues I have with it are as follows:
I will concede that React is harder for front-end developers who don't necessarily know Javascript all that well to pick up, though.
Wow, awesome reply. Thank you for taking the time to respond :)
I just want to add that Laravel comes with its webpack-based build tool: laravel.com/docs/7.x/mix
The default installation is configured for Vue, but you can change it to React easily: laravel.com/docs/7.x/frontend#usin...
As it's really just webpack, you can even use Svelte with relatively simple setup. Basically you can bring any major UI/frontend stack that you are most comfortable with to use with Laravel.
Mix can also be used outside the context of Laravel. I use it on a legacy Zend 1 project I maintain where I've been using React for new front-end work.
The only thing that required more work is versioning - I had to roll my own solution for that.
Laravel and Vue are awesome, plus both come with some of the best docs around.. So it's a win-win if you need to look-up smth ;)
Very true, the Vue documentation is really thorough and I have noticed the same with my experience with Laravel so far :) Always a huge plus when getting into something new!
Google Docs, Markdown, and VSCode.
(sorry, I'm a blogger by trade 🙃)
Over engineering something isn't something to brag about, your stack is perfect for blogging.
This is my favorite response
If I were aiming to deliver a project on time, I'd choose what I know: Ruby + Rails + Postgres + Vanilla JS (I don't know much about Front-end development >.<).
If I was wanting to try something new then it would be: Elixir + Phoenix + Go + Postgres/Mongo + VueJS.
Python, FastAPI, Typescript, React, and PostgreSQL
Something like this: github.com/Buuntu/fastapi-react
thanks , I was looking to use fastapi for my new project . You assemble all what I need in one place.
I'm pretty-well bought into Kotlin at this point across the whole stack. I love using Ktor for server-side apps, I'm primarily an Android dev where Kotlin has its greatest usage right now, and the fact that I can write Kotlin instead of JS just makes me giddy. Especially using this all together with MPP, sharing data models and logic is just wonderful and such a pleasant development experience.
I'm in the midst of learning Kotlin. I introduced it at work, and it's pretty much just a way for me to get some functional programming in our Java 6 EE-targeted application.
Do you have (or know of) any open-source examples with Kotlin across the whole stack? My "learning" part is writing an application which, for now, uses Angular on the front end.
And, for data access, do you use Exposed, Hibernate/JPA, roll your own, or something else?
React for the front-end, with Typescript. I can't say I have a go to technology for the back-end. But Java Spring Boot was fun, Loopback 4 was okay. I'll probably choose a Node.js base technology for the back.
VsCode for the editor, Chrome for the browser. And these days it's mostly RATM for the music.
try Strapi (for nodejs)... I used Spring Boot for a time, but I think java is so bored. Loopback 4 have a good model also, but Strapi has a visual model editor... and, when you change some model, all rest api and graphql api are updated automatically.
true, strapi is helping a lot with front-end focused developer like me 😊 cut down development time quite significantly
For the work I'm getting paid to do, from bottom to top:
Our products are heavily regulated hardware, and supported for the foreseeable. There isn't really a "quickly knock up a prototype in docker" situation.
If I could chose, I would switch out the Microsoft stack for Django on Linux, as I find that easier to work with, but it's not too bad.
Python with django if its a large monolith app.
Go or Node for all other project and apps.
Vue on the frontend in almost all cases (unless its just static html, but even than vue can be embedded easily if something a little more exotic is required).
I make us of the entire jetbrains suite of dev tools (big fan).
We're a two person shop developing mobile products with the goal of doing big things on a small budget. Ideally we get where we're going without the need to raise capital too early.
With this in mind we choose open source, community driven tools that provide high developer leverage.
I've put the following in categories in ranked order for what's most familiar, safe, and known to me down to what I'd like to use and learn and isn't "just hype" to me.
Front-end Web:
App:
Backend Service (My current "shop" is very Java-heavy):
Event-handling:
DB:
So putting it all together, my most likely, realistic stack I'd build today would be:
As far as other tools, theres are "givens" for me: git, JetBrains IDEs, VS Code, AWS (Fargate, S3, SNS, SQS, Athena, Data Lake, etc.)
My go-to stack is to not have a go-to stack, but choose the the tools fitting the job. Of course, choices are somehow limited. Trying to write it down:
I've been super into:
Everything Azure just works perfectly, and I appreciate I get over $150.00 per month for personal projects to learn all this cool stuff 😎
Mostly PHP + Laravel
git for content, postgrest for api/db, sinuous for html/signaling/frontend, immer for immutability on frontend, goober for css primitives, esbuild for stinking fast builds, typescript to think, firebase for easy cloud stuff without think like good auth, users, and file storage.
If the application is very frontend focused with a simple backend model I would go with Serverless technologies first, as it would dramatically speed up time to market:
If I need to build something with a complex backend I would go with a Typescript Node backend and pull out other technologies like Rust or F# for things that need more perf.
Something I'm still figuring out an acronym for, but let's go with something broad: RNS (React Native Serverless). Quick, flexible, scalable, without dev team fragmenting, minimizing vendor lock-in as much as possible/convenient, and in line with my aversion to needlessly complicating things.
By React Native, I mean as a unified codebase for mobile, web, and desktop (the latter two thanks to React Native Web and the last thanks to Electron at least until there's a viable out of tree RN solution for Linux). By serverless I mean multi-cloud FaaS, DBaaS, and usually Firebase Auth.
Gridsome or Nuxt, Apollo for bigger apps with complex GQL APIs.
I usually prefer to remain Serverless with lambdas but if I'm handling a back end as well, it'll definitely be node until Deno is production ready. MySQL for my DB needs.
After a long route through C, .NET, Java, PHP and their associated back end infrastructures, I've landed in the Python world, having tried Flask and Django in recent months. Quite nice. I'll do my next personal project using Django, to bed in the knowledge. I know React best (with Typescript) and it would be my FE go-to, but I'd like to try Vue in anger.
I'm relatively framework agnostic out of necessity, I work as a consultant and the ability to learn and adapt and recognise and apply patterns is generally more useful than specifics for me.
i.e the decision has often been made for me :)
For simple JAM stack projects:
Gatsby + Netlify (hosting, identity, functions) + Airtable.
For light-weight full-stack projects:
MEAN (MongoDB + Express + Angular + Node) stack.
For more robust full-stack projects/microservices:
Angular + SpringBoot + Relational DB (MySQL / PostgreSQL) + Docker.
Right now it is pretty much a .NET Core back end with a Vue frontend.
Though I did just start a personal project that uses Node on the back end and Vue on the frontend. Mostly because I wanted to get better at Node.
I do plan on taking a look at other backend solutions soon. Just to get some more ideas, but right now I really love .NET Core.
For serverless things, websites, prototypes, web apps, time sensitive stuff:
For web apps, monoliths, things that need extensive databases and models, more security and control, or apps I won't be maintaining often:
API Only:
In general I'm most comfortable with Javascript, however the build processes and configuration issues can be a nightmare. Working with sequel based databases with Ruby is leaps and bounds ahead of Javascript so I stick to that but have moved away from rails in favor of Roda and the Sequel ORM these days.
I enjoy the security of typescript especially when working with lots of external data sources. It can make your head spin trying to remember the data structures of a headless CMS, plus a database, plus a myriad of other services so typescript helps there. However, I find that typescript / javascript apps are best if you are working on them every day. If you build something then come back a few months later you may spend the next day debugging the build (babel, webpack, typescript...), the ecosystem in JS is really what gets me down.
Recently I'm getting more into Go for back end work for first class types support and a nice simple language with amazing speed. That being said the front end tooling and templating stuff that Go offers is a little lackluster so if working on a monolith I'd say Go may not be the best pick and is more of an amazing API language.
In Android I'd go with writing the app in Kotlin, using Dagger Hilt for Dependency Injection and using Jetpack + Material Components for building the UI.
For cross-platform CLI stuff, Rust and its huge crate ecosystem is my new love.
Lately, backend has been go+fiber with mongodb or mariadb & react on the front end.
I am a lot happier with go vs node vs python.
On my list of things to tinker with are nextjs and rust on the backend.
In regards to web development, although I work with ASP.NET MVC at my daytime job, if it was a personal project or freelancing stuff, I would go with Node, MySQL, Express and EJS pages. I work quite fast with it and fits me like a glove.
Rails/Minitest/Postgres/Redis/StimulusJS/TailwindCSS/Heroku.
Sapper/Svelte for front end and "micro back end"! Otherwise it's a lot of Nuxt and Express for larger projects, since Sapper is still very much in beta still. But Sapper is SO much more productive for me than Nuxt, which is even more productive for me than React...
For CMS and/or data storage, I've either been using Airtable or Fauna for small projects
May be a little dated but still quite reliable:
Node+Express with TypeScript, process managed by PM2 in cluster mode.
PostgresSQL
VueJS for the frontend
Can always look to the future to have the node parts switched out for Deno.
Golang for APIs, utility scripts and command line tools.
Symfony for more "monolith" projects. (also Interested in Nest.js on this category).
Frontend: Vue/Nuxt/Tailwind.
Static sites / landing pages: Gridsome/Hugo.
Datasores: Postgres, FaunaDB.
Cache: Redis
CI: Github Actions / Giltab
Hosting & Infrastructure: DigitalOcean, Google Cloud Run and Netlify.
Domains / DNS: Namechep and Cloudflare.
Cloud Storage: Google cloud Storage.
Headless CMS: Strapi or Directus
I think I can build almost anything with this ;)
For small and quick setups, POCs I use
Sometimes I throw in Typescript as well when I have good planning in advance. 😅
I started it out as an one time thing, but immediately fell in love with the simplicity and elegance with which you can do things in RxJS.
Been thinking of giving RxJS a try on the backend also.
I GROK websites
GraphQL
React
Okta (ok, so I needed auth and wanted to make the acronym work)
Kotlin (with Spring)
I didn't include any databases in the acronym, as I kinda treat them like managed services now anyway.
I created a basic skeleton on github, but I actually named it "KROG" because I didn't see "GROK" at the time :P
Recently, I've found myself using a couple of Google Cloud Functions to complement the actual backend. For small and simple projects I usually stick to Node. For greater projects, however, I prefer Go.
In the frontend, I use React for web apps and Svelte or Sapper for websites.
My extremely original setup 🙄
Nostly next.js , handles both backend and frontend code.
Knex.js for Query building and postgres for DB.
That’s the base stack right now.
Once I’m done with test cases for routex, I’ll start using it for the api’s and knex and react/preact for the frontend side of things.
For econometrics, data analytics:
R with the Rstudio ide
Python with jupyterlab
For Web services:
Vscode
Nodejs / express / mongo (just baby steps)
Django ( i am not even born yet)
No frontend framework yet. 😔
Almost for any project I've been using Quasar Framework for frontend development (apps, websites, etc).
For hosting and authentication usually I'll go with Firebase.
If I need a more intense backend, I start with Mojolicious. For database, it depends on the usecase... Or PostgreSQL or SQLite.
If I need a server, usually go with a Ubuntu VPS on DigitalOcean with the latest LTS version.
Personal projects Rust/Postgres/RabbitMq
Work Lambdas in .net core, SQS and Aurora serverless
Asp.net Core with Razor pages and ms sql database. Some libraries to deal with Excel files.
Python/Flask for the backend, plain ol' HTML (with progressive enhancement only) for the frontend. Scaling horizontally like it's 1999.
dotnet core + Vue with TypeScript.
Where is the love for Angular :(
I usually use: Angular for front + Node or Go for back.
Everyone runs for the newest thing as soon as it hits the shelf.
Python Monolith (Preferred): Django + VueJS (NuxtJS)
Python Microservice: Flask / FastAPI + VueJS (NuxtJS) + Kubernetes
VScode
React
Node.js
My to-go tools:
Im really jamming this stack right now, Vue , Netlify (for serverless functions & hosting) firebase (for DB & Auth).
pun intended
Node js + Typescript + Prisma + React + GraphQL
Cannot beat Rails+React for bigger stuff. Jamstack/Gatsby for smaller stuff.
Rails + Vue
and by this i mean Rails API
MERN - because it's so easy to bootstrap 😉
Back End with nodejs + strapi + mysql
Front End with ReactJS + typescript
App with React-Native + typescript
Angular+NestJS in a monorepo orchestrated by Nx. I actually just wrote a dev-post about it 😅
Django for backend, vue for front end (gridsome or nuxt) mostly.
GRANDStack. Neo4J + React is a major wombo-combo. Personally I've been building it with Next.JS as well so it's all serverside.
I prefer .Net Core, Mssql and ef and angular but I actually started a Blazor project (serverside) not long ago and I kind of like it.
Strapi + Nuxt.js most likely, at least the it wasn't needed a too complex business logic.
Hello is fastapi production ready? I take a look and I love it.
I use Django but it miss lot of stuff like pagination.
Hasura / Serverless (AWS Lambda / Typescript) / Terraform / React / Apollo.
gitlab.com/maxcan/hasura-react-aut...
Let's prototype the way people hate it
Groovy+Micronaut
MongoDB
RunCSS, which is a runtime version of TailwindCSS. See here: dev.to/mudgen/runcss-a-runtime-ver...
DRF + Vue/Gridsome/Nuxt.
Option A) Rails Full stack App with VueJS components here and there for highly interactive requirements.
Option B) Phoenix framework with Phoenix LiveView
Vue (Nuxt) + AWS + MondoDB + Netlify
elm for the front-end not the slightest hesitation
Backend: maybe Haskell or clojure or maybe roll the dice on yatta
and some event-store approache for the backend!
Haven't found a single reason to not use Rails. For the frontend I really like Stimulus but I use a lot of Vue at work.
Surprised no one mentioned OpenFaaS....
github.com/rberrelleza/openfaas-pl...
MERN
I mostly use Node on back and vanilla with no frameworks on front. I'm starting to try Deno, though and it looks nice.
Graphql and React.js(Next.js specifically) to solve real world problems.
For hobby projects, i use Rust and Haskell.
preact and python fosho
Go-to:
It used to be expressjs, react, typescript... but these days it is just rails, postgres probably with react and typescript if it is really needed
The ability to get things up quickly that rails provides is really underrated.
GQL and React (Gatsby) these days...
Sass -> Angular -> .Net Core -> RavenDb
CodeIgniter
MySQL or MariaDB
PHP
Javascript with Jquery
Clojure. All the way down.
Golang + boltDB or badger-db.
Vuejs for embedded application.
VFT (I know its not a thing):
Vue,
Firebase,
Typescript
Additional stuff:
SASS,
Vuex,
Vue router
ReactJS, NodeJS, Azure Functions, and CosmosDB 👌🏽
Python + CockroachDB + Nuxt.js
When I need to be productive
Rails + Stimulus & Vanilla JS + Turbolinks + Heroku + Redis + Postgres
When customer real ask for it and pay the bill on time spent
React
VS Code/Jupyter Notebook
Python and
Machine learning
Usually my projects consist of:
Drupal large.
Wordpress small.
On EcoWebHosting.co.uk
<3
Go lang mostly
Vanilla HTML/SCSS
Vanilla TypeScript
Vanilla PHP/MariaDB
the old but GOLD
Mern
Either React + firebase or MERN
PHP/Laravel and JS pay the bills. I'll occasionally use Vue, if the client side interactions are complex enough.
React + Mobx
Elixir/Phoenix + Postgres
Python, JS+Node, Nginx, no frameworks except jquery
why are only a few going for Gatsby, it's great tho. my go-to stack would be React+Firebase. I'm not really into backend development, so I prefer to go serverless with Firebase.