• 0 Posts
  • 23 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle


  • Cheaper & faster development by leveraging large libraries/frameworks, but inability to automatically drop most unused parts of those libraries/frameworks. You could in theory shrink Electron way down by yoinking out tons of browser features you’re not using, but there’s not much incentive to do it and it’d potentially require a lot of engineering work.



  • count_dongulus@lemmy.worldtoProgrammer Humor@programming.devC++
    link
    fedilink
    arrow-up
    17
    arrow-down
    1
    ·
    17 days ago

    Try porting a very small bit of behavior into a new tiny library or module that is Typescript based and independently published. Enable the strictness checks in tsconfig - really, really resist the urge to use any, and enforce that any is disallowed in tsconfig. Familiarize yourself with its utility types that really trip new authors up. “Record” comes to mind here, and others that involve generics if you haven’t before worked with generics. Some of the type error messaging can be pretty obtuse - don’t be afraid to paste them into an LLM (or use Copilot enhanced Intellisense) to explain what it actually means. IMO the type violation messaging is a weak dev experience point for new authors, so don’t sweat it if you occasionally “struggle to make the squiggles go away”.


  • count_dongulus@lemmy.worldtoProgrammer Humor@programming.devC++
    link
    fedilink
    arrow-up
    68
    arrow-down
    1
    ·
    17 days ago

    This is why I will never touch Javascript again. Long ago when I worked on web stuff, half my workflow was spent in the debugger tracing garbage to find where a typo was. The industry moved to Typescript, and now assuming the strictness checks are enabled, if some Typescript transpiles successfully, I can be 95% sure whatever fuckup I observe at runtime is a logic problem.

    Weakly typed languages were an awful idea. But in general, if the compiler isn’t able to detect most runtime issues (like with C++ here), it’s not going to be the most productive language to use for building solutions compared to smarter alternatives.






  • The idea is to have water or molten salt cool the walls of the torus from outside, and those drive ordinary turbines like any other generator. The main issue is that particles fly out of the confined plasma donut and degrade the walls, whose dust flys into the plasma and reduces the fusion efficiency. They’re focusing on the hard part - dealing with the health of plasma sustainment and the durability of the confinement walls over time. Hot thing that stays hot can boil water or salt to drive regular turbines, that’s not the main engineering challenge. I get your frustration where it feels from news coverage that they’re not focusing on the right stuff, but what you’ll likely eventually see is that the time between “we figured out how to durably confine a healthy plasma” will quickly turn into “we have a huge energy output” much like inventors puttered around with flight for hundreds of years until a sustained powered flight design, however crappy, finally worked. From that point, it was only 15 years until the first transatlantic flight.