Storage: Postgresql Backend: Go (no framework, just the standard library) Frontend: Vue Working great so far. A little longer to get things up than using Rails/Django, but the extra speed and control is really nice. Using Go's templating engine to assemble Vue components into HTML tags works well.
What are you using for SSR? I haven't yet seen any concrete tutorials for getting this up and running with Vue and Go. All I've been able to google is augustoroman/V8 and dop251/jago and other derivatives.
Ask HN: Go-to web stack today?
251–260 of 453 posts
Re: Ask HN: Go-to web stack today?
#252Earlier quoted context omitted.
No, not right. I have work on a daily base with redux unfortunately. Redux is not too hard, but it's poor in design. Also you will have to give up redux soon, the hype is over and better things are at the horizon. There is definitely some pride in dev's working with redux, once they understand it they feel like they've grown as a developer. Do you really think redux is the holy grail of stores? If you're really smart…
Wow. What an incredibly ignorant and embarrassing point of view. > Redux is not too hard, but it's poor in design. You have not once yet stated why it is "poor in design". > Also you will have to give up redux soon, the hype is over and better things are at the horizon. I do not care for hype. I am embarrassed for you that you use hype as a measure of a technology's quality. > There is definitely some pride in dev's…
I have to work on a daily base with redux because almost every stupid company is using that nowadays. Some codebases are so horrific that I simply quit the job and find something better.
I actually said why it is poor in design: endless switch statements with reducers, do you think that is great design? Every component that wants to use a store needs to 'connect' to it with a higher order component, ever seen chains of hoc's and still know what's going on? Then you need to write time and time again mapStateToProps and mapDispatchToProps. Do you think that's great design? Even if there would be no other state management system yet, it still sucks. Even Dan Abramov says you probably don't need redux, still everyone is using it for the most simple apps.
You might want to use a router, well you're kinda locked into redux so you need redux-router. Example from the redux-router repo:
import React from 'react';
import { combineReducers, applyMiddleware, compose, createStore } from 'redux';
import { reduxReactRouter, routerStateReducer, ReduxRouter } from 'redux-router';
import { createHistory } from 'history';
import { Route } from 'react-router';
This, for just wanting to use a fucking router that works along with my store! You think that is great design? React is great design IMHO, not redux. Dan Abramov is a great guy, highly talented, times more intelligent than I am, but his design principles are really poor. Same counts for hooks, a fun experiment for a counter demo, but poor design for larger apps. I hope it will never become a hype too.Redux is just one of the many flux implementations. Not the best, but a flavour that you may like or dislike. Unstated is a client store that is a wrapper around the new React Context API: unstated: https://github.com/jamiebuilds/unstated
Re: Ask HN: Go-to web stack today?
#253Why would you even need a front end framework if you want to quickly put together a simple website? use php laravel and you get everything set up, use .net core and you also get everything. Elixir? Vue? React? say whats the hip web stack today instead of go-to. Also people mention nginx, again use apache because it has letsencrypt has easy support for HTTPS certificate.
Re: Ask HN: Go-to web stack today?
#254For web applications
React with optional state management (Redux Saga / Mobx) for the front, hosted on Netlify.
Ruby on Rails in API mode, with Postgres running on Heroku if the API is non real-time or high traffic / spiky. Go with DynamoDB if it is.
Re: Ask HN: Go-to web stack today?
#255- On the frontend, use React with TypeScript. Create React App now makes it dead easy. Just do: npx create-react-app myapp --typescript - Do not use redux until you know React well. You might not need it. If you do need it, use `redux-starter-kit` offered by the core Redux team. - For backend, just use Django (or Rails). Elixir's Phoenix is also very well thought out. - If you use node: express, sequelize. Async/awai…
Have any tips for converting an old and cumbersome rails app to react?
Re: Ask HN: Go-to web stack today?
#256Re: Ask HN: Go-to web stack today?
#257Earlier quoted context omitted.
Although I think it's not a big issue, I'd look into Vue instead of React. Imo it's simpler and give you a more complete solution out of the box (routing, reactive data layer). Now, I've barely tested Django, but I would not go the python way unless you have a good (other) reason. Rails seems to have a much more developed web development community. Node might be a great choice due to you being able to use the same la…
> Now, I've barely tested Django, but I would not go the python way unless you have a good (other) reason. Rails seems to have a much more developed web development community. Having used both Django and Rails extensively recently, I disagree. Maybe 5 years ago, yes. For two examples I ran into yesterday, check out https://github.com/rails/rails/issues/32790 and https://github.com/rails/rails/issues/31419 which featu…
https://code.djangoproject.com/ticket/15619
ActiveStorage is relatively new feature which also isn’t really big of a deal. Most issues mentioned in above links can indeed be solved by using the direct methods without given abstraction.
Using both Rails and Django I much prefer Rails, but I don’t see a point in bashing the other using single picked issues as a general argument for how crappy the framework/community is.
Re: Ask HN: Go-to web stack today?
#258First, be entirely sure that you actually need an SPA. So, in stages: - Database: Postgres (you could start with any relational DB, Postgres is just one of the best). It's very, very likely that your model is gonna be relational so better pay that debt upfront. Don't even consider NoSQL this early; we're paying a heavy price on my current job because the initial developers bought that non-relational databases were be…
At least briefly consider whether or not you actually need a relational database when starting a project. I work with some rather complex data access using Postgres, JPA, Hibernate, HikariCP, and a second level cache, all within a separate microservice exposed via a REST API. To make matters worse, the responsible developer has since left the project to me. We don't even use relations, so this essentially means that…
Re: Ask HN: Go-to web stack today?
#259First, be entirely sure that you actually need an SPA. So, in stages: - Database: Postgres (you could start with any relational DB, Postgres is just one of the best). It's very, very likely that your model is gonna be relational so better pay that debt upfront. Don't even consider NoSQL this early; we're paying a heavy price on my current job because the initial developers bought that non-relational databases were be…
At least briefly consider whether or not you actually need a relational database when starting a project. I work with some rather complex data access using Postgres, JPA, Hibernate, HikariCP, and a second level cache, all within a separate microservice exposed via a REST API. To make matters worse, the responsible developer has since left the project to me. We don't even use relations, so this essentially means that…
Re: Ask HN: Go-to web stack today?
#260Storage: Postgresql Backend: Go (no framework, just the standard library) Frontend: Vue Working great so far. A little longer to get things up than using Rails/Django, but the extra speed and control is really nice. Using Go's templating engine to assemble Vue components into HTML tags works well.
What are you using for SSR? I haven't yet seen any concrete tutorials for getting this up and running with Vue and Go. All I've been able to google is augustoroman/V8 and dop251/jago and other derivatives.