It’s evidence that your password leaked. What are you on about? You think they just randomly guessed his password?
312 karma · joined March 28, 2023
It’s evidence that your password leaked. What are you on about? You think they just randomly guessed his password?
The fact that we see separate patterns of brain activity is the interesting part not any semantic argument about what you or mathematicians feel should be defined as being math or not.
It seems plainly obvious that this language just means “areas of brain that activate when dealing with math problems” vs “areas of brain that activate when dealing with language problems” and yes there is hard evidence that there is a difference between them.
This is such a toxic mentality. Yes sales always sits at the end of the value stream, but they aren’t selling thin air. Everyone in the company contributes to making that sale possible. The waiter gets a tip because “everything tasted amazing” but the chef gets stiffed because “he just made it”
As always, they have equality but some are more equal than others. And they are transparent, but obviously not on the parts where transparency would expose the inequality because that wouldn’t be popular.
You could already do everything you are proposing t-strings will make easier with just strings or f-strings.
‘query: SQL “Select …”’
“Wait” you’ll say “then the function taking the string has to parse the string and will have to add ugly logic grabbing variables from globals()!” Ah yes. That’s such an ugly solution… let’s instead codify just that as the official best practice and sell people on it by prefixing a t to the string so they don’t notice…
Then the t is redundant and we don’t need t strings involved in any way. This would work just as well. In fact better by using html("<h1>Hello</h1>") and have it return a html object instead of returning a just a string which is what t-strings will do. So literally the only contribution from t-strings in that context is to make things worse.
If they had just standardized some way of putting semantics into the template everything would be better. Let us define a “sql = temlate(….)” and use sql”…”
This is such a strange take on t-strings. The only way for anything to infer that the template string is supposed to turn into valid HTML or SQL is to base it of the apparent syntax in the string, which can only be done in an ad-hoc fashion and has nothing to do with the template string feature.
The way the feature has been designed there is no indication in the string itself what type of content it is or what it will eventually be converted to. It’s all handled by the converting function.
As others have added, something like sql”select * from {table}” would have been able to do this, but there’s not even any guarantees that something that is in a template that will be converted into valid sql by a converting function should be any type of valid sql prior to that conversion. For all you know t“give me {table} but only {columns}” might be a converted into valid sql after the template is processed.
The way I was taught it and the way that worked now for my now 3 year old is just to say pirates buried a number under the X, and that we need to guess what they buried. If the concept of a number being hidden is a barrier to understanding for anyone they have seriously bad teachers.
Funny enough I read not that long ago about a case where an algorithm broke all those three points! Can’t remember where of the top of my mind, I think it was the Louisiana Prison board or something like that.
But never mind that, you are arguing against yourself so I’ll kindly step aside and let you at you.
Can’t fault cursor for letting people install extensions when most of those, if not all of those, developers want their extensions on cursor.
Call it a conspiracy but I won’t at all be surprised when someone discovered they have transferred a large amount of funds to some “family friends” that look suspiciously like them but live in the Cayman Islands.
This is such a small UX thing but it’s so damn important. The simple fix is to not auto-name notebooks untitled-# when the user clicks new notebook just ask the name straight away, if they can’t name it don’t create it. It might add the smallest amount of friction to the UX, but it’s so damn important.
Also the choice of json as the file format is just plain wrong. Why the project hasn’t just abandoned that entirely and done a json-#python back and forth when writing to file is beyond me. There are extensions that do this, but that’s a really clunky interface, and while I can set it up for myself it’s difficult to force upon others in a corporate environment.
Great to see someone is taking the seemingly small things up, because they mean a world of difference to the overall ecosystem.
The reason we have touch screen phones today is exactly because Apple dared to challenge that assertion. We should not assume that what is out there now is the end goal. Users don’t have a choice they can only buy and use what’s available to them in stores. The second touch screen phones were available the entire market shifted in a short period, but the mantra at the time was just like you have now “physical keyboard are the only way” who knows what could come from people who think outside the box in the future.
Knowing the name of the service helps the attacker, knowing the name of government officials working at city hall helps attackers, knowing the legal description of what a parking ticket is helps attackers. If you are sued and decide you want to hack the government knowing the details of the suit against you helps you in your attack.
The barrier is not “any helpful information must be censored” the barrier is “don’t disclose passwords or code that would divulge backdoors” a schema cannot be that.
So you yourself have already seen the demise of the programmer so why are you arguing against it? Software development isn’t going away. But just like we no longer have tweeners in animation, we’ll soon no longer have programmers in software development. Then soon there after we won’t have “front-enders” and “back-ended” the term “full stack” will lose meaning and at the end what we call a software developer will be more akin to what you today call a business analyst than a programmer.
They couldn’t in the UK either which is why they completely removed encryption, they could do the same in the US if the government pushed for back doors.