![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
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 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.
Still working on an assertions library that I started a few weeks ago. I finally managed to get async assertions working:
expect!(foo(), when_ready, all, not, to_equal(0)).await;
It also captures values passed down the assertion chain and reports them on failure (without requiring all types to implement Debug
since it uses autoref specialization).
Hopefully it’ll be ready for a release soon.
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.
Reminds me of a card game my brother taught me once. I managed to take two games off him after dozens. He was using me to test some decks he was deciding between taking to a world championship, that he won 4th in. It’s technically possible to win a game, but there’s practically a 0% chance I’d have won a match.
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.
Looks like the article requires an account. Is there an archived version?
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.
Does the bill explicitly state “AI deepfakes”, or is it all deepfakes? Where does the AI part come in (outside of some generative AIs being able to help make them)?
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.
GN’s charts usually compare against a few gens of somewhat comparable products, so I wouldn’t be surprised to see a 12th gen CPU or two on the charts. I’d also expect to see some 7000 series Ryzen chips and maybe a 5000 series one. I believe they normally include these older gens for people who skipped a gen or two to see what they’d get out of an upgrade.
I think accessibility is widely misunderstood. The way I view it, it’s not only about giving people who need them more ways to access something, but also giving people who want/prefer them those methods as well.
One example of this is wheelchair ramps. Building the ramps benefits those who need them by giving those people a way to go up/down an incline, but many people use the ramps. The ramps are also for those who would prefer to avoid the stairs.
Digital tools are another example of this, and a great one. Keyboard accessibility is a must for people with visual impairments, but also a preference for many who prefer not to move their hand to the mouse constantly. Keyboard-accessible tools are almost always a better experience to all users as a result.
Not building for accessibility is honestly just lazy. It shows that you don’t care about your customers, and you don’t want them to have a good experience. At best, you want to force your experience on them and only your experience is allowed (my biggest gripe with Apple products honestly).
As for digital art, I’ve seen a lot of what you mentioned, and I think it’s honestly been going on for centuries at this point. It’s problematic, especially because not everyone wants to create art in the One True Manner™ and may want to experiment with new ways to create art, or may want the art as a part of a larger project and don’t really care about the means (as long as it’s ethical).