Seems like most of the projects that get the axe have been neglected for a while first. Probably no one is really pouring their heart in to these things enough to be too upset.
Every project I've touched has withered and has been cancelled (except for one, but it has only been out for a year). I'm convinced that it's my super power.
Didn't you see how much credit was given to the investment group during the parade last Summer? They're going to have to install tables for the new courtside seating so that handjobs can be given out under them.
Look past the marketing. They aren't selling "we run algorithms on your data" they're selling "we run algorithms on all your data". There is still a large value proposition in managing large data and until something like GCE manages to completely remove the liability of bad developers using its platform, there will be room for these types of services IMO.
Really ? I always thought them as synonyms and "Software Engineer" as a more "upscale" title (which is kind of stupid, IMHO).
From Wikipedia:
"The term programmer has often been used as a pejorative term to refer to those without the tools, skills, education, or ethics to write good quality software. In response, many practitioners called themselves software engineers to escape the stigma attached to the word programmer. In many companies, the titles programmer and software developer were changed to software engineer, for many categories of programmers."
I don't use or develop for OS X, but I know it has a reputation for some pretty bad desktop applications. Do people think React Native might lower the barrier enough to improve on this problem? Thinking of getting a Mac soon and am curious.
This is completely the opposite of the case, in my experience. People complain about some things like Mail and iTunes, but overall software for OSX is typically head and shoulders above its Windows and/or Linux counterparts.
For a recent example, having gotten used to Transmission (BitTorrent client on Mac), I was absolutely floored at how absurdly complicated and ad-ridden Windows alternatives are.
I have to echo this. I really wonder where you got that impression because it's the opposite of both the reputation I hear and my own experience.
There are very few applications that I miss from Windows. Most big cross-platform applications like Photoshop (or even SourceTree) are almost identical, but the majority of Mac-only apps that I try are fantastic.
Reeder (RSS client), Fantastical 2 (calendar), Tower (git client), iTerm 2, 1Password, Transmit (FTP/SCP client) and TextWrangler/BBEdit are just a couple of examples of apps I use every day that I think really show off what Mac developers can do.
There are many apps that are miles ahead of Linux or Windows equivalents: OmniGraffle, OmniFocus, Acorn, Pixelmator, 1Password, iTerm, Alfred, (Git) Tower, etc.
Can't you just use Transmission on windows? It's a GTK app and they're better on Windows than MacOS. Or you can always use it's web interface on Windows.
Transmission on OS X uses native UI components[1] rather than GTK. In fact they seem to have 3 sets of UI code (AppKit, GTK+, Qt), plus the web interface, plus whatever they're using on Windows (might be GTK+ or Qt there?).
Having used Transmission on both Windows and OS X, I vastly prefer the OS X version. It never crashes, gives nice notifications, and is generally very pleasant to use.
Those are also all apps made by Apple. You might be able to reasonably argue that there has been degrading quality in Apple's own apps. Personally, I love Mail and don't use any of the other native apps.
I don't think that really says much about the quality of the ecosystem for developing native apps though. Some of my favorite apps are Notational Velocity, 1Password, and Sketch.
> reputation for some pretty bad desktop applications
Compared to what? I like native OS X desktop applications better than native Windows, Linux, iOS, Android, or Windows Phone applications, and I like them MUCH better than web apps.
The main reason OS X desktop apps tend to be so nice is (a) Apple’s first party software in the 2000–2010 timeframe was mostly quite good, setting a high standard; (b) GUI conventions are reasonably standardized and developers tend to follow them better than on other platforms, in particular using native widgets which handle edge cases better than various ad-hoc custom (i.e. buggy) widgets on other platforms; (c) the Mac app economy has been pretty good for independent developers, and there’s a cultural expectation of paying for software which is much less present on other platforms, so as a result developers can afford to invest the time necessary to add polish.
Maybe React Native will lower the barrier and we'll get some of those javascript vector graphics, publishing, video editing, and music composition apps ported to the Mac, so people won't have to suffer from pretty bad apps any longer.
The only complaint I have about native Mac applications is Finder: it's frustrating and practically useless. Fortunately, there is a rich and robust CLI ecosystem, so I can largely avoid using it.
Would be interesting to find out the value (upvotes) of sponsored content vs. unsponsered content, as well as comments from green users vs normal users.
I think it's also important to point out the the timeline for all these events is murky at best. We know when the West announced their support for these various movements, but that doesn't always represent the exact time or size of the support given..
I actually think Go's simplicity is a weakness because it will only get you so far. Take web development for example, all the tutorials show json.Unmarshall, but this one stackoverflow post says I should use json.Decode. Oh shoot now I'm having all sorts of problems because I don't really understand json.Decode.
Furthermore I think most people reach for Golang in the beginning because they want performance. However I've found it incredibly easy to write unperformant Go.
I think Golang will ultimately be a very important stepping stone in language development in terms of concurrency, type systems, standard libraries, deployability, and many other categories. I think a lot of important programs will be written in it. And ultimately I look forward to how future languages draw from it.
> I think Golang will ultimately be a very important stepping stone in language development in terms of concurrency, type systems
"stepping stone" usually implies progress and Golang was a regression on both fronts, and while its deployment story is ok that's in no small part because it just opts to statically link everything by default, which the field has been going back and forth on basically since the beginning.
"Take web development for example, all the tutorials show json.Unmarshall, but this one stackoverflow post says I should use json.Decode."
Plenty of JSON libraries in plenty of languages have both a function to decode JSON and an object that allows you to decode JSON with some settings. That's not really a Go-specific issue.
