I wonder if people have come around to the touchbar. It was almost universally derided on HN when it became a thing. Personally, I haven't, which is one of the reasons I'm glad I switched to the M1 Macbook Air which doesn't have the touchbar. Now I can change the volume and the brightness without having to look down!
I never used it, but I'd love to try. I think that it's a great concept, because I rarely use Fx buttons, I can't memorize them. They're useful for debuggers, but every IDE defines them differently, so I just gave up. I think that I'd love this feature and it's sad to see it gone, I'm considering buying M1 Macbook 16" and according to rumors it'll have ordinary keyboard.
Of course Esc must be a separate physical key, but they did it right in the latest revisions.
I’m on the side that mostly dislikes touch bar (although my opinion is nowhere that extreme. Slight preference at best).
But I tell you what, it was the first time in my 30 years of being around computers that I had to reinstall the OS because my Esc key disappeared. No joke.
Even tried contacting Apple support.. nobody was able to help me to reset settings and make Esc come back. I think that’s kinda hilarious situation.
There is some weird point to your comment. If the touchbar was truly useful/successful it would be on the Magic Keyboard.
Due to laws regarding workplace ergonomic you’re required to have a real keyboard, you cannot use the one on the laptop (this is in Denmark). That means that the Magic Keyboard is a requirement in professional settings. The touchbar therefor is specifically NOT for professional use, it’s not available.
I think if “anyone” actually cared for it, they’d have offered it. I don’t see them introducing a pro-pro-keyboard with Touch ID plus Touch Bar in addition to one with just Touch ID, but I can imagine a world where only an upgrade with both existed.
For example you could convert the heat into photons (infrared radiation) and beam that out of the room without needing a pipe. You would probably need an infrared transparent patch on the window to aim at.
You can’t. The second law of thermodynamics prohibits it.
“It is impossible to devise a cyclically operating device, the sole effect of which is to absorb energy in the form of heat from a single thermal reservoir and to deliver an equivalent amount of work.”
Nitpick on nitpick -- you absolutely can convert heat energy into electric energy. A dynamo on a heat engine does exactly that. What suffices is temperature differential.
It is a terrible analogy, a modern physicist would prefer being caught dead rather than using it, but one can think of heat as a liquid (traditionally called caloric ) stored in a vessel. Temperature is the level of the liquid. For flow you need another vessel where the level is low, that would allow flow of heat from a vessel with higher level to a lower one and one can then convert that flow into power of a form one desires. Its possible to go in the opposite direction also, that's called a heat pump. Charge and voltage would be another (incorrect) way of thinking about heat and temperature.
If you want to do real-world things, like change your project settings across different compilation targets (AppCode has a buggy/incomplete settings interface that can't be trusted), use the interface builder (inc. previewing your UI, inc. creating/editing the UI if you're not using SwiftUI), debugging the UI hierarchy, performance profiling, etc., you'll be switching over to Xcode. Once again, in theory you could just have everything running off whatever `make` toolchain you prefer, but if you're making apps for a company, and sharing code with other team members, chances are your exotic setup isn't going to cut it.
i think people might be conflating needing to install xcode vs launching xcode
if you want to build ios apps installing xcode is a requirement (to get the proprietary cli tools) but launching xcode is not required
to build native mac apps, neither installing nor running xcode is necessary, as you can build with the smaller cli-only tools which include only mac os headers/libs
The two are added with some extra protections. Something that cannot be done with git-checkout without breaking scripts.
I believe git-checkout could silently overwrite data in one case (can't remembe the details). And git-swith will stop you from moving the branch when you're in a middle of a rebase or other multi-command operations. It also tries to avoid entering detached HEAD mode by default.
It's definitely geared towards newcomers. But even I'm glad it catches me from doing stupid things from time to time.
The problem is that this breaks down when you specify both arguments. Doing `git checkout branch file` checks out file from branch to the working tree, but doesn't change HEAD.
And apple shouldn't bribe politicians nor use their immense wealth and power to lock down supply chains, driving out competition. Free market is an imaginary concept that has never existed nor never will.
Nor Raytheon, Lockheed Martin should lobby politicians for bigger defense budgets, etc... But that's how it goes. Not using Apple products and telling all your friends/family to not use it either is a good start. Go and be that guy.
