53 karma · joined January 22, 2021
my list of complaints
- strong smell of chemicals when i first started using it - can be hard to remove things without burning myself e.g. english muffins - sometimes it burns things/sometimes it doesn't toast them enough. i have figured out which settings work for some common use cases, but it feels like a toaster should be able to figure it out w/out crazy complexity.
also, and this is just my opinion, but the absence of plane crashes does not mean it's safe! some faulty things exist for years before anything happens and/or the issue is noticed.
- downside of delaying 5g is slightly longer download speeds (?)
- downside of interference is planes might crash (!)
why not just give the FAA all the time it wants
seems like a case where there are two evils and one is way lesser!
Why does Germany care if there is an additional option for other countries?
- many (most?) programmers were taught C/C++ for several decades
- some programmers taught themselves rust because they were driven and interested
- these rust programmers are probably better programmers on average
- they wrote (or would write) better code that is somewhat elegant. and they have the advantage of starting with code that has had its memory bugs fixed over the last few decades
So I wonder if you had taught the masses rust starting in the 1980s... would the masses have found other way to write buggy/crappy code?
(I realize this could sound a bit condescending; fwif I did not teach myself rust so i'm not counting myself in the 'better' group)
(i agree penalizing individuals for not choosing expensive cars/stuff seems cruel)
- mouse select
- same keyboard shortcuts as vscode
other than that it's the same as nano
> I've stopped writing unit tests
i think this is generally bad and might only be more productive for uncommon workflows (if at all)
I agree it would be nice if you could get an assert in operator*. But you can already fire up a debugger or sanitize build and get a nice error message anyway, so it's nbd.
yeah, but the same graph never shows modules being faster... it only ever shows them being the same or slower. If I'm going to put in all that work, the result should be *faster*
so usually (but not always), sizeof(int ptr) == sizeof(func ptr)
> Waiting for Cross-Platform standardized SIMD vector datatypes
We sort of have this? compiler loop vectorization is, effectively, this. Granted it's not standardized.
> nonstandard extensions ... to run computations in parallel on many cores
std::thread?
> Debugging cross-platform code using couts, cerrs and printfs
True, but i think this is not the language's fault. C/C++ debugging tools are great (the best?).
Debugging any sort of meta-programming is a mess; would definitely agree w/ that. hopefully concepts will help.
> Forced to use boost for even quite elementary operations on std::strings.
This one i agree with.
and if you have kids, you might need to pay for childcare and maybe even their education