naman34

C# is a faster Java.

That second things is a typo.

swift-wasm exists

The feature exists, but it’s not so easy because there is a lack of documentation.

Good to know. It’s an old blog and I’ll be moving it away soon. This just makes that work more urgent for me.

Seift has great C, C++ and Rust interop.

And despite Swift for Tensorflow being killed, there’s still decent python interop.

Now, setting up a project for that is probably quite hard because the documentation is non-existent.

There’s lots of interesting ideas in languages but most of them fail to be mainstream at all. When comparing new languages at the level of Rust, Swift, Go and maybe Kotlin are the only real competitors.

Sadly, Swift also produces large binaries unless you use Embedded Swift which is still early.

The documentation uses “copied” for value types that are copy-on-write.

The documentation has oversimplified a bunch of the mental model and it causes incorrect understanding.

Swift’s documentation is quite bad TBH. The biggest thing that still needs to be improved a lot.

And that article is from 2020. A lot has changed since.

I added a new section to the post with links and information to dispel this myth that Swift is only for Apple platforms.

Saw the talk announcing Rise in person and it was very impressive and seems like a pragmatic approach to server-driven UI.

It’s server components without the wait.

We're solving the performance pitfall of CSS-in-JS libraries by making a compiler instead. In the vast majority of cases, there should be zero runtime cost to using StyleX.

Griffel and StyleX arrived at very similar ideas and we've discussed the possibility of sharing more code between the two.

There are some meaningful differences in the API choices, but the high-level design is pretty much the same.

Hey! I'm the maintainer of StyleX and I just wanted to say that you would probably like PandaCSS or Tamagui.

We don't think the Tailwind way of styling is readable in the long term, but we see the value is being able to author that way. We're looking into a VS Code plugin, that would let you author your styles inline and extract them out when you save.

Hey! We support dynamic styles, too.

We're continuing to work on optimisations for StyleX, and I'll be looking at Tamagui for inspiration!

StyleX supports this pattern. You can export a bunch of styles in one file and then import and use them in another.

You can import many different styles and apply them conditionally etc.

Also, completely dynamic styles are supported. We were inspired by Linaria's solution to generate CSS vars and set their value with inline styles.

Thanks WA. Autocorrect can still bite you!

I agree that it is tough to compete with twitter. They have money and a huge reach. Periscope will probably get some advantage when it comes to integration with Twitter.

But there are also downsides to being tied to twitter. For example, I don't expect Periscope to every integrate with Facebook or any other competing platform. Upclose already works with Facebook.

I'm not trying to say that this is going to be easy. I'm just saying that don't count us out yet.

Hi Tim, video streaming usually needs a good internet connection. But with upclose, you should still be able to stream reliably to people near you, as we use a peer-to-peer streaming solution.

Disclaimer: I work for upclose.me

I think Periscope is great. Other than the nice logo, Meerkat was always very rough around the edges, Periscope actually looks very nice in comparison.

It also has less latency.

We are obviously looking at the competition very seriously, here at upclose. For now, we have confidence in our ability to compete. Though we haven't managed to ride the hype wave like Meerkat and Periscope, we have steady growth.

We are also the only platform that also exists on web and Android, and with virtually no latency.

I would love to hear your thoughts on upclose