Comments by "⃠" (@U20E0) on "Fireship" channel.

  1. now I’ve decided that I’m not going to learn it after all.
    313
  2. a good point. But unfortunately things require money.
    109
  3. a bad manager amplifies it
    65
  4.  @apuji7555  that’s where the implicit int came from, probably.
    39
  5. they've found a way to anger everyone
    37
  6. probably including other criminals
    37
  7. notably it is also the only one not trying to “fix” C
    26
  8.  @Croesquared  you can? Does that not make it “incompatible with itself”?
    24
  9. To add, Apple themselves encouraged Microsoft to port Windows to Apple silicon... why? the answer is that macOS makes them practically no money. Apple is a hardware company.
    24
  10.  @mikadofxx9030  They aren't. Apple has specifically made sure that third-party OSs can run and can do so safely and without sabotaging the system's security model The drivers and some other important bits of code being private is of course a big obstacle, but it's one that can be and defeated, as the Asahi Linux team has proven.
    23
  11. afraid of lawsuits
    20
  12.  @Croesquared  in that case, I misunderstood you, significantly.
    20
  13. ( the answer is probably yes, everyone has tried that at some point )
    19
  14.  @CarlBach-ol9zb  Apple's documentation on the boot process as well as documents from the Asahi Linux project
    16
  15.  @archthearchvile  HolyC is best language
    13
  16. it's doesn't need 40GB, but the more you have the better.
    13
  17. it’s almost a century at this point
    13
  18. makes sense
    12
  19. But did he make a language at any point?
    8
  20. that’s a problem with your IDE, not the language
    8
  21. they are also not even remotely new. This has existed for (well) over 5 years, and no-one is using it anywhere, except in aircraft HUDs because that's an actual use-case which can't be replaced with a cheaper alternative.
    7
  22.  @mastershooter64  but the error handling ( or lack thereof ) is exactly the same between C and asm, so this question makes no sense here.
    7
  23. 1: true 2: i still don't understand why people like voice input
    5
  24. Also I’m wondering if either of them are stealing your code
    5
  25. i knew they did something skewy in that comparison (any "xxx is yyy% better than zzz" selling point ever does that), but using a machine that's not even representative of the CPU?
    5
  26. + it only goes to OpenAI after a confirmation
    4
  27. fn is not that uncommon. And yes, the language’s syntax is very unconventional in every way possible. Multiline strings are achieved by prefixing a line with \\
    4
  28.  @daleryanaldover6545  why do people hate Ruby??? It’s a good language as far as I can see ( which is not all that far )
    4
  29. 1. function parameters are always immutable. 2. No. 3. a switch statement exists, but it’s quite unusual. It returns a value. Like in C it can only match against enum or integer constants, but Zig has built-in tagged unions (union with attached integer that tells you which member you should use), and switch can match the tag of the union as well. 4. not really sure what you mean by that 5. Yes. Zig distinguishes between several types of pointers, and allows pointer arithmetic (sometimes). 6. OOB checks will happen if the array has known bounds, and Zig errors if a constant array is not terminated with the requested value. Like C, strings are just an easier way to initialize a char array. Other mildly interesting things: Arbitrary bit width can be specified for integers: u5 and i7529 are both valid types Integer overflow is UB — if you want an automatic overflow check append | to the operator and % if you explicitly want to allow overflow Inline assembly is supported Vectors are supported Standard library is quite large
    4
  30. Bringinh back concepts that were unrightfully buried actually is innovative
    3
  31. the metadata saying the image is “valid” is simply lost in that case
    3
  32.  @colbyboucher6391  truth
    3
  33.  @linuxpropaganda  ( i deleted a comment on accident. Mobile devices suck ) That applies to the very existence of ISPs too. And ultimately, the root cause of nearly every problem is “human nature” — or, more properly worded, us ourselves not letting us ourselves have what we ourselves want us ourselves so that we can blame it on “them”
    3
  34. We know a lot of [ insert anything ] that are true but politically incorrect
    3
  35.  @dhruvakhera5011  this statement is politically incorrect))))
    3
  36. on windows ARM
    3
  37. @X() is not any worse than __builtin_X().
    3
  38.  @elirane85  Even if it isn't new ( it certainly is big though ) it's presence at CES will probably cause it to become more popular
    3
  39.  @Lara-dr8is That shouldn't be considered an issue though. Sure, the AI can write something racist if you ask it to, but so can everyone else.
    3
  40. Text is superior in all ways.
    3
  41.  @francisco444 the point is that people overhype things just because they are new, even if it isn't actually better than what already exists, or even if it's much worse ( look at all of the "definitely not just an inefficient train" things that happened some time ago )
    2
  42. the macOS variation is more confusing
    2
  43. anotherJS is a better and more fitting name ( i found it somewhere under one of the top comments (
    2
  44. yeah, 53% is a bit too much to be believable. And it somehow manages to rival Apple's pricing because why not. The main factor isn't the memory but the fact it's a MacBook Air and not a Pro. the Air cannot utilise anywhere near the full power of the CPU after some time under load, and something tells be the benchmark results were taken after that time passed. why? because it has no active cooling! it wasn't designed for performance, it was designed for portability and energy efficiency.
    2
  45. You can’t compare them in a meaningful way. Zig is a drop-in replacement for C designed to cut out boilerplate and make some features (like vector types) more usable. Rust is a C++ alternative designed around memory safety
    2
  46. Yeah, i don’t thing calling free on a random variable will end well.
    2
  47. simply because censorship of any form is bad.
    2
  48.  @linuxpropaganda  it does indeed apply to everything ( i know even less about crypto nonsense; but i do know that it solves nothing )
    2
  49. you do realize that this extends beyond “internet privacy”
    2
  50. tires
    2