dschuessler

We wrote E2E tests with Cypress before Playwright was around and it was awful. The API is weird to the extent that it is basically a DSL based on Javascript. And the tests were flaky because rerenderings could happen between Cypress getting the DOM element and interacting with it. It seems they haven't fixed that one to this day.[0]

The team is also very confident about their approach. They build their own asynchronous concepts that are not interoperable with async/await, openly acknowledge that it is hard to wrap your head around and then dismiss these concerns by asserting that "Asynchronous APIs are here to stay in JavaScript.".[1] The Github issue about the lost DOM elements is also full of answers by a team member intent on writing blog posts that explain what the user is doing wrong rather than fixing the root problem.

I'm really glad that Playwright came around. It is intuitive, pragmatic and has none of the problems above.

[0]: https://github.com/cypress-io/cypress/issues/7306

[1]: https://docs.cypress.io/guides/core-concepts/variables-and-a...

I tried it with one of these image-based PDFs and didn't get it to work. Is this Apple-Silicon-only? Or is there any other step you need to do?

I love HN for tech discussions in which the actual people involved pop up. Thank you for that great piece of software you worked on.

Out of curiosity, was there a team exclusively dedicated to the Preview app? How autonomous were you in deciding how to improve the application?

Preview is one of the single-best pieces of software I use in my daily life. It manages to be incredibly powerful without bloating the UI while still remaining usable. It is unfortunate the name suggests it being a simple preview application. It's far from it.

Given they are not interested in a tech career, I'd say they should learn to program if they:

- want to do something with computers no currently existing program allows them to,

- want to create something with artistic value (games, websites, computer graphics),

- enjoy it for the sake of it.

I can't come up with any other reason why they should.

On 60fps every frame is displayed for about 16ms. So lags can only appear in multiples of 16ms. How do you come up with 1-2 ms delay per keystroke?

To answer your question though: I find Slack's typing responsiveness acceptable.

EDIT: To narrow down the source of your problem you might try to use Slack in the app if you are using it in the browser or vice versa.

Not a light switch but German computer mouse producer Nager IT tries to disclose their supply chain. Not even they have a clear understanding of where their raw materials come from...

https://www.nager-it.de/static/pdf/en_lieferkette.pdf

Now I want to see an actual match with these cards. Imagine having to come up with fitting strategies for that bunch of uncanny-valley Pokémon you've been dealt with. Given the vastly varying damage some of these critters do, it will probably be more of a game of chance.

I wonder if anyone had tried to get it running on Wine. If they have a working Windows binary, it should work just fine for decades to come.

I am rather concerned about the recent willingness of some HN commenters to jettison basic practices of civilised discourse when it even remotely involves the Russian-Ukrainian conflict.

If one has a convincing argument, one should just make it. There is nothing pedantic about that. Insinuating derangement and denying common sense should not be necessary. Those who feel they have to resort to such practices usually do so precisely because they are unable to make a convincing argument. Why else would one act like this?

