Besides, the survey you mention used just 1000 phone calls in the US and doesn't disclose education level, it doesn't depict global population properly.
145 karma · joined February 15, 2014
Besides, the survey you mention used just 1000 phone calls in the US and doesn't disclose education level, it doesn't depict global population properly.
With more and more code being written with AI (which has notoriously inefficient solutions to simple problems), I expect this issue to become more prevalent. I just hope we optimize at the source of the problem (AI and humans using it) and not on platforms (compiler and engine/kernel heuristics)
Sadly wm in MacOS is like notifications on iOS: with enough time you get used to the unproductive mess they are, but you'll be missing out on better solutions. And since probably all MacOS devs are using Mac, they won't see/understand other (better) approaches.
What kind of sites do you visit frequently? Because as a Firefox user, I rarely see issues like this and it's usually related to either chrome-specific things they didn't bother to implement in a compatible way or very cutting-edge features that are not fully available in browsers yet.
I know Firefox had issues in the past (I suffered them myself) but I don't remember having issues with it over the last bunch of years, and it's my main (only) browser.
No, people are used to an UI language, which in the case of iOS is quite consistent across applications. You expect certain things to work (e.g. flicking in from the left edge means "go back"). There are platform-specific patterns and I'd rather have the app behave accordingly rather than being consistent with other OS' version. The real 0.1% here are probably the users of your app with active devices in both Android and iOS!
You're forgetting about the first W in WWW...
All those domains can be avoided just using an ad blocker, I suggest ublock origin.
- Let me pick a database when I start so the data types are restricted to that particular database. This can help down the line with other quirks and particularities of each db.
- I'd love to be able to use this and convert it to a model for my ORM (I'm currently using Prisma, but depending on your vision this could expand to other languages and ORMs such as, for example, Django). This would be helpful because I'd be able to jump from design to implementation without rewriting everything as models in my ORM.
- The nodes to establish relationships are difficult to click, and several times I ended up dragging the table instead. Consider making them easier to grab.
- If I delete a property from the table (in the grid) there's no quick way to undo. A toast message with an undo link would be helpful.
- The "delete diagram" option didn't ask me for confirmation and even if I saved my diagram before, it's gone. And this option is dangerously close to "Rename"!
You can request a backup of your data from https://takeout.google.com/settings/takeout