Thinker

How long has it been since you used Teams? I’m no apologist, I have plenty of gripes with that piece of crap software, but this seems like a crazy stretch. Teams makes it almost trivial to embed code blocks with syntax highlighting for a wide array of languages, which can be easily copied out of Teams or opened in a separate viewer for easier reading.

Thank god Temporal is finally in Stage 3, and already rolled out in Firefox. I can’t wait to be done with JS’s Date forever.

I agree, except that we are legally not allowed to control the software on our phones in lots of cases. Notifications, ads, upgrades, etc. are all controlled by the manufacturer and it’s illegal to override their software on the device you own.

Add to that that specific pieces of software are becoming increasingly necessary to function in society, and you start to see that it’s not really a matter of individual choice, anymore than people shopping at walmart can be blamed for buying processed, sugary foods when that’s 90% of what walmart stocks (And all they promote), and walmart is the only affordable option in their community.

Congratulations, you’ve illustrated the difference between syntax and semantics. But any competent compiler also handles semantics (just in a separate phase of compilation), because that’s necessary for any useful conversion to machine code, not to mention optimizations.

Except an LLM has no way to roll anything random, it will just predict the most likely text for a random roll, which isn’t remotely the same thing.

I mean, the simple proof is that Rust has been growing by leaps and bounds in the embedded world, which is the closest to bare metal you get. It’s also being used in the Linux kernel and Windows, and there are several projects building new kernels in pure Rust. So yeah, it’s safe to say that it’s as close to the metal as C.

Also, the comparison to Java is understandable if you’ve only been exposed to Rust by the memes, but it doesn’t hold up in practice. Rust has a lot more syntax than C (although that’s not saying much), but it’s one of the most expressive languages on the market today.

My preferred variation of this is to make it an open question that leaves them in the position of authority, and assumes that they made a deliberate decision.

For example, instead of “Why aren’t you using StandardLib that does 90% of this?”, I would try “Could this be achieved with StandardLib? Seems like it would cover 90% of this”.

For anyone interested in learning more about bloom filters, this is a technical but extremely accessible and easy to follow introduction to them, including some excellent interactive visualizations: https://samwho.dev/bloom-filters/

It’s not just a proposal, it’s already fully defined and almost completely implemented - I believe they’re just waiting on a standards update from ISO for time zone stuff.

I think they’re referring to the fact that Edge runs on the Chromium engine which, as the name implies, is a Google product.

Flatpak is definitely the way to go if you’re still getting started in your Linux journey.

The reason that flatpak apps are typically more up to date is because they are most often managed by the actual developer of the app. In contrast, the default apps in the Pop shop (which are deb packages, but that’s not super important) are managed and updated by popos itself (and/or Ubuntu/Debian that popos is built on), which is why they’re often slower to update. The developer has little to no day of when these packages are updated, and usually most packages are frozen between major releases of the distro.

This is, in part, a correlation. To some extent, compiled Rust is fast because compiling Rust is slow. That is, Rust does a lot of work (static analysis) at compile time so that the runtime binary is as fast as possible.

This is a really neat concept. I love that they’re recognizing the tradeoffs of both tiling and floating window managers and imagining a better way.

I think the mosaic idea is interesting and has a lot of potential. I agree with their self-assessment that it’s success depends greatly on the simplicity and utility of the window preferred size API, and how willing/able app developers are to adopt it. This is unfortunately yet another place where the fragmentation of the Linux ecosystem shows it downsides.

Nonetheless, I’m really hopeful about this. I would love to see a future where mosaic window management becomes ubiquitous. But really I’d be happy as long as my desktop supports configurable workspaces.

Yes, that is true. But actually it’s more than that: you don’t need a dev to display static content or a decent commerce page anymore. Square space and it’s competitors give more options at a better value to the layman than devs using PHP or jQuery could hope to these days. We have the simple websites, so frameworks very specifically target productivity and maintainability for complex web apps.

This is not true. The higher complexity of frameworks is unarguable, but it reflects the higher complexity of modern web apps. The reality is that React/Vue/Svelte achieve things that are simply infeasible with e.g. the LAMP stack or jQuery.