Here's some feedback if it's helpful for the author.
As mentioned in the comments, the script is supposed to cover fresh grads and Windows users with no prior Linux/macOS experience.
The experienced users having their own opinion about the configuration would still require time to find and configure company-specific conventions and settings they're not aware of. The common reaction is such opinionated scripts are avoided at any cost, so developers still spend time filtering the file(s) to find important bits. If the information is also in the documentation, it's ok - the script can be safely ignored. Otherwise, it can be annoying and leave a bad impression.
For the next version, I'd try to make it friendlier for both groups of users. I'd say being able to revisit what exactly is to be installed would enable more people, save time and energy. The experts would only get necessary business settings integrated (via the advanced mode), while beginners would have complete installation (via the basic mode). It was a pretty common approach with TUI installers back in the day.
Homebrew-wise, I'd replace separate brew commands with a Brewfile and 'brew bundle install'. It'd keep the package list isolated from the logic. Regarding the packages, I'd also put all version-sensitive software away from the direct Homebrew control. With programming languages, it'd be a version manager like 'asdf' and so on.
I haven't invested in a Nix configuration yet, since my small dotfiles repo works fine so far. There are obvious benefits, of course.
Interesting observation: many people in the russian segment of the Internet use `)` instead of a period at the end of a sentence.
If you write a conventional sentence with a period, sometimes people might think you're not alright or even annoyed. Appending `:)` afterwards might be considered a sad smile. We have expressive parentheses and emojis here, but you put that sad smile, what's happened? It's all fine, I just follow the punctuations.
I find it curious that even using emotions in the Internet can be different within a single culture, not to mention others.
I think you could also utilize 'Brewfile' with pinned versions, where needed, and the latest available for the rest. I manage my environment this way when migrating from one work laptop to another. Works fine so far.
Alternatively, you can create your own 'tap' to gain more control over some packages.
For databases, I'd stick to running them as containers, too.
Homebrew is not ideal, of course, but there are ways to achieve desired goals until we have something better.
I agree. Lately, I try to refrain from using the term 'best practices' in favor of 'good practices', 'common practices' or even 'my practices' for several reasons:
- True best practices mainly refer to standards, and this list is very slowly updated, unlike the number of false ones;
- It's often used for marketing purposes, which works well, but doesn't always imply quality;
- Since this spreads fast, we often have things at the places where they do not fit, but squeezed into, because it's the best, so we must have it;
- Forms a wrong mindset to rely upon someone else's experience instead of learning and gaining own understanding.
In the end, we have tons of inapplicable or controversial information to filter, which doesn't make things better, in my opinion. Sharing is great but we should do it responsibly.
It's also a bit funny to watch how the best practices suddenly become the worst.
I have a similar experience. Technical challenges are one thing and they can be interesting, but ethics is more important to me.
It was painful to observe that people from countries with difficult economies can spend so much money to hunt for pixels. This is their choice, of course, but at the same time it's a proactive work to keep them hooked.
After I realized what I was getting myself into, I completed the existing tasks and left the company. It's not for me.
Yeah, this really sounds to me like a sunset of x86 hegemony with such arguments. Not to belittle the game market, of course. It's huge. The hybrid chips they're planning to release are unlikely to be cheap. We'll see.
Also, not every x86 software needs to be ported, given the available alternatives and cross-compile features.
Very good advice, I second this. For developers I also usually recommend VSCode plugin or Lens for those who can't stand VSCode for any reason. It seems to be a common choice.
Hi! It seems some graphic content is served via 'http' instead of 'https', raising an exclamation mark in browsers:
https://terminusdb.com/documentation/
Also, a small typo in 'Quickstart Ac(c)ademy'.
Thanks, and looking forward to checking TerminusHub!
Zoom?! What a twist! Congrats to the Keybase team! Although it's time to drop the account and move further, I'll keep it for a while in case of another twist.
For Windows ScreenToGif seems to be one of the best due to a small footprint and features available.
On Mac I was using LICECap as well, but wasn't too satisfied with the blurry picture, color palette and low frame rate, although it's still good if needed urgently.
Trying to find something else I bumped into Kap[1] with mp4, gif and webm format exporting, also simple trimming is included. I'm not that happy to know that it's an Electron-based app, but that's the price. Apart from that the size of webm files is even smaller than mp4 and browser support is pretty good these days.