ARussell

It would be nice to see how this differs from SolidJS.

I'm a bit confused by the marketing verbiage and tool name. Is this going to target React only, or will it (eventually) support other solutions which use JSX, such as SolidJS?

Who would control it? There isn't just one "Linux community". There are multiple organizations that use Linux, and the ones that are well-managed tend to do the best. How would the key people behind Gnome and KDE resolve their differences, or any of the smaller projects? Should everyone just use ChromeOS?

I read this article and ended up with the exact same question. Does it mean that it wants to imitate Chromebooks, where the most important app you use is the browser, and all of your apps are in the cloud rather than on the desktop?

Perhaps you are right, and also then again perhaps those companies find that they have cause to file a lawsuit.

I'm not GP. I didn't make that argument. I agree that Amazon is not obliged to allow just anyone on their platform. Sellers must abide by the rules that Amazon sets in place. At the same time, Amazon must abide by the laws of the locations at which it wants to sell. So if a state says that they cannot force a seller to keep their lowest price on Amazon, then that's the way it is.

And Amazon needs to follow the rules and laws of the place that IT'S trying to sell at.

Personally I just don't think Ramda fits really well with JavaScript's mutable and often object-oriented nature. It goes against the grain too much for my taste, and it doesn't work very well with Typescript.

In a professional setting I will probably always reach for Lodash due to it's maturity and mindshare. Personally, though, I really prefer Remeda (https://github.com/remeda/remeda) as a pragmatic and flexible API.

Sure, I can clarify.

1. I know GitHub stars aren't everything, but Playwright has 41.9k at the moment, and Cypress has 40.5k.

2. Playwright is backed by Microsoft, and given how happy I've been with how they manage Typescript, that makes it a pretty safe bet to me.

3. Cypress is much older, so I discount a lot of the blog posts in my evaluations. In fact, I count such things against it sometimes, because oftentimes when I'm hunting for a solution to a problem, all I can find are outdated answers. I run into this a lot with AngularJS and Angular.

4. Playwright is included in most of the recent comparison articles I've run across. I don't really keep track of these, but searching again I quickly ran across 2 examples:

  * https://blog.checklyhq.com/cypress-vs-selenium-vs-playwright-vs-puppeteer-speed-comparison/
  * https://www.testim.io/blog/puppeteer-selenium-playwright-cypress-how-to-choose/

Thanks for the answer! I'm probably personally leaning towards using Playwright for future projects, reading that. I believe Playwright may be passing Cypress in community size, and simplicity is subjective. They both look quite similar, from this outsider's perspective.

You recommend Cypress as an "obvious" choice, so I am curious whether you evaluated Playwright. If you did, why you find Cypress to be the clearly superior choice? Genuine question.

I refused to ever subscribe to cable television because of commercials, and I suspect I am not the only one. I never subscribed to Hulu, either, for the same reason (if they have an ad-free offering now, I've missed it because I stopped paying attention to them). I also will not use Netflix's ad-driven tier when it comes out.

Kagi (a search engine you pay for) has a feature called Lenses. One of the default lenses is for "Discussions". It's been quite helpful for me, personally, so far.

I think "tech company" is a near-useless label, anyway. I struggle to think of any company that isn't, or at least shouldn't be, a tech company. Everyone uses technology to provide their product or service, even if they are rudimentary ones. There are those companies that are pushing the boundaries of what was previously possible, sure, and if that's what people agree is the definition of "tech company" (high innovation), then surely Netflix counts. No one watched much TV on computers or phones before them.

I'm sure a lot of hard work went into this, so I mean no offense here when I give my honest feelings.

The big differences between v1 and v2 make me uneasy. I am reminded of the constant API churn of React-Router, or the complete change from AngularJS to Angular. This approach makes me very hesitant to learn the library, because I am afraid of having the choice of painful upgrade or a dead dependency down the road.

I am also wary of the library being VC-funded, because I am afraid of what kinds of features will be held at ransom down the line once they need to start making money.

You could opt to improve upon the standard practice, right? I have only played with Demo a little, but the deps file seems only like a convention rather than a strict rule.

Why not instead create a deps directory, and keep in it one file per dependency? Inside each file, you re-export the library from URL.

This way you can import from files rather than URLs elsewhere in your code, and it should be clear which dependency is being imported from the file name itself.

I asked this question, as well, and the answer I got is that Deno already does these things.

After about 14 years of considering Vim as my primary text editor and slowly attempting to forge a configuration that I was happy with, I recently resigned to the fact that I simply was never going to actually reach that point of having a configuration I'm happy with. I don't use Vim outside of the terminal; I spend most of my time in IntelliJ IDEA. I never found the Vim key bindings in IntelliJ IDEA close enough to the real thing to use, either.

So if I can't keep muscle memory of Vim keybindings, and I have never found a Vim configuration I've been happy with, why was I so stubbornly holding onto the idea that Vim was the right editor of choice for me? I don't know, but I finally changed my mind and looked for another editor. A dead simple one with sane defaults.

It came down to Nano vs Micro for me. Both are great. I ended up liking Micro a bit better, although I'm very glad to see that Nano development is still active.

No, you're not. But I'd not say something beforehand, because there's nothing wrong with such a project succeeding if that's what ended up happening. Being able to say "I told you so" isn't worth it.

Although I personally think Rust is fine. It's just that I thought the frontend and backend split is too complex. I am looking for something simpler than neovim, personally, and xi didn't tick that box for me.

Will Rust bindings be available, despite their decision to write this in C++?

You absolutely could. But most don't, because, as has already been mentioned in this thread, and explained by Adam Watham himself(1), it's not usually the appropriate thing to do. Components are usually a better abstraction than CSS classes.

1: https://adamwathan.me/css-utility-classes-and-separation-of-...

Personally, I feel like they should have tightened integration of Google Photos with one of their existing messaging apps rather than creating yet another messaging app within Google Photos. If I were a betting person, I'd say that this feature is one of those that Google will end up just removing.

Wasn't support for that removed?

I'm not saying the UI of their system is great, since I have never seen it, but I believe it's a better idea to have the "test" alert be very similar to the real one. When the time comes to send a real alert, the operators should be practiced. Diverging the UI could cause confusion in am actual emergency, wasting precious moments.

This is very similar to my experience, as well. I tried Nix for over a year. It has excellent ideas and principles. In practice, though, I ran into so many bugs that were near impossible for me to figure out on my own. I personally didn't find the community all that helpful, either. YMMV.

I'm curious which plugin you used, and why you didn't like it?

This is unfortunate. I have their alarm and find it quite useful. It's nice being woken up at a decent time in my sleep cycle rather than having to hit the snooze button so often because I was woken from a deep sleep. Are there any alternatives?

I'm probably hoping too much if I want them to give me a way to root my Sense as well as an open source version of their server software I can run and point my Sense to.

I'm confused. Isn't Eta the new name for GHCVM? https://github.com/typelead/eta/commit/76cdf91843ad679bcb441...

Maybe try out Nix while you're at it, too! I'm using NixOS, and I'm pretty happy with it so far. The standalone package manager fills the same niche as Homebrew, I think.

For some reason I've been thinking that Akka HTTP is basically Spray 2.0. Is that not right?