sushisource

I agree with the overall point, but I don't agree that those who "came up from the bottom" are sort of magically imbued with this moral superiority that

> But the worker, who had to make hard tradeoffs, learn to serve and deal with having little, is naturally on a different level.

Implies. Take running for example. No one in modern society "needs" to run, but I took up endurance running and doing something like running a marathon teaches you a lot. Probably many of the same lessons you're imagining.

All that to say, growing up poor I'd agree is probably pretty likely to imbue you with those learnings. It doesn't mean that people who haven't experienced scarcity have never learned those lessons.

The standard tools have a lot of cruft. `grep` being case sensitive by default is I think a good example of a default that used to make sense, but is probably better the other way around today. There are countless other such examples.

Your comment reads as a no-true-scottsman "look how skilled I am" signaling device. You're not necessarily wrong, but you're also clearly fighting a pointless battle, and sound a bit out-of-touch.

Yes, the tools already exist and work. No, they do not need to be re-written, but the new versions are often substantially more usable and newcomers enjoy that. Such is the nature of life. Things change. Accept that and you'll be happier.

Your attitude might win some points with other fight-the-tide-till-my-last-dying-breath types, but it reads to me as "It is the children who are wrong!"

I worked with a guy who had the same attitude about always using kubectl over the gui because it was "faster". He was demonstrably slower at quite a few common tasks, like discovering errors in logs across many pods, than others who used the gui.

MRI isn't necessarily going to reveal reasons you'd have knee pain while running. For example, I know for a fact that if I don't routinely roll out my IT band, it gets too tight and that then results in pressure on the outer portion of the patella. It's rather unlikely that'd show up on an MRI, except perhaps for someone noticing "Hey, maybe your IT band is tight". Even then, probably not, since it tightens as I begin running.

So, there's probably something real going on, and something real you can do to fix it. Consistent stretching, rolling, and low-weight exercises to build strength in muscles like your hip abductors makes a world of difference.

If you're not doing those things, start there. Really do get a roller. The IT band cannot be stretched - since you can't exactly flex your femur.

Coke users might have been a more apt analogy given weed is increasingly legal around the world, but, yeah. Wooosh

I mean you're not wrong, but you could say the same thing about breathing or walking. They're complicated on some level, but we do them just fine.

To me this is really a point about just how good the interface of wheel/pedals is, that any moron off the street can be taught to drive in a matter of hours.

Overall I agree, and you write a good comment, but:

> And the reality is most driver, even those slightly below average are basically good drivers.

Made me laugh out loud. Not even necessarily because it isn't true (though I'd tend to disagree), but just because I'm the kind of person who constantly complains about shit drivers.

Thanks for the laugh, lol.

In my experience as demand has increased due to the pandemic, prices are reaching the point where I'm not willing to pay them, and I make good money like most people on this site.

If that's any indication of what's to come when they need to stop bleeding cash... not looking great.

No, I don't think it's pure conspiracy. Hence, "some truth". I do think that

> America's goal is not to protect Americans' privacy. It is to protect its own monopoly on violations of Americans' privacy.

Is a gross overstatement, though.

Indeed. It's something I rarely hear mentioned, but I have found valuable about recreational drugs - they teach you a lot about how your body works and what certain things feel like. A lot like tasting a spice in isolation allows you to pick it out in a complete dish.

Indeed. 2020 has never made https://en.wikipedia.org/wiki/Hanlon%27s_razor more relevant. People want to see conspiracies and patterns in everything. There's probably some truth to some of it, but I'd bet a lot of money most of it is just the result of people bumbling around and trying to cover their own asses.

