41–50 of 304 posts
My current employer will be devastated. The user interface of our currently in development program requires IE + Java applets.
'In development'. Does this mean v1 hasn't even shipped yet?
My current employer will be devastated. The user interface of our currently in development program requires IE + Java applets.
This sounds like the stuff I worked on 15 years ago in the oil and gas sector (in fairness, IE + applets _were_ the best choice at the time).
Depends on the constraints. Qt was around and mature for many years in 2006. Ruby on Rails had it's first release mid 2004. Django mid-2005.
Again it depends on the constrains, what you can "the best choice in 2006" is limping now. Meanwhile an app built in 2006 on Qt/RoR/Django would be on a platform that is currently still being considered for green field devt.
Without knowing all constraints I'd be willing to say that IE+applets was not the best choice in 2006, neither was: GWT, WebSphere or any of the MS GUI toolkits around in that year.
I'm still on the fence wrt Vaadin. It was not around in 2006, but soon after. Never used it, but it seems to still be actively maintained to this day.
My current employer will be devastated. The user interface of our currently in development program requires IE + Java applets.
Why?
Surely it's not a greenfield project.
That's a real end of an era. Internet Explorer's legacy engine is going to be relegated to old grayhair horror stories. Not unhappy it's going away, but it feels like a big chapter is closing.
relegated to old grayhair horror stories. The real shame of IE's passing is that we'll forget the lessons we learned and therefore repeat that particular disaster. It's already happening. I'd be happy to relegate the nightmare of IE to old war stories... except the same thing is happening today! Different method, nearly the same end result. We nearly lost the damn open web to the horror of IE6 and the peak "embrace,…
IE6 was also a good browser. It didn't stay a good browser over the 5-10-15 year lifespan it had (depending on who you ask) but at the time of release it was easily the best.
Earlier quoted context omitted.
relegated to old grayhair horror stories. The real shame of IE's passing is that we'll forget the lessons we learned and therefore repeat that particular disaster. It's already happening. I'd be happy to relegate the nightmare of IE to old war stories... except the same thing is happening today! Different method, nearly the same end result. We nearly lost the damn open web to the horror of IE6 and the peak "embrace,…
> Unlike IE6's reign of incompetent terror, Chrome is actually a competent browser. Techies are embracing the takeover instead of fighting it. It's guaranteed to succeed. IE6 was also a good browser. It didn't stay a good browser over the 5-10-15 year lifespan it had (depending on who you ask) but at the time of release it was easily the best.
My current employer will be devastated. The user interface of our currently in development program requires IE + Java applets.
I'm really curious what client requirements drove that decision. 'In development'. Does this mean v1 hasn't even shipped yet?
yes
My current employer will be devastated. The user interface of our currently in development program requires IE + Java applets.
> currently in development program requires IE + Java applets. Why? Surely it's not a greenfield project.