From the Hacker News Guidelines on commenting (https://news.ycombinator.com/newsguidelines.html):

> Please don't post insinuations about astroturfing, shilling, bots, brigading, foreign agents and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email hn@ycombinator.com and we'll look at the data.

If you want to dodge leetcode interviews, consider https://github.com/poteto/hiring-without-whiteboards

As a German, I can assure you: It is neither used, nor permitted. I like the idea though.

That's a great idea and it turned out way better than the headline made me fear. You keep the spirit of her drawings but present it in a really creative way.

I also like the no-bs approach on the technical side. This is indeed a page that does not need a single line of Javascript and it's a testament to what you can do with most basic web technology. I hope this lightness will have its big comeback someday.

I wonder if this modification could at least be made harder by having some kind of heartbeat. Build in a microphone whose sole purpose is to receive inaudible, high frequency impulses (maybe a hash signal?) from the speaker every once in a while. If the signal does not arrive in time, the AirTag shuts off.

Of course, no measure can beat physical access to the device but you could at least make the tampering about as expensive as building your own device from scratch.

This seems to be the golden way of solving the problem Postman is attempting to solve. Have your request collection as code that you can develop with your features and check into your VCS.

I always dreamed of something like this and was more than surprised that it doesn't seem to exist. Does anyone know of a similar solution for node.js?

> but it shows the lack of discoverability that happens when the list of settings gets long and you have to dig for them.

I wonder to what extent command palettes are the solution. At least for me, they are the pinnacle of discoverability. Throw the list of all settings and actions into an easily discoverable command palette and let the user search for them by filtering the list. Make it fuzzy enough to account for different formulations of the problem. VSCode does it (mostly) right.

Thinking about it again, I think the actual conflation I was getting at is the equivalence of "not being kind" and "being a prick" that you implicate right from the start.

> Kindness Is A Hidden Software Engineering Superpower. Sounds fuzzy and a bit bulls*itty, right? Well, it turns out that if your teammates are pricks, you tend to quit or stay and be unhappy and demotivated.

But one is not automatically a prick if one is not kind in the sense you specify later on. Not smiling, not being compassionate, not asking for co-workers' weekends does not make anyone a prick. At least I'd hope so.

Therefore, it seems to me that you are writing about two things at once without acknowledging their difference: "Being kind" and "not being a prick". I’d pick one and go with it but not both at once.

(As an aside, I became more aware of that difference after watching the series "The Fall" about a Belfast police task force trying to catch a murderer. Some of the characters in the police force (esp. Anderson's) were not kind, but they were not pricks either. They were more or less just doing what was needed to get the job done. It is this series that recently made me aware of how unfashionable this kind of work culture has become in my domain.)

Lots of good advice. However, I feel that in recent years a certain kind of professionalism is in decline that I begin to miss. It is the culture of professionalism in which personal care is not being conflated with professional care. This article is partly engaging in this conflation.

Caring about co-worker's weekends and "rudeness, bullying, demeaning comments, and insults" are not values on the same dimension. Neither are "compassionate" and "critical" code reviews. I do not want people to see me on a slope leading to misconduct just because I don't care about their weekends or show compassion in my code reviews. I really wished that these things were kept apart.

Have you directly compared one and the same movie on Netflix and another medium (DVD/Blu-Ray/another streaming service)? Maybe your problem isn't with Netflix.

Movies generally tend to have a high dynamic range. That's how they play in the cinema where action scenes are supposed to stand out from the dialogue and that's how many people want them in their home theatres as well.

I personally did not notice anything special with the audio on Netflix.

I do not know the answer but here is another place where people might be able to help you out: https://retrocomputing.stackexchange.com/

I am curious about your third point. Why do you consider project choices that are good for "big tech" to be a reason to turn away from Linux?

I would have assumed that many contributions by corporations are in the end a net benefit for both corporations and customers or at least not detrimental to customers.

Do you consider some corporate contributions to Linux to be harmful towards consumers? Or is it more a decision of principle?

Not necessarily. If you get used to using `delete` all the time, that is most likely what you would use on the server too. Once you trip over it missing, you are reminded that you are in dangerous territory.

Working link: https://medium.com/@scriddie/multiple-regression-in-pure-sql...

Here is more information on the mentioned fund: https://sovereigntechfund.de/en

Judging from the Github project page, it uses Wine itself, so is probably just a GUI frontend to it.

What makes you think that a computer analogy is an apt description of the inner workings of the brain in the first place?

I see this analogy sometimes here on HN but as far as I can recall I have never heard anyone using it outside, let alone medical experts. So I am skeptical of the idea that this is the right angle to look at the brain.

Yes, I see how it can be understood that way. GP has edited it anyways to clarify this point.

You literally edited that in after my answer.

This is breathtakingly bad advice from a security perspective. If secrets might sit around in a repository you don't just publish it and bet on people not looking for them, at least not if data security is of any worth to you.