Not forgetting Trump personally ordering the withdrawal of all US forces in Northern Syria in his first term, on a weekend so none of the generals were around to talk him out of it.
This resulted in the Turks moving in, massacring all the Kurds they could find, and a few thousand ISIS prisoners (including 60 'high value targets') escaping as the Kurds guarding them fled for their lives.
However Trump said this didn't pose any threat to the US because "They’re going to be escaping to Europe.”
The Chinese system is hyper conservative, essentially fascist, it’s not actually socialist in any way, shape or form. It’s also hyper capitalist, with minimal regulation or consumer rights. The top levels of the ‘communist’ party is now packed with billionaires. What regulation there is, is mostly aimed at maintaining party control and prestige.
Both unchecked conservatism and unchecked socialism are toxic. Unchecked anything is toxic. That’s human nature, yet (to simplify massively) we still need both conservative and socialist elements in a balanced society.
Also they’re only the cheapest at the point of generation, you then need to transfer that energy where it’s needed, and when it’s needed (storage). Also manufacturing capacity for renewables infrastructure, vehicles, batteries, etc, etc, is constrained. And then there are products that can’t be substituted by renewables such as plastics, fertiliser, etc. So many factors. It can’t happen too soon, but it will take many decades.
It was/is mostly the same practice except for the cases where it really counts. Window managers in general, xdotool, all kinds of input mapping and automation or the fact that you can write a screenshot tool in less than 500 LOC are only possible if you talk to X directly. And there the possibilities are almost limitless. And thanks to the xcb library it's actually somewhat convenient to use.
Also certain types of power tools for mac probably need use Quartz directly as well.
> Window managers in general, xdotool, all kinds of input mapping and automation or the fact that you can write a screenshot tool in less than 500 LOC are only possible if you talk to X directly.
Honestly I think this is a pretty fair approximation of "no one". How many people are writing tools like this vs. the number of people writing regular applications? A very small number, I'd say.
And after working extensively with both libX11/libxcb and libwayland-client directly, I can say that none of them are particularly pleasant to work with. Actually, no, that's not true: libwayland-client wins, easily. Every single Wayland protocol has code generated for it that works exactly the same way. I suppose the same is (more or less) true of libxcb, but libX11 (and all the other libraries you might have to use, like libXrender, libXrandr, libXext...) are a complete mess.
And even then, libwayland-client has a much lower number of concepts you have to understand than libxcb does, simply because the Wayland protocol has a small number of concepts you need to understand. libxcb is definitely an improvement over libX11, but it can't magically make all the underlying X11 protocol concepts become unified.
Having written a new gtk program recently I had to implement Wayland and X -isms in the code. Off the top of my head X prefers using W_Class and Wayland prefers app-id with each window having a role set. Both are fine. I honestly think Wayland is nicer but realistically you code for both. To get a global hot key you register it with the compositor and it works. But you can run a background daemon to catch all keys if you really want.
And why should we optimize for "how many locs can I write a screenshot tool in"? I would prefer to having 1-2 decent ones that have all the necessary features and call it a day. They can then have a simple API so you can script whatever you want.
Why would I want to add more complexity to a display server?
Creating a window and Vulkan context and receiving input events (e.g. what game-like applications need) is fairly trivial via Xlib but far worse in Wayland. The Xlib API also sucks compared to Win32 or Cocoa, but writing a Wayland client for something as trivial as creating and managing a window is much worse than on any other platform (see: https://www.p4m.dev/posts/29/index.html)
Basic window system functionality really needs to be provided by the OS, not by 3rd-party libraries. And there's no reason why simple things like creating a window should be drastically more code in an OS API than in a wrapper library like SDL.
Also Apple are masters of the up-sell. Someone who knows $600 windows laptops are crap might just buy a cheaper Chromebook because crap is crap, but they might spring for another few hundred bucks for something they have confidence is actually pretty nice and has brand Caché.
Makes me think if it was carefully calculated strategy, so Windows users would feel more familiar with new os. Everything in MacOs is frustratingly unusual for windows users, but at least annoying bugs are there. And you google how to deal with it, getting familiar with the os.
I think the target demographic is also young people raised with iPhones. So for them the new interface design is good for similarity (not for older Mac-people). As if apple planed that all along...
In the USA the government health programs for people in low incomes, children and pensioners cost about as much as a typical European single payer health system. Then tax payers get to pay to be gouged by health insurance companies to get any cover for themselves.
This resulted in the Turks moving in, massacring all the Kurds they could find, and a few thousand ISIS prisoners (including 60 'high value targets') escaping as the Kurds guarding them fled for their lives.
However Trump said this didn't pose any threat to the US because "They’re going to be escaping to Europe.”
https://www.brookings.edu/articles/trumps-syria-withdrawal-i...
reply