You can move before you make a profit however ? Seems quite self defeating for Germany - all the companies that are about to break out will move out just before hitting profitability ?
Well, a tiling window and workspace manager. But as I am typing this, I’m realizing they hammerspoon can probably do some of the window placement, but maybe not handling workspaces and global state.
I was hoping I could be lazy and ask, and a not-lazy person could give a ready made answer :)
It can definitely handle virtual workspaces and global state (if I'm understanding what you mean). I have an Aerospace-like implementation here: https://github.com/mybuddymichael/Helm.spoon
It has several features from Aerospace, but Hammerspoon's window management performance is not nearly as good as Aerospace's (not surprising!).
Overall, I've found it easier to just fork Aerospace and add various extra features to it, so that's what I'm doing now.
If workspace management is an another term for managing desktop/spaces, then you are going to be hard pressed to find anything that is not a brittle hack.
I am writing a window manager bundled with other knick-knacks for myself. I have a "solution" for moving windows between spaces, but in the most vile way possible.
The only way I have managed to move windows between spaces is by, and this is no joke, recording the mouse position, moving the mouse to an app's titlebar, automating the 'click and hold' on the window's titlebar, then having the keybindings for "Switch to Next/Previous Space" fire off, and then moving the mouse back to the original position.
Because of the animations, all of junk requires carefully timed, short sleeps, which are also not likely consistent across various hardware/OS versions (can't test it myself).
Also, I have no idea what happens if my solution is tried on apps with pop-up windows, 'headless' apps (no title bar), electron apps, etc..
Apple's support for spaces is notoriously atrocious. There is no clean way to move windows from one space to another or to create/delete spaces. Though there was a built in way in OSX Snow Leopard, IIRC. Why it was removed? I have no idea.
Aerospace creates its own virtual desktops/spaces instead of trying to fight against the OS. I have never used Aerospace, so I cannot comment on its efficacy. But that is probably the cleanest solution we currently have available.
Aerospace is pretty cool, i recommend it, but I have not really worked out how full screen interacts with spaces. It’s a mess with and without aerospace.
TOASTER: Howdy doodly do! How's it going? I'm Talkie -- Talkie Toaster, your chirpy breakfast companion. Talkie's the name, toasting's the game. Anyone like any toast?
LISTER: Look, _I_ don't want any toast, and _he_ (indicating KRYTEN) doesn't want any toast. In fact, no one around here wants any toast. Not now, not ever. NO TOAST.
TOASTER: How 'bout a muffin?
LISTER: OR muffins! OR muffins! We don't LIKE muffins around here! We want no muffins, no toast, no teacakes, no buns, baps, baguettes or bagels, no croissants, no crumpets, no pancakes, no potato cakes and no hot-cross buns and DEFINITELY no smegging flapjacks!
TOASTER: Aah, so you're a waffle man!
LISTER: (to KRYTEN) See? You see what he's like? He winds me up, man. There's no reasoning with him.
KRYTEN: If you'll allow me, Sir, as one mechanical to another. He'll understand me. (Addressing the TOASTER as one would address an errant child) Now. Now, you listen here. You will not offer ANY grilled bread products to ANY member of the crew. If you do, you will be on the receiving end of a very large polo mallet.
Not sure that’s true in general, but the comparison here is between Linux and macOS. And I believe that for the set of users contemplating Linux, GP is largely correct.
Care to explain? I see that statement in this thread, but I am not sure where this is grounded in fact.
This is very interesting, because there must be a line here that AI is crossing, and the line is not clearly determined yet.
Is linting code crossing the line?
Is re-factoring code with automated tools like bicycle repair man crossing the line ?
Is AI doing a code review and suggesting the code crossing the line ?
Is writing code with a specific prompt and sample code crossing the line?
Is producing a high level spec and let the AI design details and code the whole thing crossing the line ?
So, where exactly is this line ?
The next interesting question is how this could even be enforced. It's going to be hard to prove AI use when using strictly local models. Maybe they could embed some watermark like thing, but I am not sure this can't be circumvented.
Would really like to see some legal opinions on this ( unlikely to happen :)
Yeah, that's what the link I posted also discusses (but then goes into much detail, but then offers no actual resolution).
I guess we will have to wait for cases to be brought and resolved at the courts. Not a great recipe to be the leader in AI, it must be said.
An updated copyright bill from legislature, or even positive regulatory action from the executive branch would speed things up and give much planning certainty to actors here in the US.
The rest of the world won't be waiting though -- maybe Europe, but Europe sadly doesn't really matter that much anymore :(
The dismantling is usually faster in other countries, as Telcoms owning this equipment either are or were state owned monopolies. In the US, the payphones were probly owned and swapped and back and forth between myriad providers.
If you look around you'll see people already putting the new, chinese made DDR4 through its paces, it's holding up far better than anyone expected.
Every single time I've had someone pay me to figure out why their build isn't stable, it's always some combination of cheap power supply with no noise filtering, cheap motherboard, and poor cooling. Can't cut corners like that if you want to go fast. That is to say, I've never encountered "almost ok" memory. They're quite good at validation.
The danger is we’ll start to see more QA rejects coming into the market. The temptation to mix in factory rejects into your inventory is going to get very high for a lot of resellers.
Nobody would deliberately sell QA rejected memory. I do not think you understand what this would result in, even in markets with relatively dogshit consumer protection laws.
Noice!
(I'm of course spitballing ;)
reply