It has atrocious error handling, and there’s no reasons why arrays should only be 1D.
- 0 Posts
- 27 Comments
Since you mentioned LocalSend: https://syncthing.net/. It’s a way to sync files between devices. And since I bring my phone wherever I go, that means it works seamlessly for me.
All you said also applies to Linux!
flying_sheep@lemmy.mlto Linux@lemmy.ml•GNOME 49 Alpha Released With X11 Support Disabled By Default, Many New Features1·2 months agoWhen Ubuntu LTS stops shipping X11 in 2032, that’ll hopefully have changed
Aw, didn’t know that! Maybe make an issue? Yakuake works under Wayland, so there’s nothing that should stop them
Yes, it calls that its “quick terminal” feature
flying_sheep@lemmy.mlto Linux@lemmy.ml•KDE's New Distro: Btrfs-Based, Immutable Linux OS, with Flatpak and Snap9·11 months agoOoo damn that sounds exactly what I’d like to try.
On the other hand I feel like I’m too old for this shit. My system works fine, I understand everything, and things rarely break and never in an unrecoverable way.
It’s been great almost since I started using it.
I started using it exactly when 4.0 came out, because that’s when I started using Linux and I thought learning 3 didn’t make sense. But 4 only got stable around 4.4 I think. The problem was that 4.0 wasn’t intended to be for end users yet, but distributions didn’t realize that and packaged it right away.
KDE didn’t repeat that mistake. 5.0 was almost completely smooth sailing (some applications took a long time to port and looked ugly, that’s it), and 6.0 was completely seamless.
If I had to guess, probably variable refresh rate
flying_sheep@lemmy.mlto Linux@lemmy.ml•Your Most Frustrating Configuration Experience?6·11 months agoHuh, I found it to be so much easier to set up than nginx that I wrote the devs a little thank you message
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!
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!
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.
flying_sheep@lemmy.mlto Programmer Humor@lemmy.ml•Popular Programming Book "Clean Code" is being rewritten4·1 year agoHuh, 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.:
- if there is a problem, you can more easily narrow down where it is (e.g. if part2 calculates as expected and part1 doesn’t, the problem is probably in function1, not function2 or function3). If you have to understand the whole do_stuff before you can effectively debug it, you waste time.
- if the function needs to be optimized, you know immediately that function1 and function 2 can probably run in parallel, and even if you don’t want to do that, the slow part will show up in a flame graph.
Finally! Nushell is awesome. The infrequent deprecations are a bit annoying, but I prefer them to having a bad program go 1.0