Ask HN: Starting a project today, which web framework would you use?

94 点作者 betimd大约 8 年前

If you will start your project today (medium to large application) which web framework technology would you pick: - Asp.Net Core - Node + Angular - Node + React - Django or Flask - Rails - Laravel or Zend - Play Framework - Other

88 条评论

sharmi大约 8 年前

My usecase is mostly side-projects that I want to take to the market. So I stick to Django.Why?* I am already familiar with it's advantages and quirks. So I can get running faster. The knowledge that I have accumulated in my previous projects will be handy to get going. Time to market is important for both validating the product and avoiding a burnout.* There is a well defined way to do most common stuff. So you need not experiment and reinvent the most basic stuff. All those get out of the way and I can concentrate on the meat of the problem.* Many libraries like auth, rest framework are battle tested and most likely tested for security vulnerabilities. if you are taking something to market, it is in everybody's best interest to ensure security is taken care of by the pros. Django is solid in that aspect.* Though python may not be the most performant language (I have been bit by that a lot in data processing) it is still fast enough for websites with normal loads (which is 99.999% of today's websites).* If I do have a performance bottleneck, there are lessons from pioneers on how to optimize it.For me, django fits all these needs. For you it might be Rails, Node, Play or Phoenix. I used to want to learn Phoenix and Play.But I realized it is a no-win situation when you mix a brand new tech with brand new product.Now I reach out to new tech only if it fixes a sore need that my existing toolkit cannot handle.For example, I am looking into webpack and purifycss, because django does not have the necessary functionality to trim the fat in bloated CSS, while Node stack excels.If I work on a interaction heavy front-end, I might reach for vue or react, and that too only if I really need it.Else, I am quite happy with django/vanilla-javascript/sass/bootstrap(for prototyping)

评论 #14396007 未加载

Existenceblinks大约 8 年前

Frontend: ElmBackend: Rails|PhoenixDatabase: PostgreSQLI don't understand why people still write javascript except legacy codebase maintenance although I respect everyone's freedom. Especially, sorry, React/Redux why? Yet, people are obsessed managing state on client (browser), that's the bad days of whatever framework including Elm. 90' Game developers would wonder too since they often prevent corrupt states from bad people was trying hard to mess (cheat) game states, thus source of truth and constraints must only live on server. States on front-end must be just something only for sake of displaying.

评论 #14394578 未加载

deedubaya大约 8 年前

Everyone is posting layers upon layers of components and frameworks. It just seems so bloated, so hostile towards the developer.From my experience, the more independent projects you include, the harder an application will be to maintain, let alone configure and build. Am I just old and cranky? Or is there reasonable justification to do this?

评论 #14400617 未加载

评论 #14394622 未加载

评论 #14394529 未加载

yeukhon大约 8 年前

1. Django 2. Pryamid 3. FlaskI used to use Pyramid for everything unless I needed forms and UI then Django is a no brainer choice. But I stopped wanting to setup SQLAlchemy and writing bootstrap codes for managing test states etc. I still love Pyramid because of its flexibility, but perhaps I need to invest time in the plugins to see if there's anything quality to support SQLAlchemy integration much like Django's ORM out of the box, and whether there's quality test integration out of the box much like django test command. Flask I have a love & hate relationship too. I feel like the community is too lose. I used to write Flask apps but back then half of the recommended libraries/projects would not have updates for months. I can't trust code that isn't widely adopted and widely used, because I don't want to be the only one filing bugs. At least Pyramid has built-in Authentication modules that you can use, but Flask I'd have to rely on the community project which to be really honest, I am not sure if I want to trust it in the long run. So these days, I fall back to Django first, Pryamid second, then Flask finally (especially convenient for quick projects).I don't really do any front-end development because I totally not good at it, so I gave up ~3 years now. But I would look at EmberJS and React.

scarface74大约 8 年前

* What I would not use is any language that is not statically typed. The compiler can catch an entire class of errors and there are great tools for automated refactors. For me this narrows down my choice of languages to C#, TypeScript (Node), and if really necessary Java. But today I would probably use Kotlin instead of Java if possible.* Technology is a means to and end for me - to get stuff done and to remain marketable. So I would probably choose the front end framework that is the most marketable. Which seems to still be Angular. Two advantages - when it's time to switch jobs I have more choices and when I'm looking for contractors to come on to projects that I'm over, Angular coders are a dime a dozen.That being said, I'm really finding the combination of Bootstrap + JQuery + Handlebars to be refreshing for non-SPA websites.* Databases. If I'm spending other people's money, I prefer SQL Server/Entity Framework as an MS person. When NoSql is the right choice, SQL Server has pretty good support for JSON. It really is the best of both worlds.If I'm spending my own money or don't have a budget, I would probably choose either MySQL (relational) or MongoDB (NoSql)* I know this wasn't part of the question, but for hosting, AWS all of the way and I would use as many of their services as possible except for DynamoDB. It just feels a little odd.* And to go even more down the rabbit hole. I would hate coding without my JetBrains subscription. Right now, I just have Resharper. But if I were doing this as a side project I would have the subscription that included everything.

评论 #14406966 未加载

1ba9115454大约 8 年前

Rails. No question.In my 7 years of using this framework I have come across nothing that comes even close to in terms of LOC, ease of pickup and quality of the end product.

LouisSayers大约 8 年前

Rails + JQuery + Postgres + HerokuWhy? It works. It's not gonna have crazy changes. It's simple. There are a million relevant resources to help learn how to do x, or help you if you get stuck. It's easy to hire skilled people that know this stuff back to front.btw - you don't start a medium to large project. You start a small one, build incrementally, and see what happens. If you have success, then you can spend money building in whatever you like.

realharo大约 8 年前

Depends on the project, but most likely just Node + express + TypeScript on the backend (so no "framework" in the traditional sense).On the frontend, React + MobX + TypeScript.This of course means it would be a single-page application.Benefit of using TypeScript on both client and server is that you get to automatically share the schema of the data they're exchanging (and maybe some more code as well, like validation). For free. And when you change the structure of something - and you will - you get immediately alerted to any issues on both sides (e.g. this property is now required, and you omitted it in this function!). This is huge because maintenance is often more difficult than writing the initial version - and I don't even mean the initial released version.Also you get to potentially reuse some of the code in the future for a React Native based mobile app.I'm also eyeing GraphQL and Apollo a bit, but I don't have enough experience with them to use them in a "real" project just yet.

评论 #14396088 未加载

评论 #14400632 未加载

TurboHaskal大约 8 年前

Mojolicious (Perl), Spring Boot (Java / Kotlin) or plain Go. Depending on productivity, performance and hardware constrains.If it's the typical CRUD site I'd use Django (Python) if I worried about finding developers, otherwise sticking to good old Catalyst (Perl) or perhaps giving Phoenix (Elixir) a try.

评论 #14392490 未加载

评论 #14396672 未加载

jetti大约 8 年前

Phoenix (Elixir) for the backend because I started with Elixir this year and really enjoy it. If the app was simple enough and I was feeling up for a challenge than maybe just Erlang directly with Cowboy (so no real framework).For the front end: Elm or maybe Ember.js. I started learning Elm this year too and like it but I possibly would go Ember because it seems interesting and since I have a membership to Daily Drip I have free tutorials on Ember (as well as Elm and Elixir)

richardknop大约 8 年前

Django if front end is complex (lots of forms, complicated templating, need to have a free admin interface for out of the box).Or if the front end is simple, I'd just write it in Go using core net/http library.To make it more maintainable, I'd probably split the application into two components, so backend could be API written in Go and front end a Django app.

borplk大约 8 年前

Node + Koa + React (server side rendering) + ReactRouter + Redux + TypeScript + PostgresNot because they are so great but because everything else is even worse.After significant React experience I can no longer tolerate send-html-template-sprinkle-javascript stacks.The downside is that the amount of boilerplate is unbearable. There's significant friction in the tooling because of transpiling, sourcemaps, multiple layers of sourcemaps, file watching, having to produce multiple different bundles for server side rendering, client-side bundle and so on, testing with transpiling is a pain, test coverage with transpiling is at times borderline impossible, proper isomorphic data-loading is difficult and the list goes on. Still prefer it to the other stuff.

评论 #14394081 未加载

评论 #14394318 未加载

pleasecalllater大约 8 年前

I think there is just one sane choice: I'd use the one that I know best, and the one that has huge number of users (which means it's more battle tested).In my case it would be Django + PostgreSQL.

