I've followed the gme saga off and on for the past few months, I've never once seen the theory debunked. If this is actually the case, could you post a link to it?
IMO Swift is a language written by a compiler guy to solve compiler problems. the syntax is dense because it forces you to make a lot of decisions that could otherwise go unmade in objc.
If a variable is read-only, you're forced to think about that by deciding between let/var. contrast this with objc, where all vars are writable unless you do the extra work of adding the const keyword. objc makes us do more work to get the faster (and safer) behavior.
Similar with Optionals, you're now forced to decide right away if a parameter can ever be nil, whereas with objc you didn't need to declare nullability. Again, it makes the safest and fastest choice easier to make, and allowing nullability is actually more work.
Generally Swift forces you to pass as much information to the compiler as possible at compile time, and it does it with a delightfully readable syntax. This theme repeats itself throughout the language. more information at compile time is always going to result in safer and more predictable behavior.
full disclosure: i'm an iOS dev working in objc and swift. i love both languages, and i think swift is the obvious path forward.
another Brooklynite here. this is 100% true. You absolutely needed to "trick" the driver into letting you into the car. I've had taxis drive off, or refuse to let me in. When I was in the car, they would say they can't take me to my destination because their "shift was ending" and they had to go in a different direction. Many of these incidents happened in the LES, which is right next to the bridge I had to cross!
Taxi drivers also never know the destination, I got pretty good at giving my directions speech (to a well known neighborhood)
And taxis cost more!
As far as I'm concerned, the old way of hailing can rot, the old taxis can rot. they can't hold a candle to uber, and they'll never be able to become competitive on price or quality given the cost of a medallion.
ports put a limit on how thin the laptop can be. a VGA connection can't get smaller, an RJ-45 jack can't get smaller. the dimensions of the laptop define how realistically "portable" it may be, which is ostensibly the main argument for laptops in the first place.
HR could totally act in the way the article describes. They exist to protect the interests of the organization, and to minimize boat-rocking. It would be easy for HR to dismiss her claims in the very same way that you are. Before we start down the path of victim-blaming, lets at least consider the possibility her claims are valid.
I don't understand the couple other posters who are dismissing this article. it is exactly what it claims to be, a practical introduction to functional programming.
I'd also like to echo poster vvanders sentiments about Rust and how it compliments the functional style. I've experienced the same feelings, although I did it while working in Swift.
And for those out there asking "why is FP better", I submit that it allows for fewer ways for me to shoot myself in the foot.
this "article" reads like it was written as propaganda by in-house HR to retain staff.
3% is basically a non-raise, it just keeps up with inflation. an extra 5% is alright, but is not adequate to retain talent who knows their worth.
i once received an annual raise was 2.5%. i pushed back a bit but not too hard, as i've done this enough times to know that it is never worth the amount of stress involved.
fast forward a few months, i'm walking out the door to a new gig with a signifigant increase (lets say 20%).
old mgmt didnt see it coming, despite the ample warning i gave them, and ample opportunities to correct the situation.
they never do, just accept it and move on
this is strictly anecdotal, but i just was notified of a pending charge to my credit card, for ~$1000. The charge was from stripe, and I've only ever had transactions processed through stripe for 1 transaction, with 1 vendor.
so either the vendor screwed up, or something is insecure..
This is a great point as well, and I wish I did a better job articulating that in my own comment.
Ultimately, there is nothing noble about "good hardware" in a vacuum. Hardware and software can achieve nobility only when they're serving humanity, be them rich or poor, technical or non-technical.
I just can't bring myself to feel the author's anger, in any capacity. He wants to position this as a jab against those who build their own PCs, but that is utterly irrelevant. What percentage of those 600 million five-year-old PCs do you really think are being thoughtfully maintained by modders? Does the author realize that most people do not want the responsibility of maintaining their own hardware? Or that they don't have the knowledge to do so?
Allow me to paint a more realistic picture: many of those PCs are junky, dusty boxes, running some outdated version of windows, filled with bloatware and riddled with security issues. Inside them are a bunch of spinning platters just waiting to fail. And when they do eventually fail (due to wear, or a virus, et al), someone's Grandmother is going to be shit out of luck, with no way to get at her email, saved photos, or anything else.
A properly configured iPad, leveraging iCloud for device backups, photo backups, email credentials etc, solves all of these problems. And they'll even configure the iPad for you in the store, so grandma doesn't need to know how to do any of it. Do YOU want to be the poor sap attempting data recovery on a failed disk, then realizing that even if you do recover grandma's data, you've still got to go buy a replacement drive, find a copy of windows that grandma knows how to recognize, and install everything exactly as it was before you got there? I've been that guy before, in both a personal and professional capacity. You will eventually fail, memories will be lost, tears will be shed.
We must not gloss over the fact that the iOS ecosystem does solve some very real pain points for real people.
Take-home projects can be a double edged sword... for a given project that is estimated to take 4 hrs, i will typically spend about 16 hours on it. working straight through the night, chugging coffee and/or beer. I work by banging out an ugly PoC, and then I refine it drastically over several iterations. My final versions are award-worthy, but the early ones are really bad and sloppy. I am the type that is great at simplifying, but bad at coming up with the initial statement.
If bar is nil, you'll get a runtime error "unexpectedly found nil when unwrapping bar"
in my opinion, the benefit of optionals in general is that it allows you to guarantee at compile time that certain variables (non optionals) will _never_ be nil, which enables all kinds of compiler optimizations.
I remember being dumbfounded when they announced they were removing check-in functionality. It was the main thing I associated with the Foursquare "brand" and I was a heavy check-in user at the time (the game mechanics were great).
They must have known everyone was there for the check-ins, and it seemed arrogant of them to believe they could force all their users to migrate to some other app. (talk about shooting yourself in the foot)
I never downloaded Swarm on principle (i can check in with the Facebook app if i really want to). Foursquare did this to themselves.