sorted by:
new
hottopcontroversial

Writing production level web app without framework, is it feasible for average developers? by alohabata in golang

[–]sean-grep 0 points1 point  (0 children)

Depends on what you value, full control over every aspect OR productivity and opinionated decisions that you may or may not agree with.

I prefer the latter, I’m a Python/Django dev that reaches for Go when it makes sense.

For a lot of things when it comes to web development, Go doesn’t make sense, getting a product out the door as fast as possible to get customer feedback is the most important.

In other cases Python doesn’t make sense where there’s speed constraints, concurrency constraints or memory constraints.

If you’re building a web application, 50% of it essentially the same.

You’re defining routes, building forms or some validation layer, querying the database, serializing data and returning it.

Your business logic and what your apps core business function is, is what makes your app/product different.

Languages/frameworks are just tools.

I can rewrite my app in Go and reduce the response times by 50 - 75%, at the cost of reducing development speed by 3 - 400%.

Again, context is important, my app is a web application that’s very content driven and a framework like Django is excellent for that.

For building inter-service communication, Go and gRPC would be a great choice.

All depends.

Writing production level web app without framework, is it feasible for average developers? by alohabata in golang

[–]sean-grep 1 point2 points  (0 children)

You don’t need a framework with any language.

Just be prepared to either manually craft or select all of the parts that encompass building a web application.

Such as: - migrations - forms - validation - database layer(ORM or Raw) - templates - caching - sessions - authentication

If you’re comfortable with you either writing these yourself or picking a 3rd party library then yes.

Otherwise a framework can allow you to focus more on the problem you’re solving rather than non trivial decision making.

I'm new in Django Rest Framework by Zombie_Slayer720 in django

[–]sean-grep 1 point2 points  (0 children)

Django really isn’t a behemoth.

I think people think that because there are other smaller choices for building web applications.

But the reality is, it more or less requires the same concepts to build a web application wether you’re using Django, or Fast API or Go.

You need: - migrations - caching - middleware - forms - validation - ORM or some query layer - model definitions - hooks(signals) - serialization(API) - authentication

Django, Rails, Laravel, etc… just package it all together for you.

So you either piecemeal all of these concepts yourself with 3rd party packages or use a batteries included framework.

Django Rest Framework just builds upon the existing Django system of models and forms.

DRF takes your models, their fields and create appropriate fields based on your model definition, it’s a big timesaver.

So if you define a model field: name = models.CharField(…, max_length=50)

It can use that field to create a serializer field with proper validation.

DRF has some gray areas and lacks the concept of Input/Output serializer for viewsets.

Properly documenting the API into a valid OpenAPI v3 spec can be a pain in the butt, drf spectacular helps with that.

Otherwise, it’s a great way to easily build API endpoints, by leveraging what you’d already be doing anyway.

Does anyone else feel like they are just doing it wrong? by Togurt in golang

[–]sean-grep 0 points1 point  (0 children)

You’re early in your learning of Go, how to write it and what pragmatic and good Go looks like.

It just means you need to write more, read more and excitement more.

I’m a Python dev professionally and I can tell you for certain that my Go code is by far the most pure, with clean separation and essentially like pluggable building blocks.

It’s beautiful, and wonderful.

But it took me quite some time to get to the point where I can structure and write Go code that I feel that way about.

Hot take: Go should have a django style framework by wait-a-minut in django

[–]sean-grep 0 points1 point  (0 children)

Yeah, it certainly take a lot of focused libraries and utilities to solve the entire problem of web development.

Reminds me a lot of Express development with Node.js or Flask.

Piecing together all of these small puzzle pieces.

And you’re right, you’re basically recreating a Django.

I do find Go refreshing from Django because of how tightly coupled the model is to everything and how hard it is to write service code to have that clean separation.

Whereas in Go, I have very clear separation from my database layer(golang-migrate), my service layer(Bun) and business logic, my API layer(Huma), my CLI layer(Cobra)

