It’s almost like these fucks don’t understand anything about the technology they’re touting
It’s almost like these fucks don’t understand anything about the technology they’re touting
This is an informative answer, thank you
But wouldn’t he have to repay such loans?
Not any language. I code professionally in F# which has semantic whitespace and it has literally never been an issue for me or my team. In contrast to Python, it’s a compiled language and the compiler is quite strict, so that probably helps.
They hated him because he spoke the truth
I’ve been using Windows personally and professionally since 3.1, and Windows 11 was the last straw that finally got me to jump over to Linux for my home PC. I hate what Windows has become but I’ve got a lot of history with it. My experience with Linux (Mint FWIW) has been as smooth as it ever was in Windows, neither of which was perfect. I’m a definite convert from Windows and would encourage most people to consider taking the leap themselves.
I gotta disagree with you about modern Powershell and terminals in Windows, though. Good terminal? Windows Terminal has been around for years now. It’s fast and functional. Whether Powershell’s parameters are “sane” is probably a matter of taste, but I’m definitely willing to stick up for its usability. Yes, the parameter names are much more verbose, but they all get tab completion out of the box, and you don’t have to type the full names at all, just enough of the start of the name to be unambiguous. For personal automation scripts, I think Powershell is way ahead of Bash. Parameters get bound automatically without needing to write for/case
loops with getopts
. You can write comments at the top of the file that automatically get integrated into Powershell’s help system. Sending objects through the standard pipeline means you spend a lot less time and code just parsing text.
Wait, this is for a Raspberry Pi? I thought we were talking about Linux as a desktop OS. You wouldn’t run Windows on a Raspberry Pi, so while I’m sorry you’re having trouble with your Pi’s fans, I don’t see how that’s relevant to the merits of Linux as a desktop OS.
Is that supposed to be a real example? It’s just that fans are controlled by the BIOS, not the OS, so fixing a fan problem would usually involve either updating your firmware, which I have never seen done via a terminal command, or changing a BIOS setting, which could involve rebooting and holding a key like F2 to enter the BIOS settings menu (not Linux, usually a quasi-graphical mouse-driven UI) to change something there.
I really don’t understand the objection to using a terminal to get things done. It’s just a window that you can type text commands into. You don’t even have to come up with the commands on your own, you find the ones that solve the problem on the internet, copy and paste, and boom problem fixed. How is this different from looking up a solution to a Windows problem that walks you with a series of pictures through using Regedit or Group Policy Editor, only instead of pasting text into a terminal, you have to click through dozens of menus, trees, and tabs to find the setting you need to change? You’re still looking up solutions online in either case, but the Windows solutions require navigating windows with dozens of mouse clicks versus copying and pasting some text in Linux.
Meh. It’ll still have all the weaknesses of other LLMs.
Sure, let a text generator try tactics
Spot on description
Because you still need to be able to understand what’s actually getting executed. There’s no debugger so you’ll still be debugging Bash.
Are you saying that you want to separate your two logical sections by having different levels of indentation and that’s what makes Python go crazy?
Since it’s a superset of JSON, couldn’t you just use the JSON notation if you hate the semantic whitespace?
I like the idea in principle. For it to be worth using though, it needs to output readable Bash.
let
is also used to declare values in better languages than JavaScript, such as Haskell and ML family languages like OCaml and F#
Where I work, Senior Engineer is an IC role. They attend the same meetings as other engineers. Its the Staff+ Engineers and managers that attend more meetings (in ascending order)
I did that this year, smooth sailing so far!
Yes, this. Refactor first to make the upcoming change easier and cleaner, not after. Don’t ask for permission, don’t even call it refactoring or cleanup. Just call it working on the feature, because that’s what it is. Don’t let non-engineers tell you how to engineer.