IHeartBadCode @ IHeartBadCode @kbin.social

Posts

1

Comments

618

Joined

2 yr. ago

He found out that getting bad press is better than no press. Like the original thing that got him caught up in the headlines was crass but that's sort of his humor. This one, he's just being a gigantic penis about it and banking on the follow up outrage.

The thing is the anti-politically correct shtick only last so long. At some point it just becomes noise and then you have to up the ante which in turn alienates more people. Rise and repeat till it's difficult to get a booking anywhere but FoxNews.

Like much of anything. It's his career, far be it for me to tell him how to run it. But his comedy routine as of late has just turned resentful and aiming to get as many people to gasp "Oh my, he's such a bastard!" And in reality it just comes off as a big yawn.

So they will probably have to argue that the ratifiers of the amendment were so worried about insurrectionists taking over government that they wanted to prevent it, but not enough they thought the presidency should be barred to insurrectionists

Except we have the record for for their debate saying that the 39th Congress who passed the 14th Amendment knew that the Office of the President was indeed an office to be guarded. The reason they enumerated the others in Clause 3 was because multiple people wanted to ensure that those folks too were covered.

But even if the President isn't enumerated Trump has this problem.

The powers not delegated to the United States by the Constitution, nor prohibited by it to the States, are reserved to the States respectively, or to the people.

— US Constitution, 10th Amendment

So it not being specified by the Constitution nor being codified by Congress as law, how States want to look at the 14th is up to them. So even if SCOTUS wants to play the "The President is not listed" card. It's not explicitly denied. The tenth amendment indicates that if it's not denied, States get to run with it.

What SCOTUS can rule upon is "due process" which is asserted by the 14th clause 1. SCOTUS could indicate that the process by which Colorado took doesn't meet this bar. But then, SCOTUS would kind of be on the hook for indicating "well what is the official process?" And if they say "Well Congress has to make it up" then we fall back into the "if Congress doesn't say anything, States get to run with it" problem that the 10th amendment grants.

See Colorado isn't trying to impose their will unto everyone, which means this squarely falls into a "State's rights" kind of thing. And that's going to get tricky for the Conservatives to word salad themselves out of that corner they've painted. That's not to say they won't, but it's going to be an interesting read to say the least on how they rule.

I can understand their hesitancy to rule with Colorado because then it'll open a floodgate that we all know that particular states will attempt to abuse. But boy oh boy have they been so strong on States should get to do what they want so hard that this kind of thing was just waiting to come back and bite them on the ass.

For anyone curious enough. Power is vested via 22 USC § 2318. Fun fact. Since 1988 this power has been invoked 59 times. 25 of the times have been for the Ukraine-Russia war. And of course twice for Israel just this year alone. For those doing the napkin math here, out of ALL of the times this power has been cited by a President (or related officer), 47% of them have been under Biden. Just FYI.

As much as I liked to blame Governor HVAC. It's really the fact that the Frist family exists.

For those wondering. Yeah. They absolutely did say that.

Yeah here in Tennessee we have filial laws that puts some of that debt that parents rack up on the backs of the children. TCA § 71-5-115.

GenX here as well. My mother died horribly of cancer when I was 13 and my father left about two weeks after her death and I was legally transferred to the State's custody.

I've been told I'm "lucky" in that I'll never have to shoulder my parent's debt. So, you other people don't know how lucky it was to be an orphan! But no really, a finical planner literally indicated to me that, THAT was a positive. And somehow that's really colored my opinion on where we are as a society.

It's less executive action and more pipeline issues.

The department related to approval for these things just hired 140 new employees that just got through on-boarding for this specific task. That 140 is literally the max Congress approved for handling applications in all tiers of the program, with a lot of Senators having hoped that somewhere around ½ that number would have been the final tally hired in.

Those new employees will then need to navigate the 50+ page applications for each bid. With something around 480 bids in the first CHIPs acceptance round. So around 180 people will need to digest as quickly as possible somewhere around 24,000+ pages of applications. That's not counting any kind of objections that might have been filed by State, private citizen, and also competitors (Samsung and Intel have a few of these already on some of the first tier 1s already).

And all of this is just the first steps of the program that was written out by Congress. Congressional oversight, because remember all executive agencies established by law have Congressional oversight, has been really clear as mud on some of the finer details of this program. Biggest back and forth is the offshore but American funding, which holy crap I can't write enough about how complicated that debate has become.

All of this is happening on the several step process that Congress prescribed for this whole thing. Because, tier 3 and tier 2 funding are good candidates for abuse of funding. Solyndra echos can almost be heard when mentioning this. Or more recent example of what could go wrong when you just open the flood gates, PPP loans.

Thing is, companies complain money isn't coming fast enough all the time. The money could be on it's way next week and they'd still complain that it wasn't there on Monday. The more important thing is that the money isn't being wasted too badly and that's only happening with careful consideration. This is literally the exact same thing I said about Trump's wall. One, I don't think it would work anyway. Two, it's ignoring a lot of commitments we have internationally. But three, if we're going to do it, at least have a plan for properly spending the money which Trump did not because it basically took military funding and diverted it toward the wall, and thus it fell into one of those "you either spend it or lose it" and it meant that the construction had to be rushed and why a lot of "Trump's wall" is mostly falling into the Rio Grande or made of metal slats that can easily be sawed through with a hand saw.

