• 0 Posts
  • 16 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.





  • BartyDeCanter@lemmy.sdf.orgtoAsklemmy@lemmy.ml***
    link
    fedilink
    arrow-up
    2
    ·
    5 months ago

    Oh, nothing about it sounds unrealistic, just kinda pointless. There absolutely are rugged laptops and gaming laptops and probably even some combination of the two out there somewhere. But they both tend to be quite expensive and nothing you mentioned seemed to indicate the need for portability. So, why a laptop and not a desktop? You’ll get a lot more bang for your buck and can have the exact keyboard, cooling system and whatever else you want, plus a much more repairable system.




  • 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.