140 karma · joined September 25, 2019
If you've ever trusted a vendor install from any manufacturer you've made a bad decision. Lenovo is just the one that got caught doing something silly.
alias ls='ls --hide="lost+found" --hide="#*" --hide="*~" --hide="*.pyc" --hide="*.egg-info" --hide="__pycache__" --color=auto'
But I'll be adding your item into my config for the rotated versioning, I wasn't aware that emacs does that but I assume it'll save me anything from few hours to a few weeks yearly. Thanks!Seemed weird to make up a codeword but I wasn't aware of any standard convention, and visually highlighting high impact issues (w/ the bonus of greppability) seemed like a sane approach in rapid development environments.
Edit: I should contextualise this by noting I have basically no experience with pharma so grain of salt blah blah
I imagine MS/Chrome will treat this as an emergency out-of-cycle patch which I don't think many people would disagree with :)
But to contradict your point, there's also a fair amount of Python which is a dictation - Guido even called his job role 'Benevolent dictator for life'. I really hated some of the guidelines as a new programmer but after dealing with them for some time I understand that consistency is far more important than preference in many/most/all cases.
If anything, the one thing I hate about Python3 is dynamic typing - inferring datatypes in function bodies is great but strongly typed (and _enforced_) parameters and return values would clean up a lot of the problems I have seen, and created in the past.
Edit: This comment ended in man-shrugging, but Hacker News stripped the emoji.
Have you had any issues you suspect may be driver / gfx related?
I've only ever really dealt wit nVidia and Intel graphics, and highly prefer intel due to tearing fixes.
I'm not a gamer, but do need at least basic hardware acceleration for X rendering etc.
Motivated is a keyword here. Opportunistic attacks occur, and probably make up for the majority of such attacks.
You can apply for Chrome preload via https://hstspreload.org/ which I ends up in Chrome source, the list is then replicated to other browsers by their maintaniers.
HSTS Preload will prevent initial-access downgrade attacks for clients using versions of browsers with your domain as a HSTS preload. The downside is preload removal is difficult and would take a fair while to propogate.
Also another common misconception is disabling port 80 will remediate the issue - if an attacker can intercept and modify traffic they are able to open and redirect the port to a node under their control. https://letsencrypt.org/docs/allow-port-80/
When I was working on a host where I needed two layouts (US-Dvorak + US-Qwerty for other users) I ended up solving the problem using AutoHotKey to hook all keys and send a different keyevent. It was pretty gross but it bypassed all the issues I was having in a convenient way.
Perhaps you could hook US symbols such as "$" and rebind to UK equivalents with AHK? Alternatively, creating a modified EN-US keyboard layout which has relevant key-symbols would also work / be less hacky, but probably require more effort.
Microsoft Office, if anything, has gone completely backwards in regards to UX. On a fundamental level it 'just works' but when I started becoming more of a power user I found reproducible bugs, unexpected or inconsistent behaviors, and a complete lack of extensibility for creating / modifying docx documents programmatically in !C#.
By far my least favorite issue is the constant battle I have with locale - I'm not sure if the document creators local was set to EN-US or if my system config is not correct, but every time I try and force the document to EN-AU it seems to switch back seemingly on a per-section basis or something. The most amusing side effect of this is the 'Read aloud' voice changing gender mid sentence but the amusement is quickly offset by it deciding to auto-correct perfectly valid EN-AU spelling for its American localisation for the fifth time in a paragraph.
It' very similar to what we were doing with stored procs 15 years ago and just moves the problem from business logic back to database layer. Given the choice, I'd prefer to write constraints in !SQL, personally.
What about group/role based security concepts?
I can't think of any other justification for .sucks to charge as much as they do for registration other than to ransom large companies.
TLDs are a complete wasteland any way you look at them.
com.au domains (owned by AUDA) at have a policy against squatting but it's reactive, toothless, time consuming and painful. On releasing a squatted domain, it's flagged as being a squatted domain (rather than expired) and AUDA approved registrars such as drop.com.au host blind auction domains, with the highest bin winning. Meaning you're either paying more than you need for a resource that should cost $15AUD to fight off real or imaginary squatters who will offer you the domain at a highly inflated cost. If you lose the auction any money you bid ends up as non-refundable credit within Drop.com.au ecosystem. I'm still unsure if it's good intentions gone bad, or just blatantly corrupt.
/rant
I'd kill clin.sucks as a mail domain.
I love how it's easier to steal my identity than to intercept my encrypted web traffic.
Society really could do with a cryptographically sane method of authentication - think an PKI-type verification but in replacement for '100 points of id' / Social Security Number / Tax File Number etc.
Surely the cost of implementation wouldn't outweigh the cost of identity theft and other types of fraud which can occur due to the current flawed system?
Maybe the costs are/would be paid for by different parties, but indirectly we all pay for them through insurance premiums and taxes which cover the (preventable) financial damage anyway.
I don't understand why your being standoffish over a technicality.
I'd love to know which ones! I was a bash user for 10 years, ZSH defaults put me off and it wasn't till I ran oh-my-zsh that I really learnt what I was missing, the following make me feel like a 10x-er ;) :
- zsh-autosuggetions - zsh-syntax-highlighting - colored-man-pages
Edit: And the `zstyle ':completion:*' menu select` autocomplete