Do people understand the impact ChatGPT can have on how we control our software? No more hunting through menus among a thousand options to figure out how to do something. Just use natural human language. The UIs we've had to design and live with will be a thing of the past. Yet no one seems to be talking about this.
And if you do describe the actions that the computer is to take, in rigorous, clear, unambiguous terms that cannot possibly be misunderstood, congratulations, you're a programmer using a programming language.
ohhhhh, the reason i couldn't find any device-specific code in the binary i was reverse-engineering is because it was all living in encrypted lisp blobs
(Go ahead, argue with me. Whatever notional safety you're adding by making sure every email and Teams chat from me comes from βMaximilian" doesn't outweigh the many annoyances this causes me and my colleagues, and if you think it does you've proved my point.)
That kind of rule isn't for adding safety. It's for deadnaming trans people. If someone suggests such a rule to you, then that someone is probably a bigot.
I wonder if anyone has ever written an embedded #RDBMS in which there is no run-time #SQL interpreter, and all SQL queries are translated into machine code at compile time.
Kinda like #Rust sqlx, except queries are fully compiled at compile time, not just checked for correct syntax and types.
I'm guessing this would be extremely specific to one #programming language, and outright impossible in most programming languages.
Just a reminder, if you're in a state without access to abortion, there is a network of care, providing safe, effective, and free abortion pills and information.
Provocative statement. But not unexpected given the rise of #LargeLanguageModels and their ability to transform one language to another. In fact, this capability exists now and is being built into products, increasing productivity and sprint velocity.
How are you leveraging these technologies to realize the same benefits?
I have just learned that Visual Studio Code on Mac/Linux not only supports, but expects .sln files, and now nothing in the entire world makes sense to me anymore. Your cross-platform open source editor for your cross-platform open source command line toolchain relies on the pure-text proprietary container format for your 30-year-old single-platform GUI IDE? β¦ what does it even do with it? A VSCode popup says C# code completion won't work without it. What does it expect to be in there?
How are you even supposed to create them? As far as I know, the usual way to create a .sln file is with Visual Studio. Which I thought VSCode was supposed to replace.
That's actually pretty much how I feel about the average voter: willfully thick. Grown, clear-thinking adults should not need this much persuasion to vote correctly. Maybe they do need it, and more power to you if you think you can do it, but I'm appalled that you even need to.
In a sensible world, a career criminal who openly plans to impoverish the entire country wouldn't have a snowball's chance in hell of securing a majority of the vote for any political office. It'd be unthinkable.
Side note: these people are also weirdly forgetful of their own childhoods.
Notice how they're always freaking out about kids these days doing some new thing, like video games or social media? Always with the damn moral panics. Have they forgotten what it was like when they were kids, rolling their eyes while their elders freaked out about them listening to rock-and-roll music?
I learned as a kid that moral panics are stupid. Why didn't they?
Sure, Biden is much better than the worst POTUS ever, Trump, but Big Oil are making "record profits":
Chris Heyes:
"[β¦] if I'm not mistaken we're pumping more oil and gas than any country in history ever and [Big Oil] are making record profits, right?
Lisa Friedman:
[β¦] You know, you're absolutely right. The Biden Administration is overseeing record oil and gas production [β¦] and they're not eager to tout that"
That's not the only way to crash the economy. Another way is if oil suddenly becomes unavailable, and all commuting of workers and shipping of goods stops cold. Instant Great Depression. People will start dying very quickly.
I have no sympathy for the oligarchy and its greed, but I do want to keep myself and my fellow working-class Americans alive.
If you want to put an end to Big Oil profits, you do it by making oil obsolete. It can be done, and it slowly is being done, but there are a lot of serious problems that need to be solved along the way, and that's going to take time, effort, and patience.
If you try to short-circuit that whole process and just shut down the oil industry right now, all you'll accomplish is making millions of innocent people suffer.
This is funny. OpenAI, who scraped the entire internet to build its product, is now enforcing copyright via notices. They still donβt give credit for stealing content from everyone, yet now acting like holier-than-thou https://www.reddit.com/r/ChatGPT/comments/1cnvyzp/
so, you've seen β’ and β’οΈ before. but like. why are there two. well, i have an explanation! the answer is: FE0F
first, unicode. unicode is a standard definition of a bunch of codepoints, where a codepoint is just a number with meaning. for example, unicode codepoint U+263A refers to βΊοΈ, or "White Smiling Face", and U+1F431 refers to π±, or "Cat Face"
so, lets start by looking at the codepoints for β’. decoding it, it becomes the codepoint U+2122, referred to as "Trade Mark Sign". this was added in unicode 1.1 in 1993, a decent time ago!
next, the codepoints for β’οΈ. decoding it, we get two codepoints! U+2122 (β’οΈ) and U+FE0F. wait. who is FE0F. why is he in my emoji
well, unicode isn't as simple as a series of codepoints that refer to single characters. take a look at eΜΜ for example. this is three codepoints, U+0065 (Latin Small Letter E), U+0301 (Combining Acute Accent), and U+0317 (Combining Acute Accent Below). the first codepoint is simple enough, it's just e. the next two, however, are combining codepoints. this means that they combine with the codepoint before them to modify it. U+0301 adds an acute accent above the previous codepoint, and U+0317 adds an acute accent below the previous codepoint. this example specifically isn't very useful (i don't know any language with a eΜΜ character beyond conlangs), but it becomes very useful for languages that use a lot of diacritics. imagine if we had to make a new set of characters for each set of possible diacritics! big waste of space, we shouldn't have done that!
so, what is U+FE0F? well, it's a special codepoint called "Variation Selector-16". variation selectors are a reserved block of 16 unicode codepoints. only some have been defined, but among those currently in use are U+FE0E (VS15) and U+FE0F (VS16). from wikipedia: "VS15 and VS16 are reserved to request that a character should be displayed as text or as an emoji respectively." so, what's happening with β’οΈ is that it's combining a U+2122 (β’) and a U+FE0F (Variant Selector-16) to create an emoji version of β’. they're the same character, just that one has been instructed to become an emoji!
I dislike UTF-16, because it imposes a hard upper limit on how many code points are representable.
UTF-16 can represent 1,112,064 code points.
UTF-8 and UTF-32 can represent 4,294,967,296 code points.
But because a bunch of APIs use UTF-16 exclusively (including Java, JavaScript, and Win32), the remaining 4,293,855,232 potential code points can never be used without causing massive, nearly unfixable breakage in a lot of important software.
If we develop warp drive and meet a bunch of alien races, will we finally abandon UTF-16, or will we turn tail and run back to Earth so that our computers don't all explode? π€
A Tesla owner has been charged with vehicular homicide for killing a motorcyclist while browsing the web on their phone while the car was on Autopilot. According to the driver he was βputting the trust in the machine to drive for him,β
