Hacker News new | past | comments | ask | show | jobs | submit login

Huh! That's my experience of performing, for sure, but Meisner wasn't presented to me that way. One of the teachers of a workshop I was in had studied with Meisner, and had led (I think?) the London Meisner Institute, so I figured I was getting it straight. She approached repetition exercises more like intuitive textual analysis - finding the subtext, as you (or someone else) said up-thread. I've never had trouble supplying more subtext than anyone could ever want, so that bit didn't do anything much for me.

Neither did the crying and the yelling. I did too, just so as not to be left out (crying and yelling is always good fun), but they all took it so damn seriously that I wasn't sure where the line was between useful work and self-indulgence.

Oh, and also I think a professional actor ought to be able to drop in without having to drag someone else through ten minutes of repeating the first three words of their lines back and forth until the syllables are drained of all meaning. True story! I was as good a sport about it as I could be, but gosh... It was drizzling, and the lighting guy fucked off for tea, and I sure wished I could too.

I know more direct ways to get students to drop their inhibitions and tune into each other than repetitions. (Oh, and the audience! Everything I've seen of Meisner neglects the audience, and I think being aware of them is really important for stage work. Camera, same, for screen acting.)

Anyway, I'm sure I'm just missing something, and being grumpy. Like I say, I've seen positive results for some actors (though not the chick in the rain), so it's doing something, and I'm glad it works for you.


Compiler Explorer (https://news.ycombinator.com/item?id=33224542) - Oct 2022 (107 comments)

Compiler Explorer (https://news.ycombinator.com/item?id=24066570) - Aug 2020 (48 comments)

Compiler Explorer (https://news.ycombinator.com/item?id=18671993) - Dec 2018 (44 comments)

Whenever you see REST in the article, think RPC. The author even says REST is simpler than GraphQL but I suspect they hadn’t implemented a REST API… ever.

It's like the British Royals - way too many people obsessed with it...and keeping those obsessions going is a steady paycheck for way too many "journalists".

Can only agree with author on all points. GraphQL was nice for the types, and precious little else. But we have better solutions utilizing just the types now, so it was still valuable.

Important in this context is the board members insinuation that sam was unwanted. According to pgs account, that was not the case.

Perhaps we can agree that "firing" is a fairly fuzzy term, and maybe not fit to meaningfully contain, both:

a) me losing my job because I am (apparently) not creating enough value for the company

b) me losing my job because I am not willing to split time between my main gig and my unicorn startup

And the tip is to use a Syringe to "pour" the ink.

I still love GraphQL, but much of the love comes from using tools like PostGraphile which generates the API for you based on your database schema. I then add my own Javascript plugins as necessary. Going back to REST and hand writing everything gives me the shivers, how much time am I spending just translating data A to data B?

Authorization: I do it in the database using roles, row level security and column level security. It works well and I defer everything to PostgreSQL's security controls, it feels like the right place to do it and I don't have to worry about it going out of fashion, PostgreSQL is here to stay. Anybody else who talks to the database directly is also subject to the same authorization rules, which is nice.

Introspection: this should really be disabled on production services. Only enable it for development.

N+1 problem: I don't really have a problem with N+1 because PostGraphile converts the request into an efficient query. In other cases this problem presents itself in REST too and the article proposes hoisting N+1 queries to the controller, but that's just really moving the problem around, and you can do this with GraphQL too.

The other problems, yeah sure they are present and a worry if you're running some highly visible/very loaded public API.

It's a well-argued piece which examines the phenomenon from a perspective outside of the cultural context in which it was created.

If you disagree with the author's argument, could you be more specific as to why?

I’m curious to know why it happened only today. Was it some new sanctions? Were they slow to apply existing restrictions? Does it have anything to do with official sanctions at all?

many of these concerns are mitigated by ensuring you are using trusted documents (https://benjie.dev/graphql/trusted-documents)

This leak (https://hexdocs.pm/google_api_content_warehouse/0.4.0/api-re...) seems related to their deprecated Document AI Warehouse API (https://cloud.google.com/document-warehouse/docs/overview) According to the API overview page: "Document AI Warehouse is an integrated, cloud-based platform to store, search, organize, govern and analyze documents and their structured metadata (called Properties). Documents include structured (e.g. forms, invoices) and unstructured (e.g. contracts, research papers) and their Properties (metadata) includes AI-extracted data from documents and manually or AI-assigned tags (for example, account number, loan ID, document type)."

Judging by the package of the leaked stuff (GoogleApi.ContentWarehouse.V1.Model.....) these seem to be just the methods Google used internally to do this AI analysis of your documents (when you used their now deprecated Document AI Warehouse api).

What im trying to say is we basically got the method signatures of internal code used by some deprecated GCP API. If that is the case, why are people saying this is a leak on how Google Search works and giving SEO recommendation based on this? AFAIK Document AI Warehouse is not Google Search

what do you think.

That might be what they meant by "robust permissions model".

To throw another anecdote into the bucket, whenever I'm asked for the last four digits of my ssn or phone number, I have to mentally say the whole thing.

I live in Germany, a country infamous for its strong employee protections. It’s very hard to fire someone here. Yet, I don’t see how this is in any way unjust. Your employer pays you for putting your skills and time to their use.

If you start working on a side gig, that will take up a chunk of your time and invariably occupy your brain; thus, your employer doesn’t get their full value out of you anymore. Up to a certain degree, employers (have) to tolerate this—in Germany, that would be when your performance at your job starts to suffer from it. But once your commitment to the side gig increases so much that you’re about to become CEO, there’s no reasonable way to claim you can still carry out your contractual duties to your employer.

If your employer then offers you to either step down from that side gig or lose your employment, that is completely reasonable and frankly something you should expect?

Put differently, if you pay me to paint your shed, and after finishing the front side I went off and painted my own house with the rest of the paint, you certainly wouldn’t consider the job done or full payment to be justified.

IMO GraphQL is a technological dead end in much the same way as Mongo is.

They were both conceived to solve a perceived problem with tools widely adopted at the time, but ended up with something which is even worse, while the tools they were trying to replace rapidly matured and improved.

Today OpenAPI REST and Postgres are rightfully considered as the defaults, you even have PostgREST combining them, while most of those who adopted Mongo or GraphQL have either long migrated or are stuck discussing migrations.

Worked on two GraphQL projects; I was quickly cured from the hype. I recognize a lot of points in this article.

In both these projects the GraphQL had started small. I came in during a more mature phase of these projects (2 and 4 years). That's where the requirements are harder, more specific, and overall complexity has grown. Hence you logically spend more time debugging, this is true for any codebase.

But GraphQL has everything in it to make such problems even harder. And both these projects had clear signs of "learning-on-the-go" with loads of bad practices. Issue descriptions were much vaguer, harder to find in logs and performance issues popped up in the most random places (code that had been running and untouched for ages).

Fun fact; in both these projects the original devs who set it up were no longer involved. Probably spreading their evangalism further elsewhere.

RPC and REST are just more straightforward to monitor, log, cache, authorize and debug.

This! I was stunned by the quality and availability of good coffee down under. I figured it was a tea culture and wasn't that a mile of the mark.

I have Chrome, Edge and Firefox installed and I never understood the performance complaints about Firefox. There is no difference in loading times between any site I frequent. I believe this is a wrong meme to be honest.

Edge was a decent browser for a very short time when it was just a minimal browser. Around the time they switched the engine. Today is in no way better and in quite a few parts even worse than Chrome.

It's not graph, and it's not QL.

>> Guns are one of the most dangerous things a person can own

> Actually it's an extension ladder.

Fair point, but I think it's more useful to consider that an extension ladder is a tool designed for non-violent uses, and deaths involving extension ladders are (nearly?) all due to accidents.

Guns are tools designed to inflict injury and death. While many gun deaths are accidental, the guns in those instances are performing to purpose.

> We literally invented metal detectors and have dogs that can smell guns and explosives because sometimes mentally unwell people have weapons.

I don't particularly want to live in a world where we have to have metal detectors and dogs present at the entrance to any decent-sized building. That sounds pretty dystopian.

+1 but this is absolutely not happening. We’ll be hearing about sama and OpenAI for a long, long time.

You chose to be fired, basicly quit.

(this whole terminology debate is so futile and useless, mental food for the bored. WTF cares which exact colorful sticker we put on disagreements and the consequent parting. It's over, carry on.)

Remember when Apple (who always toots the privacy horn) leaked photos that some users explicitly deleted 10 years prior?

Even if the intentions were good (and I doubt it), there's always human error. That's why we must fight against any surveillance tech.

thats not a graphql thing. my startup uses graphql and it does not map anywhere near closer to 1:1 with our database. what you're talking about is the litany of RAD api backend apps that take your db and expose a graphql endpoint.

Works where archive.ph is blocked:

Disable Javascript.

(Tested with text-only browser.)

What in earth are you talking about? PG is clearly saying he was running both for years, everyone knew, everyone was happy, but when openai became a for profit, it was time to choose.

Nothing nefarious, nothing sneaky, no tricks, nada, ziltch.

The immense bias, bull, made up junk, and outright maliciousness in some of these replies is beyond disgusting.

I think this currently exists in some shape or other, I don’t have a facebook account but I can click on profiles of businesses and get their opening hours and pictures of their menus or whatever. In think there must be some stuff with a public context.

Not the person you're replying to, but I fully support repealing the 2nd amendment and strictly regulating gun ownership, up to and including total bans on certain classes of firearms, magazines, and ammunition. I would also personally have no problem with a total ban on any kind of firearm ownership, but I don't think the evidence supports that a total ban would make us meaningfully safer than more targeted restrictions and regulations. But for the guns we might allow in my fantasy of a US with sane gun laws, every gun owner should be required to take both a safety course and general training course, and complete practical skills exam before being licensed (yes, licensed) to own a firearm. That training should have to be repeated (perhaps an abbreviated version) at some reasonable interval, such as every year or two.

Regarding your nitpicking of what "assault" means, that's irrelevant. But to discuss it anyway: "assault weapon" has not become an umbrella for any semi-auto weapon. Semi-auto pistols, for example, are not what people are talking about when they want "assault" weapons banned. For people who don't really know much about guns, "assault weapon" means "a type of gun that someone in the military on a TV show or movie might have slung across their chest". An imprecise definition, to be sure, but in general I'd agree that no random civilian has any need for such a weapon. And any civilian who believes they have an actual need for such a weapon probably should not be trusted to have one.

I do know people who own some of these types of guns. They're responsible, train, and treat the weapons with the respect and care they are due. But I still don't think they should have them.

I was refraining from making a comment that these would be easy to spot because they were actually being helpful and (apparently) answering the question..

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact