caditinpiscinam (u/caditinpiscinam)

caditinpiscinam commented on Live facial recognition cameras may become 'commonplace' as police use soars theguardian.com/technolog... · Posted by u/c-oreills

caditinpiscinam · 7 months ago

Cities are banning face coverings too.

https://www.inquirer.com/news/philadelphia-ski-mask-ban-bala...

At this rate they should just make everyone wear a big QR code containing our names and social security numbers on our shirts. A sort of license plate for people. Would save on processing power at least.

caditinpiscinam commented on Design for 3D-Printing blog.rahix.de/design-for-... · Posted by u/q3k

lawn · 8 months ago

What an impressive looking article (I've only skimmed it so far).

I've been meaning to try my hand at CAD and designing models to print but I haven't quite made the jump.

One thing that has given me pause is a good CAD program for Linux, does anyone has any good tips for a complete Newbie where to begin?

caditinpiscinam · 8 months ago

As a fellow linux users and 3D printing newbie:

- Tinkercad (browser) fun and great for very simple projects. Like the MS Paint of 3D.

- OnShape (browser) seemingly pretty powerful, but not the easiest to learn in my experience, and has some annoying bugs.

- Plasticity (desktop) I played around with the free trial and liked it a lot, found it more intuitive than OnShape.

- Womp (browser) not CAD software, but easy to use and great for making free-form/organic looking designs.

- Blender (desktop) not CAD software and haven't used it myself, but I've seen others use it to design 3D prints.

caditinpiscinam commented on Ruby methods are colorless jpcamara.com/2024/07/15/r... · Posted by u/pmontra

vlucas · a year ago

Long-time JS/TS/Node programmer here.

Knowing ahead of time which functions are async is a feature.

It's a big neon sign that says "hey, this function call is expensive". This is a good thing for programmers to easily see and know at the call site.

If you make multiple calls with async/await in a row, the performance issues are plainly obvious at the call site. With "colorless" functions, this information is hidden in a deeper layer. You have to know what the function does on the inside to even know what its performance impacts are.

Also, a nitpick - you can call async functions from sync ones, you just can't access the return value. Sometimes, you don't need to.

caditinpiscinam · a year ago

If explicitly marking expensive IO operations using async is a feature, then why don't languages with async make their "print" functions asynchronous?

caditinpiscinam commented on Alphabet to invest another $5B into Waymo techcrunch.com/2024/07/23... · Posted by u/chrixf

adventured · a year ago

Those reasons are similar to why Americans aggressively dislike public transportation. A single digit percentage of experiences are horrible (or worse).

Trapped in a small space with sometimes psychotic, violent, smelly, modestly insane people. Somehow the proponents of public transport haven't figured out that's undesirable. It's not at all remotely worth the risks, unless you have no other good options.

caditinpiscinam · a year ago

I've faced way more danger and discomfort from crazy drivers on the road than crazy people on a bus.

caditinpiscinam commented on Cow Magnets stanfordmagnets.com/cow-m... · Posted by u/Tomte

saagarjha · 2 years ago

By eating them you shorten the length of time they stay miserable.

caditinpiscinam · 2 years ago

"a most delicious, nourishing, and wholesome food"

caditinpiscinam commented on Some notes on Firefox’s media autoplay settings in practice as of Firefox 124 utcc.utoronto.ca/~cks/spa... · Posted by u/ingve

pier25 · 2 years ago

> This seems like a more realistic solution

It's completely unrealistic to break a major browser API.

caditinpiscinam · 2 years ago

How many web apps from 15 years ago still work? Flash, Java applets, browser specific hacks, fingerprinting, cross-origin shenanigans... all locked down or eliminated. The internet evolves by breaking APIs.

caditinpiscinam commented on Some notes on Firefox’s media autoplay settings in practice as of Firefox 124 utcc.utoronto.ca/~cks/spa... · Posted by u/ingve

pier25 · 2 years ago

Wouldn't it make more sense to just stop using apps like ESPN instead of breaking a major browser API and big chunk of the internet?

caditinpiscinam · 2 years ago

The key to what I'm envisioning is that it wouldn't break a site like ESPN entirely -- it would just break the SPA behavior by making links behave like links. The end result is that the site would be more usable, not less.

For sites where SPA behavior is necessary (like Spotify), opting in could be done with a one-time browser prompt, like how location access and DRM playback are handled.

This seems like a more realistic solution than just avoiding these sites altogether, for the same reason that people use ad blockers instead of just shunning sites with ads.

caditinpiscinam commented on Some notes on Firefox’s media autoplay settings in practice as of Firefox 124 utcc.utoronto.ca/~cks/spa... · Posted by u/ingve

akira2501 · 2 years ago

> where click handlers for <a> elements

None of our SPAs use <a> elements for clickable navigation. In fact, most of them attach a click listener to the root element, then let the individual clicks bubble up to there. We use data parameters on the individual elements, and if the click handler sees one of those, then it activates the history state/navigation.

In terms of autoplay, a trick we have to play for iOS is, when you click on something we play a 0.25 second silent MP3 through the audio element. Once that's done, it's "active" and we can use it to play audio.

It's a radio "boombox" type application, so this feature is expected by our users to keep audio playing when they navigate to different features within the player.

caditinpiscinam · 2 years ago

That makes sense for an audio-player application -- something like Spotify where the user expects playback to continue when navigating pages. Even so, I rely on the fact that Spotify links are actual links, so that I can open multiple tabs when I need to, for example when putting together a complicated playlist. Have you considered keeping <a> links as a fallback to support this sort of use-case?

caditinpiscinam commented on Some notes on Firefox’s media autoplay settings in practice as of Firefox 124 utcc.utoronto.ca/~cks/spa... · Posted by u/ingve

Spivak · 2 years ago

So SPAs would stop using a elements, style buttons like links, and attach handlers to those. I don't think you'll be able to accomplish what you want.

caditinpiscinam · 2 years ago

They could get rid of links, but that would break search engine indexing. This wouldn't be an issue for legitimate SPAs like Gmail, but would be disastrous for content-based sites. More likely is that they'd keep <a> elements but hide them from the user.

Either way, my proposal would make sites that eliminated or hid <a> elements stop working by default, which would disincentivize hostile UX practices.

caditinpiscinam commented on Some notes on Firefox’s media autoplay settings in practice as of Firefox 124 utcc.utoronto.ca/~cks/spa... · Posted by u/ingve

pier25 · 2 years ago

Why would you want to break SPAs?

caditinpiscinam · 2 years ago

Because most SPAs that I interact with (like ESPN) have no business being SPAs (in the sense of hijacking navigation). The main motivation behind constructing them that way seems to be to circumvent UX safeguards.