mobitar大约 8 年前

There are pros and cons for each.React: once you get the framework down, it's a lot easier to build a native mobile app with React Native. There's no Angular Native.Angular: powerful and abundant. A little different, but flexible. Answers on SO for every little thing that will come up to ask. Not sure if newer frameworks will have that same luxury.Rails: a lot of convention. But once you get it down, you'll be able to build complex apps in little time. Also a lot of community support and search engine presence.If it helps, I've open-sourced all code around Standard Notes. It's mostly a Rails/Angular stack.<a href="https://github.com/standardnotes/" rel="nofollow">https://github.com/standardnotes/</a>

评论 #14410012 未加载

smilesnd大约 8 年前

If I was to start a project today it would be Elixir using cowboy and plug. I like to keep things simple. If I thought the project was more on the medium size I would probably use Asp.Net Core. For the frontend I like to stay vanilla and use bare bone so html/sass/typescript with maybe jquery if needs be. Postgres for my database needs.

gtf21大约 8 年前

Frameworks? none.Technologies? node.js + express; postgres; react + reduxWhy? Speed and flexibility of development (although tbh this is just about what you're used to), using the same language on both ends, and I really like js.

评论 #14394281 未加载

评论 #14400374 未加载

metachris大约 8 年前

Backend: Django as soon as you want an admin interface for your models. It just saves so much time, and nobody enjoys writing those dumb CRUD routes. If you don't need an admin interface and want to stay in Python, I'd recommend Flask. Else I'm also enjoying Node.js.Frontend: Vue.js or React.

harel大约 8 年前

Backend: Django (Python 3.5+). Yes flask might be lighter etc, but at the end of the day, when you need to do things quick, batteries included approach goes a long way. Also, it will be easier to find developers who can hit the ground running. Most of the time, I would use it for an API layer coupled with Django Rest Framework.Database: PostgreSQL 9.6. That's easy. You get the best of all worlds here. RDBMS with indexable JSON document store. Stable, fast. There is no other choice for me.Front end: Depends. React/Redux works for me 80% of the time. I prefer to use Semantic-UI (the React port is excellent) for the presentation. The other 20% are simple admin only apps where plain old html would do just fine. I now try to avoid all-in frameworks which tie you in like a Catholic marriage.Async: Celery + RabbitMQ. It works, and works very very well as a background task/job runner.Source control and Project Management: Git and Github.Specialised system apps - Go(lang). For fast specialised servers, websockets, etc.Deployment/Provisioning: Ansible.Bonus points: Personal Development: Learn a new language every year. Do a little project in it.

thiagooffm大约 8 年前

Rails: stable ecosystem, just heroku it

评论 #14392316 未加载

ryanom大约 8 年前

Django has a lot of nice things that come with it and you can get a project setup in a flash using CookieCutter-Django: <a href="https://github.com/pydanny/cookiecutter-django" rel="nofollow">https://github.com/pydanny/cookiecutter-django</a>

strictnein大约 8 年前

Other: the one you're most familiar withIf you're starting up a new project, choosing the "best" framework vs the one you're most familiar with is going to make everything that much more difficult. You're going to learn something before you can build something? And build something more slowly because you're trying to learn something?My untrendy answer:<pre><code> Frontend: Backbone/Bootstrap Backend: Node DB: Postgres or Mongo </code></pre> If you don't know those things, then this isn't the right answer for you, but whenever I start up a new little project in my spare time and utilize Backbone, it's like a breath of fresh air, compared to most of the current popular frameworks and what we have to use at work.

renke1大约 8 年前

My current stack:Backend: Go (standard library mostly, httprouter, and some homegrown libraries for stuff like dependency injection, configuration etc.)Frontend: TypeScript (with React and Redux/mobx)Other than that, I think using something like Kotlin, Swift or Elixir could be interesting in the backend, too.

评论 #14396458 未加载

bussierem大约 8 年前

I've created a list of every technology (language, framework, DB, etc) posted as of 0913 May 22: (This list may contain some overlap, since I don't recognize like 75% of these names)Elm, Rails, Phoenix, Postgres, React, MobX, Typescript, GraphQL, Apollo, Kotlin, Mojolicious, Sprint Boot, Go, Django, Catalyst, Node, Koa, ReactRouter, Redux, C#, Bootstrap, JQuery, MongoDB, Express, Vuejs, Flask, Swift, Elixir, Cowboy, Plug, Asp.Net, Heroku, Tornado, SQLAlchemy, Celery, Clojure, Ring, Compojure, ClojureScript, Reagent, Knockout, Meteor, Haskell, VanillaJS, ReasonML, Tachyons, Flow, Redis, EventStore, Suave, Python Bottle, Preact, Play (Scala), Sanic, Loopback, Werkzeug, Laravel, AngularJS, EF Core, Dapper, Vert.x

