TehPers

Biden gets a rousing tribute from Democrats as he passes

I knew he was sick, but holy crap.

the torch to Harris in 2024 DNC speech

Oh, phew

I’m not sure I see the issue. Is there something wrong with them reporting on Ukraine’s Kursk region? Doesn’t seem like an illegal border crossing to me.

Two can play at this game.

Their GPUs are already bricks. Just throw the GPUs.

Hey look, the classic “America bad” comment on a post critical of China!

Are these people bots or something? It’s possible to be critical of both at different times.

I think it’s good to document why things are done, but extracting things out into another function is just documenting what is being done with extra steps. This also comes with a number of problems:

1. Not all languages are readable. Documenting what is being done is important in some C, or when working with some libraries that have confusing usage syntax.
2. Not all people reading the code know the language or libraries well. Those people need guidance to understand what the code is trying to do. Function names can of course do this, but…
3. Not all types can be named in all languages. Some languages have a concept of “opaque types”, which explicitly have no name. If parameter and return types must be specified in that language, working around that restriction may result in unnecessarily complicated code.
4. Longer files (the result of having dozens of single-use functions) are less readable. Related logic is now detached into pointers that go all over the file all because of an allergic reaction to code comments, where a simple // or # would have made the code just as readable.
5. Function names can be just as outdated as code comments. Both require upkeep. Speaking from personal experience, I’ve seen some truly misleading/incorrect function names.

If those functions are huge units of work or pretty complex, I can agree. For most cases though, a simple code comment should do to explain what’s going on?

While impressive, a minifier can bring it down to 1 line of JS! I do like that this can function as a reference for making simple canvas-based games though.

While I agree, it makes connecting to localhost as easy as http://0:8080/ (for port 8080, but omit for port 80).

I worry that changing this will cause more CVEs like the octal IP addresses incident.

Edit: looks like it’s only being blocked for outgoing requests from websites, which seems like it’ll have a much more reasonable impact.

Edit 2: skimming through these PRs, at least for WebKit, I don’t see tests for shorthand IPs like 0 (and no Apple device to test with). What are the chances they missed those…?

What’s wrong with putting tampons in the men’s restrooms at schools? Won’t they come in handy if there is a shooting?

Anyway, this reads to me like free advertising for Walz.

(Disclaimer: do not try to use a tampon to patch a bullet wound)

Imagine how different the story would be if they compensated people for this data. “10% off Geforce NOW if you let us use your gameplay footage as training data!” (for example)

This is obviously cheaper and there’s way more data to train with, but it just continues to skirt a line in copyright law that desperately needs to be tested.

Honestly, regardless of what happens to Intel, I’m hopeful for Qualcomm providing a real alternative in the CPU space, especially an alternative as meaningfully different as using an entirely different instruction set. More diversity between competing products in the space can only be a good thing since it gives consumers more meaningful choices to make when deciding between products.

People talk at the urinal?

People on Chrome adding Reddit to their Google searches already use Google. People not using Google who don’t search “Reddit” are going to see fewer Reddit results.

No, this won’t kill Reddit, but it certainly isn’t helping them get more traffic.

Joke’s on Reddit. I’ve been blocking their results in the search engine I use for months!

I wonder if this will end up being pursued as an antitrust case. If anything, it’ll reduce traffic to Reddit from non-Google users, so hopefully that kills them off just a little faster.

If Biden wants the immunity amendment to pass, he needs to show people what the decision means, guns blazing (okay maybe not that extreme). Otherwise, these would never pass. They make too much sense.

I also avoid query syntax generally because I find it hard to map to method syntax with more complex queries. It’s a cool concept though, despite it being painful to use.

For library code - yes, you’d usually want to direct users to the correct way of using the library, so you’d be more likely to come across fallible build functions or a bunch of type parameters to constrain when it can be called.

For applications - honestly, it’s your code, so do what makes sense to you. Using a build function can help you ensure your settings were fully configured before using them, but it’s up to you if that’s the direction that makes the most sense to you. One benefit is you only need to perform the check once, but the downside is having another “built” type that you need to keep in sync with the original type. You can also look at libraries like derive_builder if you want to have your builder generated for you to avoid needing to manually update two separate types.

C# also has a built-in query language (LINQ). I think it might just be simpler to group them together to avoid nuances like these, though I don’t think anyone would complain about not seeing LINQ on a query language list either.

I wonder how many people learned Lua for this reason (CC and friends).

Frozen bread is magical. Microwaving it for a short time is all it takes to go from frozen to perfect. It’s honestly amazing. No need to put the bread in the fridge at all - just freeze the whole loaf and defrost slices when you need them.