The only thing I liked was arch’s pretty boot sequence … which I stared at for a while because SysV init was so slow.
The only thing I liked was arch’s pretty boot sequence … which I stared at for a while because SysV init was so slow.
systemd, not SystemD, or system d.
But yeah, wonderful talk!
Because they just have their own brain chemistry as the basis of it whereas the above comment clearly states:
Rust has proven empirically that the tradeoff between performance and safety doesn’t need to exist.
Which is truth. And it’s much easier to base a coherent argument on truth rather than vibes.
Weird how he’s helping the far right in both cases.
Python is just glorified shell scripting
Absolutely not, python is an actual programming language with sane error handling and arbitrarily nestable data structures.
I don’t like the indentation crap
Don’t be so superficial. When learning something, go with the flow and try to work with the design choices, not against them.
Python simply writes a bit differently: you do e.g. more function definitions and list comprehensions.
Not only is there a UInt8Array, there’s also a bunch of others: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray#typedarray_objects
Once git no longer depends on it, it’ll be gone from my system
Nah, gross. You need to set a bunch of global options to get sane behavior on errors.
Nushell is shaping up really really nicely, and it’ll actually stop executing if something fails! Even if that happens in a pipe! And it’s not super eager to convert between arrays and strings if you use the wrong cryptic rune.
Huh, I really like code like that. Having a multi-step process split up into sections like that is amazing to reason about actual dependencies of the individual sections. Granted, that only applies if the individual steps are kinda independently meaningful
To adapt your example to what I mean:
Baz do_stuff(int count, boolean cond) {
Foo part1 = function1(count);
Bar part2 = function2(cond);
return function3(part1, part2);
}
This allows you to immediately see that part1 and part2 are independently calculated, and what goes into calculating them.
There are several benefits, e.g.:
dbg!()
for Rust users
He works on Linux where he controls the whole stack down to the metal and I love that for him, but other people have to call library code, and them debug that if it doesn’t work as they thought it would.
You can theme plasma and turn the effects off. Why isn’t that exactly what you want?
You’re right, of you have compete freedom, do that. If the place you want or need to go to is most comfortably reachable via rattlesnake road, bring boots.
In other words, if you don’t think the wasm landscape is mature enough to build a web thing with it, you are stuck with JavaScript, but you don’t have to rawdog it. I haven’t run in a single weird thing like this in years of writing typescript with the help of its type system, ESLint and a formatter.
Just use a formatter. It’ll show you that the second one is two statements:
{}
(the empty block)+[]
coerce an empty array to a number: new Number(new Array())
I haven’t read anything this cursed in a while
I usually write “POSIXy shell” but I thought that was clear from context this time.
The problem is that exit statuses !=0 aren’t treated as error by default (with a way to turn that off for individual expressions). Instead you have to set multiple settings and avoid certain constructs in bash/ZSH/…
Everything that works like a modern programming language by default is fine of course
Yeah, and that’s just one of many many things to consider.
As a long time former ZSH user, I’ll definitely include ZSH in shell languages to avoid for scripting.
The problem is simply the number of rules and incantations to slavishly include everywhere to make your script bail on error. set -e
is not enough by far.
Python with plumbum or nushell are definitely better.
That’s just completely wrong. Just try e.g. replacing the journald backend with the old text based syslog, and not only will you discover that is possible (which directly contradicts what you just said), it’s also easy!