So sure, whatever, but the more important thing.... Well let me clarify, the more important thing from my perspective, so totally cool if someone disagrees, is that the money is carefully spent wisely. It doesn't have to be a homerun, I just would rather the money not be tossed all over the place like PPP was.

And I get some of the arguments for why PPP was done the way it was, but to put it to scale, I would prefer handing it out like a 3, I understand why people would want it handed out like a 7, but holy fuck we handed it out like a 9.3. Where 1 is being penny up the ass to make copper wire tight about the money and 10 is prolapsed colon flow of money out the ass. It was really indefensible how just loosey goosey we were with that money. And yes, there's been other times we've done that (cough military cough), I didn't like those either.

One of the specific issues from those who've worked with Wayland and is echoed here in Nate's other post that you mentioned.

Wayland has not been without its problems, it’s true. Because it was invented by shell-shocked X developers, in my opinion it went too far in the other direction.

I tend to disagree. Had say the XDG stuff been specified in protocol, implementation of handlers for some of that XDG stuff would have been required in things that honestly wouldn't have needed them. I don't think infotainment systems need a concept of copy/paste but having to write:

    
Some_Sort_Of_Return handle_copy(wl_surface *srf, wl_buffer* buf) {
//Completely ignore this
return 0;
}

Some_Sort_Of_Return handle_paste(wl_surface *srf, wl_buffer* buf) {
//Completely ignore this
return 0;
}


  

Is really missing the point of starting fresh, is bytes in the binary that didn't need to be there, and while my example is pretty minimal for shits and giggles IRL would have been a great way to introduce "randomness" and "breakage" for those just wanting to ignore this entire aspect.

But one of those agree to disagree. I think the level of hands off Wayland went was the correct amount. And now that we have things like wlroots even better, because if want to start there you can now start there and add what you need. XDG is XDG and if that's what you want, you can have it. But if you want your own way (because eff working nicely with GNOME and KDE, if that's your cup of tea) you've got all the rope in the world you will ever need.

I get what Nate is saying, but things like XDG are just what happened with ICCCM. And when Wayland came in super lightweight, it allowed the inevitably of XDG to have lots of room to specify. ICCCM had to contort to fit around X. I don't know, but the way I like to think about it is like unsalted butter. Yes, my potato is likely going to need salt and butter. But I like unsalted butter because then if I want a pretty light salt potato, I'm not stuck with starting from salted butter's level of salt.

I don't know, maybe I'm just weird like that.

Over on Nate's other blog entry he indicates this:

The fundamental X11 development model was to have a heavyweight window server–called Xorg–which would handle everything, and everyone would use it. Well, in theory there could be others, and at various points in time there were, but in practice writing a new one that isn’t a fork of an old one is nearly impossible

And I think this is something people tend to forget. X11 as a protocol is complex and writing an implementation of it is difficult to say the least. Because of this, we've all kind of relied on Xorg's implementation of it and things like KDE and GNOME piggyback on top of that. However, nothing (outside of the pure complexity) prevented KWin (just as an example) implementing it's own X server. KWin having it's own X server would give it specific things that would better handle the things KWin specifically needed.

Good parallel is how crazy insane the HTML5 spec has become and how now pretty much only Google can write a browser for that spec (with thankfully Firefox also keeping up) and everyone is just cloning that browser and putting their specific spin to it. But if a deep enough core change happens, that's likely to find its way into all of the spins. And that was some of the issue with X. Good example here, because of the specific way X works an "OK" button (as an example) is actually implemented by your toolkit as a child window. Menus those are windows too. In fact pretty much no toolkit uses primitives anymore. It's all windows with lots and lots of text attributes. And your toolkit Qt, Gtk, WINGs, EFL, etc handle all those attributes so that events like "clicking a mouse button" work like had you clicked a button and not a window that's drawn to look like a button.

That's all because these toolkits want to do things that X won't explicitly allow them to do. Now the various DEs can just write an X server that has their concept of what a button should do, how it should look, etc... And that would work except that, say you fire up GIMP that uses Gtk and Gtk has it's idea of how that widget should look and work and boom things break with the KDE X server. That's because of the way X11 is defined. There's this middle man that always sits there dictating how things work. Clients draw to you, not to the screen in X. And that's fundamentally how X and Wayland are different.

I think people think of Wayland in the same way of X11. That there's this Xorg that exists and we'll all be using it and configuring it. And that's not wholly true. In X we have the X server and in that department we had Xorg/XFree86 (and some other minor bit players). The analog for that in Wayland (roughly, because Wayland ≠ X) is the Compositor. Of which we have Mutter, Clayland, KWin, Weston, Enlightenment, and so on. Which that's more than just one that we're used to. That's because the Wayland protocol is simple enough for these multiple implementations.

The skinny is that a Compositor needs to at the very least provide these:

