91–100 of 122 posts
DB: Maria. again, familiarity is key. been using MySQL for almost 20 years and it does what I expect.
UI: nothing fancy. bootstrap and, if the use case absolutely requires it, jquery. have been going back to fairly js-light designs lately and clients seem happy for it.
Earlier quoted context omitted.
Do you self-host them in Linux? Or are you using something like nginx reverse proxy?
We use nginx as a reverse proxy. It was a little bit of a pain to set up with all the SSL stuff at first, especially since we wanted to keep hosting some Wordpress blogs on URLs nested within the .NET infrastructure, but overall it's worked out well now that it's up and running. Each site gets its own dotnet instance, and for a while I was even running them all within a screen session. It was kinda neat to be able to…
I've tried different JavaScript frameworks. I've seen Backbone, Angular, Knockout, Rx.js, React, Redux, MobX, Rails, Asp.net, Meteor and Django, I've tried almost every popular option to compile/transpile into JS - Coffeescript, Typescript, Livescript, Gorillascript, Fay, Haste, Elm, GHCJS and Babel. I've used Grunt, Gulp, Browserify and Webpack. Nothing ever made me so happy and so excited as Clojurescript. Things a…
could you please point me towards some good resources to get started with clojurescript?
Earlier quoted context omitted.
I've always been curious as to how you structure your models in Django. I'm building a personal project in Tornado and MongoExpress, and the only thing I can see about structuring my models is to put all of them in one file called models.py I'm used to the RoR way of doing things, so this seems very counter-intuitive to me. In addition, whenever I try to break the classes into different files, I'm not sure of where t…
You can make `models` a package, where `models/__init__.py` just imports models from the package's modules (`models/thingamabobs.py` and ` from .thingamabobs import Thingamabob`). Also, you shouldn't need to worry about database connection logic in Django unless you're doing something very specific.
The problem with Tornado is that it doesn't come with an in-built ORM like Django, which means I need to actually create a connection to the Mongo instance I'm using. Hence the confusion. Python doesn't have initializers like Ruby does (that I know of).
It depends on the use case: - For API based work, I love Flask (Python). - For full fledged application, I am loving Laravel (PHP). With PHP7 and package managers such as composer and the awesome laracasts tutorials, it is just a breeze.
Meteor - It's a fullstack framework that let's you write JavaScript both on the front- and backend. It let's you choose what you want to use for your frontend (e. g. React, Vue, Blaze, Angular...). Best feature: It's realtimeness. And right now I'm trying Laravel (PHP). It has a great documentation. I like the ORM and that it's easy to use. I want to build an API with it and consume it with a SPA and react.
Is using Javascript on the back end really a positive thing? There isn't really a choice on the front end.
There are plenty of better solutions like PHP, Ruby or Perl.
Django. I like the "batteries included" aspect. Flask and Sinatra are fun, but I wind up spending more time than I'd like stitching authentication etc together instead of building the project.
I've been using it for over a year, and it is fantastic. In fact, I've just started my own personal fork to streamline some things to my dev process.
Anyway, one of the many nice freebies is a full user registration / password reset / oauth solution baked in.
Also, I should mention this is created my the same guy who wrote "Two Scoops of Django".
Earlier quoted context omitted.
Is using Javascript on the back end really a positive thing? There isn't really a choice on the front end.
This is the main criticism of Javascript on the backend. People didn't have choice on the frontend (and largely still don't unless you transpile), and for some reason people thought it was a good idea to bring this "language of necessity" to the backend. There are plenty of better solutions like PHP, Ruby or Perl.
For us not-so-smart-people who liked MS Access: PHPRunner. From a programming standpoint, it's the worst thing in the world: A Windows GUI thing that builds PHP apps and it's closed source. From a get-stuff-done standpoint: I made a tracking web-app for large expensive tools that knows about Customers, Project Locations, Scheduling, Work Orders and Invoicing - it will grab a customer signature and email them the rece…
Django. I like the "batteries included" aspect. Flask and Sinatra are fun, but I wind up spending more time than I'd like stitching authentication etc together instead of building the project.
You might want to look At cookiecutter Django [1], which is an excellent boilerplate generator for production-ready Django apps. I've been using it for over a year, and it is fantastic. In fact, I've just started my own personal fork to streamline some things to my dev process. Anyway, one of the many nice freebies is a full user registration / password reset / oauth solution baked in. Also, I should mention this is…