If the former, I would imagine that'd make searchability harder for larger volumes of logs.
893 karma · joined October 2, 2020
If the former, I would imagine that'd make searchability harder for larger volumes of logs.
I find that a bit exhausting; beyond simple use-cases, I've found it easier to just do it myself.
I assume running an app in a container wouldn't allow you to sidestep that problem?
If you're interested in this stuff, I think you might enjoy Manuel DeLanda - he gives Deleuze a sort of analytic treatment. His book "A New Philosophy of Society: Assemblage Theory and Social Complexity" takes a lot of ideas from A Thousand Plateaus, but makes them clearer and more accessible.
Another suggestion if interested in Deleuze, and more specifically A Thousand Plateaus: someone named Brent Adkins has a great companion for the work. Unless you have extensive experience with the thinkers & ideas referenced in ATP (e.g. Freud, Marx, Nietzsche), I found secondary sources very helpful for setting up context around certain terms and concepts.
How are exactly does continental philosophy factor into these other topics?
But I've noticed in spite of improving my dental habits, my gum health has remained pretty poor. I've wondered if it may have something to do with the acidity of my coffee (no sugar, since I drink it black), so as an experiment, I've tried switching to loose leaf black tea instead.
I've noticed I don't get nearly as jittery from a couple cups of black tea vs a cup of coffee. I also get sleepy as I should at normal times in the evening. Completely anecdotal, but at least to me it feels that the rise and fall of the caffeine boost I get is more gradual, without crashes or rougher withdrawals.
I do miss the flavor of coffee though; not crazy about the tannins in black tea. I may give matcha a try next.
When we can't admit this, either fear or a reflexive optimistism takes over our thinking as we try to guess at the future. And articles like this simply stoke these emotions further, benefitting the author with clicks while leaving people more anxious about their lack of knowledge about the future.
Assuming the growth rates are static, then sure. But in reality they're fluctuating too, and we can't know how they'll change in the future. Plenty of technologies have had fast early growth, only to peter out long-term.
Sure, I would agree that the current JS ecosystem has its issues, but work can happen at either compile/design time, or at run time. Shifting work from one step to another has trade-offs that may or may not matter for a given team or product.
For small hobby projects? The scale makes these problems pretty insignificant, so handling more at runtime ain't so bad. But the number of possible problems multiplies as your codebase increases in size, and by solving these problems sooner, you spend less time overall dealing with them.
I'll give credit to the post about the fragility of certain build tools long-term in the npm ecosystem, but I don't think that's a reason to shrug off build tools period. We just need better, more stable ones (and I think we're starting to finally get there).
Honestly I think this is where Blazor really shines: not in a web app, but as an alternative to the old XAML-based UIs - or even better, an alternative to Electron for desktop app development.
As much as I want Blazor to work out well, those load times are too abysmal for me to seriously consider Blazor outside of internal apps.
Why? Mainly because I'm familiar with them, and would be most productive with these.
I'd almost like to reach for Blazor, but if it's at all public-facing, I don't think I can justify using Blazor at this time.