Also saying Apple reinvented the cursor is a bit much. Highlighting elements, snapping, and changing the cursor weren't just invented. The author really bought into Apple's marketing here.
35 karma · joined July 13, 2017
Also saying Apple reinvented the cursor is a bit much. Highlighting elements, snapping, and changing the cursor weren't just invented. The author really bought into Apple's marketing here.
Memory fragmentation is another legit concern I guess, as far as I can remember iOS has no memory compaction. Again not a necessarily an issue for a short live user space application, it is a larger one than memory leaks at least at my company. In some hot spots of our app we specifically slow down reading of some queries to reduce memory fragmentation.
Frankly Chris Lattner's claim that a GC leads to 2x-3x memory consumption over ARC is unfounded and sorta shocking coming from someone held is such high esteem. It's something thats continually shown to be untrue.
It always seems Swift's biggest selling point is it uses ARC instead of a GC, which is either not a large issue or a GC is actually more beneficial. Other than that you still haven't dealt with the toxic "Swifty" community, the terrible tooling situation, the immature libraries and frameworks, etc, etc.
There seems to be so many better solutions to writing server side code. This is all coming from someone who uses the language on a daily basis.
ARC would be just one my issues using Swift outside of iOS.
I think you are overstating the pause duration of a modern GC. I have used both Go and the JVM server side, not at a huge scale but enough to see GC effecting response times. They add some fluctuate, but nothing compared to network latency or the multitude of other factors that fluctuate heavily. It was never significantly relevant for response times. I'm looking at my server logs right now and theres not even a real correlation between GC and response time. Unless you are considering a 0-10ms fluctuation.
If you are interested in using an ARC server side I know Kotlin Native is using ARC however their implementation eliminates the cyclical reference issue.
-Note- I'm not saying one is better than the other. ARC works great on iOS for creating applications.
So I have considered F#, but it doesn't seem that compelling. Also it seems like the tooling is worse on other platforms.
I can imagine this is an especially important advancement for server side JS. Not something I personally care about tho.
The hype machine surrounding Apple did not want to hear this and were just caught up with the idea "Apple could data mine you while maintaining ur privacy".
I don't think this is the case. The letter comes off as very genuine. It very much feels like what a immature "tech bro" would write. So much so when I first read it, I only skimmed it because it was so drab. You could have been at a bar surrounded by a bunch of drunk tech employees and heard very much the same thing. I only read it in entirety after the buzz got to loud to ignore.
Also I don't think there's a good chance he'll win a discrimination case against Google.
I'm not sure whether or not he deserved to get fired. Sundar's response was well written and is worth reading Damore, however childish his written seems, is not young and has worked at Google for four years. He's by no means a junior engineer. At the very least the lack of understand of software development speaks for something.
"And let us be clear that, yes, such policies mean every once in a while you will not hire the most skilled person for a job. Therefore, a value judgement must be made here, not a logical deduction from data. Is diversity important enough for you to temporarily tolerate an increased risk of not hiring the most qualified person? That’s the trade-off nobody seems willing to spell out."
This is not how "affirmative action" works. "Affirmative action" states that if you have two "equally" qualified candidates you favor the least represented in your society or company. Thus there should be no added risk.