ris

43 ms·

391.
by ris 6y ago
So... Nix is just a package manager, but it's a package manager that tries to be as generic as possible and only have the attitude that a "package" is just "a bunch of (immutable) files that depend on the presence of ano
392.
by ris 6y ago
> A single implementation I consider this one my biggest concerns about adding a Rust dependency to a core package. Especially when in https://forge.rust-lang.org/release/platform-support.html "Tier 1" i
393.
by ris 6y ago
> With x, packaging in Python is a solved problem This is the claim that has been made about every "advancement" in python packaging for the last 20 years. Some of us have been kicking around long enough to remember the great s
394.
by ris 6y ago
> At the end of the day the migrations framework is just a SQL dependency graph. It's not quite . During operation it actually mutates an in-memory shadow of your model structure. And that's really clever, but if you've g
395.
by ris 6y ago
I can't say I can recommend following almost any of this as "general" advice. It is, at best, advice from a complete expert for complete experts who are already pushing the edge of what django should be used for, and who ne
396.
by ris 6y ago
What I don't understand about Briar is how it can scale . Surely it can't know ahead of time which users are going to "travel to another part of town" and should therefore have messages pre-loaded onto their devices.
397.
by ris 6y ago
The mere possibility of this underlines the relevance of RISC-V.
398.
by ris 6y ago
Comprehensive? No PureData.
399.
by ris 6y ago
> but I'll withdraw it if the response is a resounding "boo, hiss" Boo, hiss. The parentheses-less function call is the second biggest obstacle to ruby readability.
400.
by ris 6y ago
> One of the reasons I don't like ORMs is that I'm not able to see the underlining query and truly optimize a service. The vast majority of your queries will not fall into the category of "bottlenecks that need to be opt
401.
by ris 6y ago
> I've actually liked Analog Device's documentation as a hobbyist Even reading their datasheets, I often felt like I was being taught a full lesson on the topic, which is great when you're an amateur and lack some of the f
402.
by ris 6y ago
Heavy reading of LWN.net articles.
403.
by ris 6y ago
Interesting project, but its name sells it incredibly short.
404.
by ris 6y ago
So many times this. "Clear code shouldn't need comments" - clear code can make it easy to see what but it can never say why . Let me know what corner cases you thought about when you wrote this. "The comments are in t
405.
by ris 6y ago
Therefore SQLAlchemy.
406.
by ris 6y ago
"I know this! It's UNIX!"
407.
by ris 6y ago
I think the answer to the "how to support enough of the ecosystem to be useful" question really lies in making it super straightforward for package authors to integrate it into their packaging/testing/ci pipelines. If pe
408.
by ris 6y ago
> Not to mention a better packaging and deployment story. Go's "packaging and deployment" is enough to rule it out for new projects for me.
409.
by ris 6y ago
I spend so much of my time doing an invisible facepalm over dogma that developers believe, but can't ever justify why . It's always stuff that sounds sensible, but the lack of nuance makes them so destructive in practise. Wheth
410.
by ris 6y ago
This. I think the author is making the mistake of comparing it with what I would call "new world" OSs. Very broadly I would categorize most OSs of the 90s into old-world and new-world, common traits of the old-world being: - M
411.
by ris 6y ago
Al-right! I'm taking this thing to Mexico!
412.
by ris 6y ago
If you hadn't sold yourself out of the free market, you would be able to choose what architecture machine you bought.
413.
by ris 6y ago
So, "work in progress".
414.
by ris 6y ago
gofmt's idiotic handling of maps and forcing them to align entries was enough to put me off the entire idea of autoformatters. Enforcing a code style where adding a single byte can result in an unlimited-number-of-lines block in a diff
415.
by ris 6y ago
Not to hand, but it's not amazingly hard to reproduce. You just have to build quite a complex query (many joins in our case) and play around with the clauses, watching the EXPLAIN output.
416.
by ris 6y ago
> a fragile mess Oh, I'm not saying it wasn't a fragile mess... Seriously I actually considered the fragility of it to be a positive, precisely because it wasn't a hard "optimizer decision" that I was forcing. If
417.
by ris 6y ago
Something you'll discover when you do enough query optimization is that postgres' query planner isn't clause-order invariant. i.e. a AND b won't necessarily give you the same query plan as b AND a. My first reaction wa
418.
by ris 6y ago
Absolutely, there are many things that can be done to mitigate this kind of thing, I'm merely advising caution over people immediately reaching for a solution where they're executing thousands upon thousands of lines of code over
419.
by ris 6y ago
Amongst all the praise we're seeing for this approach here, may we please just have a minute's silence for the various exploits sqlite has seen when loading arbitrary database files over the years? My recent favourite being https
420.
by ris 6y ago
I'm sure you can. And if my aunt had balls, she'd be my uncle.

More ›