ledauphin

yeah, this is a significant hole in the locked cockpit door plan.

based on the article, it doesn't sound like this has anything specifically to do with temperature - the issue is more about whether there is moisture in the air.

If it were just a temperature thing, you'd think it could be automated, but I don't think that's really the main thing they're dealing with here.

In theory this means switching the system off when you exit the clouds.

This is usually pretty noticeable, but maybe less so at night, since you might be breaking out into a pocket or a clear layer between other layers, without visibly seeing much of anything outside.

I would hesitate to comment on the feasibility of this beyond what the interviewed persons have said, precisely because they're not clarifying (to the readers in any case) what the actual thresholds here are. And the interviewees don't seem convinced that this is a reasonable/safe requirement.

yeah, I appreciate this clarification. "publishing" seems like a nebulous concept to me and the general act of publishing something rarely seems to be what draws the attention of the lawyers (whereas making money seems clearer-cut).

So I suppose the question will hang on whether OpenAI is "publishing" if it returns similarly infringing results for the same prompts, even though those results are individually generated for a given user query.

there are a lot of interesting legal questions here, but surely in the Adobe/Mickey case, it's the user's input that's infringing. In the examples provided here, the user's input is obviously not infringing, so that leaves... the model's output?

i think the concept of "source code as AST" or something like that is basically a fine one, but the devil is in the details. your "true source" must continue to support (just off the top of my head):

- precise "decompilation" to readable, idiomatic text - comments - line numbers or some semantic equivalent

but would they have liability if they submitted their "output" to a senior artist, who immediately shot it down as obviously infringing? Surely not. It's not illegal to draw Mario - just illegal to make money off your drawing.

I think the real question is whether OpenAI should be allowed to charge for generating infringing content. Even though the unit cost of the Mario drawing is negligible, the sum total of their infringing outputs may be making them a lot of money.

i can see you are probably a polyglot, working in several languages with regularity.

it would certainly be frustrating to have to juggle these semantics as you switched back and forth.

however, languages are just that - they have their own meanings, and unfortunately they can't all be the same across languages (or they'd all be the same language).

I strongly sympathize, but my thinking on this is that it's _extremely_ hard to find someone whose ethics match yours without thinking deeply (and you and the writer both being exceptionally transparent) about what _motivates_ your ethics.

What I've found is that it's not at all hard to find someone who comes to conclusions that frequently make me feel 'satisfied'. But that, if I'm honest, it's often exactly the kind of echo chamber the parent post is warning about, precisely because the 'analyst' is avoiding transparency about their priors - and in fact avoiding any examination of them at all. And without that transparency and curiosity, the 'analysis' is really just very basest form of partisan politics, which is to say "We'll support each other as long as we agree."

I wish you luck in finding thoughtful and transparent analysis, though!

this was my thought as well

I don't know if I agree or disagree with your general thesis, but it has to be pointed out that the JavaScript ecosystem is even more complex than Python -- despite the fact that it doesn't have to deal with a C ABI -- and I think this is in fact largely because the language has resisted change so much that everything has just moved beyond the language itself to some form of transpilation.

The world changes. Software development changes. The best way to guarantee that your entire codebase will become an obsolete monolith that eventually needs to get replaced is to make sure that you choose an ecosystem that isn't growing and changing too.

Yes, there are COBOL and Fortran and whatever else programs still running out there. But software is not mostly a "one and done" thing, and unless you're confident you're writing something that's "one and done", then these comparisons are truly irrelevant.

This is wonderful! A feature request: when I hover over your nose, I would like to see you cross your eyes!

it's not that uncommon to work at a company where the engineers have no idea that churn is up 25%, much less that customers are complaining about slowness.

companies get so fixated on having their engineers do "engineering work" that they don't communicate what's actually going on at the business level.

it's not actually primarily a lubricant, it's an octane-increaser (detonation reducer)

the storage format may not be the only consideration - it may be preferable to have an in-memory representation that is also inexpensive.

I'm particularly curious about TX - it's really impressive that a satellite would be able to pick out a signal coming from the tiny thing I'm holding in my hand.

doing this on an annual basis is such an obviously inefficient system (on both sides) that you'd think somebody would've developed a basic mathematical approach by now to disrupt the market.

but of course in practice, most US healthcare consumers don't really have an actual choice about who they buy their healthcare from.

ooof. Bandcamp is the only place I know of that provides an actually user-friendly experience for buying music. They've seemed maybe a little too good to be true in this modern age.

it does not need ground friction and what you're proposing could absolutely work if water could be sourced in sufficient quantities.

in that region, maybe they get enough snow that they don't need to truck in water....

yeah, this isn't Python, this is pandas. Run far away from pandas if it's not too late.

critique: (almost) no one wants to work 30 days a month. ;)

more seriously: I assume you plan to pay for hotel rooms?

also: why 2 hours max? If you're paying for one night in a hotel, then surely you could pay for 2 nights, making 3 or more hours feasible.

this is the _first_ place I've seen anyone clearly articulate an actual use case for subinterpreters. Thank you!

what's especially interesting about this is that it could create a new "meta" for static typing in Python.

One significant issue with static typing in Python is how much boilerplate is required to use types when also doing the sorts of things that dynamic Python is really good at - for instance proxying functions. If you want to do that now and preserve the types, you need to re-declare the types of everything in the wrapper.

Now, if the underlying function already made use of Unpack, you could "reuse" that type in your own wrapper with low boilerplate and less chance of things diverging in hard-to-refactor ways.

I'm very curious to see how this works out in the Kotlin ecosystem, given the amount of async code out there (and the associated function coloring issues).

yes, but is it actually harder than Stopping Cruises, which is what the activists apparently want? Obviously not.

I've been excited in the abstract about PRQL for quite a while. But something FQL seems to have a much better handle on is the value of document-orientedness, or what you might alternatively call "gradual schematization".

This problem has been solved (if not beautifully, at least acceptably) by modern SQL databases that support a JSON storage format and associated "secondary query language".

I know PRQL has had an open issue on this subject for a while. I just want to note that I think this is truly one of the critical "missing pieces" to PRQL, without which it may never be able to break out into common usage.

does this provide sane default behavior for refreshing expired auth tokens and retrying random client timeouts? the "official" SDK has driven me absolutely crazy trying to wrap all the different pieces with retries so that basic long-running operations won't randomly raise spurious exceptions...

The blame here may indeed lie with whoever decided that reusing an old flag was a good idea. As anyone who has been in software development for any time can attest, this decision was not necessarily - and perhaps not even likely - made by a "developer."

I think this is meant to be in reference to recent events where Flexport rescinded job offers. For the Hacker News audience, this is not positive advertising, to say the least.

hey, thanks for putting this out there and also for iterating on it! I will start using sending this to folks as a reference now that I know it's being maintained!

The insight about thinking deeply is compelling, and I believe it's partly true. We could all benefit from sitting silently and thinking more often.

But I also suspect that it overvalues individual insight and undervalues the normal process by which most complex ideas with application to the "real world" actually get created - through back-and-forth interaction between people.