HN user
In Perl -> is the dereference operator, similar to C.
So when you see
$a->[2]{"bar"}
$a->[2]->{"bar"}
And that's why it is best to avoid GPU-acceleration unless you truly need it.
GPU drivers have always been full of bugs and will always be, since modern GPUs are ridiculously complex and designed for speed rather than reliability.
The standard flag package in Go also supports GNU style flags.
Good to know there are other solutions than Cloudflare to block those leeches.
I love Go's letter casing. It's such a neat way to remove cruft.
There are usage statistics of most IRC servers and channels on https://netsplit.de/networks/top10.php
Gloriously useless :)
It's an electron app, so I guess at least 1GB of RAM.
I love this article! It is not the first time I hear the bad reputation of aspartame is unfounded.
AFAIK, there was only one study which said aspartame was dangerous: they fed a rat with a HUGE amount of it (like way more than a human could consume, in proportion) and the rat got ill or died I don't remember. That "study" was obviously flawed yet the media kept talking about it everywhere.
At that point, it wouldn't surprise me if the sugar industry is behind this.
message to OP: you see? All you had to do is create some drama and now people are interested in you :)
Why indeed! Recent versions of GNU cat (and other coreutils) include those optimizations.
https://git.savannah.gnu.org/cgit/coreutils.git/tree/src/cat...
If you wanted to have 2 redundant hosts, you could use something like GlusterFS for the replication. I have only tested it with XFS, but apparently it supports ZFS now: https://gluster-documentations.readthedocs.io/en/latest/Admi...
On Linux with glibc, ldd -v will give you similar information, though less pretty of course.
No one cares how big it is.
A lot of people care, especially Linux users.
Disk space is still cheap on end users machines.
Not cheap for everyone.
Neither Flatpak nor Snap have increased memory usage because of containerization.
Yes it does, because you end up loading multiple versions of the shared libraries.
There is also the memory used by the flatpack/snap daemons. Snapd is quite big since it is written in Go.
Don't remove it. Please. I'm begging you ;_;
So what? Just because IPv6 does does not solve all the problems in networking it's trash and we should abandon it? No thanks. Where I live, ISPs are starting to share IPv4 addresses between several customers, which creates many problems.
And QUIC over IPv6 is still a lot better than QUIC over IPv4.
We simply put all the team's keys in an S3 bucket. Each server regularly syncs the bucket and updates the authorized_keys file.
Too bad the FCC does not think about space pollution. The astronomers were already very fed up with the Starlink constellation interfering with their observations, now they will have to deal with twice the number of satellites. Not to mention the risk of collision in space which keep going up.
This looks a lot like what France Press did in 2007: https://en.wikipedia.org/wiki/Google_News#EU_copyright_and_d...
This is fantastic news! I'm glad perl 5 is evolving again.
Oh. I was expecting someone to post the original APL paper here.
"the industry consensus is that 5G will double to triple energy consumption for mobile operators" - https://www.fiercewireless.com/tech/5g-base-stations-use-a-l...
Needless to say that ecologists see the 5G deployment as utter madness, especially since, in their view, 4G is good enough.
Nice to see we're going back to simple counters like in the 90s.
Any news about Firefox? Are they also impacted?
FYI, MongoDB now passes the Jespen test suite. It's just as safe as Postgres, while much easier to use.
It seems 90% of the emails are just newsletters (LeMonde, Korben, Google Alerts...). It would have been so easy to remove those!
For you :-)
docker-compose 1.11.0 will be released soon with support for secrets, probably using the same system.