midrus

7 ms·

31.
by midrus 5y ago
I find Laravel (with something like livewire or Unpoly) quite easy, well documented and battle tested. Of everything I've tried in my life this is the best "one man army" stack I've seen.
32.
by midrus 5y ago
The trick is to be able to route users traffic to different deployments. You can run two versions of your application concurrently, and have a dial to progressively shift traffic to the new version, as soon as you notice anything wrong you
33.
by midrus 5y ago
See my other comment [1], it might be hell because you're missing the right tooling. With the right tooling, it's heaven actually. [1] https://news.ycombinator.com/reply?id=30900066&goto=item%3Fi...
34.
by midrus 5y ago
> If you truly want to get rid of your a staging environment the minimum that you need to feature flagging of _everything_, and I do mean everything. That is honestly near impossible. You also need live preview environments for each PR&#
35.
by midrus 5y ago
And yes, you need blue/green deployments in addition to feature flags, as it is not easy to feature flag certain things, such as a language runtime version update or a third party library upgrade, among many other things.
36.
by midrus 5y ago
Good monitoring, logs, metrics, feature flagging (allowing for opening a branch of code for a % of users), blue/green deployment (allowing a release to handle a % of the user's traffic) and good tooling for quick builds/relea
37.
by midrus 5y ago
You're probably not the target market. Not everyone knows how to setup a server by themselves and run a blog and keep backups and keep it running and update it, etc..
38.
by midrus 5y ago
I've worked both on large Vue and react projects. Wouldn't pick myself Vue ever if I have the choice. Vue is certainly easier to learn, and comes with a lot of oficial libraries such as vuex, Vue router etc. But that's all ab
39.
by midrus 5y ago
>As a user of service I want guarantee that my data will be processed as per my requirement and then it will be left alone. This is totally orthogonal to self hosting. You can ask for a service to be operated for you and also ask for you
40.
by midrus 5y ago
In my opinion, what makes a "language" the best for webdev is not its syntax. It is the ecosystem, the libraries, the amount of people that know it, the learning curve, the editor plugins available, the frameworks, etc. Ocaml? Elm
41.
by midrus 5y ago
As a user of a service, unless it is for learning or paranoia reasons it makes no sense to try to self host the same it doesn't make sense to have your own mechanic workshop in case your car breaks or your own hospital in case you need
42.
by midrus 5y ago
So much underestimation here regarding what it takes to have reliable, secure and resilient self hosted services. I've seen far too many disasters because somebody thought it was just easier/cheaper to self host.
43.
by midrus 5y ago
Any runtime that has the concept of "thread locals" or "thread safety" have this sharing problem, no need to exploit y anything. Of those you mention I've worked with Python and java and their runtimes do have this
44.
by midrus 5y ago
Honestly, I can't care less about "languages". To me they're just syntax. And for all the kind of web applications I've built, the performance has never been a big concern over other stuff such as building features,
45.
by midrus 5y ago
I think the opposite side of the spectrum in the sense we're talking about "stateless" here would be something like node.js, or Go, where a single "process" is kept alive at all times and responding to every request
46.
by midrus 5y ago
Thanks for this. Helped me a lot to calm down a bit.
47.
by midrus 5y ago
> "rerender previous form pages over and over again, except hidden" There are modern ways to do this, see Unpoly, HTMX, livewire, hotwire, etc. You're comparing with an outdated view of what an MVC application looks like.
48.
by midrus 5y ago
*figma, not dogma. Autocorrect messed up and just noticed.
49.
by midrus 5y ago
This works great as long as it is not a first visitor though. For new visitors with a spotty connection this will be a nightmare. Also I assume any new update you release which might need to refresh the cache would also be a problem in this
50.
by midrus 5y ago
> done correctly Big assumption. This is what the whole discussion is about. Doing "correctly" an SPA is incredibly expensive. I can also assure you that when an MVC application is done correctly you can have an equally good
51.
by midrus 5y ago
> they work if your connection is flaky, Not saying it can't be done, but I haven't seen many SPAs that handles well flaky connections. Most stall with no indication to the end user, endless spinners or just broken in some rand
52.
by midrus 5y ago
> Put the user first, consider the trade-offs that work towards that goal, and see what shakes out. In my experience, every single team I've been part of that was building an SPA was because they put the developer experience and des
53.
by midrus 5y ago
Then you can use Livewire, Unpoly, or HTMX. MVC doesn't mean 90s style reloads anymore.
54.
by midrus 5y ago
I'd say it is very practical for hiring, as you will need just 1 or 2 developers that knows JavaScript and (Rails|Laravel|etc..) for every 4 or 5 you'd need otherwise (some that know JS, some that know backend, and some to coordin
55.
by midrus 5y ago
You're describing an actual client side (mobile or desktop) application made with web technology, not a web application. That's a fair use of SPA tech. As soon as you need authentication, showing data across users, allowing visito
56.
by midrus 5y ago
The alternative to SPAs is not 90s pages reloads. Nowadays you have livewire, hotwire, unpoly, htmx and several other modern solutions.
57.
by midrus 5y ago
As an ex-member of a team who used react, redux, typescript, observables, epics, thunks, custom hoome-grown validation libraries, websockets and elixir deployed in two different microservices to build a... signup wizard... I can confirm thi
58.
by midrus 5y ago
Same experience here, in our case with Laravel. The project started as a Next.js SPA and after we needed to add authentication, translations and background jobs things became so crazy and so "custom" that we ditched it and in almo
59.
by midrus 5y ago
GraphQL is just another artificial solution to a problem created by SPAs themselves. Same as SSR, hydration, server components, client side routers, dynamic bundles loading, dynamic translations loading, etc, etc, etc. A whole industry of w
60.
by midrus 5y ago
> but most of the SPAs I have to use are garbage As an example, look at reddit. I'm still using old.reddit.com because I can't stand their fancy SPA UI. It is so bad to the point, as a user, I enjoy a lot more HN's interfa

More ›