It is still possible to adjust the speed in QuickTime Player: from .5 to 2x. Not available via Quicklook, but definitely there in the player, either in the menu bar or by clicking the >> in the video window.
Does this also mean only using "standard" parts? Or does the manufacturer have to over-produce the parts for, lets say 7 years, and then warehouse and ship those parts, probably multiple times. Or keep a low rate production line running for 7 years? What happens to the parts that don't get used? Are they scrapped?
That "what if" cost is going to be built into the cost of the laptop. Repairability doesn't always keep the cost low. The purchaser will definitely have to foot the cost otherwise it isn't sustainable.
> Does this also mean only using "standard" parts? Or does the manufacturer have to over-produce the parts for, lets say 7 years, and then warehouse and ship those parts, probably multiple times. Or keep a low rate production line running for 7 years? What happens to the parts that don't get used? Are they scrapped?
None of that is relevant in this context: The parts are available, but the laptop is designed and built such that the alone keyboard cannot be replaced.[1]
[1] Not sure if this is possible on that specific laptop, but with a steady hand, a tiny drill, maybe a magnifiying glass too, you can maybe drill out the rivets, then replace the keyboard, then either re-rivet it back again or tap very tiny thread into the laptop and use screws.
The laptop is deffinitely designed in a way that the keyboard is extremely hard to replace. Took me like 5 hours across 2 days. Rivets are not even the worst part, I used tiny drill and carefully glued in the replacement keyboard using phone screen glue (B7000) between the keys. (glue needs to go both on the frame and on the keyboard as there is a gap that needs to be bridged) Since there are screws along 3 of its edges, I deemed it good enough. drilling and tapping or riveting would have been extra painful.
What makes the repair more complicated is that
1) you need to take out basically everything to get to the keyboard. There are many different screws, luckily ifixit has a disassembly guides with their sizes. Still it was a bit painful to reassemble.
2) One of the things you need to take out or at least lift is the glued in battery - this took a lot of careful prying with thin plastic sheet and dousing it in ipa.
3) backlight is glued on to the case in an extremely fragile way, so it needs to be replaced with the keyboard or will probably look uneven after repair. (i reused the old one as I don't mind it but still, it could just have been glued to the keyboard itself and it would be easier to repair.
Repairability definitely doesn't keep the costs low. If it was cheaper and easier, it wouldn't have to be regulated. As for supply chain management, companies that get that equation correct are going to benefit. Which is exactly how it should be.
We define the rules of the game and companies that can best implement those rules will succeed. That is capitalism.
It won’t self resolve because consumers don’t fully factor in every detail while buying, and they often don’t get such granular choice anyway.
It’s easier and more profitable for companies to make a product that catastrophically fails around about when the new model is out. So that’s what they do. Until just now when the EU is reeling them back in line.
> Does this also mean only using "standard" parts? Or does the manufacturer have to over-produce the parts for, lets say 7 years
Why not? I don't understand how it's legal for manufacturers to produce absolute trash that can't be replaced and will just end up in a landfill. I think 7 years is far from enough, but because computers evolve quickly maybe 15 years is ok. For the rest of electro-mechanical goods, 50 years should be the baseline.
If a car or fridge from 50 years ago is still working with proper maintenance, that should be the minimum to be expected from products released today.
I don't understand your math. The 1mm (the wall) was there already, so why is it being counted here? Plus, multiplying by 1 doesn't do anything? Also, the 2mm extra won't be solid plastic (they'll be solid air, since that's why we're adding the extra thickness, for the room.
If anything, the extra material for the case would be the perimeter length times the perimeter wall width times the height.
The post was fixed about 30 seconds after making it - due to the *s being interpreted as italics. It is a shame there isn't a preview button when composing posts.
There's a new field in your profile called delay. It's the time delay in minutes between when you create a comment and when it becomes visible to other people. I added this so that when there are rss feeds for comments, users can, if they want, have some time to edit them before they go out in the feed. Many users edit comments after posting them, so it would be bad if the first draft always got shipped.
Delay is initially 0. The maximum effective value is 10. It only applies to comments.
That may not even be where the devices are most toxic to the environment :\
How about all the energy waste for manufacture of what are "engineered" as effectively disposable components & assemblies in numerous facilities?
Also scattered local emissions, not only at the factories and delivery ships & trucks, but consumers kick up all kinds of exhaust and waste just earning the money to participate in such a scheme. And way more so for short-lived products that are the least bit overpriced compared to how they could be from the same factory.
Please can you explain the evidence that this is generated content.
Yes, the site is new, but other posted articles are 100% consistent with the author wanting a guaranteed level of local inference with large models.
What I read was written by a skeptic who took claims and systematically addressed a number of issues. The debunking was concise and used simple sentences.
The boxes in the pictures were, to my eyes, generated manually using the macOS Preview annotation feature. They are not well aligned. I've used this technique many times to general overlays. If this were me, I'd get called out. I like nicely spaced and proportioned boxes! NB: iFixit tear downs are mis-aligned as well and it bugs me.
People have a distasteful habit of assigning others into boxes. Particularly if that box currently has a negative connotation. Boxing is a primary tool of the; misguided, bullies, sycophants, censors and those with an unspoken agenda. Humor: Which box applies?
I am not sure using sandbox-exec is a good security architecture for AI agents. It sure is convenient and available to everyone right now. I've made another comment elsewhere in this discussion about what I think "deprecated" means - it is a sharp tool that could break if not tracking everything that changes, including every change in a SW update. It is also easy to get wrong if there is not a "(default deny)" in the profile. An agent could escape if they can find a mach service or some other system call coordinated proxy service. Java, Silverlight and Flash had backdoor communication mechanisms with other instances of themselves that could be abused.
The Sandboxing and Entitlements mechanisms are very different. Sandboxing can only drop access to resources, it cannot grant access that was not already there [1]. Entitlements are all about giving additional selective privileges or to make the sandbox NOT remove access (like full disk access or debug ability ). Entitlements are bound to processes only and are non-transferable. This is in contrast to a capability based system where they can be passed around. Reasoning about capabilities is challenging because analysis effectively requires global knowledge of the system. Binding entitlements to libraries or Frameworks would turn them into capabilities.
[1] a GUI app can restore access to files by using a trusted external selection process.
Edit: change footnote reference to prevent markup error.
This is true. I was being brash. Let me say instead that the split in reasoning and evaluation as it exists on macOS in this area is rough and potentially not needed. Granted, I don't have a better answer in my back pocket, and the fact that Apple has kicked the can for 15 years on trying to harmonize these is a sign it's hard.
I took the "granularity doesn't cut it" comment to mean there aren't enough entitlements to eliminate the need for custom SBPL. Followed by a sentence about apps that have temporary exception SBPL. Combining the two seems to imply that if there were more entitlements the custom SBPL might not be necessary. In the followup you noted; the split in reasoning and evaluation is rough and potentially not needed. I read this as a conclusion of wanting to do something, but could not as there were not enough entitlements to make it work, so custom SBPL would be necessary.
"sandbox-exec" is deprecated in the sense of "please don't use this method to run sandboxes" rather than the mechanism going away.
If you are using "sandbox-exec" then you are likely maintaining your own seatbelt profile. Keeping those up to date can be challenging, especially for 3rd parties as any changes to underlying Frameworks and libraries can break a hand crafted profile.
If you are using it to secure your own stuff and accept this and not complain, even for minor SW updates, then you are going to be fine. Don't ship things to 3rd parties without also accepting this. That is what this deprecated means.
I've written to <voxmeditantis@gmail.com> about how deceptive it was to put the Editorial Note at the end instead of upfront. I stopped reading because sections felt fabricated - but it was presented as an oral history or actual interview. What a terrible way to present the work of a pioneer.
There is something off about this piece. Particularly the section that starts "You passed away on your eighty-eighth birthday – 4th August 2020. Do you reflect on mortality?"
I stopped reading after that.
An Editorial Note is at the bottom (as others have now noted), it should have been at the top. Had I not seen other comments I would likely have believed everything was made up. This is a terrible way to recount the memory of Frances Allen.
