HN user
I like this argument/reasoning more than any I've encountered so far. Thank you! Enabling the disabled is definitely a positive and this is a strong argument for the "pro AI" column.
Is the hard evidence of AI being a net improvement for society in the room with us now?
Back in the late 90s the Michigan Tech CS labs had 2 preferred machines for students to remote into, Colossus and Guardian.
I always enjoyed the reference as well as this movie’s a kid!
And your life might be very privileged to so flippantly disregard anyone’s reality that is just that difficult.
I can appreciate that Discord is dealing with a lot of sides on this issue, and this response seems well measured with meaningful changes to the roll-out. As someone who has been fretting about replacing Discord communities with an alternative, this makes me feel better over all.
I think Java has plenty of features that end up implicitly banned at least. e.g. you will really never see a `java.util.Vector` in any modern code base. No one `implements Serializable` anymore in practice. `Objects.equals()` and `Objects.hashCode()` get you through 99% of equals/hash code implementations. The list goes on.
I guess the difference is it's rarely "dangerous" or "hard to reason about" using the old features unlike what I see in the C++ list. Java replaces things with better things and momentum shifts behind them kind of naturally because the better things are objectively better.
I always advocate that TODO comments include a link to a ticket tracking the TODO during code review.
It’s easy to get a team to make this 2nd nature and gets immediate debt in the backlog. It can of course still be ignored and unfinished for a long time still but no amount of automated nagging will change that in my experience
Java 8 -> anything 11+ wasn't great at scale. It's been smooth sailing for a long time again though.
Who is characterizing the other evidence as "equally specious" besides you in this new strawman argument?
Is your position that there are zero reliable indicators that fascism is on the rise in the United States
Looking at this in a vacuum, sure maybe it's time to touch grass.
Looking at this in the context of everything else going on in the country, maybe there are a lot of warning signs that are pretty hard to ignore?
Notably, a lockfile does not solve this problem either.
I think you misread my response. I think assuming Amazon did this to hurt “s3 compatible” services is cynical. Amazon implemented a feature, well within their rights. Writing a blog post saying they “broke backwards compatibility” is cynical and disingenuous. Amazon never committed to supporting any random use of their SDK.
Less charitable or More cynical? How is Amazon supposed to track a 3rd party pulling their SDK and then reverse-engineering their own service side to work with the SDK? Assuming we're all okay with that premise to begin with, all sorts of other questions start popping up.
Do these 3rd parties get veto power over a feature they can't support?
Can they delay a launch if they need more time to make their reverse-engineered effort compatible again?
It seems a hard to defend position that this is at all Amazon's problem. The OP even links to the blog post announcing this change months ago. If users pay you for your service to remain S3-compatible that seems like its on you to make sure you live up to that promise, not Amazon.
Clicking through to the actual git issues, it definitely seems like the maintainers of Iceberg have the right mental model here too. This is their problem to fix. After re-reading this post this mostly feels like a click-baity way to advertise OpenDAL, which the author appears to be heavily involved in.
Hard agree. If AWS were offering “S3 compatibility certification” or similar I could see framing this as an AWS/S3 problem. This seems like the definition of “S3 compatible” changed, and now everyone claiming it needs to catch up again.
Does 5 of a kind beat a royal straight?
If an Uber driver caused you to miss a flight by driving around a parking lot in circles at a speed you can't exit the vehicle, you don't think it would be a reasonable request for the customer to ask Uber to make it right?
When you call from a cell phone, public safety answering points get your gps data from the carrier. Landline calls have their associated address data sent. This is called e911 and has been a thing for over 20 years.
The person answering the call will ask for a specific address, but does not need it to send help towards you.
It would be less weird because I'm in public with a different expectation to privacy, but your point about surveillance in general is noted.
As a cost-to-entry for a casual player, this seems like a pretty hard sell. I'd rather just find something else to play personally, than deal with a webcam and some invasive recording situation to play.
Assuming you mean "undefined" as "unprovable", this still seems like an extreme stance to me. I also think, even if we had this the next goal-post would be "provenance of the video".
I read this as 20% on top of the 30% that already happened 3 months ago.
Actually, I'm asking Google to serve me a file via a GET request. The response they send back includes the content along with an ad. Google would prefer I watch the ad but since the bits are on my computer and Google has no say in how I operate my computer, which bits I read, or how I allocate my time their wishes don't really matter after they've sent me the bits I care about.
Google could just say "no" and not send me any content at all. I'm not "taking" anything though.
And yet it's optional and they also keep sending me the same videos for free along with ads.
I could opt to close my eyes and ears for every ad they send instead and it would have the same effect at the cost of my personal time. Ad blockers are just time shifting Tivos in disguise. Google has no say in how I spend my time interacting with the bits they already sent to my computer.
If this is the analogy, why doesn't Google try something like protecting from sticks in the first place? For example, they could lock all of YouTube behind a login & paywall.
It seems like YouTube is attempting to FORCE people to adhere to its desired business model. If ad-supported video playback is not economically viable, then maybe it's time for a new model to be born? There is no obligation for me to pick up the stick and hit myself with it because Google says I should. I downloaded a bunch of bits that Google sent to my computer, and then I read the bits I cared about. That's how every webpage has worked in my experience.
A similar realization had a major impact on how Blizzard approached end-game raiding in WoW. In the first 2 expansions, only the most dedicated players were seeing the final boss and culmination of the storylines. It took 40 players working together to get there, and those 40 players had to execute complex fights in order to reach the end. Though a very rewarding experience for those who could do it, Blizzard did the math and realized they were excluding the VAST majority of their playerbase from the coolest content. They were spending tons of money creating this content and no one was experiencing it!
In the 3rd expansion and ever since then, end game content has been tuned to be a lot more forgiving and to require less people. There are still complex and rewarding fights, but ramping up the difficulty is "opt-in" generally speaking.
This is likely one of the reasons the game remained so successful for so long. Prior to this mentality shift, it was very common for end game MMO content to only be seen by a small minority of the players.
This is every Lombok lover's favorite strawman argument I've run into.
I've been coding in Java professionally for ~20 years. I can count with zero hands the number of times I've been burned by a getter or setter getting changed into something surprising.
If you really need auto-generated getters/setters/builders - Immutables [1] is a library that does it using bog standard annotation processing rules that don't require hacking your build process.
Ugh Lombok! Literally everything it does is replaced by any competent IDE with auto-generated methods, with the added benefit of not requiring special build handling steps because the library can't play by the normal annotation processing rules.
There was maybe a time Lombok made sense. It does not anymore. Death to Lombok.
As someone who has recently went through an EV shopping and purchase exercise, the dealership model has SO MUCH room for improvement.
Every dealer was immediately talking to me about financing options and specials before I even sat in any single car, let alone test drove one.
Of the 5 makes I test drove:
only 1 was willing to have the car configured with an actual single-pedal-driving experience (Volvo). Most were worried that my unfamiliarity with single-pedal-driving would lead to a bad test drive experience.
only 1 was willing to talk to me in clear terms about how route planning and mapping would work with the charging network. 2 different dealers told me I would have to download "an app off the appstore" for route planning & charging.
every dealer had some sort of dealership mark-up on the EV. Usually in the range of $1K - $3K. The Audi dealer was kind enough not to lie to us about the purpose, it was a dealership markup that he thought would be negotiable if it meant losing the sale.
Our Tesla test-drive experience - we showed up for our appointment, got some brief instructions / Q&A, and were handed a set of keys to tool around with for an hour. Another Q&A after, and no pressure to do anything else. We left without any purchase commitment, and made that separately online on our own time after more deliberation about the decision.
My partner and I went into this process sure we would pick a non-Tesla, it was the last car type we test drove after weeks of trying others. Every dealership turned us off in some way. That combined with the raw numbers (price of car, range, cargo space, towing capacity) it's no contest that Tesla has both the best EV and the best buying experience for an EV.
and honestly a remote exploit for that has never been spotted in the wild.
What? Citation needed.
This spread through Minecraft servers like wildfire. The damage was mostly kids crashing the game on other kids, but that's still a denial of service.
Log4Shell definitely had "in the wild" exploitation. A trivial amount of googling gives evidence.
Here's the most disingenuous part for any defender of KF so far. The linked Twitter feed has a post from the KF operator:
"For the time being, I am locking the threads of the most prominent members of the hashtag campaigns against us... I'm tired of hearing about it."
Very "Free Speech" of KF. This is all just public information after all, isn't it?