It doesn’t take a genius to realize the night-and-day difference between how an adult and a child talk or write. You’re interacting with a glorified pattern detector. It’s its whole job!
It's been six years and rust-analyzer remains the slowest and buggiest LSP I use. It's amazing how quickly it goes from "incredibly responsive" to "it's faster to compile in another terminal window" as the project size inches upward. (even with splitting into multiple crates!)
@jorandirkgreef@sehz_ai They’re both Turing complete languages, obviously, but some patterns might be more awkward or require more friction. But you might be surprised at the kind of abstractions rust lets you write, even for non-idiomatic patterns, with some creative lifetime annotations. Zig is nice.
@CryptoCyberia Windows 2000 was undeniably stable. But it was still common and easy for bad third party drivers to give you BSODs because it was before user mode drivers were a thing.
[2]After our failed competition, we headed to Apple Store and bought the mbp m5 and spent less than half an hour to set it up and found a fixed offset is changed 1 bit on it, so we just change 1 bit on our exp and it worked with a 100% success rate. Yes just 1 bit change, 1 to 2.
Anyone remember when Bun forked Zig and said they "optimized the compiler with AI"?
They made the compiler non-deterministic -- Meaning sometimes it will work, sometimes it MAY not.
Schrodinger's cat ahh compiler. 🤡
Boost Blueprint 048: Boost.PropertyTree. A generic hierarchical key-value store that reads and writes JSON, XML, INI, and its own INFO format through one unified API
Query nested values with dot-delimited paths: pt.get<int>("server.port"). If the key may not exist, use get with a default value or get_optional returning boost::none. Iterate subtrees. Modify in memory and write back to any supported format. One data structure, four formats, zero schema boilerplate
Level up your C++ architecture. Follow @Boost_Libraries for the #BoostBlueprint series
#cpp
@jarredsumner@simonklee But how many of those were due to index-out-of-bounds that are still there? How many were papered over with unsafe? Rust provides these guarantees when the code was developed in it, not automatically ported over with minimal oversight by an agent.