Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing TogetherJS

hacks.mozilla.org

Post reply on HN
Print view View original

31–40 of 87 posts

Re: Introducing TogetherJS

#31

Post by aray »

mntmn wrote: post #27

I am building an actual service using technology like this (but we wrote our own, not TogetherJS). It's cool, but don't forget that this is really a "utility" and it's the mix of factors and features that you build on top of this that make an actual product out of it. I'm currently compiling a (somewhat biased) feature-by-feature comparison on creative realtime collaboration tools. Feel free to comment and suggest mo…

A bit meta, but I think it's really telling that you're using a google doc (also a great collaboration tool) to compare.

Re: Introducing TogetherJS

#32

Post by mntmn »

aray wrote: post #31
mntmn wrote: post #27

I am building an actual service using technology like this (but we wrote our own, not TogetherJS). It's cool, but don't forget that this is really a "utility" and it's the mix of factors and features that you build on top of this that make an actual product out of it. I'm currently compiling a (somewhat biased) feature-by-feature comparison on creative realtime collaboration tools. Feel free to comment and suggest mo…

A bit meta, but I think it's really telling that you're using a google doc (also a great collaboration tool) to compare.

That's totally intentional, we didn't want to implement a spreadsheet. Yet. ;) I made a list of use cases under the main table that clearly states Google Docs as currently the best tool for tasks like spreadsheets, Word-like document authoring and such. I'm well aware of NIH.

Re: Introducing TogetherJS

#34

Post by inthewind »

r00fus wrote: post #23
laureny wrote: post #12

Earlier quoted context omitted.

> Tell your users to use a real browser Suddenly I have the impression I'm on Slashdot in the early 2000's.

Funny how the progress of time moves seemingly extreme positions into mainstream acceptance. If you told me 13 years ago that the US would elect a black president twice, I'd have laughed at you.

(I get annoyed when people cite Obama as being a black president! How about Grey? http://news.bbc.co.uk/1/hi/world/americas/us_elections_2008/...)

Re: Introducing TogetherJS

#35

Post by r00fus »

inthewind wrote: post #34
r00fus wrote: post #23

Earlier quoted context omitted.

Funny how the progress of time moves seemingly extreme positions into mainstream acceptance. If you told me 13 years ago that the US would elect a black president twice, I'd have laughed at you.

(I get annoyed when people cite Obama as being a black president! How about Grey? http://news.bbc.co.uk/1/hi/world/americas/us_elections_2008/... )

Not my terminology [1] [2].

Black is a culture in the US as well as ethnicity. Barack Obama identifies himself primarily as an African American/Black as does most of the nation. Don't see what's wrong.

[1] http://en.wikipedia.org/wiki/Black_people [2] http://en.wikipedia.org/wiki/One-drop_rule

Re: Introducing TogetherJS

#36

Post by Mikeb85 »

r00fus wrote: post #23
laureny wrote: post #12

Earlier quoted context omitted.

> Tell your users to use a real browser Suddenly I have the impression I'm on Slashdot in the early 2000's.

Funny how the progress of time moves seemingly extreme positions into mainstream acceptance. If you told me 13 years ago that the US would elect a black president twice, I'd have laughed at you.

Extreme position?

Given that so much software requires installing the JVM, or CLR/Mono run-time, or widget toolkit, or even is specific to an operating system, is it really that much to ask that users install a certain browser which literally runs on any OS, is free and open-source, and can be installed in seconds/minutes?

Why do we rail against people for using the wrong OS, make people dual-boot and run virtual machines, yet installing a different browser is completely unacceptable?

No one minds that so many apps are iOS/OSX/Android/Windows exclusive, but when web-apps don't run on IE it's a problem...

Re: Introducing TogetherJS

#37

Post by mcphilip »

Mikeb85 wrote: post #9
mikegioia wrote: post #3

This looks great but it seems they have no plans to support Internet Explorer ( https://togetherjs.com/docs/#browser-support ). That's a shame because most of our users who need this level of support all use IE :/

Who cares. It's IE which needs to catch up to the standards Mozilla and Google are implementing. It's not like Windows users will be left out in the dark, they can always install Firefox. Tell your users to use a real browser, or write a letter to Microsoft telling them to get with the times... Even the University I attend doesn't support IE with their web-apps. They support Firefox...

It's comments such as this that bubble up to the top of the comment chain that often makes me wonder if only a minority of HN users have deployed to enterprise environments with rigid infrastructure policies.

In my more cynical moods I wonder what percentage of users have non-novelty code in production at all.

Re: Introducing TogetherJS

#38

Post by phowat »

mikegioia wrote: post #3

This looks great but it seems they have no plans to support Internet Explorer ( https://togetherjs.com/docs/#browser-support ). That's a shame because most of our users who need this level of support all use IE :/

Mozilla has a considerable stake on WebRTC's success, and a good way for them to push it's adoption is to help make useful web apps which rely on it. It would be counter productive, and a huge amount of wasted work, for them to support non-webrtc enabled browsers. As someone who is also actively working with the technology and betting on it's success, I'm actually happy they don't support IE/Safari.

Re: Introducing TogetherJS

#40

Post by Mikeb85 »

mcphilip wrote: post #37
Mikeb85 wrote: post #9

Earlier quoted context omitted.

Who cares. It's IE which needs to catch up to the standards Mozilla and Google are implementing. It's not like Windows users will be left out in the dark, they can always install Firefox. Tell your users to use a real browser, or write a letter to Microsoft telling them to get with the times... Even the University I attend doesn't support IE with their web-apps. They support Firefox...

It's comments such as this that bubble up to the top of the comment chain that often makes me wonder if only a minority of HN users have deployed to enterprise environments with rigid infrastructure policies. In my more cynical moods I wonder what percentage of users have non-novelty code in production at all.

Fair enough. If you need to support outdated browsers because of someone else's technology choices, that's a differentiating feature for you and your business, and I respect that (and I hope you're charging a decent amount as compensation for the fact you're supporting their older technology).

But if you're interested in the advance of technology, especially when it's pushing the boundaries, a little bit (or a lot) of idealism is a good thing.

Plenty of people make a (from what I hear) very lucrative living programming in COBOL, and I respect them for it. Lots of people still program in Fortran, which is awesome. But that doesn't mean we should be limited to COBOL and Fortran because someone else is...

Post reply on HN