Reading what they're offering, the stand-out to me is making publishing the applications easy for others on your team to use. That would he a pain point for non technical users.

I get your point. But if sharing with others is a vital part of this, then ... they'd be better off sticking to web apps instead :) "Create with glaze, hit publish and we'll give you an url".

Even though they portray some of the benefits of this app as unique to desktop apps, they're not (e.g. storing data on device, offline mode etc.).

Am not a hater. Love Raycast. Saw the post and opened the link intrigued what they came up with and was somewhat disappointed tbh. Good luck to them anyway!

Then the follow up question, how do you combat that? Not likely through developing similar technology.

Same on android chrome, bars are the same height and there're no numbers next to the units.

You need to fill in some example text in the text box above, and it will then compare.

Most organizations I've set Sentry up for tunnel the traffic through their own domain, since many blocking extensions block sentry requeats by default. Their own docs recommend it as well. All that to say, it's not trivial to fully block it and you were probably sending telemetry anyway even with the domain blocked.

With the right tricks (CNAME detection, URL matching) a bunch of ad blocking tools still pick up the first-party proxies, but that only works when directly communicating with the Sentry servers.

Quite a pain that companies refuse to take no for an answer :/

Pessimism is not a uniquely American viewpoint.

"South Korea is second from bottom on our list in terms of the proportion of people saying their country “is heading in the right direction”, with only 15% stating so. A similar sentiment is also felt about the economy. Pessimism is usually the standard for South Korea; however, their economic indicator score has been particularly low in recent times, with just 8% believing the economy is “good”."

https://www.ipsos.com/en-ch/what-worries-world-may-2025?utm_...

I'm not talking about how people feel about their life or country but about the concrete actions their governments are taking to improve their quality of life. For example, they all have high speed rail, something that is essentially impossible to build in the US, whether it be due to budget, regulations or sheer political will.

Florida's Brightline contradicts that, no matter how slow California's HSR project is going. Trust in greed if nothing else. The next one to go up will be LA to Las Vegas.

I assume the startup wasn't also leveraging typescript heavily on the frontend, that tends to shift the weight in its favor. Having one set of tools to use across everything, being able to share logic and types without needing to go through lossy translation layers, and giving (especially small) teams better flexibility to move people around is a huge benefit.

We are using TS on the FE with React.

But the reality is that at some point, your FE and BE teams will diverge anyways and we use an OpenAPI spec as the contract (Nest.js, not Next.js).

So there was no benefit to using TS on both ends; only pain on the BE.

If a team is going to ship an OpenAPI spec and run it through a transformer, then it changes the selection criteria for a BE language:

    - Easy for a TS team to adopt; similar core semantics like `async/await`, exception handling, etc.
    - Flexible and pluggable OpenAPI spec generation for edge cases and advanced scenarios
    - Excellent ORM to improve productivity around CRUD
    - Good tooling
    - Extensive docs, platform maturity, but modern language features

C# meets all of those in ways that no other language and platform does.

I can't speak to your use case, but for past projects I've not only wanted to share types but actual logic. For instance, if you want instantaneous validation on the frontend, while applying the same logic on the backend with submitted data. In many instances that would be simple and maybe even serializable, but in my case I was working with architectural data that had extremely detailed logic for what was and was not valid.

That's simple; check out https://Orval.dev or https://Kubb.dev. Both of which can generate validation code (among other things) from OpenAPI.

Example with .NET: https://github.com/CharlieDigital/dn-kubb

Using a TS validation library like Zod gives you both the shared validation code for both the frontend and backend, the TS types, as well as the json schema for openapi. It's a triple whammy too good to ignore. Especially as a small team it is huge leverage enabling you to go further faster.

Getting a 402 error payment required when I try to run this, I'm guessing all of the credits for the API account have been used up. Great idea though!

It's some Loveable app thing. Fun idea though

Some humans would operate with heightened awareness and caution. Some other humans might be drunk or looking at their phone.

Much of what you suggested would not pass apple review, and would get your app removed from the app store if you tried to hide it during review.

Those are the ones that were high profile enough to warrant a Wikipedia page, it's not exhaustive. Here's a more comprehensive database: https://policecrime.bgsu.edu/

You're still citing arrested, not charged and convicted though. Those are all different, with no guarantee of the officers facing repercussions beyond a brief arrest. While those are still consequences, they have to be consistently applied (which they don't seem to be for police officers in America) or have consequences for consistently poorly behaved officers