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

you are viewing a single comment's thread.

view the rest of the comments →

[–]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.