4 ms·
It's not just you. Screaming heebie-jeebies is exactly the correct response. People who don't worry about it tell themselves that nothing that matters very muc
by ncmncm 7y ago
It's not just you. Screaming heebie-jeebies is exactly the correct response.
People who don't worry about it tell themselves that nothing that matters very much is coded in javascript, obvious exceptions notwithstanding.
Maybe the only practical way left to avoid it is to avoid javascript for things that matter, and to avoid products constructed with javascript for uses that matter. This might be an unpopular observation, but that does not make it wrong.
It is possible that WASM can fix much of this, at the cost of exposing ourselves to what might be extreme risks inherent in WASM itself. And of course, to whatever dependencies are brought in for the language we compile to WASM.
- galangalalgol 7y agoIndeed, rust is a likely wasm choice and it is working on an npm nightmare of its own with crates.io. A blessed crates pack is sorely needed to fill out the intentionally thin stdlib in cases you can't afford a dependency tree 20 layers deep for all the reasons mentione on this thread.
- steveklabnik 7y agoSeveral people have tried the "blessed crates pack" over the years, but they never gained traction, so people stopped working on them.
- vmchale 7y agoIt's unfortunate that Rust is so tied to cargo, and unfortunate that cargo insists on allowing multiple versions of a dependency. If you point out that cargo is poorly designed everyone just yells and you and says you don't understand.
- damnyou 7y agoOnly incompatible versions though — Rust dedups dependencies up to semver compatibility. I think that's the right balance. clap 3 is and should be treated as a totally different package from clap 2.
- vmchale 7y agoIt's not as bad as cabal back in the day. Nonetheless I have run into the diamond dependency problem in practice. Their solution is unprincipled and there's no way to turn off the default behavior.
- damnyou 7y agoDo you mean passing a struct from e.g. clap 2 into clap 3? Yeah that won't work directly, nor should it in my opinion. If it is frequently required, projects can and should provide a compatibility layer which does any necessary conversions.
- vmchale 7y ago> Do you mean passing a struct from e.g. clap 2 into clap 3? Yeah that won't work directly, nor should it in my opinion. I agree! But it shouldn't fail at compile time with a vexing error message. It should fail to resolve dependencies when calculating a build plan.
- damnyou 7y agoThat would seem to completely disallow any compatibility layers, which seems like a bad outcome. Unless you had some sort of solution in mind for that? I agree that the error message sucks, for what it's worth.
- nieksand 7y agoCan you elaborate on the design flaws that you perceive in Cargo?
- umanwizard 7y agoThe biggest flaw is that it makes taking new dependencies easy. I would prefer that it be hard, like in C++, so people think before doing it. The second biggest flaw is that it couples package management to a programming language, despite those being almost completely unrelated concerns.
- vmchale 7y ago> The second biggest flaw is that it couples package management to a programming language, despite those being almost completely unrelated concerns. Yes it's frustrating. I wish it was more decoupled, maybe with package standards like Haskell tried to do with Cabal. It makes it hard to use Rust as a drop-in replacement for C. I can add a few C files to a Haskell project without much problem, but most rust code goes via cargo.
- marcus_holmes 7y agoYeah, my back-end is in Go, so being able to write the front end in Go as a simple cross-compile is great, if it was that simple. We're a long way from it being that simple. There are "hello world" examples, but nothing close to a working GUI in Go-WASM yet. I'd love a clone of Vue in Go-WASM. Just saying, if anyone out there wants to give it a try ;)
- marcus_holmes 7y agohmm, I always assumed it's a single "heeby-jeeby" and therefore multiple "heeby-jeebies", because that's how English mostly does singular/plural. But the repetition in "heebie-jeebies" looks more appealing. Even if grammatically unlikely. I'm confused now. Is "heebie-jeebies" intrinsically plural (like "sheep"), and therefore the pluralisation doesn't matter? Is there even such a thing as a single "heeby-jeeby"?
- ncmncm 7y agoI can confidently state that I have never sighted a lone heeby-jeeby in the wild. Heebie-jeebies are best thought of as an affliction, like hives or bedbugs, characterized by shuddering and head-ducking. My guess is it started as a euphemism for hebephrenia, an obsolete affliction associated with youthful anxiety.
- RhysU 7y agoSeconded. Heebie-jeebies are uncountable.
- marcus_holmes 7y agoI'll go with the consensus opinion, then. "Heebie-jeebies" it is :)
- ncmncm 7y agoThe dictionaries credit a comic strip "Barney Google" with coining the expression. No saying whether that is really where the New Evil Empire got its name.