Static_Rocket @ Static_Rocket @lemmy.world

Posts

0

Comments

251

Joined

2 yr. ago

TFIDF and some light rules should work well and be significantly faster.

Ah, my last phone that no longer receives any updates. Pixel 2XL. Just keeping it around because parting with electronics is difficult.

Arch on every box in the house, including the primary router. Mixed Intel and AMD. Openwrt on every AP (unfortunately Mellanox and MediaTek firmware blobs for the radios). GrapheneOS on my daily and LineageOS on my legacy phone.

Aside from occasional games, I don't install anything I don't have the source to. My phone is the only exception, for apps required to interface with the rest of the world.

Yo, they added full page copies now? Gotta give it a spin again

Something like this can kind of be achieved programmatically by unraveling bash completion arguments and loosely parsing terminal help strings.

They aren't all formatted uniformly though, so you'll need to come up with a filtering mechanism to prevent returning garbage. You'll also always be a little out of date...

Everything loops back to steam in the end. Solid state thermoelectric devices have been around forever, and before that we had the idea of using thermal energy to augment magnetic fields and jump to kinetic energy without any intermediary conversion. All very low yield results, but we've tried it anyway.

Keep thinking about it, we need all the brains we can get, but don't write it off as a novel idea that the other egg heads just haven't gotten around to solving yet.

Data centers will probably be the only practical application. Consumer electronics will probably barely produce enough energy to power the regulator and tie-in circuit just to feed back into the pwm driver for fans nowadays.

I agree that you're not really leveraging any features of PNG like you would using JPEG or RAW here, but saying it's not meant for this use is an odd way to phrase it. There's nothing inherently wrong with wanting lossless compression on an image...

Some internet funeral aesthetics

Thunderbird, k-9, and aerc

Out of box experience is a personal preference. It always has been. Every person expects something different so I don't really care about it anymore.

It's dead now, but Apricity was the first distro I really enjoyed the look of. Now I know better than to care about out of box appearance.

Lol, changing the country of origin doesn't constitute innovation from a consumer standpoint...

Now if this was using 5nm or chiplit or any of the other buzzwords of the day it could be marketed as innovative in the modern sense of the word.

Realistically there is no innovation left for ARM platforms. They all use the same core schematics. They only control data flow and peripheral IP as a manufacturer, unless they feel like building their own core from the spec (nobody really does that anymore as ARM has been desperately trying to standardize everything). The most "innovation" I've seen has come from stubbornness around keeping legacy bus architecture around instead of adopting AXI (even when all the IP they are trying to use already uses AXI and they keep having to make translation hardware).

Fuck it. Gun it at the brick wall. Jerry's rigging up an emergency break as we speak. Don't mind that the last piece to said break may be missing.

Man who will probably die before we hit the wall

Bash, just because everything else already uses it. That and bashisms have infected nearly all of my scripts as I clumsily bump into the limitations of POSIX string manipulation.

I have found some very fun things with sed branching patterns as a result of these limitations though...

https://www.gnu.org/software/sed/manual/html_node/Branching-and-flow-control.html

That's my first thought, but my brain keeps trying to inject one immediately following "Surely." No idea why.

I feel like there needs to be a comma somewhere in that sentence but I don't know why...

Unfortunately this doesn't seem to apply to publishers or developers that don't have a landing page

I was working at a company at one point that got a contract to build something I viewed equivalent to malware. Immediately I brought it up to several higher-ups that this was not something I was willing to do. One of them brought up the argument "If we don't do it someone else will."

This mentality scares the shit out of me, but it explains a lot of horrible things in the industry.

Believing in that mentality is worse than the reality of the situation. At least if you say no there's a chance it doesn't happen or it gets passed to someone worse than you. If you say yes then not only are you complicit, you are actively enforcing that gloomy mentality for other engineers. Just say no.

Well, assuming you meant type specifier, at least not before C99. After that it is required. C23 explicitly states that a type specifier is required for all declarations.

If you actually meant type qualifier, then no. That was never required.