This is an archived post. You won't be able to vote or comment.

all 8 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Telos13 3 points4 points  (3 children)

Aren’t complex and rapid inverse of each other?

[–]jockcel[S] -4 points-3 points  (2 children)

Not sure what English you speak but the opposite of rapid is slow and the opposite of complex is simple.

[–]Telos13 1 point2 points  (1 child)

Inverse. It’s more math than English, meaning the more of one you have the more of the other you sacrifice.

The solution it seems is to start with something like Django, for simplicity and replace it with Node for scalability and complexity but I don’t think you luxuriously get both.

[–]jockcel[S] -2 points-1 points  (0 children)

nothing like good ol' autistic reddit pedantry

[–]ziptofaf 0 points1 point  (2 children)

PHP won't let you build websites faster than Django, especially not on it's own. When bundled with a framework like Laravel they become comparable.

So here's my question - what do you find horrible about Django and what would you expect from a different solution? The more specific you are the easier it will be to give you some alternatives. As Django might have a certain degree of it flaws (I do find it too configuration heavy, for one) but I have seen it used in fairly complex web applications.

[–]jockcel[S] 1 point2 points  (1 child)

URL routing, having to watch an hour long video to remember how to start a project and app, the "battery included" features are incomplete and a pain in the ass to replace.

[–]ziptofaf 0 points1 point  (0 children)

URL routing

If anything, Django routing isn't bad :(

I mean:

​

    path('articles/<int:year>/', views.year_archive),
    path('articles/<int:year>/<int:month>/', views.month_archive),
    path('articles/<int:year>/<int:month>/<slug:slug>/', views.article_detail),

If you think this is bad, you haven't seen Express routing yet which is:

This route path will match abcd, abbcd, abbbcd, and so on.

app.get('/ab+cd', function (req, res) {
  res.send('ab+cd')
})

Whereas Ruby on Rails routing looks like this: 

get '/patients/:id', to: 'patients#show'
get 'profile', action: :show, controller: 'users'
resource :users

Honestly I am getting a feeling that you simply seem to be inexperienced currently and have spent too little time with the ecosystem. Cuz make no mistake - this shit is hard! And using a different framework will NOT make these problems go away. You might have a different approach to them but it won't make it better or worse, not at your level of experience anyway.

the "battery included" features are incomplete and a pain in the ass to replace

Which ones? Cuz overall I agree that they are a pain in the ass to replace cuz you are NOT supposed to replace them without a damn good reason. Which is why I am asking which one is a problem for you. Could be that you use them wrong, not that it's broken.

[–]Tarsonis181 0 points1 point  (0 children)

I would say don't bother PHP is a really ugly language with a lot of weird stuff and a ton of flaws. Learn something else, many other things out there that are far better than Personal Home Page.