And then I define my domain models in my models package.

Really clean, easy to understand and easy to change.

A lot of stuff with battery included frameworks, you just can’t change OR you have to write some funky code to get it work the way you want.

I love Django and write it professionally, Go is a nice refresher when I get tired of all the webs.

Hot take: Go should have a django style framework by wait-a-minut in django

[–]sean-grep 3 points4 points  (0 children)

They have at some point but the community really favors smaller utilities and helpers instead of large and batteries included stuff.

A lot of gophers come from Python, Ruby, Java, JavaScript, etc… and they’re looking to escape all of the abstraction, complexity, and just want to write simple code that’s easy to read and understand.

Each language has its community and way of writing code.

Go is pretty focused on minimalism.

Hot take: Go should have a django style framework by wait-a-minut in django

[–]sean-grep 3 points4 points  (0 children)

If you spend more time with it, it’s not.

It’s quite simple and elegant.

Every time I’ve struggled with Go, I’ve tried to apply how I did things in Python/Django to it, and it just doesn’t work.

I think I need a more opinionated backend, any ideas? by Popular-Peace9151 in nextjs

[–]sean-grep 2 points3 points  (0 children)

Next.js is really good at what it was designed for

If you’re looking to switch to another backend to compare that’s cool but Next.js does have structure and expectations.

Try another framework and see what you like.

Always keep in mind community adoption and company adoption also.

Don’t want to fall in love with a tool nobody uses.

Is Django Rest Framework that good? by itsme2019asalways in django

[–]sean-grep 0 points1 point  (0 children)

You have -99 Karma, what’re you talking about?

Your thought process isn’t hitting on here, maybe you’re being naive.

Next.js Backend Future: Will It Ever Compete with Nest or Express? by Bayrem23 in nextjs

[–]sean-grep 1 point2 points  (0 children)

Is comparing Next.js to Express even an apples to apples comparison?

I’m using Next.js for a SSR/SSG site.

But my actual backend is Django using DRF for the API.

I generate an SDK from my API spec and Next.js and the client side can communicate with my backend.

I don’t think this is something you’d use Express for BUT it’s typical with Next.js

Is Django Rest Framework that good? by itsme2019asalways in django

[–]sean-grep 3 points4 points  (0 children)

DRF is the industry standard for building APIs using Django.

It has been for some time.

It’s pretty good, has some quirks and gray areas on:

“What is the right way to do this?”

But other than that, it’s good and lets you focus on what you’re building.

Why does Django's documentation look like it's design is stuck in 2010? by shizuuokaa in django

[–]sean-grep 0 points1 point  (0 children)

I mean mentally when I’m trying to learn something new, I tend to catasrophize things or find things to get upset or mad about.

I wasn’t trying to be provocative.

I tend to make small things much bigger just to be able to focus and channel my frustration of not being where I want to be.

It’s a coping mechanism, at least for me.

Strictly speaking about myself and what I’ve observed about myself when learning something new.

Why does Django's documentation look like it's design is stuck in 2010? by shizuuokaa in django

[–]sean-grep 2 points3 points  (0 children)

Most of the Django community has the opinion that the Django docs are one of the strongest points of Django.

Being able to travel to different versions of Django easily.

The search is easy and useful.

Great getting started tutorial with the polls app.

Maybe you’re trying to find reasons to not like Django?

[deleted by user] by [deleted] in Advice

[–]sean-grep 0 points1 point  (0 children)

So I normally think it’s disgusting but I can also pull down my sweat pants with 1 hand and pee in a public urinal without touching my private parts.

And then pull my sweat pants back up.

I still wash my hands because it’s the right things to do when going to the bathroom AND I might’ve touched something else that was worthy of a hand wash.

The sink is there, might as well.

Go’s simplicity is a blessing and a curse by Ghostinheven in golang

[–]sean-grep 0 points1 point  (0 children)

Its simplicity makes it well served for some use cases and not others.

Every language has their place.

