(Though that is otherwise good advice!)
1,245 karma · joined June 16, 2011
(Though that is otherwise good advice!)
(Of course, that's not what's happening at all.)
(Spoiler alert: Rust graduated to a full, first-class part of the kernel; it isn't being removed.)
Even Netflix got sued over a Black Mirror spinoff that used the phrase. They countersued to invalidate the trademark; the suit was settled under undisclosed terms. I would love to know how that went down and why there wasn't an obvious path to success for Netflix...
She's incredibly intelligent, but more importantly she's a phenomenal social networker. She always has someone to call to ask about any question or solve any problem that comes up in life, and she's great at connecting these people with each other when they have problems of their own - so they all want to help her with whatever she needs, just to gain access to a pool of people they themselves can talk to.
What do you do with a skillset like that? I honestly don't know - something in leadership, probably, something where finding the right people and setting them to work is the most important skill of the job.
> you're advocating for a toxicly positive carebear forum
Please stop putting words in my mouth.
I've generally found conversation there to be more respectful than HN, rather than less, when discussions get heated - so I had high hopes it would be a different site, but alas.
This leaves a really bad taste in my mouth.
Edit: you know what, screw it. In the spirit of "no more self censorship", here's the link: https://lobste.rs/~7u026ne9se
Honestly, if there's any chance the content they posted on your profile before locking you out comes close to defamation, I'd consider talking to a lawyer about it. It could be that getting one to send them a cease-and-desist letter on your behalf could take care of the problem.
A truncated sine wave? (insofar as sine waves are their own derivative, shifted by 90 degrees, so if I'm doing my math right they would theoretically be G∞-continuous)
I was one of the backers and I was sooooo looking forward to an affordable home SLS printer. They'd done some incredible engineering, too, in service of getting the price point down to where it was.
Scaling up was going to be a massive challenge for them, but damn, I wish they'd tried instead of phoning it in early.
(Mind you, I'm sure Formlabs paid them handsomely. Would I make the same decision under the same circumstances? I honestly don't know. So far be it from me to judge them, but man do I wish someone would do something about Formlabs' ridiculous prices and monopoly over that space.)
The X32 module interface is actually fairly simple: it's more or less just four 8-channel I2S TDM streams going in either direction. Easy peasy to interface with, nothing as complicated as AES50 involved.
AES50 itself is actually a standard; you can buy a copy of it for $50. It's basically just "Ethernet with fixed addresses and a custom frame format across two of the wire pairs, a super fast (64x the sample rate, with a -12.5% followed by a +12.5% duty cycle pulse every 2048 samples) clock signal across the other two". I've been meaning to whip up some boards that speak AES50 one of these days, just for fun.
A router would be totally possible, with of course the caveat that AES50 itself is point-to-point so you'd need some sort of out-of-band mechanism to tell the router where to send all the incoming audio streams it's receiving.
That's why this quote is relevant to this situation: it's totally Electron's fault for not adequately testing their framework against Apple's latest developer builds, but Apple could have absolutely done more to minimize the chance that Electron would make a mistake like this and cause lots of folks to be mad at Apple over it.
Should Apple be required to? No. Will they still suffer reputational damage if they don't and something like this happens? Yes.
If you owe the bank $100 and don't pay, that's your problem: you'll get in trouble for it, and the bank isn't going to be unduly harmed.
If you owe the bank $100 million and don't pay, that's the bank's problem: the loss of that $100 million is going to hit the bank hard, whether or not they're the ones who are in the right and regardless of how much trouble you get in over it.
Likewise, if you're a small time app developer and you use a private method that gets yanked and your app breaks, that's your problem: your users are going to be pissed at you, you'll take the reputational damage, and even if your users are also pissed at the OS vendor they represent such a small group of individuals that the OS vendor isn't going to be unduly harmed by that.
If, on the other hand, you develop one of the most widely used frameworks and you use a private method that gets yanked and your app breaks, that's the OS vendor's problem: the number of people who are pissed off at them (rightly or wrongly) is now much larger and they're going to take some reputational damage over it, whether or not they're the ones who have the moral high ground and regardless of how much reputational damage you also take.
And that's exactly what we're seeing here: it doesn't matter that Electron used an API they weren't supposed to, people are pissed at Apple about this and Apple, rightly or wrongly, has to contend with that reputational damage if they don't take steps to prevent this sort of thing before it happens (like letting the developers know that private-on-paper API is going to be yanked in advance, or making it mechanically impossible for anyone outside of Apple's own code to invoke that API long before someone depends on it).
Or perhaps they meant 297mm - the exact height of a sheet of A4 - and mistyped the "9".
Language changes. The construction "what's up" and its extension "what's up with ..." didn't become widely accepted until Bugs Bunny brought it into the mainstream, and yet you use it as naturally as anything else at the beginning of your message.
I don't know that it's particularly constructive to dish on this post purely on that account.
Free is free
Shit is shit
Damn
I don't know what it was about that particular sequence of words but man if it didn't get me something good.Its built-in recorder is a small part of what the overall app does.
It drives me nuts how quickly people jump on the criticism bandwagon without bothering to look up what the thing they're criticising actually does first.
(Aside: Hi Ben! If you are who I think you are, we started at the same company on the same day back in August of 2014.)
I have no idea what HN's tolerance is for the relevant medical language, so I'll put it like this: when I was on atomoxetine and after engaging in ahem activities, my pelvic floor muscle would stay contracted for something like 10 minutes. Not only was it super painful but it also made it so that I couldn't urinate at all until those 10 minutes had passed.
It was the weirdest thing.
> Much of the HN codebase consists of anti-abuse measures that would stop working if people knew about them. Unfortunately. separating out the secret parts would by now be a lot of work. The time to do it will be if and when we eventually release the alternative Arc implementations we’ve been working on.