47,766 karma · joined October 14, 2011
Groupon got to pretty much 100% penetration, still crashed and burned right after IPO. I think Zynga followed a similar trajectory.
No. But he should treat messages that are blatantly intended to provoke others as such. If someone on the flight is going out of their way to cause trouble, kicking them off is the smart move.
No it isn't. You can read that implication into it, but it's not "actively hostile" in the way that an "F... X" statement is, for any X, and it's a sign of how slanted the discourse is that you would consider them equivalent.
Maybe. It's not been a very prominent line of business for them, and even then I can recall a couple of significant dramas over that time - didn't they merge two different kinds of libraries and cause confusion? The unremovable U2 album is also a cause for concern, not because an extra album is bad but because it implies they see the contents of your library as up to them rather than you. Most of all, they went out of their way to break music being sold by Real for iPods, which hardly suggests a company committed to interoperability and open platforms.
> Hell, they ditched DRM on music in that time period too and will sell you lossless ALAC as well as MP4 audio. (They obviously weren't able to talk Hollywood into that.) Steam is DRM that ensures the capability to pull rugs.
Not "obvious" at all, and precisely the point at issue. I'm happy to buy music from Apple, but movies require another level of trust that they haven't reached yet. I will grudgingly, cautiously buy games from Steam when they're not available on itch/GoG, and maybe that's unfair, but Apple have never sent me the message that they want or care about me (a non-Apple hardware user) as a customer of their movies.
I know that's the theory, but have you ever seen it work that way in practice? Because I haven't.
> Regardless of how you write the catch-logic, the chained cause remains important for logging and diagnosis.
Sure. But if it's not being caught and handled but only logged or investigated then you're not gaining anything from the wrapper.
> Do you want layer #1 exceptions to travel all the way to #4 as-is, so that you get an HTTP 500 and you won't actually know which remote service is at fault? (Without grepping the stacktrace, which is ick.)
Yes? If it's a fail-and-alert-the-developer case then I'm going to look at the stacktrace first anyway.
I might have retries at any layer, but I don't see any case where #4 uses information from a wrapper exception from #3 to make a decision. The only thing #4 is going to do with a failure from #3 is retry or fail, and it's not going to make a different decision based on which service it was. (Maybe you want metrics or circuit breakers on the individual fortune cookie services, but in practice what I've seen is that you'd always find a way to plumb them in at layer #1 or #2, by reflection if need be, rather than have them work of the exceptions coming out of #3. I know the theory you're talking about, I've just never seen it actually work that way)
Not a crime, or certainly shouldn't be.
No they don't. The pension regulator sets very restrictive controls on what they can do with that 125b, because it's neither the company's nor the shareholders' money.
If we got a 4-hour work week that might be a worthwhile trade.
That sounds like a problem with that system. If we're 10x more productive why can't we make 10x as much nice housing?
Essentially anyone - other PE funds, competitors merging, the general stock market if you take it public. And they're not wrong want to buy it - there's a valuable business there - they're just bad at assessing the right price.
> And when does word get around, and the pool of suckers dry up?
One born every minute. And it's hard to even notice you're being taken for a ride as opposed to mismanaging the business you bought or just being unlucky.
Either the product was 10x better, which I don't think I need, or it wasn't really a 10x increase in productivity.
(Yes, all the good developers from Oklahoma move out, but the same is true of Ireland)
> "We remained lawfully committed to juducial integrity and processes ... as we were exterminated!"
If you're happy being governed without process or accountability, why not just surrender to Russia? If the EU can't maintain its principles when things get tough then what's the point in having it at all?
Why? I don't need 10x more stuff. I'd far rather spend 10x less time working. If we're talking about an actual productivity increase, let's just produce the same amount of stuff in 10x less time.
And what happened? How many hours per day/week are people spending watching now?
Does that actually work though? Who ever handles CustomerAccessException specifically, except by calling getCause() and looking at the underlying DatabaseException?
> There are many errors because all errors are contextual! Bad-input in the HTML form-submit is not the same as bad-input in the SQL query. A failed invariant of a tree that somehow made a loop is not the same as a failed invariant of something reporting negative length. An SSH handshake error is not a TLS handshake error.
But the way you handle them is the same. All you can ever really do is a) retry it or b) fail it and alert the developer. And the wrapper doesn't make either of those any easier.
I've seen it for APIs that throw exceptions for bad input or whatever. But what I've never seen is more than one catch block for wrapper exceptions (except perhaps to unwrap the cause), where the calling code handles FrameworkNetworkError differently from FrameworkDatabaseError or what have you.
> Do you think bad user input should be a result type?
Yes
> Because exceptions are essentially the same thing.
Well, except for all the ways they're not that you mentioned in the following paragraphs.
I'd consider that a positive rather than a negative. That's an important question to think about (usually) and I want the type system to help remind me.
> To be fair, #3 seems to have shades of grey. In some pls, you can call an async function from a sync one by wrapping it in a whole damn event loop system. Should that count?
I think you have to count any extra overhead where you can't just write f(), including try/catch. It's always possible to call whatever kind of function from whatever other kind of function if you put enough effort and hackery in, so if we can't use functions of kind x in functions of kind y as normal "f()" function calls then that has to be what we mean by colouring.
> When someone else writes a wrapper or higher-level layer that uses your code, then it'll be up to them to convert or wrap those results and exceptions into something suitable for their level of abstraction.
Why though? What do you gain other than longer stacktraces with all those wrappers? People always trot out some theoretical notion that a caller is going to catch that framework's different exceptions and handle them differently, but have you ever seen calling code that actually did that?
> In other words, suppose all Java methods always returned Object [0]. That would also ensure that a new return type is "always a local change" to the compiler, but I think most developers would be rightly horrified if they came across code that worked that way.
There are many different kinds of values. There really aren't that many different kinds of error - there's "transient error that you might want to retry", "programmer called the API wrong", and that's about it, most other cases (like bad user input) probably shouldn't be exceptions.