• wldisplay - This is the protocol itself.
• wlregistry - A place to register objects that come into the compositor.
• wlsurface - A place for things to draw.
• wlbuffer - When those things draw there should be one of these for them to pack the data into.
• wloutput - Where rubber hits the road pretty much, wlsurface should display wlbuffer onto this thing.
• wlkeyboard/wltouch/etc - The things that will interact with the other things.
• wlseat - The bringing together of the above into something a human being is interacting with.

And that's about it. The specifics of how to interface with hardware and what not is mostly left to the kernel. In fact, pretty much compositors are just doing everything in EGL, that is KWin's wlbuffer (just random example here) is a eglCreatePbufferSurface with other stuff specific to what KWin needs and that's it. I would assume Mutter is pretty much the same case here. This gets a ton of the formality stuff that X11 required out of the way and allows Compositors more direct access to the underlying hardware. Which was pretty much the case for all of the Window Managers since 2010ish. All of them basically Window Manage in OpenGL because OpenGL allowed them to skip a lot of X, but of course there is GLX (that one bit where X and OpenGL cross) but that's so much better than dealing with Xlib and everything it requires that would routinely require "creative" workarounds.

This is what's great about Wayland, it allows KWin to focus on what KWin needs, mutter to focus on what mutter needs, but provides enough generic interface that Qt applications will show up on mutter just fine. Wayland goes out of its way to get out of the way. BUT that means things we've enjoyed previously aren't there, like clipboards, screen recording, etc. Because X dictated those things and for Wayland, that's outside of scope.

The bullet traveled through her left arm and into her chest, popping both of her lungs. She suffered internal bleeding and was unable to breathe

That's the nice way of saying she drowned in her own blood.

"These young kids — 14, 15 years old — routinely carry firearms and this is what happens when you got young delinquents that carry guns," Gualtieri said. "They get upset, they don't know how to handle stuff, and they end up shooting each other."

Just FYI, this is not limited to children. There's plenty of adults who have zero idea on how to handle stress without flashing a piece. I've seen about six different people use that as a method of indicating I'm getting over in your lane on my way into work pre-pandemic.

And before anyone just indicate "Oh but they're in the White House". Let's not forget Melania Trump's perspective on Christmas at the White House in 2020.

Who gives a fuck about Christmas stuff and decoration? But I have to do it!

Also something Trump pointed out in the speech.

Afghanistan Surrender

Buddy Trump, you ordered the troops out of there. I mean it was "so bold™" that FoxNews was liberally sucking what can only be scientifically classified as Trump's penis. Biden was just following up with the order that you gave. WTF LOL?!

Most of the ads I've seen appear to be targeted at conservative Americans, as they're all latching onto a mistrust in U.S. President Biden and the federal government

LUL. Well at least they know their mark.

中華人民共和國政府僱員 A: 您认为我们应该针对谁？

中華人民共和國政府僱員 B: 那些买马膏来治病的人怎么样？

中華人民共和國政府僱員 A: 木瓦哈哈哈!!

Because it’s never the perpetrators that suffer. No child is born blind or brain damaged by rubella by a choice they made. They are born that way because of a choice that was made for them.

And those that perpetuate this unto children, when they suffer the consequences for their choices they fail to attribute it to their own misgivings. Instead they absolve their misgivings as the function of some deity who wishes to test their resolve. That this affliction is not of their own making but of some twisted logic test of faith.

No, this does not rid the world of those who would harm but it with absolute certainty harms those who were never given a choice otherwise.

Despite having his laptop confiscated, Kurtaj, carried out his cyber attack using an Amazon Firestick, his hotel television and a mobile phone. He broke into the company’s internal Slack messaging system to declare: “If Rockstar does not contact me on Telegram within 24 hours I will start releasing the source code.”

I just read some dumb fucking shit from the Wayfair CEO telling everyone they need to blend their personal and work life together because no one is rewarded for laziness, or some shit.

Bitch! This kid right here is a fucking genius and y'all locking him up for life because his intelligence hurts somebody's bottom line. That's the key take away here. Y'all don't want actually smart and inventive people, you want slaves.

This kid just MacGyvered the shit out of a triple-A game studio and absolute best we could do is lock him up for life? Ridiculous. This whole capitalism shit is a fraud.

What's getting yanked is that older phones won't connect to Android Auto enabled vehicles if the phone is running Android Nougat. It must be Running Android Oreo or later.

For those not remembering, Nougat was released in 2016 and went out of support in 2019. By the most recent metric (Dec. 2022) about 4% of all Android devices currently run Nougat. So this will affect all fifteen of the people still running this OS.

Most devices that were originally sold with Nougat have an upgrade path to Oreo. The bigger problem is folks who purchased devices with Marshmallow (orig. 2015) or Lollipop (orig. 2014) who stopped receiving upgrades past Nougat. These are the devices that will most likely be impacted by this change.

Personally, I like to keep my devices for at least five years, so them deprecating 2016 and earlier is okay with me.

I wish there was like a way to just have a 1-to-1 voice conversation with someone on my phone and it be universally supported across all phones.