dventimi

34 ms·

391.
by dventimi 3y ago
>>> There are countless things anyone can copy or do for free already right now, that countless people pay a company for, for no reason at all. >> Name one. > 3% tax on every transaction in your entire life going to V
392.
by dventimi 3y ago
> There are countless things anyone can copy or do for free already right now, that countless people pay a company for, for no reason at all. Name one.
393.
by dventimi 3y ago
> Harnessing knowledge of human nature does not require government support Yeah but fencing it off from others does require government support. If it's human nature to create, it's also human nature to copy. If you create som
394.
by dventimi 3y ago
> Corporations get everyone to do things they don't have to against their own interests all the time. Not without government intervention, they don't. In fact, they wouldn't even exist without government intervention.
395.
by dventimi 3y ago
Trade secrets are practically impossible to maintain without supporting legislation.
396.
by dventimi 3y ago
Well, they're the same at least insofar as they're government-granted monopolies.
397.
by dventimi 3y ago
Hang on. How would there even be big corporations to hurt small and medium-sized creators, without copyright?
398.
by dventimi 3y ago
Sure. Consider the obverse: "Humans ALWAYS have a [rational] reason for their actions." The word "always" is logically necessary and yet it sets an extremely high bar to be cleared. Is this the position you want to stake
399.
by dventimi 3y ago
> There was nothing to suggest [that SQL isn't meant to be used without joins]. Did you not bother to read anything before replying? This you? "If you were to use SQL as designed, with an idealized implementation, you would f
400.
by dventimi 3y ago
Any time. Thanks for the lively discussion.
401.
by dventimi 3y ago
> I actually like and use database security features. However, there are generally two problems with them: > 1. There is a limit to the customization 2. They are generally harder to test and change Those aren't problems that I ha
402.
by dventimi 3y ago
> What you have listed is not an actual solution, just a list of things you'd need to solve it Sorry. HN comments is a narrow channel and so I elected not to try to squeeze a full-blown actual solution through it. > I could say
403.
by dventimi 3y ago
> 3. I do think it is a big surface area. It can be reduced and, in this thread, I have never stated you cannot reduce it at all. No, but you did state, "I think exposing the entire database to users is a pretty big surface area to
404.
by dventimi 3y ago
As for the idea itself, I believe there IS a recipe for doing this right: - Role Based Access Permissions (RBAC) for course-grained control over database objects (tables, procedures, etc.) - Row Level Security (RLS) for fine-grained control
405.
by dventimi 3y ago
And yet not being a mind reader I won't know what your reason is until you tell me. You're not obliged to tell me what that reason is, of course, but so long as you don't say what that reason is, you fail to rule out the poss
406.
by dventimi 3y ago
I think that's funny because personally I DIDN'T find that answer to be comprehensive or balanced. By my lights, it seems to go out of its way to ignore the affordances modern databases offer to protect against abuse. I found the
407.
by dventimi 3y ago
I'm sorry you're frustrated. I admit that I am scoping my responses to your most recent response rather than trying to discuss the system as a whole. In my experience, that's common in threaded comment systems. Whatever it
408.
by dventimi 3y ago
I know. I think he was just taking the piss and I love it. And yet, there's more than a grain of truth in this quote and in other salty aphorisms from Dijkstra, especially: "The tools we use have a profound influence on our thinki
409.
by dventimi 3y ago
Compared to Dijkstra I'm quite certain that I'm a miserable programmer.
410.
by dventimi 3y ago
I believe he was being humorous. Either way, I don't take it too seriously. After all, I also started programming with Basic.
411.
by dventimi 3y ago
> I'm implementing a language that is more user friendly for users to work with than SQL "User-friendly" is a matter of judgement not of fact. > I am making a concrete statement here: that 200 lines of code is a lot sim
412.
by dventimi 3y ago
"It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration." --Edsger Dijkstra (1975)
413.
by dventimi 3y ago
I'm not evaluating what's being proposed here. In this thread anyway, I'm responding to this comment, which I regard as untrue: > They could write some pretty rough queries that could make guaranteeing QoS difficult or imp
414.
by dventimi 3y ago
Fair enough! Thank you for sharing!
415.
by dventimi 3y ago
So what? That role has read-only access probably to all the relations, and it has a statement_timeout of '2 min'. Evidently, that's acceptable to its maintainers and we're in no position to say that they're wrong.
416.
by dventimi 3y ago
Judging by some of the comments here it wouldn't surprise me if there are some people operating under the mistaken belief that "full privileges" is the only option. Establishing that "no privileges" (or "nothi
417.
by dventimi 3y ago
Unsurprisingly, the answers to that security question including the accepted answer, are full of mistakes. This is such a sad state of affairs.
418.
by dventimi 3y ago
Not if the tables in the schema that's changing are hidden behind an abstraction layer of views and procedures, they won't.
419.
by dventimi 3y ago
I think you are wrong. I think you are "confidently wrong" as evidently the saying goes, on many points. - GraphQL isn't meant to bundle many operations together. People mean things and the people who created GraphQL said wha
420.
by dventimi 3y ago
Why did you write this?

More ›