The question on its own is useless given the audience - yes. However if you combine that question with the - e.g. - primary field a person works in it gets interesting.
Say a person said they're mostly writing finance software and Go isn't a language they'd prefer to use for their next project.
Those two data points on their own also don't tell much - but if multiple people answer with that combination the Go team knows that they aren't covering the needs of the finance sector appropriately.
With that knowledge they can e.g. request more information from those people and start working to fix those issues.
As a person who is mostly writing finance software I can tell that Go is not very well suited for any kind of rich application domain (which finance definitely is). OOP and Java + C# in particular have a very strong hold in finance. We can argue whether composition is an adequate substitute for inheritance, but the lack of generics is pretty much a non-starter.
Go works very well in domains with a well-defined and limited set of entities.
> What causes OOP to be well suited for finance's use case?
What are the short-comings of structs/interface methods that Go! provides in the financial space?
“Things” in finance are amenable to the classical PIE of OOP. Many concepts, e.g. financial instruments are extended version of something that was invented earlier. E.g. you have an abstract concept of an interest rate swap and specific versions of it (like fixed-fixed, foxes floating, cross-currency etc). This works pretty well with inheritance and polymorphism.
When you talk about money, finance is very particular about what you can do and what you cannot do. E.g. if money are subtracted from one account, they should appear in another, or balance cannot go negative. It is easier to enforce rules like that on a language level with encapsulation.
> If Go! had generics, would that change it's suitability for finance?
I believe so. You have built in “generics” for most popular collections like maps and arrays, which is fine for command like utilities and lots of system-level software. But in finance (an other problem domains tbh) you often need a generic version of a more complicated data structure, e.g. dataframe, tree, implementation of flyweight pattern, or data cube.
> I would think that first-class concurrency would be useful in that space, is it?
Good support of first class concurrency is useful everywhere. Just so it happened that given that C++, Java, and C# together reign in different domains of finance, we are already quite comfortable with concurrency primitives of these languages (usually some kind of multithreading)
More like Go’s building comes building-agnostic, whether you have 20 stories or not. Anything you need (such as a generic elevator) can be added on. No need to walk 20 stories every day because you can just add what you need in through reusable packages.
Maybe language communities are formed from people that need or don't-need those kind of affordances. e.g. Imagine the office environment you'd have if all your cohort were people that walked 20 flights without making it an issue.
> Go team knows that they aren't covering the needs of
This is true for anything where Go is underused or not used and the bias here still stands, since those people are very unlikely to be represented in the survey.
I think most people don't see the value in RSS feeds because they are used to the business of forums and social networks - where you don't need (or have the capability to) process _all_ the information.
RSS feeds are perfectly suitable for stuff like blogs, podcasts, webcomics, etc.pp. - not for platforms where a new item pops up every few seconds.
For podcasts people use a separate app like PodcastAddict or iTunes - for webcomics and blogs the author(s) usually also have twitter to announce a new item or an entirely separate platform like DeviantArt or WebToons.
So RSS is indeed not required to keep track of new submissions. I actually have a colleague who isn't using RSS feeds and instead keeps bookmarks and checks each page individually (given he only keeps track of maybe ~30 pages).
In conclusion - I think they don't see a value in RSS feeds because the existing options they're using already fulfill their needs.
> RSS feeds are perfectly suitable for stuff like blogs, podcasts, webcomics, etc.pp. - not for platforms where a new item pops up every few seconds.
I definitely agree; a noisy channel is bad for RSS.
> So RSS is indeed not required to keep track of new submissions.
Disagree hard here. I have a twitter account, but while it's not a waterhose, I would 100% miss new comic post announcements - assuming that an author's twitter account only announced new comics, and didn't just tweet other things.
Comics are the perfect use case for an RSS feed: they've mostly got a stable and slow publishing schedule, and not time-sensitive. I can ignore that folder in my reader for weeks, and then go back and catch up.
Doing that manually by clicking bookmarks seems like insanity to me, now.
Terms of Service Violation
Your usage has been flagged as a violation of our terms of service.
For inquiries related to this message please contact support.
For sales inquiries, please visit
http://www.bloomberg.com/professional/request-demo
If you believe this to be in error, please confirm below that
you are not a robot by clicking "I'm not a robot" below.
Please make sure your browser supports JavaScript and cookies
and that you are not blocking them from loading. For more
information you can review the Terms of Service and Cookie
Policy.
Block reference ID: 2f6bf840-a96b-11e8-8a1f-91588296f859
Lots of news websites seem to think they can't function without tracking readers. I wonder how they got by when street corner newsstand were the only way to get views.
Not really, newspapers made most of their money from advertising. You still see people handing out free newspapers in cities, but the advertising is worth more when someone pays for the paper as it’s assumed someone is going to read it vs using it as a free stack of paper.
Well here's the fantastic thing about newspapers and newspaper websites - you have the option of not buying them, and not visiting them. It's much nicer for the rest of us if you exercise those rights rather than complaining.
Here's a good, fairly non-technical guide on things you can do to avoid geoblocking. It's targeted at Australian shoppers but would also be relevant to Europeans wanting to access international websites.
> You need someone who can bring other developers along, teach with purpose, and etc. Experience developing alone does NOT automatically provide that.
And the bloke needs time to train. If the developer is getting chased from dumpster to forest fire and back he won't be able to pass on knowledge and best practices.
Say a person said they're mostly writing finance software and Go isn't a language they'd prefer to use for their next project. Those two data points on their own also don't tell much - but if multiple people answer with that combination the Go team knows that they aren't covering the needs of the finance sector appropriately. With that knowledge they can e.g. request more information from those people and start working to fix those issues.