paperplane

joined 2 years ago
[–] [email protected] 2 points 4 hours ago

Should also be noted that macOS does support Bluetooth File Transfer natively, so they did already implement it elsewhere.

[–] [email protected] 50 points 1 week ago

JS is fine, it's more that people overdo it and bundle their heavy, deeply layered frameworks with thousands of npm dependencies for the web. Often times analytics/tracking/ad libraries are a major contributor of bloat, I once shrunk down a package-lock from thousands of lines to a few hundred just by stripping the telemetry libraries from an open-source app.

Use the right tool for the job. Sometimes it's a static page, sometimes a server-rendered dynamic page and sometimes a single-page application, all of those can be made performant.

[–] [email protected] 4 points 2 weeks ago (1 children)

Having the ability to overload functions or constructors without a million Stuff::with_x variants is something I consider more ergonomic and not unsafe. I know the Rust community prefers explicitness in many places, but explicitness and safety are somewhat orthogonal in language design. I consider e.g. Swift to be a safe and ergonomic/sugared language, that borrows, no pun intended, a lot of ideas from Rust

[–] [email protected] 6 points 2 weeks ago (3 children)

As long as you limit yourself to a subset of modern C++, it's actually a decent language. Less guardrails than Rust, but more syntactic sugar (think overloading, default parameters, implicit this, implicit reference-taking, implicit conversions). You could argue those are anti-features, but even as someone who really likes Rust, I gotta admit C++ is occasionally more ergonomic.

[–] [email protected] 9 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

VSCode + CodeLLDB is great (and FOSS), surprised no one mentioned this yet

[–] [email protected] 5 points 1 month ago* (last edited 1 month ago)

Seriously. There are a lot of parallels between GPUs (or NPUs for ML inference) and quantum processors in terms of being architected towards a more specialized form of computation and I could totally see QPUs being a thing in the future, probably mostly for number cruncing (see Grover/Shor's algorithms). Though if Grover search suddenly becomes the way of quickly searching for files or something, who knows, maybe this might be more useful for general computing than we think.

In the 80s no one thought computers would be something normal people would use at home, they were seen as a tool for mathematicians and nerds. Now look at the world today. Who knows what the future will hold.

[–] [email protected] 4 points 2 months ago

I know a bunch of larger C++ apps that use vcpkg for cross-platform (Windows/macOS/Linux) builds of their dependencies and it seems to work pretty well

[–] [email protected] 16 points 2 months ago (2 children)

When case insensitivity is the default I always wonder how many apps unknowingly rely on that due to typos somewhere. I encountered this once while porting a Windows/macOS app to Linux that someone imported a module with the wrong case and nobody noticed

[–] [email protected] 5 points 5 months ago

Tbh rust-analyzer is still pretty great. What bothers me more is that Kotlin is pretty much the only language without an official language server, because it doesn't align with their business interests...

[–] [email protected] 2 points 6 months ago

It's opt-in in Swift 5 mode and opt-out in Swift 6 mode, the Swift 6 compiler supports both modes though and lets you migrate a codebase on a module-by-module basis.

Agree that opt-in sort of defeats the point, but in practice it's a sort of unavoidable compromise (and similar to unsafe Rust there will always be escape hatches)

[–] [email protected] 2 points 6 months ago (2 children)

Swift does have data race safety as of Swift 6 with their actor-based concurrency model and are introducing noncopyable types/a more sophisticated ownership model over the next few releases

[–] [email protected] 1 points 6 months ago (4 children)

Swift fits the description too

view more: next ›