

Fair point, but good luck convincing them about it.
Fair point, but good luck convincing them about it.
I’m not saying “don’t make progress”, I’m saying “try to make progress across the board”.
IMO another example of pushing numbers ahead of what’s actually needed, and benefitting manufacturers way more than the end user. Get this for bragging rights? Sure, you do you. Some server/enterprise niche use case? Maybe. But I’m sure that for 90% of people, including even those with a bit more demanding storage requirements, a PCIe 4 NVMe drive is still plenty in terms of throughput. At the same time SSD prices have been hovering around the same point for the past 3-4-5 years, and there hasn’t been significant development in capacity - 8 TB models are still rare and disproportionately expensive, almost exotic. I personally would be much more excited to see a cool, efficient and reasonably priced 8/16 TB PCIe 4 drive than a pointlessly fast 1/2/4 TB PCIe 5.
Assuming you meant GB/s, not TB/s, I think it’s for the sake of convenience when doing comparisons - there are still SATA SSDs around and in terms of sequential reads and writes those top out at what the interface allows, i.e. 500-550 MB/s.
Somewhat agree, but since Scrum is supposed to be bent to the team’s needs, it might differ from team to team, but it’s fine as long as those numbers are consistently used in one team.
If story points are now hours, I hope you’re fine with me putting a 40 on that ticket.
“T-shirts are amazing - your body goes into one hole and goes out of three.”
Windows Mail was IMO perfect for simple mail at home. Now they replaced it with Outlook with slightly updated UI but also with ads.
Guess what - I started looking for alternatives. So far Wino Mail seems pretty good - someone else on here recommended it.
Technically correct if you die… with the caveat that you won’t be able to do much else.
- Ducks is heads because ducks have heads.
- What kind of scary ass clowns came to your birthday?
It would be just very slightly suspicious if a bot knows when you’re about to die.
Nothing in common actually (besides the somewhat close spelling). It’s a male name, sort of a variation of Peter, same meaning (i.e. a stone, a rock), different etymology.
I’d argue that deploying from one codebase to 3+ different platforms is new functionality, although not for the end user per se.
I wish though that more of the web apps would come as no batteries included (by default or at least as a selectable option), i.e. use whatever webview is available on the system instead of shipping another one regardless of if you want it or not.
It’s my actual given name.
I’ve tried SwiftKey as well, but last I remember it was a bit sluggish. I’ll give it another try, thanks.
I’ve tried HeliBoard as already suggested elsewhere, but I find its autocorrect and suggestions absolutely abysmal in English and even worse in my native Bulgarian. With Gboard I can usually type a letter or two and it already knows what’s up, and it often knows what’s the next word based just on the previous one.
How’s your experience with it?
Well, over time, you accumulate some judgment about things like that. But you have some point too.
For anything that doesn’t seem entirely obvious I try to leave a comment. It could end up being helpful to me some time later, because let’s face it: your code is indistinguishable from someone else’s code 2 weeks after you commit it.
Imagine the market being saturated with all kinds of keyboards in various form factors and layouts and someone holding you accountable for what you’re using.
I used to think I can’t do without an F-row. Nowadays I use a bunch of 60-ish boards (a Boardwalk, a Lily58, an Elora) and it’s all fine. Even back when I was using a 75%, I was used to have e.g. the arrows on IJKL on a layer (of course it doesn’t work well for games, but for things like text editing I’d argue it’s even better than dedicated keys). In general I’d suggest to everyone to challenge themselves a little bit with things that don’t seem good at first but might end up being useful in the long run.