brokenbyclouds

Can you go into any additional detail about why firechat shut down?

making web apps is the least exciting thing wasm could be used for. plugin systems, embedded, serverless use cases are much more interesting off the top of my head.

i think we live in a world where we can do both: we can do wasm and we can continue making improvements to the big three webdev tools.

I think this article does a decent job of highlighting many of the reasons why Closure has fallen into obscurity. https://effectivetypescript.com/2023/09/27/closure-compiler/

I feel so seen in such a bad way

I might be misinterpreting what I'm seeing but I don't see titles on any of them. For instance, on one in southern California, the icon showing the podcast art makes it clear that the title of the podcast is Ridiculous History, but when I tap on it, I only see the episode title and have no other clue to tell me what podcast it actually is that this episode is part of.

Now that I'm describing it in more detail I think what I should have said initially is that I'm looking for the title of the podcast itself, not just the episode title.

Fantastic idea. Minor issue is that when you tap on one of the flags, you get the podcast episode notes but you don't get the title of the podcast. Title needs to be prominent.

I mean, that's almost exactly how mainstream Hollywood treats actors, women in particular, as well. It tracks to me.

Intentions are useless in this case. What matters are the incentives.

It's ok everyone, they must misspelled Go as Kotlin

The lake is great but it has good days and bad days like anything else. I lived near the lake for years and still think it's heart-rendingly beautiful. Flies weren't usually a problem, there are all kinds of animals living nearby that you wouldn't expect like seagulls, buffalo, etc.

And then yes there were occasional times where the lake would recede a bit and the smell could make you flinch from miles and miles away.

As others have said, the problem is the lake drying up from lack of incoming water.

The consequences of the lake drying up is the end of the "lake effect" cycle, the arsenic in the dried lakebed being released into the air, etc

The legal system governing water rights in the western United States is utterly absurd. I think it was a stupid system in the beginning but is orders of magnitude more stupid today given the challenges facing the region.

It also happens to be a system that people will legitimately fight and kill others to preserve. The political challenge to change this system is enormous and I'd bet most people have no idea how fucked it is.

This is a very naive, inexperienced view of politics. In politics, many people have acted in ways they did not believe were right. Many others have acted without a thought given to whether they were right. In some situations, wars have resulted from political actions, but in many other instances, political actions has prevented wars that may otherwise have taken place.

Not taking sides is a political action in itself. Not wanting to be involved doesn't mean you aren't involved.

Dear God this is a tired point. The rest of the damn paragraph of the Wikipedia article fully addresses that. Nobody who uses the term "serverless" thinks that magic fairies are replacing servers. The point is who is managing it for your application or business.

https://shatterzone.substack.com/p/ai-is-coming-for-your-chi...

100% rollout is the default for me when submitting an app. You're saying it's not for you?

"I reply to comments without reading them or understanding them."

"I wish this person being persecuted by her government would stop being so political"

Use Expo. Ignore anything that ever mentions having to "eject" because that's the giveaway that the information is hopelessly, uselessly out of date. It's fine.

The single threading isn't an issue for many backend use cases and even though JS was initially designed for use in the browser, there's been a decade of development on the language and ecosystem for using it outside the browser.

Ejecting is an outdated concept when it comes to Expo for the past two years or so. The eject command in the cli is just an alias for the prebuild command even.

The way Expo builds your app these days let's you add native code as you want, modify your Gradle and pods files as needed, and you can still be on their managed workflow where you don't ever need to have Android and iOS folders in your repo. It's a really great time to be using Expo.

There's nothing that requires you to use EAS Update though. You could just stick to submitting builds through the app store like normal.

React Native over flutter all day every day. There's almost nothing you can't do in the react native world when sticking with the managed Expo workflow these days.

After Compose Multiplatform has matured a bit more I'd be seriously considering using that for everything going forward.

https://www.jetbrains.com/lp/compose-multiplatform/

I'm skeptical that was ever the rain for the rationing.

Are you including Discord in the list of people using Discord as a forums?

https://discord.com/blog/forum-channels-space-for-organized-...

Not trying to be sarcastic, just haven't had a chance to use this feature and wasn't sure if you were taking that into account.

I thought the secret to getting to the front page was posting about a neat thing you can do with sqlite

The Expo team has done fantastic work to make building react native apps easy and flexible. Nothing but good things to say about their current direction and approach.

I think that they meant that you'll know Twitter has definitely hit it's decline when other media is focusing on what's happening on other platforms instead of Twitter.

This is the equivalent of a first year physics student saying Einstein comes off like a newb.

Nicole Forsgren is legit.

I believe react native uses zerover and will therefore never hit 1.0