News for hackers. Stuff that matters.
Re:Introducing TogetherJS by Mikeb85 on Wednesday October 16, 2013 @06:19PM (#6562457)
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...

Re:Introducing TogetherJS by mcphilip on Wednesday October 16, 2013 @09:10PM (#6563096)
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 by Mikeb85 on Wednesday October 16, 2013 @10:17PM (#6563335)
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...

Re:Introducing TogetherJS by ux-app on Wednesday October 16, 2013 @10:43PM (#6563396)
> "makes me wonder if only a minority of HN users have deployed to enterprise environments with rigid infrastructure policies"

I haven't, so I'd appreciate some perspective on this.

If an org does not allow other browsers besides IE, what are the chances of, for example, having a QT exe that simply wraps a webkit webview installed? I assume all orgs would have some procedure for requesting and then deploying third party software. Is this route an easier sell than simply saying "Please use Chrome or Firefox"?

Thanks

Re:Introducing TogetherJS by sgift on Thursday October 17, 2013 @02:05AM (#6563894)
There is usually a process to introduce new software into the environment. This process can, depending on the rigidity of the environment, take from a few month to years and involves all kinds of hand-offs by various departments. A top of the head list of things that are considered:

  - Security
  - Retraining
  - Support
  - Deployment (can we roll this out centrally?)
  - (various things I've forgotten at the moment)
This assumes you have the political clout to initiate such a change. Quite often it is part of the requirements which are defined before there is a project ("We have foo, your software has to run on it") and you cannot influence that.

And if one or more of the mentioned parties is actively hostile to you (sometimes only one person who doesn't like you for whatever reason is enough) this can take much, much longer. Or doesn't happen at all.

Re:Introducing TogetherJS by laureny on Wednesday October 16, 2013 @06:22PM (#6562468)
> Tell your users to use a real browser

Suddenly I have the impression I'm on Slashdot in the early 2000's.

Re:Introducing TogetherJS by r00fus on Wednesday October 16, 2013 @07:03PM (#6562633)
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.

Re:Introducing TogetherJS by Mikeb85 on Wednesday October 16, 2013 @08:42PM (#6563010)
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 by r00fus on Thursday October 17, 2013 @01:52AM (#6563867)
> 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?

13 years ago this was not the case. That was my point. At that point, few alternative browsers existed, and Netscape had just released a bloated undesirable release.

Nowadays, the PC itself is a fortress under siege, and Windows only runs on 30-ish percent of all PC/tablets. Webkit is ascendant, and IE persists in being difficult for developers. Now is the time to code for Webkit or HTML5 compliance.

Re:Introducing TogetherJS by laureny on Wednesday October 16, 2013 @11:00PM (#6563450)
> 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?

Yes, it can be.

Can you think of certain situations where doing this is extremely costly (in money, time or both) or do I need to give you a few examples?

In my experience, people displaying this kind of naïveté have never been in a situation of large leadership (where you are in charge of a large organization or when your decisions can impact hundreds of employees across a company).

Re:Introducing TogetherJS by beagle3 on Thursday October 17, 2013 @03:56AM (#6564138)
> Can you think of certain situations where doing this is extremely costly (in money, time or both) or do I need to give you a few examples?

Yes, I can.

But I can also think, actually, remember, the cost of supporting Microsoft's non-standard Web implementations. For some reason, many people on this thread assume it's legitimate to ask Mozilla to spend time supporting Microsoft products, but it is not legitimate to ask users who want this functionality to support Mozilla's product (by installing it).

Ladies and gentlemen: Actions and decisions have consequences. Choose Windows Phone, and lose a native YouTube app. Choose Internet Explorer and have no access to latest-and-greatest web stuff.

It's as simple as that. There is no reason for anyone to feel entitled to more work spent to support their favorite browser -- even if it was the most popular, which it hasn't been for quite a while now.

Re:Introducing TogetherJS by Mikeb85 on Wednesday October 16, 2013 @11:17PM (#6563490)
Of course it could be costly (in time mostly). But eventually, everything reaches end-of-life. Windows XP, IE6, IE10 will too...

For years, organizations said switching to Linux is more costly than paying the MS tax. Recently, many large organizations rolled out Linux installs on a massive scale (European government institutions).

Anyhow, installing Firefox on some workstations is relatively small compared to say, replacing COBOL, or Windows XP...

Edit - and while I don't manage a large computer install base, I use them at a large organization with thousands of installs (a University), and they somehow managed to install Firefox on every single computer.... (but they still advertise COBOL jobs)

Re:Introducing TogetherJS by brokenparser on Thursday October 17, 2013 @02:02AM (#6563890)
And for those intranet sites which only work on old IE, you could use the IE tab add-on (see https://addons.mozilla.org/en-US/firefox/addon/ie-tab/ ).
Re:Introducing TogetherJS by inthewind on Wednesday October 16, 2013 @08:06PM (#6562866)
(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 by r00fus on Wednesday October 16, 2013 @08:34PM (#6562980)
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 by Mikeb85 on Wednesday October 16, 2013 @11:52PM (#6563570)
That's what society sees him as. And what society thinks goes to a certain degree, because if society was advanced enough to see him otherwise, we wouldn't talk about ethnicity in general.

One of my favourite quotes, from a friend of mine (though I'm sure many others have said it), "We're all beige"

In the end, everyone is mixed, everyone is human.

Re:Introducing TogetherJS by mikegioia on Wednesday October 16, 2013 @07:04PM (#6562634)
Unfortunately we have a lot of school administrators using our app with their Dept of Ed issued computers. The same DOE that actively encourages everyone to use IE and disallows software upgrades without IT help. Trust me, we try to get them to switch to Chrome/FF but it's an uphill battle.
Re:Introducing TogetherJS by annnnd on Thursday October 17, 2013 @06:49AM (#6564531)
This should actually help you - the less developers support IE, easier will be to find reasons for the switch.
Re:Introducing TogetherJS by Cthulhu_ on Thursday October 17, 2013 @03:42AM (#6564101)
> Who cares. It's IE which needs to catch up to the standards Mozilla and Google are implementing.

That's interesting. A time ago, people were moaning at IE for coming up with their own standards / CSS things / Javscript features; now you're saying that they should do the same with things Firefox and Chrome introduced?

I'm being petulant on purpose, don't mind me ;). The HTML5 standards are of yet not standardized yet, so tbh I don't know if they actually should.

Re:Introducing TogetherJS by jongalloway2 on Wednesday October 16, 2013 @11:05PM (#6563462)
Re:Introducing TogetherJS by keshavagrawal on Thursday October 17, 2013 @04:04AM (#6564148)
Yes its IE who needs to implement new techs/standards.

"Tell your users to use a real browser" - Even I don't love IE and don't remember the last time when I used IE but calling it not a "real" browser would be too much I guess :) I think with IE 10 and IE 11 they are making progress. I am sure they will launch WebRTC support as well.

Re:Introducing TogetherJS by shellehs on Wednesday October 16, 2013 @11:28PM (#6563522)
Maybe not because doesn't support IE, maybe because IE doesn't support... You can't count on this.
Re:Introducing TogetherJS by ocfx on Wednesday October 16, 2013 @06:21PM (#6562462)
lol yeah telling our clients to use a real browser is totally going to be good for future business with them..
Re:Introducing TogetherJS by Mikeb85 on Wednesday October 16, 2013 @06:37PM (#6562525)
What would you tell someone using Windows 95 who's complaining that your app won't run?
Re:Introducing TogetherJS by mixmax on Wednesday October 16, 2013 @06:46PM (#6562558)
That would depend on how much money they will pay me.
Re:Introducing TogetherJS by mixmastamyk on Wednesday October 16, 2013 @07:12PM (#6562670)
Exactly. Note that Mozilla isn't being paid for this tool. It's open source though. So those who require IE support are welcome to pay someone to or add it themselves.

Everyone is happy, except those who want goodies for free. ;)

Re:Introducing TogetherJS by ericd on Wednesday October 16, 2013 @10:57PM (#6563442)
Except that it might be in Mozilla's best interest to make it compatible with all the major browsers if they want this to see any sort of real adoption.
Re:Introducing TogetherJS by Mikeb85 on Wednesday October 16, 2013 @11:23PM (#6563510)
Why?

Firefox + Chrome make up the majority. In mindshare, a vast majority.

Mozilla's only interest is in advancing the web, and web technologies. Not catering to a competitor's old technology...

Re:Introducing TogetherJS by ericd on Thursday October 17, 2013 @12:46AM (#6563727)
Because until IE reaches Opera levels of usage, there are a large number of sites that don't target programmers that won't be able to build on stuff like this, because they don't want to cut out a big chunk of their potential market.
Re:Introducing TogetherJS by shurcooL on Wednesday October 16, 2013 @07:00PM (#6562617)
That could be the problem right here. Or it may not be a problem, depends on your values.
Re:Introducing TogetherJS by djrobstep on Wednesday October 16, 2013 @06:57PM (#6562606)
Your clients might appreciate advice on how to use technology better?