What is the best language / framework / stack that you can do work most or fast or most productive for a single developer . Python with django/flask , Ruby on Rails with ruby , rust with some frame work , Node js or something else. preferably with a easier learning curve .<p>Scenarios :
1. Webapps<p>2. Simple Website<p>3. Simple social media
Ruby on Rails has recently started actively marketing itself as the solo developer framework. I've worked with it for a long time now (among a bunch of other languages and frameworks) and I have to say the recent updates to the frontend 'story' are really compelling for a solo dev.<p>One of the compelling reasons to write JS on the server was to have the same language and ecosystem in the client and server, and things like Turbo for Rails really go a long way towards delivering on that for Ruby (although of course you still need to understand javascript and browsers.)<p>That said, if you're already familiar with something else, then pick the most mature batteries-included framework in that language. Languages are just a tool for the job, it's incredibly unlikely as a solo dev that you can pick a "wrong" one.
When I work on solo projects, my goto is what I've dubbed the HAG stack:<p><pre><code> - HTMX: For client/server interactions. Returning HTML fragments is easy and lightweight.
- AlpineJs: For interactivity that doesn't require a http request, think toggling sidebars etc...
- Go: Primary development language, simplistic and easy to get started with. Fast compilation and with embedded files I can ship a single binary for deployment that contains all required assets.
</code></pre>
Tertiary and other tools/services I use:<p><pre><code> - Turso (Sqlite): Primary datastore, great to use for a "db per user/tenant" approach."
- Redis: Sometimes I use redis over turso, depending on need. Also used for caching. I've been moving much more into Turso though, especially with the embedded replica's.
- Docker: Everything is built into docker images. For my Go app I disable CGO and use Google's "distroless" container images as the base image.
- Fly.io: Hosting everything.</code></pre>
1. Web apps - Ruby on Rails hands down, every time. with SQL lite works pretty good on smaller projects. this is if you're working on a project yourself or have a very small team. If you're doing full stack and if you're doing turbo/stimulus it's a bit harder to hire people that have all of that. In my experience, easiest to hire full stack devs are with node/react stack. Coincidentally that's the group of people with largest knowledge gap in the either stack, people tend to specialize in one<p>Not sure about 2 and 3, not my cuppa tea
I think .NET has gotten, or rather failed to shake off, a reputation as slow and Windows-only.<p>It's very powerful, the tooling is free and best-in-class, self hosting on a cheap Linux VPS is trivial and the framework itself includes almost any functionality you could wish for with installing random packages.
I think it is very, very hard to beat Python+Django. As long as you're willing to conform to the "Django mindset" and the boilerplate it requires you can get simple websites up and running in no time. You also get so much "for free" that most other frameworks does not provide you with. The only major drawback is that Django is not great if you really want to do things your way.
Rails is by far the best time saving all-in-one tool.<p>Nextjs for example don’t come even close - you can easily waste a month just properly setting up your monorepo with all necessary bells and whistles.<p>With this come also the scaling pains and downsides, which might only be relevant to a tiny percentage of solopreneurs.
PHP, Yii2 Framework, Nginx.<p>Productive out of the box, comes with bootstrap 5, jQuery( yeah i know).<p>It's has amazing documentation easy to learn. It uses PHP for templating, so you can prototype very quickly.<p>Collection of wisdom:<p>- A single dev will be more productive with a mature framework 10+ years, most of it has been documented, bugs fixed, tooling matured. Old is tried and true<p>- JavaScript libraries rot very quickly. Try running any node project from 2 years ago? Now try running any PHP, Django project from 15 years ago see the difference.<p>-C# and .Net is amazing<p>-Sqlite is amazing<p>- I was an angular/react dev for many years, now I'm pumping server side html templates and jQuery like there's no tomorrow. It's so easy, so simple. Why push json on the backend, then another project to consume/validate that JSON on the front-end, when I can just push everything as HTML.<p>- It's not just easy to develop, it's also ease of deployment.
I think there's a good argument for Elixir and Phoenix. It's shocking how easy it is to do just about anything with it. An excellent database wrapper, incredible async story, beautiful at real time. You can substitute in a JS SPA framework if you need to, but I think you can go really far with LiveView before that's a requirement.
Flask + Svelte is very accessible. When my Middle School students wanted to "build an app" I would roll up a boilerplate with Flask, Svelte, and SQLite on Replit (would not recommend anymore - Replit has jumped the shark) and they were able to become very productive very quickly.<p>EDIT: this was after 1-2 months of intro Python and JavaScript, so they weren't going in blind but also didn't have to learn, say, React. If you know some Python, you can use Flask. If you know some JS, you can use Svelte.
Productivity can mean speed, or it can mean reassurance that code will be easy to understand and refactor in the future (which compounds speed).<p>The past few months I’ve been working heavily with Python type hints and pydantic which makes it bearable.<p>Golang is strongly typed but it’s difficult to transform data handily with one-liners.<p>I’ve used Java and Spring but it’s very verbose<p>In my experience, TypeScript and its ecosystem has been very productive. It runs on backend and frontend, and the type system is very expressive. I always reach for it first.
LAMP (or LEMP) stack, hosted on a single VM (probably Digital Ocean).<p>You probably want to use a framework of sorts. Laravel or Symfony are good. Not mandatory though.<p>Server side rendering to start off with. Bulma for CSS. Alpine for JS.<p>Throw in some cronjobs for scheduled stuff.<p>Maybe a bit of Redis for sessions and caching.
Absent any other info, for a "single developer in 2024": Python and Django. Reason: You're statistically the most likely to know Python at least a little bit.<p>In general the selection algorithm for results-driven development is: First, go with whatever web framework you're most comfortable with. If you don't have any, go with whatever the most popular framework is, in the programming language you're most familiar with.<p>The reason this works well is because your question is ill-formed. In general, I haven't seen any hard evidence that Django vs. Rails vs. Laravel vs. Node vs. (etc.)-based projects have big variations in lead time to new features, lead time to bug fixes, etc. Your knowledge of the underlying PL, framework, and their quirks dwarfs any technical advantage they might have over one another.<p>(For the sake of completeness: If you don't know any programming languages, go with whatever the most popular language is. How do you know what's popular? Intuition! Most people's brains will answer "Python" or maybe "JavaScript" to that question, and those are both great choices. If you're the kind of weirdo who says "Ruby" or "PHP" or "Scheme", you might as well roll with it, because that answer comes from a part of you which is constantly noticing the trends in its local environment, and it probably has a lot more logic than you would expect.)
Supabase as a backend and any framework they support on the front. They do the auth, database, API, pub/sub, and you can use postgres' built in security features. Then you can use their 2 levels of server side functions if you need it - postgres functions or their deno lambda functions.<p>I've really enjoyed it for any play projects, they give you so much out of the box, and you can run the stack locally on docker.
Well, back when I was single, Ruby was definitely the answer. Now that I'm married I would still try it, or some or the JS frameworks backed by the big companies and still alive. I don't think my wife would mind me using Ruby.
As always with these things it really depends on what you're trying to do and what your skill level / background is.<p>Personally I find PHP + Laravel is great for throwing together a simple website. The amount functionality Laravel provides out of the box is incredible and so long as you're not doing anything too crazy you'll find most of the heavy lifting has been taken of for you.<p>If you need to use a modern frontend JS framework on your frontend then I'd probably go with React (or Vue) with a Node/Express API. I'm not a huge fan of using Node on the backend for professional projects be honest, but if you're a single developer I think there are benefits to using a single language on both your frontend and backend. I've tried using Vue with Laravel before, but I didn't like constant context switching between languages.<p>I've not got much experience with Ruby on Rails but I've heard good things about it and I suspect that would great option if you have familiarity with Ruby. I'm not sure if Rust would be the most productive choice?<p>If you're just getting into web development I'd go with Laravel personally. I wouldn't complicate things just yet with adding modern frontend frameworks like React into the mix.
I'm using dart/flutter. They don't get a lot of love on HN, but for speed of development and experimentation they're excellent (hot reload being extremely useful), plus they're cross platform meaning you can decide whether you want a webapp or target mobile (android and iOS) or the three main desktops. I've enjoyed learning and using them.
Cloudflare Workers, raw html/css/js (maybe TS). Can use a different "pages" provider like Netlify. It's very freeing. Especially Cloudflare, where the server side APIs are very similar to client side service worker APIs. The "low level" browser APIs can do a lot, you might be surprised. And you won't have any dependencies to update 2 years later.
Some would say Laravel and I can agree, it's such a powerful web framework to build quick. Personally I'm at the most productive state when working with Next.js + TailwindCSS & Prisma. Additionally I also use a UI library called DaisyUI that is built on top of TailwindCSS.
It depends what kind of UI you want.<p>To just get a functional website, the backend frameworks are just way more productive than having to mess around with a frontend/backend solution, so rails, django, elixir, etc all excel, are cohesive, have tons of support and libraries to cover different needs, etc, and generally not too difficult to learn.<p>Though personally I found rails' magical 'convention over config' to be an abysmal hindrance to learning how things actually work - for example many examples show code, without showing where in the filesystem the code should go - you're expected to know the convention already, and things like i18n translation 'paths' can be confusing, and fail silently.
I've pumped out many web apps using Svelte(Kit). I find it very good for rapid prototyping and exploratory programming. For example, I wrote a beat-aware video player in an afternoon or two (while I was learning Svelte).<p>Even if you are a single dev, you will probably find yourself interacting with other members of the community. (Maybe more so for a single dev?) I find the Svelte community quite responsive and helpful.<p>SvelteKit can handle both client and server parts. It streamlines a lot of the stuff most web apps need like routing. However, it doesn't include some other common stuff like auth and persistence to a database.<p><a href="https://kit.svelte.dev/" rel="nofollow">https://kit.svelte.dev/</a>
I've been doing mostly solo for +25 years and now consider Rust + tailwindcss + htmx + Postgres the best overall. Before I could have said Django, then before Delphi, then before FoxPro.<p>One thing that is important in your calculations is how long-term is your outlook. What is nice to do in one week is a huge drag doing 2 years.<p>The more involved the logic or the more you are doing the project, the more paid to have a strict stack that solves the harder problem in the most correct way possible.<p>ie: js + nosql + schemaless and stuff like that, that sound simple will give negative productivity after a certain size and time on the codebase...
If you are asking for the most general-purpose technology around right now, I would say Dart/Flutter.<p>Dart is a half-decent language, able to be used without excessive pain for mobile, desktop, web and backend development. It compiles to Javascript and WASM, as well as native code. And web can be either traditional HTML or a recreation of your mobile/desktop UI.<p>It’s a really healthy community with strong leadership and wide participation.<p>You’ll need SQL, but otherwise, you can build any kind of app with Dart and Flutter with reasonably fluidity.
People are going to hate me for this, but I'm going to say it anyway: WordPress.<p>Need social media? BuddyPress plugin.
Need a webshop? WooCommerce plugin.
Need a cheap mailing list? Mailman plugin.
Need a forum? BBPress.
Anything you can think of? Plugin.<p>I needed something fast for my own website <a href="https://rpgplayground.com" rel="nofollow">https://rpgplayground.com</a>, and took this road. Best decision I ever made. Every time I needed new functionality: ah, there is a plugin for that!
Kotlin is like a Rust with garbage collection. It has a bunch of good ergonomics, safety features and modernity, and the 2.0 release is just about to happen.<p>You can use Kotlin as a mobile frontend language as well, it's especially good on Android. And there are both JS and wasm outputs available.
Keep in mind that the average replier here is an older developer whos skillset has come from the 2008-2018 generation (Rails, Django) and have rarely ventured elsewhere. Or when they have they blame the learning curve on the tool not themselves.<p>To me it seems like your very early on your journey and haven't ever learned a web framework or become proficient in at least one language.<p>So if I was to give you a blanket recommendation: Javascript or Typescript.<p>From there you can start on the frontend side and work your way to a backend (Nextjs is a good candidate here)<p>or do the reverse and go back to front and start with Express<p>The reason im recommending this is<p>- Youll have to learn javascript anyway<p>- It has tons and tons of support (libraries, tutorials, docs)<p>- You can also venture into mobile app development if thats interesting.<p>- Once you get the hang of it I believe its faster to spin up projects than rails or django<p>This is coming from someone who has worked professionally in *a lot* of stacks<p>- Ruby / Rails / Angular<p>- Python / Django / jQuery<p>- C# / .net / knockout.js<p>- Javascript / Express / React Native<p>- Elixir / Phoenix / React<p>- Hasura / Nextjs<p>- Go / Nextjs<p>- Java / Spring<p>- Haskell / Elm<p>Aside: if you want to know my favourite stack, BE It's Elixir / Phoenix by a large margin. FE im just more productive in React/Nextjs but Remix seems cool.
JavaScript all the way - you'll probably need it one way or another.<p>So why not go with the one language that works on the backend, frontend, data processing, scrapping? Getting to a pro level in multiple languages is more difficult than mastering just one.
If you are doing webapps, JS all the way. Although don't overlook the benefit of static html/css for a lot of things, at which point Python becomes very worth it because of its integration into other things is a bit better than JS.
Most comments are just posting their favourites without reading your question imo.<p>Simplest and most productive without a step learning curve. Nodejs, javascript. Lots of resources to learn from, questions answered, basic approaches, lots of libraries, easy to troubleshoot, closest to the web stack.
Making things is the most productive stack. Your experience is the only way to know what works for you and to know what doesn't work for you. It is the only way to know what you are actually interested in doing versus what you are interested in thinking about doing
.
What I mean is, you could have started building a simple website with Notepad instead of asking a question. It would probably have been hard and not very good. Asking the question was not and turned out ok.<p>Anyway, HTML and Javascript is the simplest thing that might work. HTML and javascript are the fundamental abstractions of web development. Not knowing them is an "illiteracy."<p>Getting anything up and running will still require a lot of workflow discovery. When you have experience in a workflow you can make informed decisions about your particular needs.<p><a href="https://wiki.c2.com/?PrematureOptimization" rel="nofollow">https://wiki.c2.com/?PrematureOptimization</a><p>Good luck.