It's actually a suite of tools that do solve individual problems comprehensively. Not as small as the programs in coreutils, but still not a huge monolith.
893 karma · joined June 10, 2022
It's actually a suite of tools that do solve individual problems comprehensively. Not as small as the programs in coreutils, but still not a huge monolith.
I'm almost never CPU constrained, so I tend to have everything idled down as much as possible.
Edit: and just for context, opening firefox and browsing the web right now has me at 9W.
That said, it's not out of box like a Macbook.
I hardly travel anymore but still wind up using all of those local resources. It's zero web searches, next to no latency, and I have the structure memorized. Finding information I need is so fast.
I wish it was more popular to have a local-first mindset when writing software.
I see that 'distributed' was moved to the cloud library and I don't see any way to run this in an on-prem data center without an enterprise plan.
Sure there are other ways we could communicate offsets, days, whatever, but having everyone on the same daily schedule and just adjusting the schedule itself keeps it simple for most of the population.
You have to take a thought and distill it down to a diagram or written word before you share it. Personally, If I can't do that it tells me that my idea is still half baked.
It also teaches you to avoid throwing out incomplete ideas or asking simple questions you could answer yourself as the rtt for a response in a distributed team is too high.
I would think the usual cause is the timing was off and the spark plug fires before the cylinder reaches TDC.
I feel like OCaml has been on a fast upward trajectory the past couple of years. Both in terms of language features and tooling. I expect the developer experience to surpass Haskell if it hasn't already.
I really like Merlin/ocaml-lsp. Sure, it doesn't have every LSP feature like a tool with a lot of eyes on it, such as clangd, but it handles nearly everything.
And yeah, dune is a little odd, but I haven't had any issues with it in a while. I even have some curve-ball projects that involve a fair amount of C/FFI work.
My only complaint with opam is how switches feel a little clunky. But still, I'll take it over pip, npm, all day.
I've been using OCaml for years now and compared to most other languages, the experience has been pretty pleasant.
git commit --fixup=commit HASH
git rebase -i HASH^ #yes, include ^
# save and close the rebase window that appears
git push origin branch --force
edit, and you can re-word a commit with git commit --fixup=amend:HASHBut, I don't think that's what everyone is talking about with poor math scores. Just last week I had two college educated adults telling me adamantly that 10 * 700 was 70,000.
I will conceed though, the Tarides folks know their shit when it comes to OCaml projects.
Anyone can tell you that fishing, processing, and the markets are a very complex problem and it would be true. But I would just like to highlight this little excerpt.
> Icicle was bought by a private equity firm in 2007, and then sold in 2016. In 2020, it merged with the owner of a shuttered Petersburg plant and became OBI Seafoods. The curtailed operations last summer meant fewer workers in town spending money, and delayed payments for fishermen.
It's also my understanding that the wages for processors are less than $2 higher than they were in the eighties. Local kids home on summer break rarely work at the cannery anymore. I'll also add that a lot of seasonal workers from other countries won't be back next year because the processor is doing away with overtime. People want to show up and work 16hr days for three months, then go back to lcol areas. You can't do that when you're limited to 8hrs a day.
I don't doubt that at all. But I've also had that on a whiteboard.
Also, it sounds like your interviewer was a jerk. Which seems orthogonal to the style of interview.
I'm not older, but I was in the industry prior to the leetcode style interview. I've never sat down and "grinded" leetcode but I've also never had a problem with those styles of interview once they became common. Neither have my former co-workers. I have a few friends that are still working, past retirement age, that would crush any problem you threw at them.
In my experience, it's not much different than the whiteboard interview. Sure the presentation of a problem can stump you for a moment, but with a few good follow up questions a solution, however naive, becomes apparent.
I had a mentor early in my career that repeatedly said "There is no such thing as an unsolved problem in computer science". I think that mostly holds true, you either recognize the pattern and implement, or you learn and implement next time.
That all said, leetcode style interviews are the interview version of a "bad code smell" and I'd strongly prefer a bug-squash style, even if it was in a completely unfamiliar programming language. Actually, an unfamiliar programming language might make it fun.
I'd much rather optimize for the happy days than the shitty ones.
I don't think the markets influence child rearing as much as the headlines say.
Yeah, that's a fair point. You do get in the habit of occasionally diffing your config file against the ones with the .pacnew extension. As well as purging packages.
The installation on my laptop is on its 4th hardware refresh. Rsync or brtfs send to a new box, modify the partition UUIDs, rebuild the initial ram disk, and you're on you're merry way.
It seems like it would be fewer steps, fewer tests, and less messing around by making testing more available to the people.