381–390 of 453 posts
Scala for backend and Scala.js for front end. Use terms SPA and SSR like the cool kids do. Only you can share the same code between the two and in a strong statically typed way.
I know that its not good form to ask the reason for Downcoting but boy do web boys get Triggered by the smallest of things.
Although modern frameworks & SPA are really fancy and feel great, there mostly comes a point in a project where " client needs X" and i feel that keeping tech oldschool and using a very widely used ecosystem as a CMS base earns me the most flexibility over the sites lifetime.
It's bloat and overkill for small sites, but it gets the job done just as quickly as other systems. And on larger or more complex sites it provides all I'll need without the need to "custom build it" everytime.
(Disclaimer: I'm talking "websites" here, not specific-purpose web applications where this workflow would be a horrendous workaround)
Earlier quoted context omitted.
Also - using WebSockets for a one-way communication channel is ridiculous. I know it's the cool kid way to do things, but that invariably means it's over hyped and has a more appropriate alternative. In this case, it's EventSource/Server Sent Events. I have some sympathy for your view here, but there are some other practical concerns as well in this case. For example, EventSource/SSE are not natively supported on IE/…
Right, except eventsource is pretty simple to pollyfill because it’s just http. Websockets requires explicit support on the backend, in every layer of your http stack that it’ll traverse. If the goal is to simplify your stack, websockets is not the solution.
Earlier quoted context omitted.
I'd say that Django is not a great fit for lambda. Lambda works best when you architect you code around it, with lots of tiny methods. Django does not encourage this way of coding (just like the other frameworks).
> Lambda works best when you architect you code around it, with lots of tiny methods as a total hobbyist: why ? deploying a django app with zappa is extremely painless... its only issue is that you still need an SQL backend, as DynamoDB isn't really an option unless you want to kiss most of djangos values goodbye. that would've been my take why you'd want to use flask... because there is very little value in django i…
When your app is small and you got almost no users, zappa is great: your lambdas are lighting fast and you're in aws free tier.
When your app grows to like 200k SLOC and 50+ lines in requirements, chances are that it starts quite slow. Do you really want to pay for that?
When your load is high enough, well, aws lambdas become quite expensive even without zappa overhead compared to, say, EC2. https://servers.lol/ should say if serverless makes sense for any defined usecase.
Additionally, lambdas have hard restrictions (like 15 minutes limit) and sometimes it's a dealbreaker for you.
Earlier quoted context omitted.
Just looked at stimulus. Really cool framework. circa 2008 or so there was this concept of non-intrusive javascript where you bind js to elements. So you could wysiwyg html and then inject js where you need it. Thought that was a neat idea and like what stimulus does it. Any real life experience from anyone ?
Yes, I'm using it in the budgeting webapp that I develop and here's one little component that I shared, a calculator for input boxes https://tomk32.de/2018/08/04/stimulus-component-calculator.h... Really should add a gif or something.
If your experience is mainly in Python ecosystem Django is just hard to beat. If it's Java based then things are more complicated I think - these days I have been avoiding heavyweight back ends and using minimalist stacks of which Micronaut [1] is my favorite. I use it with Groovy (though it supports Java / Kotlin), Postgresql as database and combine it with VueJS on the front end for a very agile but highly performa…
As someone coming to modern Java from the Python world, I've been pretty happy with Spark (no, not that Spark - it could really do with a more unique name): http://sparkjava.com . It's very simple, doesn't require any of the Spring madness, and looks a lot like Flask in its minimalistic approach. It has a (pretty rough) Kotlin version. I've also dabbled with Ninja ( http://www.ninjaframework.org ) but that was ultima…
Front end: Typescript, Vue, Bootstrap Backend: Node, Typescript, Express, TypeORM, Postgres, SocketIO, PugJS, BabylonJS Webpack for bundling Digital Ocean or Azure for Ubuntu vm hosting I feel having the same language for front/back end really reduces mental overhead.
Try parcel for bundling. It's basically zero config and fast.
Earlier quoted context omitted.
The biggest benefit of Vue isn't necessarily Vue itself, it's Vuex. Contrary to React, you do use the store from the start because it makes things simpler.
We are moving away from Vuex and more and more towards Apollo.
That's the amazing thing about Vue: it's utterly void of opinions (apart from components). The ecosystem of stores (there's also the functional one) is testament to Vue achieving elegance through simplicity.
- 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…
We've been following this stalk for quite a while and are super happy with it. But there's huge downside: It's really hard to find Django/ Python engineers - let alone phoenix devs. Right now I'm considering a move to JVM. But the frameworks i've seen are all far behind Django. Any thoughts?