Why not?
All those other elements give some benefit apart from accessibility which is why they are universally used and output isn't.
Expecting all devs to test their sites with screen readers is unrealistic.
You can do that with a div. Its only use is slightly improved default accessibility behaviour.
Presumably they're counting by number of chips (or maybe cores?), in which case this isn't a huge surprise. Nvidia alone is probably a huge fraction of that.
Still impressive though.
I agree, KDE is actually pretty amazing these days. Bizarre that the Linux ecosystem is focused around Gnome when there's another option available that so much better.
Less "best kept secret" more "not very useful so nobody cared to learn about it".
Yeah but theses regulatory burdens can only be born by mega-corporations so even though it is extra work for them, it still benefits them.
RVA23 is pretty nice. This is the first RISC-V profile that's really viable for desktop class CPUs. (But I still wouldn't buy a RISC-V chip expecting to run Linux on it until they have proper support for UEFI, ACPI, etc. and "unified discover" is specified, which won't be for probably 3-5 years.)
As long as they don't remove it from the IoT LTSC edition I don't care.
I would say:
-
Just practice, do projects. Also if you can work on projects with other people because you'll read a lot of bad code and learn how not to do things (hopefully).
-
Learn lots of programming languages. They often have different and interesting ways of doing things that can teach you lessons that you can bring to any language. For example Haskell will teach you the benefit of keeping functions pure (and also the costs!).
If you only know Python I would recommend:
-
Learn Python with type hints. Run Pyright (don't use mypy; it sucks) on your project and get it to pass.
-
Go is probably a sensible next step. Very quick to learn but you'll start to learn about proper static typing, multithreading, build tools (Go has the best tooling too so unfortunately it's all downhill from here...), and you can easily build native executables that aren't dog slow.
-
C++ or Rust. Big step up but these languages (especially C++) will teach you about how computers actually work. Pointers, memory layouts, segfaults (in C++). They also let you write what we're now calling "foundational software" (formerly "systems software" but that was too vague a term).
-
Optionally, if you want to go a bit niche, one of the functional programming languages like Haskell or OCaml. I'd probably say OCaml because it's way easier (it doesn't force everything to be pure). I don't really like OCaml so I wouldn't spend too much time on this but it has lots of interesting ideas.
-
Final boss is probably a dependently typed language like Lean or Idris. Pretty hardcore and not really of much practical use it you aren't writing software that Must Not Fail Ever. You'll learn loads about type systems though.
Also read programming articles on Hacker News.
Yeah he's dead wrong here. Even clang-format - easily the worst autoformatter I've used - is an order of magnitude more tolerable than no auto-formatting.
Sure it might not always be as good as what a perfectionist human would produce, but it's sure as hell better than what the average human produces, and it means you don't have to waste time ranting like this.
I use Google Slides - you get better control over the layout.