It's a script that installs all kinds of useful stuff and sets some - in my opinion - nice options. I just recently started a new job and I had a brand new Macbook Pro up and running (as in: ready to start working) in less than 30 minutes.
A good tip is to fork it and modify it to your liking. At a new computer you can then just pull down your version and install away.
So the ironic part is this script would no longer work after these deprecations because installing Homebrew requires a Ruby interpreter[0].
Obviously these things are fixable but a whole lot of people are going to have to do a lot of work to workaround having _no_ scripting languages installed by default on a fresh Mac.
> Once Homebrew no longer has to support a macOS with a system ruby, we can even run with a considerably more up-to-date version, modulo concerns for supporting older linux(brew) OSes. We have a portable ruby that we can use to bootstrap things.
This is the first time I've seen somebody else complain about the arrow keys and I completely agree.
It's by far the most infuriating aspect of this new keyboard.
Another thing that I have a hard time explaining is my inability to orientate myself on this keyboard; several times a day I have to move the laptop around, look at the keys and "reset" myself to the keyboard. I don't know what that's about but I've only ever experienced it on this keyboard.
My personal machine is a 2014 MBP which will be replaced with something other than a mac once the time comes.
I hate my MBP arrow keys, but unless I'm doing a little work from home or in a meeting I never use the keyboard, instead I have a full size apple keyboard that I love and use with the macbook in clamshell mode hooked up to a dell 4k.
I'm probably not buying a new macbook pro for a long time... it's just not worth it to have such a high end machine that I use as a glorified traveling mac mini.
For my next work upgrade I am requesting a linux laptop.
uh, the pictures of a tiny rice-sized chip from the story were just photo illustrations. They were not supposed to be evidence of anything. It said so in the margins.
It makes perfect sense to me. I love the graphics that illustrate what the docs relate to. I don't need to do a lot of prior reading to grasp the lexicon being used.
Tesla went in the opposite direction, the anti-Prius design. Maybe it was intentional, but when I see a Tesla on the road (in the Midwest, not super common like in California), I have to really look at it while I ask myself "is that a Tesla?" because from some angles it could be a Jaguar, a BMW, an Audi, any generic luxury car. Nothing about it screams "look at me!", it seems designed to blend in.
There's nothing wrong with that approach, just presenting you with a counter-point. One of the most successful EVs on the market is intentionally designed to stand out in a crowd (the Prius) while another is (I think intentionally) designed to not stand out.
In some cases it's because the "unusual" design is actually more aerodynamic, so they are taking advantage of the "this is totally new and different" thing to finally push those changes out and make them acceptable. Like the wheel covers on the Honda EVs. They would actually make the ICE cars more efficient too, but people just get turned off by the look.
It comes and goes but every so often you get a generation of cars looking kinda weird. The logic is that it's better to inspire a reaction, postive or negative rather than being beige.
I think that they are incredibly difficult to find and most people (me included) can't identify "problems" in their day to day that could be improved by something - in hindsight - relatively simple.
I'm constantly asking myself: where are the pain-points in my daily interactions with computers/software etc.
So far there's nothing and I know that can't be true.
A big part of this is when you work on computers / with software all day, you're looking for pain points in the same place that most other developers are looking. There is certainly room for improvements in this market but it's generally much more saturated than others. (Hence the common advice to go work or talk with people out of the industry for awhile.)
Otherwise the best advice I'd give for finding problems is to start making a log of every time you get annoyed or frustrated at something. Your package didn't get delivered on time, you realize you have no milk when you're in the middle of cooking a meal, a driver on the highway is endangering people, your phone is too big for your pocket, radio stations all seem to play commercials at the exact same time, your home ran out of heating oil and no one will deliver until Monday, your hard drive failed and you realized your backup program wasn't including a new folder of vacation photos, even though you make an appointment at the barber/doctor every time you show up on time you show up you still wait 15-20 minutes, there's no Mexican restaurants that deliver to your house, you never know how your child is doing in school until they get their report card at the end of the semester.
There are dozens of tiny annoyances that we run into every day. Some have easy solutions, some less so, but they're there if you know what to look for.
That's because thinking of it in terms of pain point isn't necessarily helpful, since people have different "pain tolerance" when it comes to technology.
Try to think of it in terms of outcomes.
What are you trying to do with computers/software, and how could the outcome be massively improved/democratized?
Im a bit jealous of people building a billion dollar business that solves a problem that could literally be solved in ten minutes. The business are rarely about a better solution, its more about a better business model and better marketing!
Better marketing sometimes is the better business model.
Can you do basic scripting? Can you do advanced scripting, with such revolutionary capabilities as calling out to external APIs for stuff like OCR?
Then rejoice! As you have the potential to make your very own billion dollar business[1]! Just leverage those skills for process automation, market it as "software robots", leverage the existing perception of "robot replaces human" to make the recurring $10k/year cost for your automation script seem like a steal compared to the labor costs of a human, and through in some AI references for a bonus multiplier on your valuation potential.
Process improvement and automation has been a thing for ages. Marketing it as "software robots" is much newer. Turns out that particular phrase resonates really well with the target market.
This is compelling. I like the "pay as you go" model for data. I'm on an iPhone though and do enjoy visual voicemail - I wonder how much I would miss it? I also wonder what their beta status for iOS means and what their roadmap looks like.
I loved this app for a long time because it was the only one (that I found) that would cache comment threads on the device - this meant I could read comments on the subway and/or without access to the internet.
A few months ago the app was rewritten in Swift and lost my most treasured feature, not that it matters anymore.
Thanks for the years of connectivity-anxiety free comment reading!
Edit: If you do get passed this (I really hope you do) please consider adding an option that would fetch and save comments on the device. I'll pay for it.
I think Materialistic (a popular HN app for Android) does this. I can't remember getting "you need to be online" error ever, it just uses whatever comments cached last time I updated. I don't know if it has an iOS version.
It reminded me a lot of: https://acko.net/blog/animate-your-way-to-glory/