tarboreus大约 8 年前

Try lightweight. Flask, Skeleton, and sqlite. Don't use SQLalchemy until you need it. (Hint: you probably won't need it.)

outsidetheparty大约 8 年前

After years working in an Angular 1.x stack, I took a long, hard look at Angular 4 and decided to make the switch to Vue.js (with firebase on the back end). I'm happier and more productive with this combination than I have been with any web development setup in literally decades.Vue does everything Angular did for me without nearly as much cognitive overhead. Working in Angular just felt like an endless stream of hidden gotchas and idiosyncratic jargon; for the year or so it took me to really start to feel like I had a handle on the framework it seemed like the answer to "How do I do foo in Angular?" was always "Don't do foo; do bar, baz and bat instead, but make sure you don't quux, that'd be really bad". And even after I'd more or less gotten used to the Angular Way To Do Things it always felt like I was fighting against the framework instead of depending on it.Vue just works. The component structure is really developer-friendly, it's much easier to incorporate non-Vue code when you need to, and it all just pretty much DWIM without you having to think about what's going on in the guts of the framework. It took maybe two weeks of practice before I felt totally comfortable with the system. Clientside performance is a zillion times better than Angular; you don't have to pick through an entire freaking ecosystem of secondary frameworks just to get started like you do in React; vue-cli gives you sensible scaffolding and you don't have to spend much time fiddling around with webpack and build configuration. Yeah. Good stuff.Firebase I'm a tiny bit less unreservedly enthusiastic about -- don't get me wrong, it's super convenient, and it's nice not having to spend much attention on the network layer of my apps, but there are times I wish it were a little bit less magic than it is: I can't always tell whether I'm using it efficiently or not. And the tree data structure isn't appropriate for every project; I kinda wish there were an equivalent with the same websocket live data updates but backed by a boring old RDBMS instead of a JSON store. Plus, you know, vendor lock-in is always a concern. For a mostly-front-end guy who just wants to be able to store and retrieve data without thinking too much about it, it's fine; I'm not ready to evangelize for it quite as much as I am Vue though.

