3 ms·
Could not agree more! We have an mainly internal-only app that I work on that started out as PHP+HTML+CSS only and then over the years JS has been bolted on in
by joshstrange 12y ago
Could not agree more! We have an mainly internal-only app that I work on that started out as PHP+HTML+CSS only and then over the years JS has been bolted on in various places. At first it was just to make life easier (Autocomplete, minor AJAX) but now we have entire components that will not function without JS and could not function without JS. Recently some devs have pushed for supporting browsers without JS enabled and I have been vehemently against it for a couple reasons:
1) MAJOR parts of our app will not and can not work without JS. Period, exclamation point.
2) Because of point 1 it doesn't make sense to waste dev time on making some views work with/without JS (We are a younger company and don't have time to waste on something like this especially when it isn't public-facing, not to mention QA can't handle testing everything twice).
3) Even if V1 of a component does support both JS and no JS there is no guarantee that future updates will be able to keep feature-parity or have time to code for that.
For me JS is part of the web, not an optional add-on. It would be like saying "make a webpage that works with HTML" (IMHO).
I also feel that it's not fair to complain about the GOOGLE CHROME app store requiring GASP GOOGLE CHROME (Same for GOOGLE cloud print). Not shit sherlock. As for Apple not allowing their video feeds on anything but Safari+OS X I think this is BS, there is no good reason I can think of to alienate so many people on other OS's especially since I would think THOSE are the people you might want to reach with your keynotes to convince them why they should switch.
So while I like the idea of this Tumblr I can't help but think the JS/Google Chrome examples don't really fit and distract from the overall message. To be honest looking through the Tumblr again the ONLY valid concern is the one with Apple's keynote streaming, the other ones make complete sense. How is it Google's fault that they are pushing the envelope in terms of what is possible, even Google doesn't have the time/resources to make every one of their ideas (which may or may not make it long term) work across the board and that is their prerogative.
- oneeyedpigeon 12y ago"I also feel that it's not fair to complain about the GOOGLE CHROME app store requiring GASP GOOGLE CHROME" I read that as complaining about a WEB APP store requiring google chrome. Web apps tied to a specific browser are destructive to the overall ecosystem; you might as well just distribute native apps.
- joshstrange 12y agoOk, if Gmail was an app in the Google Chrome store only then that might be a problem but this is "Offline" Gmail which I'm sure is using Chrome-specific API's to do it's magic. Google used to have thing called Google Gears (or something like that) that was a framework that would allow for things like Offline Gmail in FF but if I had to guess they either didn't have great adoption or where too limited in what they could so they dropped it and rolled it's features into Chrome. What I'm not a fan of is "Lowest-denominator web is the best web" arguement. It's not and I'm sorry but unlimited backwords-compatibility is a pipedream, at some point you have to move forward.
- Smudge 12y agoThere are non-Chrome-specific "offline" APIs. Some already found in the wild, and some still exist as specs. Google is free to roll their own and keep it to themselves, but I think it's perfectly okay to shame them when they do. It's the same reason I was against ActiveX components in IE. Theres nothing fundamentally wrong with a company pushing things that align with their interests, but there's also nothing wrong with complaining about it like this Tumblr blog does.
- aaaaaaaaaaa1234 12y agoCan you provide any details about the internal app? What features does it have that need javascript? Also, since it's internal only, does it even need any extra compatibility, since all the configurations are known? The "web" and the "intranet" are quite different situations.
- joshstrange 12y agoSo while it is heavily used inside our company (where everyone is on the latest chrome) it is also used by LEA's which we do not control. This means we have to support Chrome/FF/Safari/IE 9+ but we have yet to come across a group that disabled JS. As for what requires JS: we use google maps and people need to be able to draw zones on the maps which is not possible without JS (unless we have them a bunch of text inputs that they could enter the lat/lon of all the vertices. That is just one example and I can't go into much more detail. Bottom line is we would not have the customers we do if we didn't use to make it faster/easier and we don't have to resources to support JS+Noscript/no JS.