I like the premise but it sounds like something where the overhead in trying to track & manage that would be overly burdensome for all parties until you just forced more reasonable terms on when material enters the public domain in the first place, at which point such a system wouldn't really be needed anyways. The last thing I want to see to try to clean up public access to work is even more complex rules and systems being layered on top of the existing system.
And their 5 year old iPhone can run a game that looks a hell of a lot better than Half-Life on 320x240@30 FPS too. Just listing that the hardware is different than the other doesn't give a comparison. Was there really not a shittily made app for the N95 at all? Are there really not apps that perform well on a 5 year old iPhone?
We're just looking at a single app optimized for a platform nearly 2 decades after release and somehow concluding people don't ever optimize software these days. Some software is always going to be inefficient as can be but there is more well optimized software available now than there ever has been.
I travel quite a bit for work, e.g. the last 30 days I've been home for 4 while travelling to 6 cities spread over 4 countries and 5 time zones, and that's not how I understood what they are saying at all. If you want a perk for travelling, these points based systems are the most Kafkaesque way imaginable to give so little for it.
And often it is like they are stealing from the company. I remember seeing on LinkedIn a ${seniorExec} of a place I worked at posting how they are a million miler first class traveler on airline X but they'll be switching to airline Y exclusively from now on because X's point system isn't as good anymore. The moral of the post was supposed to be something about treating your customers right for loyalty or something, what I took away from it is this person is throwing away my entire trip travel budget on individual flights because they are selecting how to get the best kickback. Meanwhile I'm trying to get approval to chop 4 hours off what should be an 8 hour door to door flight by spending $120 more than the recommended flight to avoid an extra hop and layover because that just makes no $ sense from a hours perspective.
The best perk I ever got for travel was an actual pay increase for it, many times larger than any hotel or flights points program has ever been worth to me. If you want to give your travelling employees a perk then that is a real way to do it, not a few brand specific dollars for each part of the trip you have to sign up for.
There is clear intent, albeit not as good as the Boot Camp days. One doesn't just accidentally the Boot Policy subsystem to enable doing so every step of the way as it is. It has even been remarked as much by an Apple dev:
> I purposely designed a mechanism so that M1 Macs would retain the capability to boot completely arbitrary code instead of XNU if users wanted. But you have to 1) reboot to recoveryOS with a physical power button press and 2) put in your SEP-backed credentials.
> The challenge to running arbitrary code of course, as @marcan42 noted in his crowdfunding effort to getting linux on the M1, is that the SOC is undocumented, so you still have to reuse bits of XNU and/or reverse engineer a bunch of stuff.
> As one senior architect said "the contract is that there is no contract". So that Apple can change things to suit its own needs, not others', to build the best macOS experience, which is what most customers (besides y'all who follow me) are there for.
12.1 also added support for raw image boot, which was seemingly for, and has only been relevant to, making booting Asahi Linux easier. Discussion at the time https://news.ycombinator.com/item?id=29591578 and an archive of the tweet's content below:
> Looks like Apple changed the requirements for Mach-O kernel files in 12.1, breaking our existing installation process... and they also added a raw image mode that will never break again and doesn't require Mach-Os. And people said they wouldn't help. This is intended for us.
OSS Resistance is about not asking for time to do something yourself while removal of unsigned casks is about what they host in the official Homebrew/cask repo. You're free to make & use your own tap to use with Homebrew without asking, so there's not really anything to square between the two stances - any conflict all comes purely from your 3rd stance about signing in general.
I just threw them a small donation for supporting this software for so long, even if it's only 98% how I'd want the project to be run all these years myself.
If you want to go some distance you're always paying something to do it - you can't therefore assume all means of going a distance cost the same and that factor can be ignored, though. A plane, train, bus, car, and taxi are all going to have different cost efficiencies (some more different than others) of going on a given type of trip. From a different perspective, they all require purchase, maintenance, licensing, and registration as well - but those are still part of TCO because it's part of the total cost. If you remove them for being the same type of cost rather than the same actual cost then you wouldn't really end up with much going into TCO even though the total cost of each is wildly different.
In general, you're almost certainly no longer on the path to calculating anything that should be called TCO once you've started removing costs associated with using the item. Apart from that, you're probably not on your way to a very meaningful cost comparison either.
I think they are just saying something like 400 * 72 gives you an absolute hard ceiling of 28k and change. Once you add in interests, sales tax, and other fees, you end up with something like the numbers you're saying. 72 months sounds stupid, because it is, but extremely long car loans are becoming increasingly common these days https://www.marketscreener.com/news/new-experian-automotive-... and you can even sometimes go to 84 if you really want that 28k number at $400/m.
KDE now supports the newer explicit sync (applications can signal when the frame is ready) and async presentation (fullscreen applications can tear rather than wait for the compositor frame sync). Fullscreen apps can also do direct scanout on Kwin now, and VRR is well supported. X11 w/o a compositor is of course still fewer steps for the data to pass through, but there is no longer anything uniquely available to that flow alone anymore.
reply