557 karma · joined May 15, 2013
http://envisage-project.eu/wp-content/uploads/2015/02/sortin...
Sure, and that's a reasonable thing to want. That's still not what the right to repair is about, though. It's about preventing arbitrary restrictions on your rights to repair, not about forbidding practical limitations on your abilities to repair (unless of course those practical limitations were created in order to impose arbitrary restrictions on your rights).
If Apple decide to integrate the battery & screen to shorten the electrical paths to that power-hungry component, then the battery becomes effectively non-replaceable. That might annoy you, but it's not a violation of the right to repair.
On the other hand, if Apple do things to ensure that only Apple repair shops can replace the battery (eg via cryptographic signing, secret APIs, or physical keys that they prefer to call screwdrivers) then they've run afoul of the right to repair movement.
There may be times when it'd be good to mandate replaceable parts (environmental motivations come to mind), but that shouldn't be the default -- those restrictions should be applied to individual industries in narrow ways and only as needed.
The right to repair movement is pushing for something that reasonably could be the default, and we would instead make exceptions for things that shouldn't be generally repairable (eg, perhaps modifications to an odometer should be tightly controlled.)
Consider this crude csv parser:
using splitBy:
csv.splitBy("\n").map(csv_row=>csv_row.splitBy(","))
using split: "\n".split(csv).map(",".split)
split was the clear winner here. Given splitBy, I basically recreated split as a lambda.I tried to create an analog to that where splitBy would come out looking better. I figured that if we didn't know the dimensionality of our data, then delimiters becomes an array of arbitrary length and we could pass data.!splitBy into something like delimiters.reduce. When actually writing that, however, I wound up recreating split again:
using splitBy:
delimiters.reduce((accum,delim)=>accum.deepMap(data=>data.splitBy(delim)),[data])
using split: delimiters.reduce((accum,delim)=>accum.deepMap(delim.split),[data])Mr.^Smith^turned^off^the^lights.^^Then^he^went^to^sleep.
It's very possible that DRY could apply even where divergence is expected. Suppose we had a requirement that "A user should not be able to resize a TextBlock if they are not allowed to read the text." At the outset, the read & resize permission logic might be identical & DRY is easy to apply. Nobody would be surprised if eventually resizing permissions became more restrictive. Even at that point, DRY applies. If you repeated the shared logic, and later you add new restrictions to the read permissions, it'd be easy to introduce a bug where you forget to restrict resizing permissions accordingly.
For example, I've played Hanabi with 3+ players where the person before me deliberately gave a misleading hint to the person after me. For example, "this is your only blue card" indicating a blue 5 even though only blue 1-3 have been played. They were counting on me to anticipate that the mislead person was now very likely to waste that valuable card & realize that I could only reasonably avert that misplay by playing a blue 4, which is how I came to realize that I must be holding a blue 4.
Perhaps that depth of theory of mind can be useful in poker, but I must confess that I'm not playing poker at a level where it'd be helpful.
Generating story...
You are thefifthsetpin, a ranger living in the kingdom of Larion. You have a hunting bow and a quiver of arrows. You spot the deer and are ready to finish your hunt when suddenly you feel something hit your back.
> take cover
You duck behind some rocks as another arrow flies into your back. The pain is excruciating, but it will be over soon. A few more arrows fly into your body before you can even scream out for help
That escalated quickly. > die
Your last moments are a quiet one
> revive
The pain is gone now, and you feel refreshed. You walk over to the bodies of your companions and look at them all. They were good men, who died doing what they loved. You look around and see that this place has been abandoned. There are no signs of life anywhere else
You really can do anything! =)I get that a lack of broad acceptance is a hard thing to source, but do you have one?
They'd consider these to be the .hk TLD's: .hk com.hk edu.hk gov.hk idv.hk net.hk org.hk 公司.hk 教育.hk 敎育.hk 政府.hk 個人.hk 个人.hk 箇人.hk 網络.hk 网络.hk 组織.hk 網絡.hk 网絡.hk 组织.hk 組織.hk
They also consider dreamhost.com to be a TLD, so it's probably not the right list for some other use cases.
Going back to traffic as the example, if I want to drive downtown to see a ballet but decide against it because traffic is bad, then they add more lanes and next year I do decide to drive to see that ballet, then I'm creating more traffic because they added more lanes. That demand wasn't induced -- it just transitioned from unmet demand to met demand.
If induced demand isn't nonsense, then I must be oversimplifying it. What am I missing?
MR. HAWKINS: YOU ARE GOING TO ELECTROCUTE ME FOR TALKING?
THE COURT: NO, SIR, BUT THEY WILL ZAP YOU IF YOU KEEP DOING IT. THE DEFENDANT ALSO ALLEGES THAT THE COURT HAS AN EX PARTE CONTACT WITH THE D.A. THAT IS NOT TRUE, AND I AM NOT AWARE THAT THIS DEPUTY D.A. —
MR. HAWKINS: THE TRANSCRIPT WILL REFLECT THAT.
THE COURT: ONE MORE TIME. ONE MORE TIME. GO AHEAD.
MR. HAWKINS: THAT'S UNCONSTITUTIONAL. (AT THIS TIME THE BELT WAS ACTIVATED.) * * *
...
MR. HAWKINS: I THINK YOU HAVE BEEN VERY UNFAIR. I THINK THESE ELECTRONIC SHOCKS TO ME WITHOUT DISPLAYING ANY VIOLENT BEHAVIOR — I THINK IT IS VERY IN-HUMANE ON YOUR PART.
THE COURT: SIR, THERE WAS ONLY ONE BECAUSE YOU REFUSED TO OBEY MY ORDER TO STOP INTERRUPTING ME. SO DON'T MISSTATE THE RECORD. THERE WAS ONLY ONE, NOT PLURAL.
MR. HAWKINS: BUT FOR A VERBAL INTERRUPTION, YOUR HONOR.
THE COURT: YES, SIR, THAT IS EXACTLY RIGHT.
MR. HAWKINS: THAT IS NOT WHAT THIS THING IS DESIGNED FOR. YOU ARE OVERSTEPPING YOUR AUTHORITY.
THE COURT: NO. SIR, ANYTHING ELSE?
Hawkins v. Comparet-Cassani, 251 F.3d 1230, 1232 n.2 (9th Cir. 2001)
He's not the last person who will realize that the market can be manipulated by sabotage. It seems important that the penalties for trying that outweigh the potential benefits.
The kite survived that & flew fine on later occasions. Now that she's seen it fly, though, she has lost interest in kites that won't fly.
A chalked tire was ephemeral. I doubt that whatever replaces it will be.
pretendscholar is asserting that because it will happen, it must happen. You're arguing that it need not despite the fact that it will.
As an example, they intentionally didn't save her from the agony of receiving CPR.
I understand that you'd still need another hashing layer before inserting it into the db, but wouldn't some hashing client-side be useful?