Tab where?
-
And yet, those toxic hellstew 90s era forums you complain so bitterly about have none of those problems.
So what if the benchmarks show devices are better? Are you building your software for everyone to use, or only the 1% who have devices that fix the terrible performance of your components?
-
And yet, those toxic hellstew 90s era forums you complain so bitterly about have none of those problems.
So what if the benchmarks show devices are better? Are you building your software for everyone to use, or only the 1% who have devices that fix the terrible performance of your components?
Look it's a valid strategy. You can generate static HTML pages and target every device under the sun, or make a dynamic js app that's constantly updating stuff behind the scenes and requires a beast of a hardware. I'm annoyed my current mobile device can't access the forums properly, but my next one probably will. This is literally the problem it will fix itself in time.
Same goes with server deployment ("but apache is EVERYWHERE") and other performance concerns.
Think Y2K bug. A small memory saving shortcut became meaningless 10 years later, but it sure caused a lot of problems. What if someone decided to save the full year to begin with? They would probably seem wasteful at their time too, but less so after the 80-ies.
The only question is whether Discourse will survive long enough to outgrow hardware constrains. Since no competition is stepping out ATM, my bet is yes.
-
Well, then.
http://www.cnet.com/news/gmail-apps-next-version-will-support-yahoo-outlook/
Doesn’t “support” means “pumping every message to a GMail mailbox”?
-
Relevant: Google's Product Strategy: Make Two of Everything at Ars Technica
Is there some very meta joke in it, or did you screw up the links?
Look it's a valid strategy. You can generate static HTML pages and target every device under the sun, or make a dynamic js app that's constantly updating stuff behind the scenes and requires a beast of a hardware.
Or just appropiate the stylesheets. Look, the problem is not how the app looks like. You can very much make your static pages look okay on any mobile device without resorting to JS fuckery. The problem is that Discourse seems to think resources on mobile, such as bandwidth, data usage, CPU and memory are free.
The only question is whether Discourse will survive long enough to outgrow hardware constrains. Since no competition is stepping out ATM, my bet is yes.
The competition is still there, firmly standing where it was, and probably barely even noticing that there's such a thing as Discourse.
-
LOL. It's a fun place to yell at each other in a safe way. I feel like going all SJW on you for your yearnings for cultural oppression or something, but it's too close to dinner time.
Arguing for a "culture shift away from hatred and vitriol" is, to my mind, more "SJW" than letting it be - Trying to dictate a community's culture to be "appropriate" is basically the cornerstone of the belief.
-
Is there some very meta joke in it, or did you screw up the links?
I'm guessing the latter: http://arstechnica.com/business/2014/10/googles-product-strategy-make-two-of-everything/
Summary to save you the bother
- 6 distinct IM clients (Google Talk, Google+ Messenger, Messaging, Google Voice, Google Hangouts, unnamed upcoming one aimed at WhatsApp.)
- 2 OS (Android, Chrome OS)
- 2 wearables (Android Wear, Google Glass)
- 2 mail clients (Gmail, Google Wave)
- 3 TV things (Google TV, Android TV, Chromecast)
And touches on a few other A/B stuff. Copy/paste:
- Nexus versus OEMs
- Google.com versus iGoogle
- Google Video versus YouTube
- Google Maps versus Waze
- Google Maps versus Google Earth
- Google+ versus Orkut
- Google Play Music All Access versus YouTube Music Key
- Eclipse versus Android Studio
- Android's Gallery versus Google+ Photos
- Native mobile apps versus mobile Web apps
-
Look it's a valid strategy. You can generate static HTML pages and target every device under the sun, or make a dynamic js app that's constantly updating stuff behind the scenes and requires a beast of a hardware. I'm annoyed my current mobile device can't access the forums properly, but my next one probably will. This is literally the problem it will fix itself in time.
Same goes with server deployment ("but apache is EVERYWHERE") and other performance concerns.
Think Y2K bug. A small memory saving shortcut became meaningless 10 years later, but it sure caused a lot of problems. What if someone decided to save the full year to begin with? They would probably seem wasteful at their time too, but less so after the 80-ies.
The only question is whether Discourse will survive long enough to outgrow hardware constrains. Since no competition is stepping out ATM, my bet is yes.
I expect Discourse to get proportionately more complex over time, to the point where I expect it will always be require high-end devices in order to be functional.
Really what we're saying here is we're returning to 1997 and 'best viewed on such-and-such browser' and we all remember how much fun that was.
-
Arguing for a "culture shift away from hatred and vitriol" is, to my mind, more "SJW" than letting it be - Trying to dictate a community's culture to be "appropriate" is basically the cornerstone of the belief.
And his ideas of 'appropriate' fail to function on any forum I've ever seen. Things like 'religiously staying on topic' simply do not happen on forums because people are naturally divergent.
-
Is there some very meta joke in it, or did you screw up the links?
I screwed up the link. Fixed now. Correct link: http://arstechnica.com/business/2014/10/googles-product-strategy-make-two-of-everything/
-
-
The problem is that Discourse seems to think resources on mobile, such as bandwidth, data usage, CPU and memory are free.
2000: Nobody Will Ever Run Photoshop In a Browser!
2014: oops
-
What's with all the Windows RT bashing? Of everything I've tried, including high-end Xeon workstations with 16 GB RAM, my Surface 2 RT is the only device where Discourse forums don't run like sedated three-legged dogs in a freezer full of molasses. Only problem is the back button doesn't work.
-
2000: Nobody Will Ever Run Photoshop In a Browser!2014: oops
So, "we'll just stop giving a shit about optimizing our code, and the market will catch on some years from now"?
Is that "thinking future", Discourse edition?
-
2000: Nobody Will Ever Run Photoshop In a Browser!2014: oops
First off: nice quoting fail. I just highlighted and clicked "quote reply", if you care to repro.
Second: apples and oranges. You are told that your software is requiring resources that most client devices don't currently have. That's the apples in this analogy. You respond with a scenario where people didn't foresee the possibility of web based photo editing, only to be proven wrong over a decade later. That's the oranges here. The two are not comparable.
-
Can we at least change
QuotetoParaphrase? If you quote someone, you don't change part of what they say just because you don't think it belongs there.
-
If you quote someone, you don't change part of what they say just because you don't think it belongs there.
I would like your post, but Discourse won't let me for another 3:07 (±difference between my system time and server system time).
-
I get that from you a lot.
-
I have no idea what the difference is between email and Gmail
That's Google's insistance on having their own apps for their own products. Gmail is, well, Gmail and Email is every other email provider.
Well, Actually™, the Email app is open-source and the Gmail app is closed source.
That's the core split. As a result of this, the Gmail app gets more branding, new features first, and Gmail-specific things.
