gfody

13 ms·

181.
by gfody 4y ago
this summarizes a lot of thoughts I've had about my music collection. I'd love to have a relational schema for it but you can keep normalizing forever, especially once you try to normalize away "genre"
182.
by gfody 4y ago
including unknowable cost/opportunity risk
183.
by gfody 4y ago
I feel like if Bard were any good they'd've used him (er the technology) to make a decent inbox policy for gmail. Or maybe that sort of work is beneath him, or would be inhumane? Or just too inefficient to be cost effective I supp
184.
by gfody 4y ago
come to think about it, I left out the part where I spent an hour customizing my settings. none of the bundled profiles looked very good on my screen.
185.
by gfody 4y ago
if you were to do something crazy like say use a 48" oled tv as a monitor, then MacType is perfectly necessary because cleartype looks terrible on rgbw subpixel and the only alternatives (switch cleartype to grayscale or disabled aa) l
186.
by gfody 4y ago
tfa is too dismissive of chatgpt which does meaningfully progress a very fundamental technology (information retrieval) by acting as a general purpose freeform index with an conveniently easy-to-learn conversational query language. chatgpt
187.
by gfody 4y ago
it is possible to reduce your query w/case statements to essentially "all cost of all employees" if you would model every type of employee and cost relationally (and then some view for all-employees which is the union of each
188.
by gfody 4y ago
I think what you're saying is accurate for describing what style of programming you might be doing, afterall we can write C++ in a declarative style. if you're coding in SQL then you're doing functional programming, but that
189.
by gfody 4y ago
SQL is declarative in the sense that you dont specify the strategy to employ in retrieving the data (ie which index to access and how, whether to sort and merge or build a hash table etc etc) however you DO need to specify how to represent
190.
by gfody 4y ago
I'm not the person you were replying to but you've misunderstood their comment - they were saying that CSV is to SQL what JSON is to GraphQL (and HTML to React) these being declarative languages for records, objects, and markup A
191.
by gfody 4y ago
this should be a cautionary tale for being careful how you model facts vs inferences, if you cant tell them apart your data is ruined
192.
by gfody 4y ago
does this include a miniport driver for regular gdi acceleration? I recently switched from a low end radeon to an arc770 and older software like beyondcompare and vs2015 became noticeably choppy
193.
by gfody 4y ago
is there an easy way to unvoicemod the streams?
194.
by gfody 4y ago
there's something like Knoll's Law for HN where everything seems like intelligent opinions until the topic is in your area of expertise and then...
195.
by gfody 4y ago
this works better if you split your whole schema into a physical and logical layer, which is a lot of boilerplate but seems like a pagni as well since physical concerns that shouldn't change logical semantics always eventually creep in
196.
by gfody 4y ago
https://www.shadertoy.com/view/XlfBRH https://www.shadertoy.com/view/MtlGD8
197.
by gfody 4y ago
> So, in some channel at some time you may be able to see Brad Pitt fighting against Godzilla while the monster is hacking into the pentagon using ssh. that's the movie GAN, more interesting would be the zero-shot translations of ep
198.
by gfody 4y ago
> The relational model has strong implications for what a storage engine should do well. agreed, the implication is that the engine should do everything well. rdbms is a product of being pulled in every direction, there's generall
199.
by gfody 4y ago
sql doesn't specify how data is stored, it's only a description of the data you want. how your data is connected or not at rest is up to the engine and how you leverage its engine-specific features.
200.
by gfody 4y ago
beg pardon I wasn't aware sql actually defined empty. of the engines I'm familiar with there is no keyword for empty like what gp is asking for (and I hold my argument for why it should not be necessary). it sounds like what you&#
201.
by gfody 4y ago
you should not need to distinguish between empty and null because they mean the same thing. if you want to select records from x that aren't in y you should use an anti-join (where not exists, not in, etc.)
202.
by gfody 4y ago
> What am I missing? only that hn is full, FULL of trolls who give the absolute worst advice possible. it's a sport maybe or it's entirely innocent and related to the Dunning Kruger effect but nothing brings it out more than da
203.
by gfody 4y ago
> Do you think that such a simple solution hasn't been explored by a team of 50 DBAs? Or that this sort of obvious problem wouldn't have been immediately fixed? based on what you've shared, yeah. I also wouldn't expec
204.
by gfody 4y ago
assuming some beastly server with terabytes of ram, hundreds of fast cores, and an exotic io subsystem capable of ridiculous amounts of low latency iops, I'd guess the perf issue with that example is not sql server struggling with load
205.
by gfody 4y ago
fwiw hacking hundreds of apps literally making them worse by fragmenting their source of record doesn't sound like a good plan. it's no surprise you have saboteurs, your company probably wants to survive and your plan is to shatte
206.
by gfody 4y ago
for about the same budget you could buy a 4-bay 2.5" nvme nas enclosure and a single 30tb ssd, and have 3 bays to expand if/when you need to
207.
by gfody 4y ago
about 4 years ago I had to choose a compression format for streaming database backups, and so I compared every option supported by 7z and it was xz that was the best compromise between performance and compression ratio
208.
by gfody 4y ago
I'm not sure if rust does this but C#'s embedded docs are integrated throughout the toolchain so they appear alongside intellisense as your writing or navigating etc. Keeping them with the code makes sense to me because they have
209.
by gfody 4y ago
> If I’d written out the query, I might have seen that I didn’t need the JOIN (or never written it in the first place). Whereas the view hides that complexity. So they can make things easier, but that can lead to performance pitfalls if
210.
by gfody 4y ago
I bet it's 95% fake credo quia absurdum

More ›