wasted_intel

4 ms·

1.
by wasted_intel 6mo ago
That comparison is made on the project homepage: "Not a security mechanism. No mount isolation, no PID namespace, no credential separation. Linux documents it as not intended for sandboxing."
2.
by wasted_intel 9mo ago
First thing I thought of, too. If not, I hope it’s planned. I’m all in on TUI tools, and vi keybinds are a necessary part of that for me.
3.
by wasted_intel 11mo ago
Validity | https://www.validity.com/ | Boston - Remote (US) | Full-time Validity is a suite of marketing tools used to ensure data quality, drive email performance, and provide advanced campaign analytics to leading brands.
4.
Original Prusa Core One 3D printer review(techradar.com)
3 points by wasted_intel 2y ago|0 comments
5.
by wasted_intel 2y ago
Love this. I use raw CLI commands until it hurts, and have recently embraced tools like lazygit/lazydocker to get visibility into otherwise opaque system/tree states, and it’s been a huge level-up. I have several user and system l
6.
by wasted_intel 2y ago
Your comment about writing a text editor library is precisely what got me started with amp ~10 years ago, where much of its core functionality was extracted here: https://crates.io/crates/scribe Good luck with the proj
7.
by wasted_intel 2y ago
I also think NixOS is more targeted towards developers. It’s one thing to learn the syntax, APIs, and abstractions of Nix/NixOS. It’s another to stack all of that on top of learning programming in general.
8.
by wasted_intel 2y ago
This doesn't mirror my experience at all. I think the biggest challenge facing NixOS is the learning curve. There's a lot thrown at you from the start, and as you start to factor your configuration into separate modules, there&#x2
9.
Arch is a gateway drug to NixOS(wastedintel.ca)
31 points by wasted_intel 2y ago|13 comments
10.
by wasted_intel 2y ago
Oh, Arch was rock solid and I was also able to keep my install going for years. However, in the few instances where I would get a new laptop or experience a drive failure, it was non-trivial to get it going again. If you're using a sto
11.
by wasted_intel 2y ago
Yep, same. Thoroughly enjoyed Arch, but slowly accruing implicit config state means you'll eventually have to re-install and configure everything again. You can mitigate some of that with dotfiles and some hand-rolled scripts, but NixO
12.
by wasted_intel 2y ago
I get the point you're making, but I'd argue that even when stated in a reductive fashion, the complex system that leads simple cellular automata to artistic expression is orders of magnitude more elegant and special than AI.
13.
by wasted_intel 3y ago
Exercising “rights and freedoms” isn’t what the people in that protest were doing. Breaking that up was the right thing to do.
14.
by wasted_intel 3y ago
> which are OSS-compliant where required This is the crux of the problem. Where Prusa is openly sharing, you have companies that are benefiting from that without reciprocating. Part of the tax you're paying when buying an i3MK4 is t
15.
by wasted_intel 5y ago
Litmus | Remote (USA, UK) | Full-time | https://litmus.engineering Litmus' goal is to help email marketing teams send better email. To do that, we've built a suite of tools to help with the building process, allow perf
16.
by wasted_intel 5y ago
Litmus | Remote (USA, UK) | Full time | https://litmus.com Litmus' goal is to help email marketing teams send better email. To do that, we've built a suite of tools to help with the building process, allow performing Q
17.
by wasted_intel 6y ago
> it is not easy for people who just can't be bothered to take the time to make anything correctly Laziness may make the problem more likely , but even a disciplined team working on security-critical software can make mistakes[0].
18.
by wasted_intel 6y ago
Litmus | https://litmus.com | Boston | Full-Time | REMOTE Litmus is building a platform to help email marketers, agencies, and companies send better email. We write and maintain tools that cater to the email design process, like
19.
by wasted_intel 7y ago
I had the same experience with the Globe and Mail in Canada. You get ads regardless of whether or not you're a paying subscriber, and while you can sign up online, you can't cancel. It was a total pain in the ass to do that over t
20.
by wasted_intel 8y ago
Thanks for the head's up; much appreciated!
21.
by wasted_intel 8y ago
> If you use it on multiple windows, doing `scratchpad show` multiple times causes one window to appear, then disappear, then next window appear, then disappear... and it does this across workspaces. You need to create a keybinding that
22.
by wasted_intel 8y ago
Try nmcli to get rid of your nm-applet dependency. ;)
23.
by wasted_intel 8y ago
I'd love to switch, but we use Zoom at work and screen sharing in Wayland was unsupported, last I checked.
24.
by wasted_intel 8y ago
i3's "scratchpad" alone is worth switching. You can show/hide a floating window on any workspace with a single hotkey. I use Chrome's app mode to launch dedicated windows for frequently used sites (Calendar, Slack,
25.
by wasted_intel 8y ago
Funny, I have an XPS13 (9370) and I love the aesthetic; the carbon fiber and metal look/feel is really nice. It's light, works well, and is quiet. The keyboard leaving imprints on the display is no different from my 2013 MBP, wh
26.
by wasted_intel 8y ago
While I agree that knowledge of what's below those abstractions is important, you also need to cater to your audience. Getting something working on the screen in front of you is exciting for new folks; lining up little victories with i
27.
by wasted_intel 8y ago
Well said. I switched to an XPS-based Arch build for many of these reasons. I think computers are generally too complicated for lay users. People tolerated the quirks because there was no alternative. Even on a Mac, which wouldn't suff
28.
by wasted_intel 8y ago
For vanilla references (&), Rust will prevent you from having multiple mutable references. Beyond that, there are several types in the stdlib[0] that progressively increase flexibility, but always safely. I think it's bad advice
29.
by wasted_intel 8y ago
Rust 2018's non-lexical lifetimes are a good example of this.
30.
by wasted_intel 8y ago
> well, try to avoid doing that I think that's pretty terrible advice for something that affects memory safety, and it invalidates your entire "the compiler will warn you" argument. There's a reason Rust has ownership

More ›