folknor
Joined 9 years ago
Joined 9 years ago
It's such a huge difference I can't quite put it into words. It's completely different. I love it - some people might not though.
It feels cool and smooth. I sleep wearing only boxer briefs, and did previously as well.
One downside is you have to wash and dry them separately - but I already did that anyway because of the load.
EDIT: Actually they didn't say that, I presumed they did because the Pro model AFAIK is the only one that comes with glass bottles insted of PET. But still, make sure you check that these bottles work with your machine :-) They dont work with mine!
Extremely cool, I will definitely check out lnav when I get a chance. I've been battling with the big players for a few months now and their systems are just so overengineered and complex for my needs that it's silly.
I just need tail -f for 10-ish servers and desktops.
I haven't even read the project readme, but I presume lnav is exactly what I wanted. Excellent!
I started using atom pre-1.0, a long, long time ago. I immediately jumped to vscode when I realised it existed.
The reason is a bit weird; it's the find-in-files/project (c-s-F/Ctrl+Shift+F) sidebar search/replace feature. Compared to the Atom (and from what I can see in the youtube talk, zed has the same "problem") which opens c-s-F results in the main window, vscode opens them in the sidebar and doesn't clutter the main view with it.
The reason this is powerful to me is that I code mostly in domain-specific, esoteric, private languages that have no API documentation, no stdlib or docs, and no online resources to learn from. So the only way to learn is by example, or talk to someone who knows. Learning by example is usually much faster than talking.
So what I do is any new project is just a subfolder in a workspace that contains all known code in the language and the way I find out how to do something is c-s-F.
When the results cover the main view, or even parts of it (which is also possible with atom), it's just way too intrusive. The sidebar file list is useless to me at this point - where the result comes from is irrelevant. So why not use that space?
Also of course the fact that vscodes cross-file search was blazingly fast was an upside as well (I believe they used ripgrep for that since the start?)
Another thing I want to mention is (and you highlight the keyword search in that youtube talk around 18:54) the power of the command palette search method that is available in vscode: first-letter-matching. I don't know what the proper name of it is, but essentially "ps" matches "pub struct" for example. Obviously it matches it with a lower score than something that starts with "ps", but it's very powerful for matching in the command palette.
Thanks for listening.
I've made 8-10 reports or something like that, because it feels like the right thing to do. Which is a compliment to your sites design.
I see you're planning to redo the front page. Why? I've never used the front page. I immediately search for the game or manually edit the URL from my browsers location bar (https://www.protondb.com/app/{id}) to insert the id of the game I want to report on.
After writing that, I do have a question; do you have objective, real data on what users want from the front page?
The only thing I want is a search box that responds to both game titles (with automagic for things like roman numerals and other game title oddities) and numeric IDs. The rest can be hidden.
In most cases, you'd probably be correct in thinking that the person would be more inclined to preserve the status quo than changing it too quickly, for fear of unforeseen consequences.
Also, a simple Google search and 30-second skim of Wikipedia throws a wrench in your assertion.
:-D
However, I'm not a US citizen so I don't follow the situation closely.
It's not a centrist policy at all - the parties (I think there are two, one of which is probably the Libertarian party) that don't support it here don't hold _any_ elected seats on any level. Not even a single city council seat in a backwater town in the middle of nowhere.
So yeah, this is the norm. I'm not saying this to argue, I'm saying it to reinforce you (hopefully that's obvious) :-)
The Browser Toolbox is the normal DOM inspector, just extended to the whole user interface. If you open the print preview, then open the Browser Toolbox, you can inspect the preview and edit styles just like any other document.
Also, @media print {} works fine, I just tested it. But I'm not sure how that relates to the original question.
There's been several alternatives mentioned on HN over the past year. A quick search through my browser history revealed https://altcha.org/open-source-captcha/ as the most recent link I'd been to.
Just to say I have no experience of any of the "alternative" captchas, I just hate the one you're using.
Also please get your app up and running fast so we can use it for our vacation in early September, haha :-) Thank you.