I have to be careful to not to start a language war…
I’d say these web sites are the people use on a daily basis.
Discourse power user
Software developer are picky.
Discourse can work like a mailing list.
If someone like, he can create a command line interface based on API which is used by our Ember program.
However, if you want to migrate to Discourse, you will still have to take migration cost into consideration. You may want to convince the community why Discourse features are good for them.
BTW, as a open source program, all assets can be served from your host.
It isn’t really a question of using it “instead of PHP” (or Ruby, or Python, or Go etc.), since it’s frequently used in combination with such a back-end language, with the exception being Node.js applications.
[quote=“elect86, post:1, topic:26651”]
Also, what kind of person puts “the web” in quotes?
I kind of get it, web today is a very generic word, so he may have his reasons…
Anyway, with my thread I wanted to see if I could find some common ground and constructive partecipation, so I would beg you guys to avoid any polemic, since this is not my goal and I guess nobody will benefit from it.
I truly believe instead the adoption of the Discourse platform for the Jogl community can brings advantages to both the parties, to the community for having a better media to communicate and to Discorse, for having the jogl in the reference list and spreading its software.
The backend, the portion of Discourse that’s running on the webserver, is written in Ruby, is based on the Ruby on Rails framework, and stores its data in a PostgreSQL database. It is isolated from other services and version dependencies, runs as an unprivileged user, and easily supports horizontal scaling over dozens of nodes.
(The only exception is the markdown to HTML converter which is executed on the server in an embedded JS engine when new posts are created or old ones need to be rebaked.)
An additional, very important point that is worth considering.
We have seen time and time again that some users have the attitude that “I am fine to use this new software as long as it acts 100% like the old software I was using before”. They are in for a surprise and you are bound to always lose a handful of die hard “my cheese may never move” users.
We try hard to accommodate for a large amount of use cases and users, but if you have philosophical objections to the existence of our product and desire a product that works exactly like your old produce there is no appeasing you.
FastBoot will allow you to deliver the HTML and CSS for a page in
it has finished loading. Your Ember app will behave no differently than
server-rendered apps when it comes to search engines, mobile users,
For everyone else, you’ll still have the responsiveness and interactivity users have come to expect from Ember apps.
I dunno how easy that would be to enable for an Ember app served by Rails, but getting the ability to fall back on server-side rendering for free (maybe?) seems pretty neat.
There are always reasons to hate on every programming language and every platform and every application. I remember when lots of people were hating on Java as a ridiculous fad and everybody should use straight C because it’s so much faster and doesn’t waste operations.
At the end of the day, none of that stuff matters. The only thing that does matter is whether the solution works for what people need it for.
Once Discourse becomes mainstream they will come around.
On a side note, about 99% of the time somebody asks me for help because some website isn’t working it’s because they were running NoScript. They should rename it “Break the Web”.
That said, I recommended Discourse anyway and usually find it to my taste. I hope the email participation feature can solve most of the issues for web-2.0-allergic people, although it challenges the meaning of “private” conversation once it transits through the NSA^W Internet tubes.
I use Firefox, and will stick with it because it allows me to zoom text only, which is an important accessibility feature for me. I don’t have any problems with it, except on Discourse sites which tend to load slowly at times - especially if I have my daily backup running. (But then, Chromium freezes altogether, so FF is actually the better option.)
Add to that mix bad code leaking memory or calling 20 third parties (wtf?), and browsing the Web becomes a very annoying experience. So, I prefer spending my time otherwise. The Web 2.0 is such a tiny part of the Internet .
That they also use it on your website is the actual concern.