thom大约 8 年前

Clojure + Ring + Compojure on the server, ClojureScript + Reagent on the client. Because I don't know any better, and want to be punished the moment I have to hire anybody.

评论 #14397934 未加载

评论 #14394539 未加载

jon49将近 8 年前

PostgRest with Mithril.js or Elm on the front end. Keep it simple. Or WebSharper with SQL Server for a more integrated feel with static typing all the way from the database all the way down to the front end. Studies have shown static typing to be extremely important for removing bugs and programmer productivity, and from what I've seen WebSharper would give the best experience for that.I've only used Mithril.js in those technologies though.

spapas82大约 8 年前

Django for the backend with a postgres database. Just use django - I am using it for around 7 years: never regretted it, always happy with my choice. This is important to me and has not happened with other things I've used (like spring mvc, jsf, angular.js, android dev etc).I generally try to avoid complex front end stuff, in most cases a little jquery and a datepicker are enough. If I need something more client heavy then I'll always try the least complex solution - if jquery isn't enough then knockout.js would suffice most of the time.On extreme cases (UI heavy SPAs) I'd use react+redux with a django rest framework backend. But only if it is absolutely required. I have measured that using pure django (and friends like django filters, django tables etc) is like 5 times productive and 10 times more DRay than if you add client side/ajax stuff to the mix (along with the required bloat like client side tooling/weback, apis, auth, routing, client side models and forms etc).

anhtran大约 8 年前

I may use many languages and frameworks in one project if needed. I will start with Django because I'm good in that skill set.

sidcool大约 8 年前

Play Framework with Scala. Very simple and super scalable.

npolet大约 8 年前

It's nice to see all the love for django here. I've been developing with django for many years now and I feel like more and more developers are finally picking it up for various projects. It's remained very popular for quite some time now. I especially love the django developers, as they really seem to put out high quality releases that make updating to the latest version fairly painless.I would also opt for django, postures and react+redux on the front for any complex hi needs. With django rest framework powering an API, building complex ui's becomes less painful. I've yet to find something quite as powerful as DRF.Recently started a large commercial project 4 months ago and I'm seriously glad I went with django.

