b_e_n_t_o_n

> Rust is not to blame

Isn't that an unfalsifiable statement until the coreutils get written in another language and can be compared?

It's not about rust specifically, it's about replacing working software with rewrites and going from a code base written in a single language to one written in multiple.

The challenge will be that first move, yeah. Current social media companies have every incentive not to let users do that.

I'm a simple man, I see a Dan post and I click.

I'm a bit concerned that the open web only won because of first mover advantage. What gives me hope is OSS winning.

I'd love to see something like atproto win though. It's clear that a major issue with social media is network effects preventing better apps from becoming popular.

Hmm, this plus the performance regressions makes me wonder if it's too soon to move to the rust version of Coreutils. And makes me wonder if this is gonna cause more pushback regarding the rust in the kernel movement.

Neat. Although I get the feeling you're more technical than you give yourself credit for. I gotta try the Figma MCP server and see if it can generate HTML and styles, as that's the most boilerplaty part of front end.

Not gonna lie I also read it as Australia....

I upgraded on launch and didn't notice anything too wrong. I like the UI and performance seems fine?

I too am especially prone to breaking my OS, as well as the software that runs on it. You aren't alone lol.

I think this change makes sense on both platforms. If you're gonna use it as an example of why merging the platforms is bad, I think you just strengthen the opposite argument.

I'm the same but opposite, I like Rust but find myself using Swift most of the time. They sort of do the same thing but coming from opposite directions. Can't go wrong with either imo.

I really do wanna try Kotlin at some point as well. Rust, Kotlin, and Swift feel like the future of languages to me.

Have you tried it since 6.2 came out with approachable concurrency enabled? The compiler is quite useful.

Swift! It actually has a pretty big server community, Vapor and Hummingbird are both great frameworks, Apple has been replacing some of their Java services with it, it's open source and cross platform and Apple seems serious about making it viable on Linux, which it is. No need for Xcode, it has an open source LSP and first class VSCode plugin.

Plus it's a fun language to write. Some people say it's a nicer, higher level Rust.

I also like the look of Kotlin but I've never used it. I think Kotlin and Swift are the two premier modern multi-paradigm languages.

I'm kind of in the same boat although the timeline is more compressed. People claim they're more productive and that AI is capable of building large systems but I've yet to see any actual evidence of this. And the people who make these claims also seem to end up spending a ton of time prompting to the point where I wonder if it would have been faster for them to write the code manually, maybe with copilot's inline completions.

Is the desktop version more than just a webview? :P

I wonder if it's a mistranslation and Hanh means it's not complicated to be a Buddha. Many things in life are very simple, and also very hard.

Even the apps I pay (or paid) for directly are local first. Eg the Adobe suite, Unity Pro, Affinity. Some, like Copilot, do require internet but there is no feasible way to get offline access for an online service.

What are some examples of popular apps that do this which aren't web apps, and could feasibly work offline? Every native app I use is local-first. Eg. Photoshop, Blender, Figma, Xcode, Zed, Kitty, Affinity Photo/Designer, Notes, Music, Calendar, Messenger, Maps, Email, etc.

I think most native apps (at least that I use) are local first. I can't think of a single one that requires a consistent internet connection to function, that otherwise could run locally. The whole "local-first" trend that has cropped up lately was at least partially influenced by web apps like Linear and Figma, and if you look at the libraries and writing being produced on this topic it's almost exclusively Javascript and about making crud web apps local-first.

Perhaps I'm missing something, but aren't local-first apps the overwhelming norm? Like if I think about the apps I use, my friends use etc, most of them are local. Unless the author means "local first web apps", which would make more sense. And I think the oxymoronic nature of a "local first web app" gives a clue as to their unpopularity.

if we can split an atom we can make a really long cable surely

We don't even really have time or energy to debate the higher levels with other people. Maybe if it's a friend or family or someone you're close with. But arguing with strangers, at least imo, is a total waste of time most of the time.

Just nod and smile :)

Why can't we just connect a really long cable from the moon back to earth and wrap it in insulation??

Why don't we just put a bunch of reactors on the moon? Seems safer than putting them on earth.

Struct embedding is sugar for

   type Foo struct {
      MyType MyType
   }

   myFoo.MyType.url

So it would resolve myFoo.MyType1.url over myFoo.MyType2.NestedType.url

Is it possible that it's like every other language, with flaws and tradeoffs that don't always make sense to everyone? Why make it more complicated than that?

Yeah it makes sense to me as well.

Yeah and you can explicitly assert a null is a string in TS, but it's explicit. You can't build a Rust program without those asserts but it's trivial to skip the type checking for TS which is more of a linter than a type system.

node main.js just runs the code. you could simply not run tsc, which plenty of people do. can you ignore all type errors in Rust?

JavaScript had to implement these checks because you could pass a function literally anything and it was on the implementation to deal with it. Typescript has this same problem tbh.