Comments by "Zer0" (@ForeverZer0) on "Fireship"
channel.
-
54
-
21
-
21
-
For me:
Micro for light-editing, config files, small scripts.
VS Code for larger scripts and mix-language projects (i.e. writing C extensions for Ruby)
The suitable JetBrains IDE for large projects and enterprise languages like Rider for C# or IntelliJ for Java (though rarely).
Years ago when I was still using Windows, I was a Visual Studio fan, but would never use it again, even if using Windows, and would definitely stick with a JetBrains product.
EDIT: Although this video is nearly a year old, I had tried Fleet on early-access, and was unimpressed by it personally. It might have its niche uses, but overall, it seems like there is always a better tool to use instead.
19
-
19
-
19
-
14
-
10
-
@alvarohigino I don't know, I personally cannot name any remotely popular language that has grown near as slow. C17 didn't add any language features. C11 was pretty much just threads. After that we have to go back to C99, which was probably the biggest change in recent history, with revolutionary concepts like stdint.h, booleans, and inline comments. If memory serves it also added variodic/inline functions at that point, which is a rather large change for a language like C, though would only bump a minor revision in any other.
Before that was the Lord's version: Holy C89, so that is over 3 decades where I can list 90% of the of "bloat" in a brief YT comment from memory.
Tooling has increased by leaps and bounds, but that isn't the language, so not really a fair metric.
10
-
8
-
7
-
6
-
5
-
4
-
4
-
3
-
3
-
3
-
2
-
2
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1