out_of_protocol大约 8 年前

Backend: Elixir, Phoenix, Postgres, Redis (All components proved to be rock stable for me)Frontend: Vue.js, ?, ?

marcus_holmes大约 8 年前

Go (stdlib + gorilla/mux) + Postgres + React/Vue/Vanilla depending on need

dexterchief大约 8 年前

It feels like the constraints/expectations we face building in 2017 are different from those of 2004 (when Rails was created) or 2005 (when Django was created). Both of these predate the iphone (launched in 2007) and the dominance of mobile, as well as stuff like Websockets (2011), 12 factor, immutable infrastructure, distributed systems...It feels extremely unlikely that that if we decided to design a framework with these things in mind we would end up with something that looks like Rails or Django (or some other RESTish/MVC thing), and yet somehow these are the things we overwhelmingly use and recommend.

jasim大约 8 年前

For projects I will maintain for the foreseeable future: Rails, Reason-React in ReasonML, CSS-in-JS, and Postgres.For clients: Rails, React+immutability-helper in Javascript, Tachyons+BEM combo, and Postgres. Possibly Flow or TypeScript.

holografix大约 8 年前

Definitely pick Python and Django or Flask for your server side.Python is a super easy language to work with and if you combine with heroku for hosting it's a no brainer.Now if you want to develop something more front end heavy maybe Flask to quickly layout your API endpoints.I would suggest learning react redux if you want to get into JavaScript as you come out the other side with a better understanding of functional programming and a pathway into modern Webdev in terms of componentisation and progressive web apps.The tool chain for React has been simplified to regular human levels of patience now through create-react-app

mythrwy大约 8 年前

Depends.Tiny project, Python Bottle.Flask if project isn't complicated or not expected to grow much or I don't care about model admin. (and maybe even Flask if project is expected to grow... Flask really is a pleasure to work with).Otherwise Django.

评论 #14395702 未加载

typednothing大约 8 年前

A web user interface is just a user interface to the actual program, which I always construct as a commandline (cli) program. It should also be easy (or at least doable) to build a mobile and/or desktop user interface for the same backend cli program. All of that should naturally be able to run as docker microservices. In other words, web "frameworks" are just a pile of retarded crap that is totally incapable of doing any of the aforementioned.

rbutler大约 8 年前

Buffalo - <a href="http://gobuffalo.io/docs/getting-started" rel="nofollow">http://gobuffalo.io/docs/getting-started</a>

vorotato大约 8 年前

EventStore + Suave + React + RXI'd be really tempted to use Fable's F# -> javascript for the frontend, but I don't know the ins and outs of that yet.

mabynogy大约 8 年前

None. Plain Javascript and static pages. CGI for APIs.

评论 #14395594 未加载

ljw1001大约 8 年前

For the backend, Kotlin on Intellij. It's crazy awesome and you can use it now for android clients as well.The Javascript transpiler is probably not ready yet (in beta) so I would use a Bootstrap and/or Material Design library with lots of components and tie it together with javascript.Database Postgres. You can go hard relational if that's appropriate or use the Json support like a better Mongo.

patatino大约 8 年前

Asp.Net Core or Flask.. why? Becuase I know them.

aprdm大约 8 年前

If it's a small project / defined REST api - flaskIf it's a big project / still not sure of the requirements - djangoFor the frontend: React

jakozaur大约 8 年前

Meteor with React: <a href="https://www.meteor.com/" rel="nofollow">https://www.meteor.com/</a>

评论 #14392787 未加载

roro5678大约 8 年前

Node.JS + Express + Vue.js

sAbakumoff大约 8 年前

Pure Go on the back plus jQuery on the front.

评论 #14395706 未加载

kamalkishor1991大约 8 年前

Ruby on rails Here is my experience: <a href="https://hackernoon.com/ruby-on-rails-is-more-productive-even-after-learning-from-scratch-for-your-new-web-app-3cb22a06fa8a" rel="nofollow">https://hackernoon.com/ruby-on-rails-is-more-productive-even...</a>

BerislavLopac大约 8 年前

For the server-side, definitely Tornado + SQLAlchemy + PostgreSQL. This is the core, with a likely addition of things like Celery depending on how large the system gets.The client side would depend on the complexity of the user interaction, but the Web part would probably involve React.

gregopet大约 8 年前

