- hatsixAndroid Studio is built on the IntelliJ stack. Jetbrains just launched a dedicated Claude button (the button just opens up claude in the IDE, but there are some pretty neat IDE integrations that it supports, like being able to see the text selection, and using the IDE's diff tool). I wonder if that's why Google decided to go VS code?
- That's the individual server, not a standard Discord policy. Subreddits can also make gates that are exclusionary. So... not Discord the company.
Even if it was, "Requires a verified phone number" is not "Evil". You might not like it, it might be incomprehensible, it might be exclusionary, but it's not "Evil".
- According to Musk, my car was supposed to be unsupervised driving by now. The shift to vision only has consumed all of their resources for the past several years, and my car has been left behind. There have been giant leaps in vision only, but it still isn't better than the vision+radar.
So, I was deceived. I didn't buy the car because of the deception, but I did buy FSD because of it.
Also, FSD disengaging when it gets sensor confusion should be considered criminal fraud. FSD should never disengage without a driver action.
- Both devices focus on readability and rely on a reflective screen. Both devices are monochrome.
This is like comparing OLED vs MicroLED. They're technically different technologies, and each has it's own strengths. The OP is saying that "Never Seen on ePaper" is like saying "The Best iPhone Ever"...
- This absolutely has not been my experience. I'm on the cusp of Gen X, but I had to turn away requests to interview after I added #OpenToWork on LinkedIn. I ended up with four full loops in a single week, and a hard choice between three offers. I definitely shook my network to get internal referrals, but once recruiting knows you are a real person, most companies move quick.
Submitting resumes without a referral is useless, you gotta work your network.
- Just like Puerto Rico and DC?
- I believe that's the Mexico/Canada Tariffs, but it's really hard to keep it straight, by design.
- What do you assume that a non-apple tablet runs, if not Android. Why would running Android be a surprise to you?
- I got my wife a Daylight tablet and she loves it. prefers the screen over any tech she has used... eink, OLED, whatever. It's standard android, so go ham.
- "Not Sure" != "ambivalent". It's a mistake to lump "Not Sure" and "Opposed" together and declare a majority, as the group as a while does not represent a specific stance. Any attempt at nuance for either side gets bucketed into the largest category.
That group seems like the most interesting question... what sub groups do they fall into.
- I tell people that Ruby is a language optimized for reading. Things just make sense when you are reading what someone else wrote, but it can be much more difficult to write something from scratch with no guidance. Take dates, for example. Let's say you are fixing an issue, validation was set to accept one week in the future, but should have been one day in the past. 1.week.from_now becomes... well, how do you look that up? You head to the Ruby Lang site and look up Integer, but Integer doesn't have `.week`, so now you have to rely on Google-fu to find what you need, but you'll get a mix of base Ruby and Ruby on Rails, which modified base classes with some syntactic sugar. Eventually you find 1.day.ago and file that away, only to go through the same research for the next line you need to change.
It can be one of the most pleasant languages to read, but a lot of hidden knowledge is required to write it like Ruby wants you to.
- I rant about rails, often, but this is just a full on garbage comment. Your evidence is "all of the rails apps stuck"... where exactly? like... you have a listing of these? Or are you just making things up?
I've done a ton of rails upgrades in my career, they've all been easier than any other framework (except the current batch of js/ts frameworks that use codemods to update the majority of breaking changes).
DHH has been making some pretty wild changes with non-Ruby parts of Rails, but Rails 8 still fully supports sprockets, their asset pipeline introduced 15 years ago. All of the other asset pipeline alternatives are still supported, even though Rails introduced "Propshaft" as a replacement.
The only thing we've had trouble with upgrading has been when Rails added full support for read/write shards... it wasn't fully compatible with Aurora Serverless at launch, but we had wanted to migrate off that anyways.
So.... try adding some signal instead of just noise. Cite specific issues, rather than just try to ride a bandwagon.
- Maybe you missed the part where I said "this is fine". I don't have a problem with what they're doing, I have a problem with people saying that Apple doesn't do something that they very clearly do.
Also, I thought I was fairly clear in my comment, but Apple removed support in MacOS 13 for Firewire Audio... so it doesn't matter what kind of dongles you have, as soon as you update to 13, your firewire camera no longer works.
It's weird that Apple is removing driver-level support for a protocol. It's unexpected. It's also a dead tech that nobody cares about. The person I was responding to wanted an example of accessories that Apple stopped supporting, and "Anything with Firewire Audio" falls into that category. It is completely, utterly unusable with stock MacOS 13, though it's likely that some people have found a way to put it back in.
- Specific to my comment, Apple removed code that supports audio over Firewire. It doesn't matter if adapters are available, cameras and microphones that used Firewire no longer work on MacOS 13+.
Again, it had a long run, I'm not upset that they "only" supported it for 10 years... but let's be very clear, the devices don't work. Also, this is them removing support for a protocol that is part of the base MacOS, so it's exactly like what will eventually happen when Apple stops supporting the original Airpods protocols.
I don't think that's any time soon, and if you're in the Apple ecosystem, go ham... let's just be very clear about the comparisons here.
- It's exactly how Apple operates. The last Apple device with Firewire was produced in 2012, though it was sold for several more years. MacOS 13 (2022) dropped the Firewire CoreAudio driver (as well as other, more niche support for Firewire). So... exactly 10 years.
If you're going to put me in a bucket, I'd be in the "Apple Hater" bucket, but I honestly think that the way that they do this is fine. It would have been better if they had jumped on the USB bandwagon earlier, they certainly love to build their own solutions that are incompatible with where the rest of the industry (see also, their proprietary wireless audio, their proprietary bluetooth codec, their proprietary thunderbolt extensions, their proprietary magsafe power connectors, their proprietary Lightning cable/connector, their forking of webkit off of khtml, their changes to webkit that are part of Safari but haven't been pushed upstream to webkit)
Anyways, this is exactly their MO and it's not bad. Apple doesn't need you to contradict everything people say about Apple.
- I'm generally in the camp of "I wouldn't miss anyone or anything involved in this story if they suddenly stopped existing", but I don't understand how engaging in a publicity battle is considered proof of anything. If their case was weak, what use is it to get the public on "their side" and they lose? If their case is strong, why wouldn't they want the public to be on their side?
I hope they all spend all of their money in court and go bankrupt.
- "Have some fun with it"... For most bands, each album they put out is a year's worth of effort and a year of income. You don't want to get de-listed from the charts because it looks like you're gaming the system. If your album charts, it's guaranteed radio and playlist placements, leading to more exposure.
Most bands are funded similar to VC.. there's an investment, then payoff then profit. If you don't payoff the investment because you "had fun with it", your band will be dropped and you are searching for a label while working your day job.
- Which is it? So problematic that you wouldn't use it even if it were exactly the tool you needed, or "a bit weird".
I agree, it's a bit weird. So is putting a lot of effort into a project that nobody is asking for and you'll give it away for free. There are many people in my life that are neurodivergent and some situations cost more than they are worth. I have had several projects I thought were good candidates for open source, but the idea of dealing with the "anonymous a-hole" has been a show-stopper for me. I appreciate that the authors of this project seem to have similar concerns, but have overcome them by creating a social contract. I believe that it's entire goal is to turn people away whose interactions may be too much for the maintainers. Good.
If reading those rules and abiding by them is too much for you, then just turn around and walk away. That's the intention and goal. They're doing you a favor, letting you know that your brand of weird is not compatible with their brand of weird. They don't have to make space for everyone in their little project, and there might not be space for you there, and that's OK.
- Also, if they're not the same recording, they're not the same album, which means that the popularity of any individual album is split. Contracts get better the better an album does on the charts, but if you release the same album three times, you're competing against yourself.
- Your experience matches the claims in the article: the slowdown isn't in adoption, but in capabilities. The article discusses how the last few years of "just throw more processing at it" has hit diminishing returns across the board. The article suggests that this pause is a great time for businesses to catch their breath and figure out what to do about the current tech, whether they've been waiting to adopt or are concerned about competing.