Wonderful, that leaves 2 things on the top of my list for spaces: having to hover your mouse over the top left corner of a space and waiting until it shows the closing icon. And Safari deciding its better to switch to a space and open a window that was minimised there instead of just opening a new window in the space i'm currently in (even with the "switch to a space" setting turned off!) when 1 want to open a new tab.
If you hold command while you restore the window from the dock it will restore into the current space. I wish i knew how to make this the default. Getting whisked away to a random space is one of the most irritating issues. Like when you want a finder window for downloads and instead of a new window in the current space you get taken cross country to on thats already open.
Thanks! Now I'm curious of all the places where there are still hidden Options key features that I haven't discovered yet. It's just everywhere, but so undiscoverable.
At least the setting does work in reducing the switching when you cmd-tab to an application with no open windows in the current space. But I think some of this annoying switching behaviour is application specific logic and they just didn't get it right with Safari, some other applications do get it right though.
Except that for macOS it uses the FileProvider Framework. So files that are rarely accessed get deleted from your local storage and synced back automagically when you access them. Saving space on your disk because on mac you can’t upgrade your ssd without a soldering iron.
> If you are using it to write code, you really care about correctness and can see when it is wrong.
I heavily doubt that. A lot of people only care if it works. Just push out features and finish tickets as fast as possible. The LLM generates a lot of code so it must be correct, right? In the meantime only the happy path is verified, but all the ways things can go wrong are ignored or muffled away in lots of complexity that just makes the code look impressive but doesn’t really add anything in terms of structure, architecture or understanding of the domain problem. Tests are generated but often mock the important parts the do need the testing. Typing issues are just casted away without thinking about why there might be a type error. It’s all short term gain but long term pain.
Well it 'working' is a part of it being correct. That is still something of a guardrail on the AI completely returning garbage output.
Also, your point is true of non-AI code, too. A lot of people write bad code, and don't check for non-happy path behavior, and don't have good test coverage, etc.
If you are an expert programmer and learn how to use AI properly, you can get it to generate all of those things correctly. You can guide it towards writing proper tests that check edge cases and not just the happy path.
I think a lot of people are having great success by doing this. I know I am.
>>Next, Apple does not respect the multiple desktop boundary...
> This is a configurable setting.
If you mean the "When switching to an application, switch to a Space with open windows for the application" settings, this works only partially. When clicking the dock icon its behaviour depends on if there are windows in your current Space (virtual desktop) or not. And don't get me started on where macOS decides new windows should go.
Reminds me of that time I was taking climbing lessons in the Belgian Ardennes. Helmet on, in harness, hanging in the ropes, holding tight to not fall, we where climbing half way up the mountain, when a person out of nowhere ask if he can pass and just flew up the key section of the route. It was just a local, casual clothes, no harness, no helmet, no rope, maybe not even proper climbing shoes but I can't recall that. Just casually climbing the mountain like he was on a lunch stroll. Even now with years of experience I still don't have that confidence.
I consider myself a little techy, since I visit this site quite often. But for me YouTube is curing me from my addiction to it by ramping up its ad blocker blockers. I know I have to wait roughly the ad’s runtime looking at a frozen video before the video actually starts playing and it is often enough to let me go do something productive or useful instead. Thanks google :)
Yeah exactly, sometimes I just give up entirely. If it's a podcast I might persist, otherwise it's just not worth it.
The compromise for Google would be to limit ad-blocker users to a reduced quality version to save on bandwidth...
After using Peertube, it would make a lot of sense if pretty much all media assets went the way of decentralisation. It lowers bandwidth, reduces server overhead and increases availability.
It’s very simple: format code to a standard. Preferably the language default formatting. But it must be a standard that can be auto formatted to with a tool. Now when someone doesn’t like that standard, they can auto format from that standard to one of their liking for local development and back again to the project standard for pushing to the project. This can even be done automatically with gitattributes during checkout and commit. But without strictly enforcing a autoformatable standard this is not possible and you end up with bikeshedding.
reply