For larger apps I'd use Grails (think Rails on Spring Boot) with Postgres. Depending on the app I'd either use the built-in Hibernate offspring or the awesome jOOQ library to access the database. No freaking idea about the frontend, so much choice..

kennu大约 8 年前

Serverless Framework + Phenomic (React static site). No servers to worry about, no OS maintenance, out-of-the-box scalability (using AWS API Gateway / Lambda / S3). All development in JavaScript, so no need to context-switch for client/server.

rwieruch大约 8 年前

Depends on the case:- Do I want to use the latest technology?- Do I want to bootstrap fast?- Do I want to experiment/learn or do I want to build a business?Depending on these questions, everyone has to decide on their own. If it would be me, I would take MERN stack (MongoDB, Express, React and Node).

评论 #14392137 未加载

slake大约 8 年前

Angular + Flask is my go to. Still haven't jumped to Angular2 though.

tdevito大约 8 年前

FAM stack; firebase + angular + material design. Get anything up and running in hours. With cloud functions you can set up server side code with minimal effort.

exabrial大约 8 年前

The choices presented make my head hurt... A simple stack is a happy life. Spend time on the business problem and choose the most boring technology available.

justin_vanw大约 8 年前

Werkzeug + Postgresql

brianwawok大约 8 年前

Django!

ashlin大约 8 年前

Having experience with Node, Rails, Go I would choose Rails for backend and Vue or Backbone (for full control) on the front.

jftuga大约 8 年前

ITT: Postgres is a lot more popular that MySQL

dna_polymerase大约 8 年前

For Python I'd use Sanic. Database depends on your needs, but for me it is MySQL mostly. Cloud Hosting from Google.

rimliu大约 8 年前

Rails. For frontend: depending on need. Maybe jQuery, maybe intercooler, maybe vue, maybe react. No Angular for sure.

cbenz大约 8 年前

Frontend: definitively Elm.Backend: Node for popularity, Elixir or Haskell to try something new, or Python Flask which I already know.

madiathomas大约 8 年前

I will write an API using ASP.NET MVC framework using C#.NET. Front-end I will use HTML5, CSS3 and jQuery.

BigBalli将近 8 年前

The answer to "Do I need a framework?" will inherently include "which" one to use.

sirrele大约 8 年前

Node.js + Loopback + Angular2 + MySQL

评论 #14392491 未加载

theoneone大约 8 年前

I would go safe and use PHP(laravel)

评论 #14398834 未加载

评论 #14396699 未加载

niftylettuce大约 8 年前

<a href="https://crocodilejs.com" rel="nofollow">https://crocodilejs.com</a>

staticelf大约 8 年前

ASP.NET Core + Angular probably

评论 #14392841 未加载

krystiangw大约 8 年前

Choose technologies you are the most comfortable with. I would go with MEAN stack.

newdayrising大约 8 年前

Definitely Elixir/Phoenix. Front-end it really depends on the type of app.

aeharding大约 8 年前

Node + Vue

scalatohaskell大约 8 年前

Scala Play backend (because i know it most), ScalaJs and ScalaReact

philmander大约 8 年前

I started one recently with Preact + Mobx. Very happy with it

samsonradu大约 8 年前

Yii2. React on the front if the UX really requires it.

Elemerald大约 8 年前

Backend: Vert.x (Java) Frontend: Angular 2 or React

Traubenfuchs大约 8 年前

Spring Boot with spring-data + MySQL + vue.js

MichaelBurge大约 8 年前

Rails + Postgres

meerita大约 8 年前

I would go definitely with Ruby on Rails.

matdehaast大约 8 年前

Backend: laravelFrontend: vuejs or react with ssr on both

romanovcode大约 8 年前

Backend: .NET CoreDb: PostgresFrontend: jQuery and Bootstrap

geekme大约 8 年前

Go + MySQL + Angular JS

hondadriver大约 8 年前

Aurelia + TypeScript for the front-end and C# on .NET Core for the back-end.

haskellandchill大约 8 年前

Haskell + GHCJS

UK-AL大约 8 年前

asp.net core + c#, typescript + react

pknerd大约 8 年前

Laravel 5.4

评论 #14398846 未加载

tarikozket大约 8 年前

Ember.js

aeikenberry大约 8 年前

Django

bbcbasic大约 8 年前

I'd use what I'm familiar with. That's be asp.net and knockout