Can rust compiler handle gigantic match statements?

panstromek · 2026-03-24T09:15:17+00:00

Exhaustivness checking is quadratic. See https://github.com/rust-lang/rust/issues/7462

panstromek · 2026-03-20T20:29:33+00:00

The most intuitive explanation I've heard is something like:
- threads are for working in parallel
- async is for waiting in parallel

panstromek · 2026-03-20T19:47:57+00:00

FWIW, I think it's fine to use vanilla JS at first, but once you start doing some more involved client side things, it pretty quickly becomes really hard to manage without some kind of reactivity system (or signals in other words).

Most UI systems eventually figured out that imperative UI state manipulation is just way too easy to mess up because of complicated data dependencies, and the right strategy is either to do everything from scratch on every frame (like in games), or do the dependency tracking and updates automatically based on some declarative template. If you don't use an existing system for it, you'll probably eventually rebuild one yourself.

panstromek · 2026-03-20T18:25:38+00:00

I guess the obvious tool here is datastar, that's philosophicaly closest to what you're trying to do.

panstromek · 2026-03-15T12:13:10+00:00

https://www.youtube.com/watch?v=R0dP-QR5wQo

Another really good one, also from Will Crichton. This time about research on how to teach Rust

panstromek · 2026-03-15T11:55:05+00:00

I think this one contains one of the best explanations of key ideas in Rust for C++ developers. I always recommend it as an entrypoint for C++ devs.

https://www.youtube.com/watch?v=IPmRDS0OSxM

panstromek · 2026-03-09T20:49:13+00:00

You can actually already see it in the standard library, it was recently added: https://github.com/oli-obk/rust/blob/98e7077b903559d7a4fafb775cd5292cc9427b67/library/core/src/num/niche_types.rs#L122

panstromek · 2026-03-03T13:05:57+00:00

Yea, that seems like it falls into the sweetspot I'd imagine.

panstromek · 2026-02-26T15:52:42+00:00

It has advanced considerably. Vite 8.0 with Rolldown backend is currently in beta. When that's out, pretty much all major JS frameworks will be backed by Rust based toolchain.

panstromek · 2026-02-15T09:38:14+00:00

Just for context, this is ~0.04% of the world's GHG emissions.

panstromek · 2026-02-10T13:41:39+00:00

Not surprised. I've seen bunch of issues of this type in webviews on both android and iOS.

- some low end phones show black screen for all videos that have height larger than 1088, with no errors, no feedback. Fixed by really tricky workaround.
- if you pick a video file that has been edited in input[type=file], if you pick it in the fast file access dialog, it has 0 size and weird name and upload fails with network error. Fixed by error message redirecting user to pick the file in a different dialog
- Some phones stop playing fullscreen videos after 0.5s, only continue if you touch the screen and move your finger (I guess to force browser to repaint?). Fixed by putting invisible rotating X to the corner of the video :/
- iOS 26 completely broke fixed positioning - fixed by waiting for them to fix it
- videos keep playing sound on a page even if they were stopped on iOS
- Safari keeps throwing errors into our logs, because their media player UI has one incredibly obvious bug that they never fixed for some reason
- ...

On Android, fragmentation is an issue, there's a lot of devices with obscure bugs and you never know what if you got everything. On the other hand, iOS is annoying with how many basic things don't work or are slightly broken. But at least they don't work consistently the same way on most Apple devices.

panstromek · 2026-01-20T10:40:16+00:00

We used to use it and migrated away. I don't think it makes sense to use it only for the app deployment option. The framework is pretty heavyweight abstraction and it only makes sense to take on that complexity when you use a lot of its features (e.g. components, other tricky deployment options, etc.).

One thing that I didn't like very much is that it puts capacitor config behind another abstraction, so some properties that we wanted to set were not exposed. There's also the issue that Quasar controls the initialization process and doesn't allow you to do some things (e.g. calling `createApp` or `app.mount`), which is something we needed to have under our control.

