Hacker Newsnew | past | comments | ask | show | jobs | submit | bkdbkd's commentslogin

It forces a change, where none is called for. Compatibility works both ways. What doesn't matter to me the lib dev, may for matter for someone else. The world is built on portable, flexible code, and pinning to something unnecessarily, breaks that one small part of the world. It's adding an unnecessary requirement. Life is hard enough.

Couldn't agree more.

that is not a thing. it's not how compilers work.

Strictly speaking it does as miscompilations are a thing.

Furthermore the go version covers the stdlib so any bug there is resolved thus, and for obvious reasons those generally do not affect compilation.

I do not think this is a very compelling argument or likely to be an actual concern, but it is a thing.


Awesome. Well done.


really really awesome.


"That 3000 dollar tool you paid us for? It's a brick." -Tim Apple


> Of course, Intel Macs will continue to get critical security updates for some time thereafter. But users should not expect to be able to update to get new features from macOS 27 onwards

Crazy to see how fast Intel got dethroned. ARM on the server is cheaper for the same performance, and the M* is unbelievably faster at the lower energy budget of a laptop.


It’s a brick, except a brick that can do the vast majority of things a laptop can do other than update to the newest OS and install the very latest software?


You might find the book: "Conceptual Blockbusting", James L. Adams helpful. It contains thoughts and activities that focus on the 'process of thinking' or problem solving. And how we go about characterizing a problem or situation.

One of the best I've read on how to think about thinking.


former Mac dev here, and completely agreed. Refactoring an app because someone else decided to change the language is a bridge to far. And if they do it this time, they'll do it again. Meanwhile the ObjC compiles.

--- Rant - With Swift Apple shifted dev power to themselves. Having gotten fat on the open world, they've backed away from every 'Open' technology they can, and replaced it with their own, ( presently all the way to CPU architecture). Yes, they are giving tremendous powers, but have they also crafted the One Ring.


Yes, but it is common for new languages and frameworks for there to be lots of change in the first few version. Then it matures and settles down. AFAIK Swift is not regularly making large changes, anymore.


Go wasn’t that way, in some respects it is a language design choice whether you want to retain compatibility


Foundation is now open source at least


I'm a sw eng. and sometimes I just need to hear the drums from "In the air tonight". Sharing in case anyone else does.


Yes, Great analogy. Remember the 2017 "Apple Commits to Pro Users" exercise? They flew reporters out for a boondoggle, gave them a tour of 'secret labs. With fresh competitive hardware coming 'real soon now'. Just spin.

https://daringfireball.net/2017/04/the_mac_pro_lives https://www.buzzfeednews.com/article/johnpaczkowski/apple-sa...


This ^^


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: