general_ai

Really, you call this "reasonable SIMD" access: https://msdn.microsoft.com/en-us/library/system.numerics(v=v...? For comparison get a load of Apple Accelerate: https://developer.apple.com/reference/accelerate. Now that's "reasonable" SIMD access, and extremely heavily optimized on both macOS and iOS for both speed and power efficiency. Similar capabilities are just one command line incantation away in Linux. And if that's not enough, you get real, actual assembly, not some "IL assembly" where you have no control over what it will emit when converted to machine code.

Here's another constraint you may have failed to consider: my code doesn't just run on Windows. I compile the same C++ code across all supported platforms with fairly minimal #ifdefs to adjust to platforms and SIMD ISA. Windows is the only platform that fights me every step of the way. Linux is great. macOS is great. iOS and Android are great. Goddamned bare metal is great (cross-compiling on Linux). UWP is awful and hostile.

C# maybe. But C# is not suitable for what I do (fast deep learning on video, images, and audio). Any kind of managed language is hostile to those kinds of things and just plain not designed for them. I want to drop down to SIMD intrinsics and assembly when I need perf, and C# won't let me do so.

But I think even folks with much more modest needs suffer with UWP. For instance, try to load an image from your hard drive (using UWP C++), resize it with Lanczos and get access to its pixels. The API is a fucking nightmare, there's no way to resize an image that I could find (unless you want to show it in the UI, in which case all is taken care of for you, but you can't get pixels from there). On macOS/iOS, it's just a few lines of rather plain looking code.

Having actually used UWP SDK for C++ fairly recently, I was left with the impression that it's a complete non-starter for most folks. It assumes too much skill on the part of the developer (i.e. "everything is asynchronous"), it uses a significantly extended superset of C++, and it inexplicably comes with _no_ libraries for such basic things as image processing, signal processing, linear algebra, etc -- stuff that Apple knocks out of the park. It's just basically WPF and very little else. Enough perhaps to write business apps, but way inadequate for anything outside this narrow niche. And because everything is async, and UI uses opaque data binding, the debugging experience tends to be a bit of a nightmare. I'm not sure what Microsoft was thinking, but Apple's approach to async (concurrent and serial queues in GCD) is an order of magnitude easier to understand, use, and debug, and OS X and iOS SDKs come with a ton more high quality features.

I'm not even talking about the article per se. I'm more taken aback by people here saying that if after 10 years of marriage, with career and kids to contend with, you're not having sex every day you're somehow a failure and your relationship is doomed. Could it be that this is not all there is to life? Could it be that a marriage can be quite all right without much stereotypical "romance"? Could it be that people are just different and some of them are quite fine with having no romance or sex for that matter for months at a time? That's something that takes some time and life experience to absorb. In particular, it's not "sad" to be consumed by kids and/or career if that's something you both want. My wife and I have been married for 17 years and "consumed" by kids and careers for 15. We open a bottle of wine every Friday, we go out to a restaurant every now and then -- that's the extent of our "romance" at this point. And you know what? It's great for both of us.

Before someone jumps in with manufactured outrage, no, I don't suggest that you ignore your partner or tolerate the lack of "romance" from their side. If that's something you (or they) need in your life, by all means, hash it out and have a mutually agreeable relationship. Just realize that some people are quite happy in other circumstances.

One does not preclude another.

As someone in late 30's, I look at this thread and shake my head. Folks, you can't apply your own stereotypes to everyone's situation. What's a "healthy" relationship to some is completely unsustainable for others. What's "romance" to some is neglect to others. People's needs differ, and not only you don't have to conform to stereotypical norms in your private life, you simply can't do it: it'd require too much willpower.

So, TL;DR: don't tell me what's "healthy" and "normal". And coincidentally, I greet my cat first when I get home, and my wife doesn't mind.

And the beauty of this is, launching these Iridium satellites is just a beta test for what they're going to do next: launch _four thousand_ of their own satellites which will blanket the planet with gigabit broadband.

250k is way too low a threshold. I'd put it at at least a million, if not more. But hey, it'll all be repealed shortly anyway, so who cares.

The game has moved from devices to services those devices provide. Having those services costs billions of dollars per year, to both keep up on the data side and to pay a small army of extremely in-demand engineers. And then, unless you're Apple or Samsung, the only significant profit stream is ads, since people have been conditioned by Google that services should be "free". I don't care how much of a genius Andy is, there's no way to really win this one.

Nope. There's just no way it can compete against Apple, Google _and_ Samsung, also known as the only three companies that make money on mobile. Andy or no Andy, you just can't enter this market anymore.

A fine example of confirmation bias: ACA aligns with Sam's ideological position, so he hand picks some examples to support it. Don't get me wrong, I think it's great that people with preexisting conditions can't be denied coverage. But is it OK that plans are three times more expensive now, with three times the deductible? I don't think so. Seems like a trillion dollar money trough for Big Pharma and Big Insurance to me.

No, those it'll probably still report (although I don't know, Jeff could forbid it: it's his personal blog, he will print what he wants).

It'll just stop taking things out of context and manufacturing outrage to generate clicks.

What do you mean "killed that"? The option is still there, it's just not easy to find. Click on the triangle next to "View Profile As" button.

