smaudet

26 ms·

301.
by smaudet 2y ago
> By Allowing the frontend to select what combination of these pre-approved queries that you already approved it can use Sure, so you are just filtering raw database access then. That doesn't make it any different - and, you still n
302.
by smaudet 2y ago
> With GraphQL the only time you need to update the backend is when those "utility" functions change (i.e. 3rd party api calls, etc) or the data model changes. This is akin to saying that "directly exposing the database is
303.
by smaudet 2y ago
Yup. And the solution to that org problem is for the front engineers to slow down, and help out the "backend" engineers. The complexity issues faced by the back-end are only getting worse with time, the proper solution is not addi
304.
by smaudet 2y ago
> What if your engineers change $client/$server and the new version makes really expensive queries? Yes, so the cost benefit here is not in favor of GraphQL. If both technologies ultimately suffer from the same issues (what to do ab
305.
by smaudet 2y ago
I think the answer is buried somewhere in the mists of...time. Put another way, there is a temporal degree of respect for the dead, i.e. can you and for how long put the wishes of the dead above those of the living. Of course, for immediate
306.
by smaudet 2y ago
> an adversary can see that your users from one region are interested in the weather and can start building a map of that traffic I think this is the most convincing argument, but, I think that some data doesn't care if it is not co
307.
by smaudet 2y ago
> Even for non-enterprise use cases I don't think non-enterprise, non machine use cases should be automatically handles, though. Attempting client upgrade is better than not, but we should be more clear about whether our devices are
308.
by smaudet 2y ago
Hmm. I think, perhaps, release versions should need this, without a flag. For testing/prototyping, it is invaluable to turn off all the security to rule out security misconfiguration instead of application error. If your API is non-sen
309.
by smaudet 2y ago
Maintainers often change (leave/die/hired out/new job). What one maintainer knew and understood, is often fairy dust/spaghetti to another.
310.
by smaudet 2y ago
> Websites are not physical neighborhoods. True but incidental, possibly anathema, to the point... Which is that physical neighborhoods make up the user-base of the web, whether they be large server farms or small form-factor computing
311.
by smaudet 2y ago
3. Hmm. I think the biggest issue then might be the inability to extend the protocol then, not the lack if TLS. Http(s) had at least some back and forth that allowed clients/servers to do protocol negotiation, not perfect, but workable
312.
by smaudet 2y ago
> do you have more faith in a company that's scraping by versus working to be profitable Working to be profitable is not correlated with well-functioning. Its usually correlated with enshittification ( https://en.wikipedia
313.
by smaudet 2y ago
> we can all aspire to work in a company where people wouldn't be outright lying, nor feel that they needed to. I think you should consider this might be antithetical to the very concept of a company - although don't misunderst
314.
by smaudet 2y ago
Yeah they kinda screwed the pooch on that. That being said, venv is the official solution, and it works fairly well. pipenv/pipx are some alternatives...but yeah. What exactly is your system installation for if you aren't supposed
315.
by smaudet 2y ago
It has been amusing watching them try to get cross platform going, I used to hear how they (c#/.net) did such a good job with backwards compatibility, however Java had been doing crazier platforms for longer and their cross platform&#x
316.
by smaudet 2y ago
I also find binaries (at least on Windows, unsure of nix) are much easier to hook into than what I remember from Java (perhaps it has changed)... About as easy as Python, at least. Which, for MS, made a lot of sense, they wanted to hook win
317.
by smaudet 3y ago
> Meanwhile, a lot of RDBMSs do store data where every fact in every field of every row is critical. Excellent point, however how many applications are truly critical? I didn´t say DMBS (R or otherwise) are useless - I would probably rea
318.
by smaudet 3y ago
I too think ORM was the wrong approach. I still enjoy SQLite - its not perfect, but every time I see it being used I get the warm and fuzzies. We should have just built better libraries around using/targeting one flavor (SQLite, e.g.),
319.
by smaudet 3y ago
> 1. There is still a lot of criticism about SQL. And rightly so, while you can write whole programs inside it, the debugger/tooling/syntax for most if not all implementations is some mix of inferior/more arcane/legit
320.
by smaudet 3y ago
I think using C as your language with which to judge language constructs is hardly fair - one of its main strengths has been as a fairly stable, unchanging code-to-compiler contract, i.e. little to none syntax change or improvements. So no
321.
by smaudet 3y ago
Per my sibling comment, I think the argument is not about speed, but simplicity. Awkward switch syntax aside, the switch is simpler to reason about. Fundamentally we should strive to keep our code simple to understand and verify, not worry
322.
by smaudet 3y ago
The issue with if statements (for compiled languages) is not one of "speed" but of correctness. If statements are unbounded, unconstrained logic constructs, whereas switch statements are type-checkable. The concern about missing b
323.
by smaudet 3y ago
> No, one doesn't need to be of good breed to be freely able to speak multisyllabic words. Eh? Not what I'm saying at all. Breed has nothing to do with it... circumstance has much more to do with word shortenings... not sure wh
324.
by smaudet 3y ago
I posit that its due to hardship - not to suggest all Australians are super hard off, but it is certainly true that acronyms/shortened words are more common in rural (think high intensity physical labor) or speed-sensitive contexts (th
325.
by smaudet 3y ago
Someone who experienced the changing and flippant tides of fortune... You learned your numbers at least mostly meant nothing, and seemingly learnt the valuable lesson of hardwork and luck (and a brain cell or two to rub together). Maybe, so
326.
by smaudet 3y ago
> I'm also sure I could find examples and get benchmarks. Right back at you. I've provided examples. Your "examples" are to say that yes, it sucks, no JS isn't better, but you won't provide any examples to s
327.
by smaudet 3y ago
> Facebook or Twitter posts? Loaded via AJAX and rendered by an engine they've written in JavaScript. Article on any major news site? Ditto. Webmail? Ditto. Blog? Editor pages definitely, unless it's an old WordPress that hasn&
328.
by smaudet 3y ago
> it would be better to accept that and implement the things that are needed to make the browser a non-awful application runtime It absolutely would not. Everything doesn't need to (and should not) be an app. Most interactions onlin
329.
by smaudet 3y ago
> profit doesn’t come from thin air (or does it?) It doesn't. Its supposed to come from your operating costs (cost of living + insurance costs). That is supposed to be where the prices come from, the problem is the insurance...if th
330.
by smaudet 3y ago
> But for some reason web folks and especially HN seem to hate the few parts of the web technology stack that actually work well (Javascript, NPM) Actually, the parts that are "awful" and "unfixable" work great. You s

More ›