3 ms·

While I am generally very skeptical of half-assed reimplementations of existing tools with a stamp "now in the browser!!!", 280 was probably the first case when

by tx 18y ago

While I am generally very skeptical of half-assed reimplementations of existing tools with a stamp "now in the browser!!!", 280 was probably the first case when I said to myself "this is damn nice!" Very well done. So much different from the typical crappy and laggy "online app" experience I've seen before. And THANK YOU!!! for not using Flash.

dcurtis 18y ago
I agree. But not only are the technical problems with most rich applications fixed by 280 north, but the UI is beautiful, easy to use, and awesome as well.
jimbokun 18y ago
"And THANK YOU!!! for not using Flash." The whole "Objective-J" thing is fascinating. From this, looks like they have ported at least some of AppKit to compile into Javascript webapps: http://280slides.com/Editor/1212695713/DocumentController.j http://280slides.com/Editor/1212695713/DocumentController.j Looks like they have brought the Mac development experience to the web in a far more literal way than I expected.
zhyder 18y ago
I don't understand why Flash is so bad. The general concept of having a plugin with a rich built-in API makes sense for a lot of reasons (natively compiled code in the plugin, smaller download of additional code). The problems with Flash are: (i) it's proprietary, and (ii) it's not on 100% of browsers. (i) is mostly a complaint from developers based on principle, and (ii) -well- isn't true for Javascript either if you include mobile browsers. Disclaimer: my app is built on Flash. P.S.: 280slides is great! And very impressive this was done with JS.
- maximilian 18y ago
  Flash sucks balls if you have an older mac (1ghz). I don't know how it performs generally on an older pc, but for me, its just aweful. I hate anything online that uses flash.
  - tx 18y ago
    Flash sucks balls because it only works well where Adobe wants it to work well, as opposed to openly accepted standards like HTML/CSS that work good enough on nearly every computer in operation.

by tx 18y ago

dcurtis 18y ago

I agree. But not only are the technical problems with most rich applications fixed by 280 north, but the UI is beautiful, easy to use, and awesome as well.

jimbokun 18y ago

"And THANK YOU!!! for not using Flash." The whole "Objective-J" thing is fascinating. From this, looks like they have ported at least some of AppKit to compile into Javascript webapps: http://280slides.com/Editor/1212695713/DocumentController.j http://280slides.com/Editor/1212695713/DocumentController.j Looks like they have brought the Mac development experience to the web in a far more literal way than I expected.

zhyder 18y ago

I don't understand why Flash is so bad. The general concept of having a plugin with a rich built-in API makes sense for a lot of reasons (natively compiled code in the plugin, smaller download of additional code). The problems with Flash are: (i) it's proprietary, and (ii) it's not on 100% of browsers. (i) is mostly a complaint from developers based on principle, and (ii) -well- isn't true for Javascript either if you include mobile browsers. Disclaimer: my app is built on Flash. P.S.: 280slides is great! And very impressive this was done with JS.

maximilian 18y ago
Flash sucks balls if you have an older mac (1ghz). I don't know how it performs generally on an older pc, but for me, its just aweful. I hate anything online that uses flash.
- tx 18y ago
  Flash sucks balls because it only works well where Adobe wants it to work well, as opposed to openly accepted standards like HTML/CSS that work good enough on nearly every computer in operation.