taftster

24 ms·

271.
by taftster 4y ago
I think that's fair. Yes, there is an escape hatch currently available. But what is hard is knowing if your application is relying on any internal/private behavior that it shouldn't. Since the dependency hierarchy of most J
272.
by taftster 4y ago
Almost. The Java module system (introduced in Java 9 and enforced in Java 11) still plagues companies and/or slow-to-update libraries. Particularly companies that have written a lot of their own in-house libraries and such. Custom libr
273.
by taftster 4y ago
Totally fair. I guess I would hope in that case that the new effort would target a modern Java release, preferably Java 17 or greater. If a company is sticking with Java 8 for new initiatives, yeah, they probably have a culture problem and
274.
by taftster 4y ago
Kind of. It gets you close. With the Builder pattern, you can easily define complex relationships for your class inner state. Like maybe if A & B are specified, then C shouldn't be specified. But if C is specified, then D should ha
275.
by taftster 4y ago
I just wish records had an easy way to facilitate and/or associate a builder with them. Wishful thinking, out of scope for what they are. And of course, it's not hard to write a FooBuilder that's defined to help construct a F
276.
by taftster 4y ago
All the while, adding its own mistakes to the pile. As an example, idiomatic Java style is moving away from getters/setters and instead favors builders and immutable types. That whole inheritance vs. composition concept is changing the
277.
by taftster 4y ago
I mean, that's OK though. Not sure why this is considered such a bad thing. You're missing out on some new language features, sure, but Java 8 is still reliable and rock solid. There's lots of companies that have hesitation o
278.
by taftster 4y ago
Shouldn't that just be ALL PROVIDERS in general? There's probably a few choice ISPs that maintain their dignity, but I wouldn't put it past Comcast, Verizon, and all the mobile providers out there.
279.
by taftster 4y ago
I really doubt that Mr. Thiel's role was intentional. He was probably just being a good steward of his portfolio's accounts and his spidy sense was going off. I don't think it was like, "Hey, I know what, I've seen
280.
by taftster 4y ago
This is insightful and totally true. It's going to take a long long time to ween off cows as a choice for meat. Impossibly long (if ever). Sad state of affairs. I do like my steak and hamburger though, and I recognize that I'm par
281.
by taftster 4y ago
That's interesting, didn't understand that, thank you. Complete anecdote, I have a relative in California whose well has ran dry. They are trying to find the money and motivation to dig a new well, but it's a dilemma, like if
282.
by taftster 4y ago
Almonds 100% agreed, what a waste. Cows as a by-product of alfalfa, also gets an amen. But really it's not the cows, per se, that's the problem. We should be feeding them other product that takes less water to grow. Alfalfa is a t
283.
by taftster 4y ago
This is absolutely one of the easiest things California can do to help mitigate (even so slightly) the complete disaster that is the Colorado River Compact. I 100% support California using all the water they can coming from their own mounta
284.
by taftster 4y ago
Thank you for taking time to reply. It's awesome to see the insider's view a bit here.
285.
by taftster 4y ago
And honestly, in my opinion, that approach is just really proving itself right now. I am so happy to see Java seemingly on the right path again, adopting solid capabilities, innovating, but letting other languages take some punches first. W
286.
by taftster 4y ago
Yes, but honest question, do you really think that if IBM had purchased SCO (and maybe throw Novell in there too) that Linux would have still had any chance? I don't know what the outcome, but I just think there's too many possibi
287.
by taftster 4y ago
And what's interesting, if the SCO lawsuit had gone any other way, Windows NT would probably have ended up completely dominating. Linux wouldn't be here and probably neither would SCO Linux either. What a dire state that would b
288.
by taftster 4y ago
This is a hilarious quote, in the article, attributed to Linus, related to the concept of source code pedigree and the developer certification of origin for any contribution. > For example, in the case of "ctype.h", what made
289.
by taftster 4y ago
Right. But the irony is, normally compared to how bungled Microsoft acquisitions are, it seems Github is allowed to continue mostly independent without a lot of oversight? At this point, though still skeptical, it seems to me that Github i
290.
by taftster 4y ago
You should write a book, or at least blog, about the experience. This would be good reading and much appreciated to some of us. I'd definitely read.
291.
by taftster 4y ago
This is the kind of stuff that makes the internet fun. I really like the types of projects that exist simply to exist. People putting out things that have no reason except for the enjoyment. It seems like we're missing this kind of stu
292.
by taftster 4y ago
Agreed on your points. I particularly like, "If it can serve data, it will serve data." Totally get that point of view. I fully wish that Intel would have gone with the "opt in" approach. Either opt-in with choices in ar
293.
by taftster 4y ago
This is a good link, appropriate for the conversation, thank you for providing it! Just to rant about this article though, I really dislike this statement by the author: > Why on this green Earth is there a web server in a hidden part o
294.
by taftster 4y ago
This might be a spoiler. There are some brilliant levels of sarcasm going on in this article. Sarcasm inside of sarcasm. An infinite recursion of sarcasm, an out-and-out brainfsck. All the while, with the question still lingering in your he
295.
by taftster 4y ago
Hyperbole runs rampant like the roadrunner on winding roads of the internet these days.
296.
by taftster 4y ago
That's a bit like saying we should defund the police. It's thought provoking and grabs headlines. It even has some merit, but it's ultimately not the solution. Reform the FDA, sure I can support that. The FDA, from my perspec
297.
by taftster 4y ago
The older I get, the more it is that "4 years" ago feels like 4 days ago. You calling out my perspective of "recently" is totally fair, because to me, it feels like recently, whereas truthfully maybe not so. Thanks for t
298.
by taftster 4y ago
I mean, that's totally fair response. I should have provided a caveat, "historically speaking", that Docker has lacked support for rootless containers. But yes, solutions have emerged recently. Podman out the gate has had the
299.
by taftster 4y ago
The biggest problem with Docker is that its containers are effectively running as root. This is basically OK when the containers you want to run are more like traditional daemons. But if you allow normal users to run containers, in a shared
300.
by taftster 4y ago
I'm surprised that the article doesn't mention the royal pain that is of the user id mappings required for execution of limited privilege containers. This is by far the biggest con and pain in the butt with using Podman.* Though I

More ›