mst

52 ms·

691.
by mst 3y ago
One would anticipate the people who've already owned snap together molecule sets for years have either already figured out a good way to make sure a bin of parts stays where it's put or accepted that it's their fate to order
692.
by mst 3y ago
You can run the underlying single static binary as a service any non-docker way you like. Your applications would be talking to it over a socket using a known and documented protocol so the implementation language isn't something the c
693.
by mst 3y ago
I tend to clone things I'm just having a quick look around in into ~/tmp - sometimes I'm intending to spelunk through the history so I don't fancy having that much data sat on a tmpfs and "running rm -rf ~/tmp&
694.
by mst 3y ago
Far too late to edit now but I'd note that Future::AsyncAwait is implemented using only public APIs - it adds the keywords using the pluggable keyword API that was added in 5.14 and 5.16 (though while code written against the 5.14 vers
695.
by mst 3y ago
And as multiple previous sequences of events have made clear, attempting to apply obnoxious monetisation strategies to a Sun-inherited project with a substantial userbase tends to mostly be a really good way to get it forked out from under
696.
by mst 3y ago
The usual term for that is 'source available.' 'Open source' generally gets read to mean 'available under an OSI or OSI-like license', and 'free software' as 'available under the GPL or a GPL-lik
697.
by mst 3y ago
I've seen molecular chemists and biologists (and even for a weird set of 3d shapes mathematicians) experiment with physical stuff before transferring the ideas elsewhere - the tactile aspect and the ability to intuitively rotate a 3d s
698.
by mst 3y ago
fatpacking bolts the source code untouched onto the front in a way that leaves you a single readable pure perl file - and is limited to pure perl modules as a deliberate decision to keep things simple and clear even if you've never enc
699.
by mst 3y ago
I tend to use it consistently to mean "the thing on the left hand side of this is a name", where in this case it's the name of a program. The commonest case is absolutely the name of a hash key, but it's well worth learn
700.
by mst 3y ago
perlbrew install 5.38.0 -Dushrplib cd ~/wdir/my-new-project; git init; plx --init 5.38.0 <3
701.
by mst 3y ago
The original perl7 plan never got past the RFC stage for multiple reasons. The current intent is to get things like the new class syntax (plus a number of other features, the exact list of which escapes me right now) shaken out and stabilis
702.
by mst 3y ago
> It has no concurrency primitives that are anywhere close to other popular languages I can switch between writing async/await based $other_language and use Mojo::Base -signatures, -async_await; for my p3rl.org/Mojolicio
703.
by mst 3y ago
Ruby is very cool as an easier, shinier, more ergonomic and elegant Perl but the lack of block-based lexical scoping with compile time checking (use strict + my, duplicated as "use strict" and let in ES6, much to my happiness when
704.
by mst 3y ago
Ovid led the specification effort and did all the boring writing it up stuff because he wanted it to exist, Stevan Little (author of Moose) originated the idea but got distracted by real life before he got it finished, a bunch of us (includ
705.
by mst 3y ago
Roughly, because (a) performance (b) the intention to makie it still possible to poke into an object's guts but more obvious that's what you're doing (c) if you really want the class syntax atop a classic blessed reference, p
706.
by mst 3y ago
> and/or not being allowed to use non-core dependencies And at least p3rl.org/Moo works with p3rl.org/App::FatPacker because I designed them to play nice with each other. I once fatpacked an http://p3rl.org&#x2F
707.
by mst 3y ago
Writing bless() yourself has only ever been advisable for low level code or as an optimisation for a couple of decades and most professional perl programmers are well aware of that. Generally you'd use one of the M* systems - p3rl.org&
708.
by mst 3y ago
use IPC::System::Simple qw(capture); my $md5sum = capture(md5sum => $fname); (discovering this exists is the tricky part, of course, but once you know it exists it works nicely)
709.
by mst 3y ago
Taint mode is something I've never got along with, but for running external programs p3rl.org/IPC::System::Simple lets you make all the shell injection risks go away (and can be used in a script destined for p3rl.org/App::Fat
710.
by mst 3y ago
Context is something you have to learn to be careful with but used judiciously is often quite neat. Sigils are great once you realise they're conjugation, i.e. $ -> the, @ -> these, % -> the pairs of, hence $foo # the valu
711.
by mst 3y ago
ingy is batshit insane (and great fun to collaborate and/or drink with) but even he didn't expect text templated turing complete YAML to happen. helm does still (last I checked) allow you to use your own transform script rather th
712.
by mst 3y ago
I've seen some slim running JVM stuff by developers who actually bothered to care about it - under 25Mb slim. Yes, lots of Java apps basically go "lol .... KABOOM " if you give them less than half a gig of RAM to play around
713.
by mst 3y ago
Historically they've generally politely ignored community rebuilders and got a trifle enervated by commercial rebuilders - they changed how they handled distributing kernel code (to a fully patched tree rather than a pristine tree and
714.
by mst 3y ago
> Red Hat is like the 10,000 pound gorilla in the world of Enterprise Linux, and traditionally has walked a fine line (well, mind you) I'm not particularly fond of this latest move but I'm unconvinced they've fallen off th
715.
by mst 3y ago
> If, instead of a SRPM, you have some small, declarative text file which gives upstream URLs, SHA256 digests and build config steps That plus a stack of patches is what FreeBSD ports and other ports-like systems use instead. (I'm a
716.
by mst 3y ago
The last time I recall a company doing the 'we will follow our GPL obligations and give you - specifically you, the recipients of the binaries from us - the source but if you exercise your right to redistribute don't expect to be
717.
by mst 3y ago
I believe that currently RH send a patch to the upstream project, then apply/backport it to CentOS Stream, then if they consider it appropriate apply/backport that to RHEL, and it's the first step there being their first step
718.
by mst 3y ago
Could equally be a move to minimise how much of the discussion that springs up around this blog post gets derailed and eaten alive by arguments and/or misunderstandings around said distinction. Though I suspect we'll both end up l
719.
by mst 3y ago
The users in question don't want a clone of CentOS Stream, though, they want a replacement for classic CentOS. Just like users who're choose to run Debian Stable want Debian Stable, not the somewhat stabilised rebuild of a snapsho
720.
by mst 3y ago
"Approximately the same lag as you used to get with CentOS" would seem pretty fair to me - I'm aware people grumbled about it and understandably so, but it was still a relatively stable and relatively co-operative situation.

More ›