__jem

6 ms·

1.
by __jem 3y ago
Right, because endless US involvement in ground wars in the middle east has always been firmly on the side of "concrete facts."
2.
by __jem 3y ago
Isn't the point of a dev environment precisely that the intern can drop tables? Idk, I've never had a shared database not turn to mush over a long enough period, and think investing the effort to build data scripts to rebuild dev
3.
by __jem 3y ago
That's why OsString exists.
4.
by __jem 3y ago
You know, minus sexually abusing his sister.
5.
by __jem 3y ago
> the return type of MyWidgetFactory() probably isn't. Isn't the return type of a widget factory method obviously Widget? This doesn't seem like a great example. Of course the method name could be wrong and not enforced
6.
by __jem 3y ago
I've worked with some databases that are 20+ years old and have outlived multiple application iterations. There's always going to be cruft in this kind of situation, it just comes with territory of supporting applications with rea
7.
by __jem 3y ago
Reclaiming the physical storage of an unused column is often a costly and sometimes impossible operation, which is why many legacy applications end up with the equivalent of my_column_final_final_v2. Database administration requires comprom
8.
by __jem 3y ago
What is the fact that many foundational ecosystem crate contain unsafe code supposed to prove? That's the entire point of the language. That someone writes a really good regex crate once and then the rest of us don't have to write
9.
by __jem 3y ago
yes, it's harmless in this position but it provides no additional benefits to the select 1 idiom and is suggestive of poor query discipline. it's far easier to say just don't ever use select * in queries.
10.
by __jem 3y ago
you're getting downvoted because it's not really a preference, it's pretty widely known to be bad practice and unhygienic in production queries. select * would get your pr rejected and chewed out by dba at every place i'
11.
by __jem 3y ago
I'm not sure this is really an issue with transactionality as a single request can obviously be split up into multiple transactions, but rather that even if you correctly flag the email as pending/errored, you either need to proce
12.
by __jem 3y ago
Rust is memory managed, it just doesn't have a garbage collector.
13.
by __jem 3y ago
Friction with modern devops practices is a big one.
14.
by __jem 3y ago
Passing around functions that have already been partially applied means that downstream users can't incorrectly call or accidentally modify the arguments which have already been applied. Whether this actually results in more safety is
15.
by __jem 3y ago
I'm not sure if he's made an official statement about his versioning policy, but if you look at https://crates.io/users/dtolnay?sort=downloads , you can see that most of his crates follow the incremental patch
16.
by __jem 3y ago
Correct, serde does not follow semver.
17.
by __jem 3y ago
Well, there is an exit path for those who want to compile from source. If you mean build from source for Cargo users, I believe there's issues with how feature flags interact with transitive dependencies that make this difficult. At le
18.
by __jem 3y ago
> I found the discussion to be mostly very civilized and focused on finding solutions for those affected. I really disagree with this characterization of the discussion. While there's plenty of more or less dispassionate comments fo
19.
by __jem 3y ago
People have complained about the build time of proc macros for ages in the community. This might be a misguided hack, but the response to this is bordering on a witch hunt, particularly when there is a glaring security hole (build.rs) that
20.
by __jem 3y ago
Only some of the providers are based on Terraform. I think it would be incorrect to say it's "powered by Terraform."
21.
by __jem 3y ago
> However, tailscale focuses on access different devices to each other, while Narrowlink focuses on access to the services trough on the agent as a proxy. You can easily do the same thing with Tailscale: https://tailscale.com&
22.
by __jem 3y ago
Could not disagree more strongly that Datomic is well maintained. I'd view it as a significant liability in any organization using it without very good reason. My experience operationally supporting Datomic at even a moderate scale w
23.
by __jem 3y ago
Well, in the real world, the premise is false, but not because writing memory safe code is in fact easy, but because in aggregate in large code bases it's impossible.
24.
by __jem 3y ago
Okay, but using unsafe for FFI is entirely different than the claim that you can only achieve performance optimizations through "dereferencing pointers without anything extra running." The use of unsafe for FFI is unavoidable for
25.
by __jem 3y ago
> SQL (ACID) over multiple non-cache-coherent nodes is extremely difficult to pull with regards to consistency, though. Thats... why it's a toy! I'm really not sure what you're missing here.
26.
by __jem 3y ago
Right, just because something is a "toy" doesn't mean it's not still impressive. If someone implemented a "toy" database that could parse and execute SQL queries, distribute data across nodes, etc., you would p
27.
by __jem 3y ago
Or, worse, you're reviewing a large diff, see the logger statement but don't notice that the junior whose code you're reviewing forgot to rethrow. Now you've accidentally entered uncharted territory where way more scarie
28.
by __jem 3y ago
On the other hand, in lots of application code, there's often not much to do other than crash or abort the request, and this can often be safer than trying to proceed along code paths that are almost always under-tested. We've all
29.
by __jem 3y ago
https://en.cppreference.com/w/cpp/language/coroutines But highly doubt you need anything like async/await for this kind of application. In fact, I'd go as far as to say async/await is almost ne
30.
by __jem 3y ago
This is so helpful, thanks.

More ›