Obi-wan and Luke looking at Washington DC, saying "You will never find a more wretched hive of scum and villainy."
Interpret as you like.
@atomicmonks.com
Making software since the 80s, mostly business, some games. Unabashed JavaScript enjoyer. Childish taste in entertainment (explosions and cartoons). Probably on the spectrum. A fan of strange haiku. #dotnet #csharp #js #javascript #anime #dnd
Obi-wan and Luke looking at Washington DC, saying "You will never find a more wretched hive of scum and villainy."
Interpret as you like.
They need more power, for their own benefit only, solution is simple: they pay for the construction and operation.
I think we've had enough socialism for corporations.
Companies won't lower prices. They'll keep the elevated prices and blame the remaining tariffs and "supply chain disruptions" to pocket any easing in tariffs.
Caveat: some may lower prices a TINY bit to try to draw customers that are gun-shy on purchases.
Where's the "set post on fire" button?
That was awful.
Well done.
To people looking to understand _why_ Democrats caved: they saw the travel issues at airports and absolutely did not want to have to deal with that for the holidays.
They caved for personal convenience. It's always about them, not us.
Dad asked me to install Linux on his PC, as he was super annoyed with Windows trying to cloud/AI everything. Was happy to oblige. Linux Mint XFCE on his older hardware and it's like a new machine.
Oh man, I remember that book.
As a developer, I'm just going to say it. AI is simply a technical debt generator.
Also, using it to render advice is like subcontracting to the Joker.
Maybe by insisting that prior to supporting any budget bill a law must be passed banning recision/impoundment?
Want to, but can't get past $50 for a matinee showing.
So the U.S. Constitution hosted at congress.gov has had Article I modified to remove the end of Section 8 (starting with mention of the navy), and Sections 9 and 10 completely. Seems like some important stuff in there. Nothing to worry about, right?
web.archive.org/web/diff/202...
"Ha ha, that's pretty funny."
Goes to console after a long moment, because, well, JS.
"This message was sent to you because you signed up to use Gemini."
No, you fuckwits, I absolutely did not.
I apparently can't be trusted to build a PC any more. Built many, but last one getting too hot. Pondered and poked, then on a whim did the "piece of paper in front of fan" trick.
I had installed the CPU cooler fans backwards. CPU up, builds a heat dome in the middle of the case.
Genius.
Every piece of information you give a company is sold and traded more times than you can imagine. And it takes much less data than you think to put together a very detailed picture of who you are, where you've been, and what you think.
When I was teaching the ultimate power move was to say you were going to contact their GRANDPARENTS. They took that super seriously.
It's useful if you need artificial stupidity.
As a dude, I find it disturbing how few guys understand this. Not surprising, just sad and disturbing.
I'm sure it's completely unrelated that most guys have thought of me as "weird" my entire life.
Strong start, appropriate expletives, but a weak finish with "nincompoop". Might I recommend:
* soulless flap-mouthed varlet
* stinky codswallop
* witless wart
* canker blossom
More seriously, why don't we hear more about WHY due-process matters?
/5 Chrome spots the honeypot field and autofills it, leaving the real one alone.
Google, why am I having to resort to such shenanigans for this?
/4 The textarea was clunkier than I wanted to maintain. Where I finally fell was adding an additional text input between the label and the input I cared about:
<input type="text" style="width:0;height:0;padding:0;border:none" name="DummyUserName" />
/3 I had removed the "for" attribute on the label also, but no joy.
There was a pretty clever example of using a textarea, which doesn't get the autofill treatment, and using CSS to make it look the same and some JS to make it act more like a normal text input.
/2 The commonly listed advice of renaming the field to something other than "UserName" also did not work. After some experimentation it became clear that the associated label ("ID") was being spotted by Chrome's autofill service to populate the now renamed text field.
1/ In case this helps someone else...we have a member management form where admins can edit user accounts. Users don't have an ID/login by default but it can be set there. The user ID was being populated by Chrome's form autofill and setting autocomplete="off" did nothing.
#javascript #webdev
/5 Chrome spots the honeypot field and autofills it, leaving the real one alone.
Google, why am I having to resort to such shenanigans for this?
/4 The textarea was clunkier than I wanted to maintain. Where I finally fell was adding an additional text input between the label and the input I cared about:
<input type="text" style="width:0;height:0;padding:0;border:none" name="DummyUserName" />
/3 I had removed the "for" attribute on the label also, but no joy.
There was a pretty clever example of using a textarea, which doesn't get the autofill treatment, and using CSS to make it look the same and some JS to make it act more like a normal text input.
/2 The commonly listed advice of renaming the field to something other than "UserName" also did not work. After some experimentation it became clear that the associated label ("ID") was being spotted by Chrome's autofill service to populate the now renamed text field.
You can tell a lot about what's going on in an area by what's for sale at the area swap/flea market.
Today's standouts: chickens, goats, fruit, veggies, plants, fishing gear, and rifles. So many rifles. No shot/hand guns, just rifles.
Hmmmm.