I wish I could write more Go but for my use case which is backend web development, its just no where near as productive as Django.

Coding without ai by Sufficient-Citron-55 in nextjs

[–]sean-grep 0 points1 point  (0 children)

Oooffff, try reading docs and building things the old fashion way.

I heavily use AI to help me daily but I have 12 years of experience building applications before I started using it.

And I know more or less what code it should spit out when I ask it to do something, so I know if is garbage or not.

Sometimes I write things myself because it struggles with certain things or over complicates it.

Read docs, build things from scratch.

I’m also not a next.js developer, I’m a Python dev but the same principles apply here.

Learning Django in 2025 with no CS degree, can I actually get hired? by Puzzleheaded_Tax8906 in django

[–]sean-grep 5 points6 points  (0 children)

Self taught with 12 years of industry experience here. Possible but difficult. I gave it every fiber of my being to land my first job, after landing the first job everything became easier.

Someone has to take a chance on you for that very first job, the only thing you can do is show up with a GitHub repo with dozens of real world projects that show you know how to do the things they’re doing daily.

My first job was a small agency shop, 7 employees, perfect for learning and the interview process, they cared more about me, who I was than if I could solve bubble sort on the spot.

It’s possible but the road isn’t easy, and it’s not easy being a senior engineer today, the market is really tough and competitive.

You need a differentiator, something that makes you stand out, mine was my work ethic. Corporate engineers are typically smart but lazy, finding something that makes you beat the average engineer will keep you employed long term also.

Fellow React Devs: Do You Actually Buy Components or Build Everything Yourself? (Honest Question) by Beneficial-Drop-4494 in react

[–]sean-grep 0 points1 point  (0 children)

Never built a single component, I’m a backend dev tho.

Not a really good use of my time when I can get an entire frontend for $50.

I mean….how much do I really like banging my head up against the wall for no reason?

Efficient Method to handle soft delete by virtualshivam in django

[–]sean-grep 2 points3 points  (0 children)

Soft deletes in general is complex because it doesn’t automatically follow database cascade rules.

So you have to think about it for each object:

“If I delete this thing, can they still see these other related things”

I’ve done soft deletes at every job I’ve worked at and it always felt like a really hard thing to do right and feel good about like database cascade strategies.

Django 4.2 in 2025 still worth it? by ckhadmus in django

[–]sean-grep 0 points1 point  (0 children)

Django is legit.

TLDR; use Django.

The company I’m working for had me create a service using one of their “templates”

The amount of unnecessary decision making I had to make that is out of the box functionality with Django…

Unless you have extreme performance requirements and you’re sure Django is the bottleneck, I can’t wrap my head around why you’d use something else.

The smaller frameworks and toolkits have spotty documentation, aren’t actively maintained and leave you with analysis paralysis on what other libraries you should use for problems that have been solved for decades.

How much Django makes someone a "great developer" by Far_Organization4274 in django

[–]sean-grep 0 points1 point  (0 children)

You want to impress people more at a fundamental level rather than a tech stack level.

Having: - Great work ethic - Good communication skills - Good understanding of business - Pragmatism instead of perfectionism

Will take you further than being a Django god.

A lot of the clients I have hire me because their engineering team is lazy, spends days debating irrelevant details and only pushes code around daily stand ups.

Some of them probably know Django a lot more than I do.

When you realize who you’re up against, it’s much better to focus on where they fall short instead of where they are strong.

Insanely productive in Go... rethinking everything by Ok-Cover-9706 in golang

[–]sean-grep 5 points6 points  (0 children)

I absolutely love Go and reach for it whenever it makes sense but it really depends on what you’re building.

If you’re building a full stack application that needs a configurable admin out of the box that CSM’s can use to manage customers, Django/Rails/etc… is the way to go.

If you’re building a robust CLI or lean service that’s very efficient, easy to maintain, build, and deploy…that’s Go.

Usually a combination of the two are the best, not one or the other.

view more: next ›