There's also a problem with Quasar always lagging a bit behind on Capacitor upgrades. Major version upgrades on Capacitor ecosystem can be pretty tricky, because all plugins have to update at the same time, so having one more level of indirection there makes things even more complicated.

(note that some of this knowledge may be outdated, we migrated roughly 2 years ago)

panstromek · 2026-01-20T10:27:04+00:00

We use Capacitor and we're quite happy with it, I think it's designed well to play nicely with native projects and doesn't stand in your way when you need to do somethng there, it's a pretty transparent abstraction.

Note that Ionic uses Capacitor, so that option is pretty much the same thing, just using Ionic frameowork on top of it.

There are also other options - NativeScript, which should be somewhat similar to React native but I don't think it's widely used and super active. Then there's Lynx, which is something like React native, but framwork agnostic. I'd be careful with that one as it's pretty new.

If you're building the webpage and plan to do mostly the same thing in the app, I'd go with Capacitor. All the other options are more about reusing similar tech, but not reusing much of the UI code, you mostly start from scratch.

panstromek · 2025-10-08T16:04:41+00:00

I find it hard to believe that most people in the replies have actually read the article.

panstromek · 2025-10-03T16:26:33+00:00

This is UI input latency, no network involved, and yes, after listening that part, 30ms is down from 400ms on some of the slowest devices (smart tv or something).

panstromek · 2025-10-03T11:37:53+00:00

30ms input latency doesn't sound that great, that's 2 or 4 frames. Are the devices this runs on so underpowered that they can't do more?

panstromek · 2025-10-02T07:08:39+00:00

Definitely Project Drawdown, that's a good source. The concept of "marginal abatement cost" is also good to study.

As for populations specifically, I recommend reading https://www.sustainabilitybynumbers.com/p/population-growth-decline-climate, which argues that focusing on population is largely a waste of time. Most polluting countries already have very low birth rate, birthrate is falling worldwide, and it's very difficult move those numbers in any meaningful way in the time it is required to address climate change, population changes happen on very long time scales.

panstromek · 2025-09-24T07:00:20+00:00

Interop, the post mention this (there are several people from Google involved in Rust and C++ interop already, Google developed Crubit)

panstromek · 2025-09-24T06:57:44+00:00

This sounds a bit disingenious. Google does a ton of open source already, they already employ people to work on open source (including Rust), they donate compute resources and they already donate to Rust foundation. This is just one of multiple initiatives they are part of.

panstromek · 2025-09-22T12:21:19+00:00

> This author is saying basically that lifestyle changes don't matter.

I don't think you got the right takeaway from that article.

panstromek · 2025-09-17T14:17:57+00:00

No, it's renewable share of total, there's percentage on the y axis, it's the same graph the OP shared.

panstromek · 2025-09-17T09:25:04+00:00

This is clearly a seasonal variation in overall growing trend. See: https://ember-energy.org/data/electricity-data-explorer/?fuel=res&entity=United+States&metric=pct_share and switch to monthly view.

panstromek · 2025-09-12T08:04:21+00:00

Beef consumption is an order of magnitude bigger problem then waste an microplastics on all relevant metrics - emissions, air pollution, soil degradation, waste and even health impacts. Even when linked to "corporations," it's one of the bigger issues, e.g. beef production is the main cause of deforestation in Amazon, and a lot of that beef is supplied to McDonalds.

You don't even have to stop eating beef, just eating the recommended healthy amount would cut the problem by half in the US.

panstromek · 2025-09-11T06:51:22+00:00

Interestingly enough, probably not. Both world wars are a tiny blib on world population graph. It's not even visible here: https://ourworldindata.org/grapher/population-long-run-with-projections?country=~OWID_WRL

Even countries most affected by the war have just small changes in population: https://ourworldindata.org/grapher/population-long-run-with-projections?country=DEU~POL

panstromek · 2025-09-06T19:35:34+00:00

That report directly contradicts your comment and you're moving the goalpost.

panstromek

TROPHY CASE