Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
What issues or gotchas will I run into if I develop web applications in Lua; is there anything I should be aware of before starting?
Any experience with developing Lua web applications?
The web application framework based on Lua that gets a lot of discussion in the Lua community is the Kepler project. The Kepler team provides integration with web servers (especially Apache), a web server of their own, useful modules, and a working MVC application framework called Orbit.
Several other projects work with or on top of Kepler's foundation. A prominent one that demonstrates that Kepler can be used for real work is Sputnik, a very flexible and extensible CMS that functions as a Wiki out of the box but which can be extended to do many other things.
Speaking from personal experience, I built a control interface for an embedded system using Kepler's Lua Pages to render and process the forms and reports without much hassle as only my second or third real Lua project. That system is still in use and I would do it again.
take a look at http://openresty.com/ (nginx and lua/luajit, async)
Go ahead and give it a shot! Lua is a very nice language.
Another MVC framework based on Lua is also Luci.
Interesting concept. I think one of the things you need to consider is which webserver do you plan to use? I think the webserver support for Lua would be flaky at best, no offense to anyone involved but its just not a common web platform.
With that said, however, the Lua Libraries And Bindings lists quite a few components that you could seemingly leverage for your efforts. I looked the list over and all things common to the web are there: databases, regex, network, zip, crypto, xml, images, etc. There's even a couple of web frameworks, so perhaps this is less rare than I thought?
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
When I was googling, I just saw that there are a number of software frameworks present. Like this,
ASP.NET - MonoRail
Java - Google Web Toolkit
JavaScript - Backbone.js
php - CakePHP
Python - Django
Ruby - Ruby on Rails
So my quection is this.
Why we use frameworks and why we spent time to learning frameworks instead of learning more advanced techniques of the programming language?
Are there any disadvantage of using a framework? (specially reduction of speed when using server-side or client-side frameworks)
So frameworks are really just collections of functions and libraries pieced together to make it easier to perform a particular tasks.
In the case of your question, you're looking primarily at web frameworks. Which make it easier to write web servers in these languages. Python Django is a great framework because it handles all of the web stuff for you. (http requests and traffic routing) and allows you to simply specify what code will run when your app takes certain requests.
So in short, frameworks try make it easier to do certain things. Of course different people think different ways to do things are easier, so that's why we have so many different kinds of frameworks.
Feel free to ask any questions. Hope this helps!
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I'm new to Nix and quite excited about it (I've been using it so far for Haskell).
I'm planning to use it to deploy Php applications. However, how Nix deals with
Php packages (installed normally or with pear).
Working with PHP webapps generally requires several running services (php-fpm, httpd, mysqld, redis, etc). The answer depends on how you manage the services -- which, in turn, depends on whether you use:
(a) The full NixOS: NixOS provides a service-management layer - you edit a config file, twiddle some flags, and turn on the services. I haven't done this myself, and I think it needs a more pointed tutorial for folks coming from a PHP webdev background, but the system does exist.
(b) The crossplatform nix/nixpkgs: There does not appear to be a canonical service-management option here. nix basically just gives some binaries (php-fpm, mysqld, etc) which you can launch yourself. It's somewhat daunting for typical PHP developer.
Full disclosure: To try to improve the situation for crossplatform nix+PHP, I've written an example project locolamp. It won't help much with learning NixOS, but it may help get your toes wet with nix+php in cross-platform usage. See:
https://github.com/totten/locolamp
After spending a week trying to configure a LAMP platform and giving up (mainly because I couldn't make PHP send emails), I concluded that Nix is not ready for developping easily PHP application in production.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Xamarin is great in theory but would it be a good fit for a small team with .Net experience that is looking to build a consumer facing (not LOB) app for Android, iOS & Windows Mobile. This is not a build and forget scenario. The app would be under continuous development, and deployment via the three app stores.
Xamarin seems better suited for a large enterprise with many resources and a pool of .Net developers. I am looking for feedback from those who have actually invested time and money going the Xamarin route.
Although I feel a small .Net team could be more productive in the short term with Xamarin, I have the following reservations that have not vanished through experimenting with Xamarin or through reading countless docs, articles and comments.
Hitting hard roadblocks after investing months on development and finding it very difficult to get the help needed to work through the issues. i.e small online community and expensive training and support options.
Xamarin being unable to do something that can be done natively.
Investing in Xamarin at the cost of not actually learning objective C (Java not a real concern).
This is similar to the many of opinionated questions about Xamarin vs full native. If you have no obj-c/java developers and only .net developers, then go xamarin. If you want a single code base and not have each app in a different language, go xamarin. They are pretty darn good at having support the day that iOS is released.
Search on here for all of the other questions about it to see peoples' pros and cons lists.
I have gone through Xamarin route and I do development on C# for many years. I do Java and learned Objective-C to develop on iOS. Right now I do it alone or at most with some friends , so it is like the small team scenario you described.
I would not go on any other route for some reasons:
Needing to deploy on more than one platform and do each one on a different language is something I dislike
Xamarin exposes all the native APIs on each platform, so I am at no loss
I can access third party native libraries on each platform with ease
The non-native issue is not a issue for me for the byte-codes are native on iOS and there is a small Runtime on Android, but on both cases the performance is not at loss
I have done some basic and intermediary stuff using Xamarin and there were no lack of support from the community, documentation or from Xamarin
I am not getting to be an expert on Objective-C, as I don't develop using it, but I am learning the native APIs and their use the same way. You will use all the same Objects, methods (protocols and delegates) you would with Objective-C but now you have a different syntax (one which I love by the way)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am completely new to writing code and am slightly confused by all the different languages. My main goal is to build websites and apps for iOS/OSX.
Which coding languages should I start with?
Here is a previously asked question which may be of use to you.
If you find that it is a bit over your head, you could start by learning the basics of HTML/CSS/JavaScript at W3Schools or by learning broadly applicable programming skills at Codecademy.
For iOS/OSX it would be a good idea to learn Objective C and get familiar with the different frameworks provided by Apple.
For building web sites, all you need is a text editor and a good introduction to HTML/CSS. If the web site should be dynamic (i.e. some content should be created when the web site is retrieved) PHP might be easy to learn and some JavaScript knowledge couldn't hurt.
Please note that applications are different from web sites! You can build web sites that look like applications and are accessed through the browser - "native" applications can only run on the device, not through a browser.
So there's no such thing as "web sites for iOS/OSX".
My main goal is to build websites and apps for iOS/OSX.
You need to define if you want to go native (objective-c + Cocoa/Cocoa-touch) or websites (HTML + JS + CSS). Which one you would choose is kind of a tricky question on the current standards. It really depends of the project and the client (sometimes even them don't know what they really want). If you are able tell us what are your goals in learning them, I can try to advise you better.
I would start with basic c because its what everything is built on. it teaches you the basic like int's, variables, pointers ect., then you could move into object oriented programing
(for other languages as well as ios/mac osx programing)
or move straight into objective c. if you want to design and build mac os x apps you need to know c, objective c, then move into the newly announced "swift" apple released this summer, they are all object oriented.
if you want to build web applications like facebook, twitter, google, ect. then i suggest php and mysqli (mysql is discontinued). you can implement a lot more than you think. you can also do object oriented in mysqli and php but you can also do it "procedural style".
be aware that ios/mac osx is a lot harder that html, css, php, and mysql.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I was wondering what are the strengths and weakness of using Ruby on Rails for Web Application development. I would like an insight from other developers as to why they have chosen to write in Ruby on Rails over other languages and technologies.
What does Ruby on Rails provide that has the edge over other web application technologies and languages?
Are there any unique capabilities that the language provides?
Thanks in advance, hopefully I will be able to make the choice as to use the language or not.
Ruby on Rails is a server side technology, it cannot be compared to Flash or Silverlight that are client side technologies, like apples and bananas.
EDIT (for the edited question)
Rails's main strength over other server side tech's is ease of use and development speed. This comes from 2 factors:
ruby is a expressive and easy language
rails provides a simple yet powerful API (call it "programmer interface") that lets you focus on "doing your stuff" rather than "how to do it"
You write less code and don't struggle with side problems.
I'd add a great mature community and plethora of plugins and ready-made code.
Ease of learning and speedy development are big pluses
It runs pretty slow though (compared to, say, ASP.net)
Faster development, slower runtime
I think, Ruby on Rails' strength is a community.
There are a lot of people to ask about framework.
Also there are many books, libs, plugins, etc.
No matter which technology or framework you will choose,
just do not limit yourself with it.
Disadvantage is that many of the folks building larger apps have continued to work with C#/Java/PHP; there's not a lot of huge apps running on Ruby.
From my understanding - it runs slightly slower than the big three up there - large apps are staying where they were.