What I find most hilarious about it is FAANG (certainly, Google in particular, since they researched this themselves and then chose to ignore their own research: https://www.wired.com/2015/04/hire-like-google/) knows whiteboard interviews are pretty bad, but they continue to use them.

I can only assume it's a means of filtering out absolutely trash candidates. FAANG also knows they are not hiring the best of the best. That's simply not possible when you're employing 10k+ developers. Some of them are going to be less than great. Your goal at that scale is just to avoid wasting a huge amount of money on a terrible hire, and whiteboarding is decent at filtering out complete trash, but the problem is we don't train people how to do whiteboard interviews properly, so they also filter out incredible developers who just aren't interesting in memorizing a bunch of algorithmic tricks they'd normally just look up, but would be perfectly capable of implementing whatever.

I think your last point is definitely valid. Best counterpoint I could make there is investing the time in linux is probably more widely valuable/applicable in terms of being able to apply it on the job.

I learned a bunch of linux stuff for fun, and it's helped me a lot in my job. I dunno if I could say the same about macOS.

The exact number really isn't the point. The point is if the terminal emulator is 1% of that 200ms (or 100, or whatever), then who gives a shit. You should be buying a better monitor first.

To some extent you're totally right. I can elaborate.

Some of it are technical choices Apple has made that make things hard. I like tiling window managers. The best (only?) one for OSX now requires you to go disable SIP to use it: https://github.com/koekeishiya/yabai/wiki/Disabling-System-I... -- this wouldn't be the case if Apple cared at all to support these sorts of use-cases, but they don't, so it suffers collateral damage from their attempts to improve security. (Again, totally reasonable business choice. Not a ton of people in this boat, but turns me off. Why can't I do this by clicking something in system prefs like when I open a downloaded app?)

Another one is, as a developer who once worked at a shop that shipped three-os software, their policies relating to macOS licensing are comical. It's almost like they don't want you to develop for Mac at all unless you're going to exclusively develop for Mac. We had moved everything to the cloud, but we still had a room full of stupid mac minis just to run our build farm. Ridiculous. The new news about mac minis in AWS is an ever-so-slight improvement.

Some of it is definitely the familiarity you describe. I don't want to have to get used to all the weird bsd-ish-but-not-really versions of the common CLI tools. I have no interest in learning apple script, etc. I'm being fairly obviously hypocritical because I was willing to learn a bunch about obscure config files on linux. But, my experience has often been that things I would be willing to invest to customize on macOS are simply not customizeable.

And, hey, perhaps I would've been willing to go through all that were it (reasonably) possible to run OSX on commodity hardware, but as a kid learning programming in the 90's macs were damn expensive compared to windows alternatives. So, I grew up on windows. It's still true. Today I could afford a Mac Pro, but it's a laughable value proposition (easily 3x-5x the cost for equivalent power) compared to building my own linux box (as to the 'your time is money!' counterargument people sometimes make here - it takes me about 2 hours to build a PC and my linux box hasn't panicked or booted improperly once). This used to make sense to me when the OS/hardware was more tightly integrated, but I don't really see how a macPro is any different than the equivalent PC you could build with the same CPU/GPU combos except more expensive and less flexible (admittedly, with a stunning case -- their manufacturing quality is incredible). Maybe they'll realize those benefits again with the M1, which is certainly cool.

Lastly, I'll never forgive them for starting the trend of eliminating 3.5mm jacks on phones.

TLDR; You're probably right. Macs aren't a great choice if you're a power user (read: control freak) with your PC.

It's truly moronic. I cannot imagine what the discussion was like in those meetings, but it sure seems like it fits the "guy gets thrown out of the window" meme format where you can imagine all the HBO streaming leaders sitting around the roundtable and one dude's like "What if we just had... one app?".

Boom. Out the window.

Sure, maybe I need to add "within reason". I agree I want my keystroke to appear reasonably quickly, let's say under 200ms to fit some of the stuff in the post.

Alacritty used to make kind of a big deal of these "benchmarks" on it's main page, and they don't any longer because the software improvements in the terminal are likely completely overwhelmed by whatever keyboard/monitor/OS you happen to be using.

That's the point. If you really care about this stuff, the terminal isn't exactly the place to go improve stuff unless it was way worse than it should've been in the first place.

I've always found this a bit funny - why are people so concerned with input latency at the terminal? (I get why I care with a phone, or gaming). It's not like anyone's typing hundreds of characters a second. I use Alacritty, but mostly because I like the way it's config file works and it does nice font rendering. The latency thing barely even registers.

At least for me the reaction is largely emotional. I like using my linux desktop because I can set it up exactly how I want, and macOS just doesn't roll that way. Now, I'm not really the target market, so whatever, but there are a few things that upset me about it:

1. I could really, really love macOS if they had a "don't treat me like a child" checkbox I could hit somewhere that would turn off some of the more obnoxious default behaviors. It took me a solid 5 minutes to figure out how to navigate to the root of the filesystem on a new MBP I recently was given at a new job. The most intuitive thing I could think to do was double click the name of the folder I was in ("Recents", by default when you first open it), which seems to do nothing except make a little icon appear and grow/shrink the window in Big Sur. Neat. The left pane, by default, literally has no means of navigating to the filesystem root. OSX has seemingly always wanted to pretend the filesystem doesn't exist. I like the filesystem. Stop trying to hide things from me.

2. This point is actually more a credit to apple than anything - the rendering, touch input, display management, etc on macOS is stellar, and it makes me angry I can't have the same level of polish on my linux install. I really, really want something that is as smooth as the macOS experience but with the customize-ability of linux. Apple pisses me off because they are incredibly close to that goal but they find it philosophically objectionable (for business reasons that I understand, but it still pisses me off)

Location: Seattle

Remote: Yes

Willing to relocate: No

Tech: Rust expert seeking to work primarily with Rust. Also know many, many other languages. Full stack, devops, distributed systems, crypto experience.

Linkedin: https://www.linkedin.com/in/spencer-judge-b2531046/

GH: https://github.com/Sushisource/

Email: sjudge <at> hey.com

For clarity, both people would need clocks though, correct? The top comment sort of implies you could measure this effect simply with one clock in the room, somehow, but you'd need two.

I agree, if it weren't for the fact that they give zero shits about Wayland support. I'd be totally fine with them staying closed source as long as they kept up with the standards.

This is a less-than-compelling retort. The point isn't "don't do it", the point is "well, why?". OP even admits the more compelling thing here would be to talk about how it's an improvement on glass thermally. The pollution savings are indeed unimportant, but make for good clickbait. That's the annoying part.

> I still very much believe nobody was in the wrong here

This just doesn't strike me as reasonable. The employee was in the wrong. Clearly. Just because the thing you support is a moral and good thing to support doesn't mean you get to foist your activism upon everyone else around you. I care about endangered species conservation - but if I did what this person did and held the organization hostage to my demands I'd be looked at sideways, and rightfully so.

It's not that there's no place for activism in the workplace, it's just that the line should be drawn at the point where it starts harming the organization as a whole.

TIL, cool that's a neat feature.

Yeah, it's definitely missing some stuff, at least. I have a port open for WireGuard VPN traffic that it completely misses, but that's UDP so maybe that's why.

"Sleep on the job" might be a bit unfair. Specialization doesn't exist but is in the works.

Why even bother at this point? PGP encryption in email is... not a good way to do secure communication.

Not to speak for parent comment, but the reason I use vim plugins in JetBrains IDEs is to have all that shit "just work". Yeah, you can setup stuff to autogen tags, but it's not always reliable. If you care about other IDE features (I do) then the list of crap you need to do to get vim/nvim to work properly piles up endlessly. I'll take the IDE with it's nice appearance and features and slap the keybindings in any day over the reverse.

I'd say this happens semi consistently to me when I get rejected. I did a tech screen (of which this is the first I've ever failed). I chose to do it in Rust as that's my main language these days. I probably should've reconsidered that decision as Rust is notoriously difficult when it comes to dealing with trees and I spend most of my time managing pointers. I described a solution to the tree problem quickly, implemented it, and then dealt with the compiler for about 15 minutes. As a result I never fully finished the task, but it was pretty darn clear I knew what I was doing.

Same thing, they came back and said no and I really have a hard time imagining why other than the interviewer not being familiar with Rust - but - hey, don't tell me it's fine to use then!

That to say, rejection feedback is almost always useless.

Agreed. It is shocking to me how rare simply accepting fault is. Maybe, 10% of the time, at best? I wish there were some better incentives to actually behave that way consistently. I often find myself thinking "Man, why am I even trying to be nice or do the right thing here when all these other assholes meander selfishly through life and have great outcomes too?"