1,596 karma · joined April 4, 2017
[ my public key: https://keybase.io/jrimbault; my proof: https://keybase.io/jrimbault/sigs/YStRMnahTqv-NqG4y2N0krmu7X--H4cModprRVH05J8 ]
* of course to a degree, let's be reasonable, it's usable in a _lot_ of contexts, but I like my types to actually mean something.
The "actual" code of ripgrep is accross its multiple support crates, which the community largely benefits from having since those are general enough to be almost foundational to any software.
imo, op is trolling, the old fashioned way
I'm sorry to get the big name out, but. It's really part of the Marxist framework that there's mostly no willful conspiracy against the worker class, the balance of power is a result of a complex but understandable system, with some corrupt actors but they don't need to be, they just have conflicting incentives.
That sentence is everything I was taught to avoid. Props to you.
I like the drug/alcohol metaphor for these things, as a child avoid them, as an adult do your thing as long as you remain sensible.
I don't know about olive species, but I know that not all cats have that weakness.
I've seen many cats lounging under (or on top of) olive trees in the Alps around Nice (France).
> In a go a string is an immutable byte slice assumed to be valid utf8, with associated methods and users which all assume that slice of memory is valid utf8.
Which is in my opinion the worst choice you could make when designing a type. If I'm working in a typed language because of so-called "type safety", if I can't trust my types to actually enforce their guarantees, what can I trust ?
I estimate I'd need about 30k€/y to be able to not skip on anything I'd want to do. (usual disclaimers apply: young-ish single man living alone, never had health issues, with no desire to live in any other way, etc)
I'd really appreciate some perspective on this from someone who knows ?
My favorite error is also rust related :
> Rust has no built-in support for immutable data structures.
This piece is flamebait.
> The authors decry the loss of goto saying it's "good for juniors but too limiting for professionals" - as if professionals aren't humans too! I'm sorry to say that, but whenever I saw that attitude before - it was with programmers that greatly overestimated their skill level.
The "I know how to use goto [replace with any feature] everyone else is just stupid" reasoning upsets me so much.
For other sites yes, often just cache/cookie invalidation is enough.
- 2019: https://insights.stackoverflow.com/survey/2019#development-e...
- 2018: https://insights.stackoverflow.com/survey/2018#development-e...
- 2017: https://insights.stackoverflow.com/survey/2017#technology-_-...
- 2016: https://insights.stackoverflow.com/survey/2016#technology-de...
- 2015: https://insights.stackoverflow.com/survey/2015#tech-editor
What's really amazing is vscode just appearing out of nowhere (7% in 2016, 35% in 2018). Blindsiding everyone. Cross platform, excellent to good enough UI/UX (very much inspired by Sublime Text but free), easily extensible in a widely available (and widely taught) language. For better or for worse.
mkdir demodir && touch demodir/{foo,bar} && rm -r demodir