• 2 Posts
  • 39 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle






  • If you mean emissions wise, that’s really going to depend on the bike. Old two-strokes rocking carbs? Yeah, they’re terrible. Modern fuel injected four strokes with cats? Pretty good, actually. And they get better mileage than most hybrids. I get 60mpg on my 900cc Triumph, which is a mid-sized bike by American standards and a big bike by world standards. Smaller bikes and scooters can get over 100mpg.



  • And… they’re basically all correct. Linux does run on all sort of machines, even really ancient ones. It has a solid command line environment, or rather lots of them. And it’s astounding powerful. Windows does still blue screen, is currently the best place for gaming, and wow is MS fucking you with Win11. Macs can have a cool setup, are really simplified for most users and expensive.





  • Take a look at what even the proposer is saying wouldn’t be allowed in:

     (1) new and delete.  There's no way to pass GFP_* flags in.
    
     (2) Constructors and destructors.  Nests of implicit code makes the code less
         obvious, and the replacement of static initialisation with constructor
         calls would make the code size larger.
    
     (3) Exceptions and RTTI.  RTTI would bulk the kernel up too much and
         exception handling is limited without it, and since destructors are not
         allowed, you still have to manually clean up after an error.
    
     (4) Operator overloading (except in special cases).
    
     (5) Function overloading (except in special inline cases).
    
     (6) STL (though some type trait bits are needed to replace __builtins that
         don't exist in g++).
    
     (7) 'class', 'private', 'namespace'.
    
     (8) 'virtual'.  Don't want virtual base classes, though virtual function
         tables might make operations tables more efficient.
    

    C++ without class, constructors, destructors, most overloading and the STL? Wow.






  • When I was a very junior EE I ended up working mostly on microcontroller code. There was one bit of extremely ugly code I inherited that parsed a terribly designed serial communication protocol by using a giant maze of nested if statements. I really wanted to rewrite it to something better, but I never quite came up a solution while I worked there. Years later after I was no longer at the company I had a stress dream about it and finally came up with a working solution. I still wish I could go fix it. I really hope it’s no longer used, or that someone else has finally fixed it.