Slashdot Mirror

← Back to Stories (view on slashdot.org)

Web Apps Language Opa Gets a Web-Based IDE

Posted by timothy on from the made-easy dept.

First time accepted submitter koper writes "The new programming language Opa makes web programming easier by providing a one-tier one-language-for-everything approach. Now it goes one step further by providing a (very-minimalistic for now) web-based IDE that allows users to compile & deploy Opa programs in one click in your web browser. Give it a spin!"

7 of 83 comments (clear)

  1. XSS scripting issues by networkz · · Score: 3, Insightful

    Neat, but that site wont work with NoScript installed unless you allow XSS.

    Not a huge problem for some, but is a deal breaker for me.

    unless there's a workaround?

    1. Re:XSS scripting issues by ThurstonMoore · · Score: 3, Funny

      Workaround, disable no-script.

    2. Re:XSS scripting issues by dkf · · Score: 2

      Fix NoScript then... since its obviously broken.

      Or add proxying to your local server for the JS content that would otherwise come from another server. Or use something else that doesn't insist on using unsafe security practices. How hard could it be?

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
  2. Re:Nice writeup by buchner.johannes · · Score: 2

    If 90% of all web apps are the same, a language (or in case of Opa, it should probably be called a web application build system) can be the magic bullet for 80%.

    --
    NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
  3. Not True with GWT by koestrizer · · Score: 2

    Google Web Toolkit allows you to create nice web client applications without any significant knowledge of HTML or CSS. Instead, you have to know the GWT Java classes (not JavaScript; it gets translated into that automagically). I used it in a real project and had to deal with CSS only to make it "nice to see".

  4. Why must every new platform have it's own server? by cshark · · Score: 2

    Okay, so this is the sixth new platform I've reviewed in the last year that has its own built in web server. Why? It's a complete pain in the ass to manage platforms that are built this way. Most of the time, the servers they come with are not as good for general purpose use as Apache, and well, because they require their own servers... you can't really run them on a traditional server if you wanted to. Now, I understand the need and desire to change the paradigm. I've been there. I've tried to do it. But the web server paradigm EVERYONE ELSE USES is not broken. Why the hell is everyone trying to replace it with something that is untested, that doesn't work as well? Why can't someone design a precise, straight forward language that plugs into my web server, which allows me to scale and thread properly to billions of connections? I'm not asking for a lot. Other than I'm asking for a lot. Apparently.

    --

    This signature has Super Cow Powers

  5. Re:Why must every new platform have it's own serve by Riskable · · Score: 2

    We had what you prefer for like a decade now and you know what? It sucks. Like PHP is somehow the the pinnacle of how application development should be. Hah!

    Not to mention the fact that managing Apache httpd or Nginx with generic language "plugins" is about as intuitive as tying your shoes using a robotic atm controlled by a BlackBerry.

    Also, please tell me how this model of development "doesn't work well?" If it doesn't work well no one will use it. Problem solved!

    Why don't you take a break from this old school, all-problems-have-been-solved web of yours and go tell some kids to get off your lawn.

    --
    -Riskable
    "Those who choose proprietary software will pay for their decision!"