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

1. because they know better. You don't have to understand it, for them to be right.

This comes from their years of experience. When you also get those years of experience, you may come to similar understanding.


Funny how a $20 cert is enough to prove identity and provide security for any domain on the web, but in order to run a calculator Apple hw, Apple HQ is the only entity on the planet capable of such complex security.


Contempt. use any apple device 2 updates back or more. you're screwed.

You would accept this in no other place in life, except that apple gives it for free, and puts a 'security' sticker on the box.

It's a racket. Planned obsolescence 2.0 - Users forced to update, update removes features, breaks working apps, breaks paid for ip ( literally removed from phones), apple blames the devs. bullshit.


It is a shame that you can't choose to get security updates only without app-breaking feature changes. So you have to update (because security, actively exploited vulnerabilities, etc.) but then your apps (mostly paid apps in my case since I dislike subscriptions and obnoxious f2p monetization schemes) break.


It mostly works?


yes. and it's what I use every day.

the plan evil though.


All that, and not a single one here is surprised at zero days or trojans or malware that come right out of this process every week.

If it works, then why aren't we surprise when it doesn't?

Because we know it doesn't work.


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.


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

Search: