https://en.m.wikipedia.org/wiki/Männergarten

Without a CS degree of some sort you're going to need to prove you can code. Dabbling helps but you'll need to show work experience.

Getting work experience without a CS degree likely means taking jobs that aren't otherwise appealing.

Contracting or freelance can be a way to get that experience since the bar for proof is often lower, especially when working in non-technical industries.

But those are jobs, and they pay money.

If you have the financial means and can attend a reputable school, I'd recommend getting the masters, or even a bachelors.

Having that degree, and learning what they teach you in a CS program, will help you get a much better job and will help you perform in that job earlier than learning as you go.

You're going to need to make the call if you can afford the short term financial hit/investment.

Because the comment on the commit that adds this to the swift source states that "It relies on ObjC interop".

https://github.com/apple/swift/commit/013aad13d4245a012cfb76...

So maybe not the runtime, per se, but haven't looked into what it's actually generating.

Assigning a block to a c function pointer is an interesting alternative, I thought we tried something like that but I can't remember now.

Hopefully @_cdecl will become a documented and supported feature.

    @_cdecl("foobar") public func foobar() {}

[0]https://news.ycombinator.com/item?id=11650628

[1]https://github.com/apple/swift/commit/013aad13d4245a012cfb76...

[2]https://swiftlang.ng.bluemix.net/#/repl/d68be430e72609717f71...

But this isn't Netflix producing high quality content while the studios lose out. It's Netflix paying the studios for quality content.

If Netflix has found a worldwide market for content, that's good news for the studios they're hiring to produce that content.

I'm curious if the additional revenue from Netflix, and presumably Amazon, Hulu, and a nervous HBO will be enough to offset the declining revenue from broadcast TV.

The retail explosion of Abbot Kinney, for example, predates any tech presence. Venice became cool (and safe) and then the tech companies moved in, along with everyone else.

EDIT: apparently this has happened repeatedly, according to a quick google search.

No doubt some sort of knee jerk process was put in place to ensure that any digital release of redacted documents must be scans of a physically redacted source.

Sort of like an analog memory hole.

At least on Kauai you can often find local beef, pork, and chicken, though it's still more expensive than meat from the mainland.

It's a vicious cycle.

I'm sure they are well aware that they're behind on the transition to streaming but are stuck with long term existing contracts that don't give them the rights they need.

The leagues want to go direct when they go streaming. Why would they need ESPN as an aggregator?

It's not like Netflix or HBO where you turn it on to browse, you're there to watch a specific game.

They're really screwed.

The IDE-like source parsing is interesting, and I disagree with some of the other commenters here that that should only exist in an IDE, but the java limitation makes that just a novelty for us.

Particularly though the gerrit-style workflow and the rules engine for permissions is enticing. We'd love to move to something like gerrit but don't want to give up the friendliness of bitbucket/github.

Nice job.

Taking the HN comment community out of the context of the site makes it no different than any other drive-by commenting platform.

This thought process: "HN Comments are great. I want comments on my site. Other comment systems are terrible. I'll put HN comments on my site". Misses the point of why HN comments are great and why these comments-as-a-platform services have all resulted in the same level of awful, despite repeated and varying attempts to solve the problem.

Put a link to HN comments in your footer, bring them here, let the community and the mods help shape the discussion. Don't take the HN conversation out of context and splat it across the web.

If you want federated comments, use one of the existing, awful, toxic commenting systems that inevitably result from that sort of usage.

One of the reasons that HN comment threads are still mostly worthwhile when other sites and comment services are swamp fires is the community that has been built here.

That people have to come here to read and reply helps us form that community and our social norms.

Sometimes it's ok to remain a small club.

It would only be revenue neutral if they had raised the absolute rates to make up for the fact that an increasing number of people are paying under the current rate.

One thing that also should be mentioned: while it's perfectly ok to want your city to stay the same, it's not practical to put the burden of growth on other cities. And it's also not legal. California law actually requires municipalities to plan for and support their share of new housing[1]. Something many cities are not doing.

[1] http://wwwww.ppic.org/content/pubs/report/R_203PLR.pdf

I think it would also be useful to survey people who looked into using Rust but decided against using it, as responses from people who suffered through the warts is analogous to looking at the damage to bombers that made it back to base. Still relevant, but not the whole picture.

I'd expect to see mobile/cross-compilation (which I know is getting better) to rank pretty high among people who didn't stick with it, but maybe I'm projecting.