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.
"P.S.: I'm unsure why anyone would think that this has anything to do with the Objective-C runtime. I guess it may if you pass any kind of ARC objects."
Because the comment on the commit that adds this to the swift source states that "It relies on ObjC interop".
Exposing a c function from an objective-c file, and then calling into our swift code from there is what we've been doing since before this feature was enabled. That of course also requires the Objective C runtime, but we haven't changed to @_cdecl mainly because I'm more worried about the behavior changing than I am about anyone trying to run our swift code on Linux.
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.
Old media is still producing the content. Netflix doesn't own lots, or cameras, or catering trucks. This is predominantly a change to financing and a change to what type of shows get produced. It's not a change to who produces them.
What's interesting to me is that while Netflix is often the primary financier, the traditional studios are still the ones producing the 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.
It was happening well before the tech boom. Venice was the last stretch of cheap sand in 200 miles, it was going to gentrify with or without Google or snap or any particular industry.
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.
Back in the '90s some government agency released a redacted report where someone had gone in and drawn black boxes in the PDF file, but the full text was of course still in the underlying data and people were able to get at it relatively easily.
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.
Likely because buying the rights to broadcast sports is expensive, free-associating talking heads are cheap, and subscriber revenue is down.
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.
Very impressive. This has some features we've been missing in bitbucket/gitlab/github and it looks like the UI is well thought out and still simple.
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.
It's how it grows, and whether growth is the priority.
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.
Sure but it's always "medium term": Taxes weren't fixed once, they are fixed at time of house purchase (and some other events).
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 of the reasons that cities build office space while ignoring residential is Prop 13 which fixes residential property taxes. Taxes on equivalent office space and the business it generates are a better source of revenue over time for cities than the fixed taxes from housing. This disincentivizes balanced planning.
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.
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.
https://en.m.wikipedia.org/wiki/Männergarten