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

2016 Stack Overflow Developer Survey Results

stackoverflow.com

Post reply on HN
Print view View original

141–150 of 175 posts

Re: 2016 Stack Overflow Developer Survey Results

#141

Post by nostrademons »

TheLogothete wrote: post #75
xemoka wrote: post #71

Earlier quoted context omitted.

In 2007. Everything changes, it's our only constant.

What has changed in the limitations of the DOM?

Quite a bit, actually. Since 2007, we've gotten Javascript JITs, Canvas, WebGL, consistent box models, consistent event models, flexbox, CSS transitions & animations, CSS transforms, localstorage, IndexedDB, websockets, HTML5 audio & video, history.pushState, and several other features. And components (custom elements + Shadow DOM) are coming, and already implemented in some browsers.

Pretty much anything you could do in a native Windows app in 2007, you can do in a webapp now, except pwn your computer. Only problem is that the goalposts have moved: now everybody expects you to be able to do it on a phone as well, as well as access the camera, accelerometer (which you can do on the web, actually), contacts, calendar, and bluetooth hardware.

Re: 2016 Stack Overflow Developer Survey Results

#142

Post by nostrademons »

fweespee_ch wrote: post #20

> The average developer is 29.6 years old. The median is 27. Does anyone else find this concerning given all the talk of age bias in tech?

In any field undergoing exponential growth, the median experience will be the same as the doubling time.

It wouldn't surprise me if tech doubles every 5 years, so 27 is not unrealistic.

Re: 2016 Stack Overflow Developer Survey Results

#143

Post by TheLogothete »

nostrademons wrote: post #141
TheLogothete wrote: post #75

Earlier quoted context omitted.

What has changed in the limitations of the DOM?

Quite a bit, actually. Since 2007, we've gotten Javascript JITs, Canvas, WebGL, consistent box models, consistent event models, flexbox, CSS transitions & animations, CSS transforms, localstorage, IndexedDB, websockets, HTML5 audio & video, history.pushState, and several other features. And components (custom elements + Shadow DOM) are coming, and already implemented in some browsers. Pretty much anything you could d…

Uhm... the DOM is single threaded and sequential. It will never EVER be comparable to native clients.

Re: 2016 Stack Overflow Developer Survey Results

#144

Post by nostrademons »

TheLogothete wrote: post #143
nostrademons wrote: post #141

Earlier quoted context omitted.

Quite a bit, actually. Since 2007, we've gotten Javascript JITs, Canvas, WebGL, consistent box models, consistent event models, flexbox, CSS transitions & animations, CSS transforms, localstorage, IndexedDB, websockets, HTML5 audio & video, history.pushState, and several other features. And components (custom elements + Shadow DOM) are coming, and already implemented in some browsers. Pretty much anything you could d…

Uhm... the DOM is single threaded and sequential. It will never EVER be comparable to native clients.

Web Workers.

Re: 2016 Stack Overflow Developer Survey Results

#145

Post by seren »

manyxcxi wrote: post #113
seren wrote: post #60

Earlier quoted context omitted.

I have no doubt that the web will eat desktop application (maybe native app as well at some point). However, they are plenty fields from machine learning, to robotics that are also likely on the rise that would require some SW development skills. Also, as mentioned by d0lph, I believe the high churn in web technology makes more people relying on SO, compared to let's say someone coding in C99. But my view is probably…

The thing is, with the ML code or the code for robotics that I've written over years, it's been predicated on the fundamentals of software development I've learned doing everything else. Good habits are good habits, disorganized code is disorganized code. In some ways all the C/C++ I've written for my various robots and gadgets have been easier than even web development UI code because my button is LITERALLY a button…

I agree with your point. When I said "development skills" it was not a judgement about talent, rather about "body count".

Re: 2016 Stack Overflow Developer Survey Results

#146

Post by TheLogothete »

nostrademons wrote: post #144
TheLogothete wrote: post #143

Earlier quoted context omitted.

Uhm... the DOM is single threaded and sequential. It will never EVER be comparable to native clients.

Web Workers.

Yeah man. I've never heard of those. They sound like the best thing since sliced bread. Only if they could access the DOM...

Seriously... what are you even talking about? Why do you even mention them? You read single threaded and thought "Quick, I must come up with an answer! I can't let a stranger on the Internet change my opinion!"?

Re: 2016 Stack Overflow Developer Survey Results

#147

Post by nostrademons »

TheLogothete wrote: post #146
nostrademons wrote: post #144

Earlier quoted context omitted.

Web Workers.

Yeah man. I've never heard of those. They sound like the best thing since sliced bread. Only if they could access the DOM... Seriously... what are you even talking about? Why do you even mention them? You read single threaded and thought "Quick, I must come up with an answer! I can't let a stranger on the Internet change my opinion!"?

So, it's hard to understand exactly what it is you're trying to accomplish and why Web Workers wouldn't work for you because basically every single desktop GUI framework is single-threaded when it comes to actually updating the components on the screen. Win32 uses the GetMessage/TranslateMessage/DispatchMessage event loop. Swing has the UI thread, and then to update the UI from a background thread, you need to call invokeAndWait or invokeLater and pass a Runnable. Cocoa and iOS have Grand Central Dispatch, and to update the UI you pass a block to dispatch_async on a dispatch queue. Android has you call View.post() with a Runnable that contains your UI modifications. WPF has two threads, a rendering one and a UI thread, and you're supposed to pass long-running operations off to a threadpool and then call Invoke or BeginInvoke with a delegate to actually update the UI from them.

Web Workers are exactly this model, applied to the web. It's a dispatch queue running inside a threadpool. To update the DOM, you postMessage back to the UI thread and make your modifications there.

Are you willing to let a stranger on the Internet change your opinion?

Re: 2016 Stack Overflow Developer Survey Results

#148

Post by SideburnsOfDoom »

jedberg wrote: post #117
SideburnsOfDoom wrote: post #86

Earlier quoted context omitted.

I have heard a candidate for a software engineer position talk with straight face about his current workplace's "devops team" and handing off software to them. So maybe it's getting that way.

If this were reddit this is where I would post a "The force doesn't work that way!" memes. I can't stand it when people ask about a "devops team". That's not devops then! That just means your sysadmins can code too. Now, if they are asking about a devops software team, that's a different story.

Yep. What it means is like "agile" did, it's reaching the "old wine in a new bottle" stage, with less actual hard work of changing the way people work for the better, and more easy slapping a new trendy label on existing practices.

Re: 2016 Stack Overflow Developer Survey Results

#149

Post by hhandoko »

enraged_camel wrote: post #131
imaginenore wrote: post #125

Earlier quoted context omitted.

More like crushes your wallet Sublime = $70 Notepad++ = free

Considering how well-paid developers are on average, $70 hardly "crushes" anyone's wallet.

True, but it will not be the only tool in the toolbox... So taking into account all the other software you've purchased, the costs will add up.

Just an anecdotal example, before JetBrains switched to their subscription model I was paying individual licenses for IDEA, PyCharm, and ReSharper. So if I had already spent over $300 p/a for IDE and tooling, another $70 will seem like an excess.

Post reply on HN