midrus

31 ms·

271.
by midrus 5y ago
(My opinions) Compared to Hotwire: I think hotwire is the best option if you're using Rails. From what I know, hotwire needs a lot more of backend "collaboration" than Unpoly, so you will need backend "hotwire" impl
272.
by midrus 5y ago
You already have that: JavaScript. Otherwise, what you are describing isn't going to be "Just Go" or "Just the language"... you'll have again a ton of libraries/frameworks on top of it... the complexity is
273.
by midrus 5y ago
For anyone wanting a "SPA" like feeling of their apps without having to deal with all the SPA complexity, and not starting from scratch or being able to rewrite their applications, try Unpoly. It is really great and very underrate
274.
by midrus 5y ago
No
275.
by midrus 5y ago
Both are safe options job wise. With python/Django it is going to be easier to land a backend position, where you will be using Django mostly for building APIS and interacting with databases and third party systems and it will be less
276.
by midrus 5y ago
There are many things that the python ecosystem does better than the node ecosystem, but pip isn't one of them. Pip (and Python package management in general) is just terrible and definitely one of the worst compared to all other ecosy
277.
by midrus 5y ago
> And having encountered something missing yet when writing Go web services How do you do form validations, translations, database access, migrations, email sending, background jobs that don't die on a deployment, user authenticatio
278.
by midrus 5y ago
I've not even mentioned Ruby. Rails. Features of rails.This is exactly the problem...people focus so much on the language they forget the ecosystem they're in, and the ecosystems matters a lot more than the syntax or the performan
279.
by midrus 5y ago
The Go hype is as bad as the frontend hype in my opinion. If you're replacing Django with Go then either you never needed Django, or you have no idea what you're getting into. At a previous job backend team decided to replace rail
280.
by midrus 5y ago
Also, pair it with Unpoly, tailwind and slippers and you get a pretty amazing frontend setup as well. https://unpoly.com/ https://mitchel.me/slippers/
281.
by midrus 5y ago
Yes, maybe in 10 years when this Go framework catches up with all the features and becomes as battle proven, well documented, maintained and funded as Django and somehow we know is not yet another thing that will be abandoned next year.
282.
by midrus 5y ago
But then how do I do microservices in a monorepo based SPA server rendered running on kubernetes?
283.
by midrus 5y ago
Or just use Django
284.
by midrus 5y ago
I can't speak much about Rails, as I've only played with it. But I've used a lot Django in the past. Regarding the Django admin (in rails you have ActiveAdmin[1]) think of it just as a glorified database explorer. It is an
285.
by midrus 5y ago
When you reach Google level scale and income. So, never.
286.
by midrus 5y ago
Sure, and rewriting everything is easy and a piece of cake too
287.
by midrus 5y ago
"...TypeScript/React/Redux Saga on the frontend..." This plus RxJS + websockets + in-house validation libraries + ... was the stack of my last company. For doing F**ng CRUD forms. This was one of the main reasons why I
288.
by midrus 5y ago
Same here, except I didn't go back to that extreme. There is a wonderful underrated middleground which is using tools such as Django + Unpoly[1] + Slippers[2] + Tailwind, or Rails + view_components + hotwire + Tailwind, etc.... you can
289.
by midrus 5y ago
I have a probably very dumb question. If speed is relative, when we say something travels at... I don't know... 50% the speed of light, that speed is relative to what? how do you know it is 50% and not 53%? How do we know we're no
290.
by midrus 5y ago
The problem with these low level frameworks is that you end up with a lot of bug and security issues you don't even know you have. I mean, for learning purposes....go ahead. I'll never use it for any production web application whi
291.
by midrus 5y ago
So... No microservices SPAs with noSQL database on top of kubernetes in a monorepo? So disappointing.
292.
by midrus 5y ago
No, thanks. Monorepos might be good for Google or Facebook where you have company-size teams to maintain all the tooling around them and there is no risk of "the guy that did all the tooling left and now we don't know how this wor
293.
by midrus 5y ago
My next phone was going to be an iphone because I'm tired of all the Google tracking (and Android itself). But now I'm holding up my purchase until they release (or hopefully abort it). I'm happy to pay more for a robust and
294.
by midrus 5y ago
Can't agree more with you. I've seen people trying to write web applications and web services with Go going crazy reinventing the wheel (hand written validations, shell scripts for migrations, raw sql because "who needs ORMs,
295.
by midrus 5y ago
I was going to buy an iPhone before they announced this, because I'm tired of all the Google tracking stuff. If they finally roll this out, I think my next phone will be a Nokia 1100. I don't have anything to hide, but I'm ti
296.
by midrus 5y ago
Ahhhh...The React Experience right there
297.
by midrus 5y ago
Add it to the pile on the back.
298.
by midrus 5y ago
Because I have work to do
299.
by midrus 5y ago
Agree. I've also tried Jinja macros and despite I was satisfied with that, it feels a lot like you're moving away from the core of dj ago. Suddenly translations don't work.and you need other solutions, templatetags don't
300.
by midrus 5y ago
I'm actually a frontend dev full time at my day job, and still think this approach is better for 90% of the things we do with react. The big drawback is that it requires using python and knowing more about backend and most frontend dev

More ›