Ad blocker?

where anyone thinks it’s ok or normal to recommend suicide to people

Except that’s already happening even without it being normalized, there have always been assholes that are gonna tell people to kill themselves, especially if they’ve never seen the person they’re talking to before. I don’t see how this is any different.

Literally the whole thing would not have happened without the policy.

It also wouldn’t have happened if a fucked up system wasn’t withholding actual, reasonable alternatives that the person was clearly asking for. That’s my point. Let’s fix the actual problems, rather than try to silence the symptoms.

…and did you notice how everyone was outraged by that? That incident was not an issue with assisted suicide being available, that was an issue with fucked up systems withholding existing alternatives and a tone-deaf case worker (who is not a doctor) handling impersonal communications. Maybe it’s also an issue with this kind of thing being able to be decided by a government worker instead of medical and psychological professionals. But definitely nothing about this would have been made better by assisted suicide not being generally available for people who legitimately want it, except the actual problem wouldn’t have been put into the spotlight like this.

I don’t want to create a future where, “I’ve tried everything I can to fix myself and I still feel like shit,” is met with a polite and friendly, “Oh, well have you considered killing yourself?”

Are you for real? This kind of thing is a last resort that nobody is going to just outright suggest unprompted to a suffering person, unless that person asks for it themselves. No matter how “normalized” suicide might become, it’s never gonna be something doctors will want to recommend. That’s just… Why would you even think that’s what’s gonna happen

I can get behind that

Ohh the “what time is it in films” argument is good, haven’t heard that one before, thanks

It’s gonna get much worse when you start to try mapping days of the week onto the new times. Are days gonna be the same everywhere as well, to stay from 0 to 24? If so, have fun saying things like “Let’s find a time on Wednesday/Thursday”. People likely couldn’t be bothered and would probably just use the day that their normal wake-up time falls on to mean the full solar day instead. At which point you could also just say okay, weekdays are still following local solar days. But now what weekday is it halfway around the world? Now you need to look up their solar day.

All this to say - abolishing time zones will introduce the reverse problem for every problem that it seemingly solves. You can’t change the fact that our planet rotates and people in different locations will follow different schedules. Turning the lookup-table upside down is just a cosmetic change that doesn’t remove the situation that’s causing the confusion. I’d rather just stick with the set of problems that we’re already used to dealing with.

No

Yup, you got it. Even the solution to your confusion. Good encryption algorithms are set up so that even the smallest possible change in the input (a single flipped bit) will produce a completely different result. So yeah, if you have just a small set of exact possible messages that could be sent, you can find out which one it was by encrypting it yourself and comparing your result to what was sent. But there is a super easy protection against this - just add some random data to the end of the message before encrypting it. The more, the harder it will be to crack.

Yeah, but by generating with AI you’re incentivized to skip that initial research stage into your own code base, leading you to completely miss opportunities for consolidation or reuse

…I think you’re confusing GDPR and GPRS? Unless I’m being whooshed here

There are some cases though where the code is just complicated for reasons outside of your control, in which case “what” comments are good - but they should never be taken at face value, but only used as a first step in understanding the code. There’s a significant risk of the code not actually doing what the comment says.

…autism is an industry??

Oh, that sounds really cool! At what time does this validation happen? While you code, or later at build time?

I’m not talking full blown ORM here, not a fan of those either. I’m talking about some light weight wrapper that basically just assembles SQL statements for you, while giving you just a little more type safety and automatic protection against SQL injection, and not sacrificing any performance. I’m coming from the JVM world, where Jooq and Exposed are examples of that kind of thing.

As the other commenter said, the Jetbrains IDEs do this perfectly fine. Although I’d also argue that if you’re working with SQL from within another language already, a DSL wrapper is probably gonna be the better way to go about this.

Well then use all-caps keywords whenever working on those systems, I don’t care. But an edge case like that shouldn’t dictate the default for everyone else who doesn’t have to work on that, that’s all I’m saying.

My ide isn’t limited to color when it comes to highlighting, so being color blind generally shouldn’t be a problem. Set keywords to underlined, bold, italic, whatever works for you.

Your other examples I can see, but at least at my work those are rare edge cases, and I’d rather optimize for the brunt of the work than for those. Of course at other places those might be much more of a concern.

I understand it as an attempt to get very basic, manual syntax highlighting. If all you have is white text on black background, then I do see the value of making keywords easy to spot by putting them in all caps. And this probably made sense back when SQL was first developed, but it’s 2023, any dev / data scientist not using a tool that gives you syntax highlighting seriously needs to get with the times

You’re right that words can be coined and their usage changed, but you seem to be misinformed about how that happens. You just deciding we’re gonna do it this way now in a random thread on lemmy is not gonna cut it, sorry