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

Stop pushing the web forward

quirksmode.org

Post reply on HN
Print view View original

11–20 of 307 posts

Re: Stop pushing the web forward

#11

Post by tutuca »

ixtli wrote: post #8

> But why do web developers want navigation transitions? In order to emulate native apps, of course. If we're doing unpopular opinion time, I think this is the real issue that no one wants to talk about. I'm all for whatever feature development the community can standardize. Apple, google, mozilla, and etc. all have smart people working for them and when they cooperate things seem to work out fine. The problem is try…

If you read further they link to a previous post that covers just that: http://www.quirksmode.org/blog/archives/2015/05/web_vs_nativ...

Re: Stop pushing the web forward

#12

Post by RubyPinch »

slinging around "web trying to be native is bad" in the way the author does is such a thoughtless argument: just because something exists in native land (a land of a lot of well paid researchers and designers, etc etc), doesn't make the idea bad for everywhere else. Maybe the idea is just a plainly good design decision?

(I mean, do you have fond thoughts of the entire page flashing white, then pieces of the page bouncing around the screen as they try to position themselves based on content that hasn't loaded yet?)

Re: Stop pushing the web forward

#13

Post by cognivore »

"However, web apps also allow organizations to write once for many platforms in a much more seamless way than most cross-platform native toolkits I've seen."

Does it? I used to think that. Until every medium-complexity or worse web project I've worked on took forever as we went through all the different browsers and OS's and now mobile and tablets and responsive and OMG just give me a decent native app tool now please.

Browsers absolutely suck at UI beyond their original intended domain.

Re: Stop pushing the web forward

#14

Post by pavel_lishin »

skwosh wrote: post #4

As a corollary I'd like to say: stop pushing JavaScript forward. There seems to be a lot of focus on providing syntactic sugar for things that already exist (like classes, decorators, etc) at the expense of flexibility and composability (executable class bodies, @foo vs normal function application, etc). What JavaScript needs much more IMO is a (better) stdlib, with more datatypes and procedures than currently availa…

Javascript has decorators?

Re: Stop pushing the web forward

#16

Post by adrusi »

bhousel wrote: post #7
skwosh wrote: post #4

As a corollary I'd like to say: stop pushing JavaScript forward. There seems to be a lot of focus on providing syntactic sugar for things that already exist (like classes, decorators, etc) at the expense of flexibility and composability (executable class bodies, @foo vs normal function application, etc). What JavaScript needs much more IMO is a (better) stdlib, with more datatypes and procedures than currently availa…

>What JavaScript needs much more IMO is a (better) stdlib, with more datatypes and procedures than currently available (including big numbers, the various flavours of trees, etc). Isn't that "pushing JavaScript forward?"

Maybe what skwosh means is a moratorium on new features in javascript so that we can refocus on the features that are useful, and actually improve rather than complect the language.

Re: Stop pushing the web forward

#17

Post by mkozlows »

I've gotta say, I'm somewhat sympathetic to the idea that we'd be better served by a period of focusing on stability and performance over new features... but talking about the IE6 stagnation era as a good thing?

Yeah, no, that was awful, and if you're holding it up approvingly, well, now I officially disagree with you.

Re: Stop pushing the web forward

#19

Post by ForHackernews »

> Interestingly, Microsoft added a similar feature to IE4, and deprecated it as of IE9. The idea didn’t catch on because back then nobody wanted to emulate native apps (which didn’t exist), and therefore nobody particularly cared if the users had to briefly wait for the next page.

> native apps (which didn’t exist)

Does this writer believe that nobody installed software on their computers before the iOS app store opened in 2008?

Re: Stop pushing the web forward

#20

Post by mkozlows »

pavel_lishin wrote: post #14
skwosh wrote: post #4

As a corollary I'd like to say: stop pushing JavaScript forward. There seems to be a lot of focus on providing syntactic sugar for things that already exist (like classes, decorators, etc) at the expense of flexibility and composability (executable class bodies, @foo vs normal function application, etc). What JavaScript needs much more IMO is a (better) stdlib, with more datatypes and procedures than currently availa…

Javascript has decorators?

Higher-order functions do the same thing.
Post reply on HN