I just export my LinkedIn profile as PDF, references and all. Have no trouble whatsoever landing great jobs.

Java's hunger for memory, combined with Haskell's unpredictability wrt memory allocations due to laziness. What could possibly go wrong.

As Alexander Pushkin(a famous Russian poet) wrote in one of his poems: "Oh it is not hard to fool me, for I am eager to be fooled."

If your quality of life is determined solely by walkability, then sure, you'd consider it "high". In the USSR things were walkable out of necessity: not everyone had cars. And besides, if you're building a block of high rises (stuffed with tiny 650sqft apartments, for the proletariat) and estimate there will be 1K kids, you might as well build a school, a drug store and a grocery store in the middle. Swimming pool within a walking distance was a rather extravagant luxury, not everyone had that. Shit, I hadn't even seen a real swimming pool until I started college. Woods, sure, that's kinda nice.

My point being, you make it sound like every town in the USSR was like that whereas in reality what you're describing sounds like a "unicorn" situation that was rarely encountered in reality. Walkability was about the only thing Soviet urban planning had going for it. Ironically, these days I live in US suburbia within walking distance of a pool, elementary/middle/high school, and a convenience store. And woods too: we pretty regularly see deer in our back yard.

Even at Google most people knew this project was stillborn. It's a combination of two factors: no one but a few geeks actually has any need for this, and the overwhelming majority of profits in the industry is taken by a company that builds the opposite of Ara, further underscoring the former point. It terms of flushing money down the drain it ranks way up there with Google Glass and Project Loon.

How does it compare to Google Kythe (internally known as Code Search): https://github.com/google/kythe?

For anything above Haswell the only things that matter are core count, frequency and whether it has hyperthreading. There haven't been any notable improvements to per-core perf since Haswell.

The only example that I know of in support of vostok's statement are a couple of HFT trading firms in Chicago. If you have the right chops, your comp _starts_ at 500K there, and then quickly goes up to about $1M/yr. But you do need elite chops, and you do have to live in Chicago, and you do have to work in an HFT firm, which is, shall we say, not for everybody.

Could be. I just couldn't find any such jobs, even after 8 years at Google, which tends to improve one's chances of finding a top paying job.

Outside of a small handful of areas (SV, Seattle, NY, a few others), it's very difficult to find anything in the $300K+ "total package" range. In SV all you have to do is get yourself hired by one of the top firms and then stay in the saddle while your stock vests and not suck too bad. Voila, 400K a year (much of which you will pay in taxes, but nonetheless). I challenge anyone to find a non-manager software engineering job that pays mid six figures in the Midwest.

Serves me right for not reading the article more carefully. Their proposal is, nevertheless, wrong in its approach to the problem. This can only be solved by putting constraints on the influx and removing constraints on mobility of the people the US does let in. With these two things in place, the rest of the issues will take care of themselves. As proposed $100K isn't much of a deterrent for abuse, seeing that even with $100K+ pay there's a shortage of _entry level_ talent in CA.

The equilibrium will be reached at a much lower price point than in the case of restricted supply of talent. Whole industries restrict the supply of workers for that reason: CPA, lawyers, and dentists being three prime examples.

People like to pretend that most things can be trivially outsourced, but that's not the case at all. Managing a team down the hallway is hard enough. Managing a team in another timezone requires the kind of skill not commonly found in US corporations.

Long time reader, first time poster. Both lawmakers being Califoria democrats, I don't trust this one bit. Hear me out on this one. I have actually experienced the H1B system on my own hide.

As others have mentioned in the comments, today H1B is basically indentured servitude visa. While theoretically you can move to another job, few people dare, especially if they have families, because in case of any screwup whatsoever, you have to leave the country within 2 weeks. That's _insane_. When I was H1-B I chose to wait until I got the green card before making any moves. That took 8 years, during which I did not quite made the kind of career progress I was hoping for. Now that I'm not an H1B, _magically_ I have no problems whatsoever with advancing my career. What a bizarre coincidence.

And I'm not Asian, for Asians it takes longer than that. Another type of abuse you often see (and that was the case with me) is companies hire a very experienced worker in a much lower level position than he ought to be in, considering the experience, and then keep them there until they either work up the courage to move, or get the green card.

The _real_ fix for this should be two fold:

1. Allow H1Bs to move more freely between jobs. If you're a programmer, you should be able to move into e.g. DevOps or Data Science, or DB administration without risking that some bureaucrat decides that's not an eligible transition.

2. Allow more time for them to do so, so they don't have to find another job before leaving their current one. Six months to a year ought to be enough. Implement a cliff of e.g. 1 year to make this more fair to employers if need be, but don't kick families out of the country in 2 weeks just because the breadwinner can't tolerate the abuse anymore.

This will make the market for H1B workers price-competitive with native workers (since they will be able to command market rates given their levels of experience), and DRAMATICALLY reduce abuse. That's literally all that needs to be done. This will also make it easier for people just out of school to get well paid jobs that would today be taken by overqualified and underpaid H1Bs, because the employer will not be able to exploit their ignorance of the job market for long.

Instead they are proposing some tactical bullshit that will only get in the way of a more comprehensive reform that the Trump administration might (or might not, the election is over) come up with.