• 4 Posts
  • 77 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • That’s entirely fair for the usecase of a small script or plugin, or even a small website. I’d quickly get annoyed with Python if I had to use it for a larger project though.

    TypeScript breaks down when you need it for a codebase that’s longer than a few thousand lines of code. I use pure JavaScript in my personal website and it’s not that bad. At work where the frontend I work on has 20,000 lines of TypeScript not including the HTML files, it’s a massive headache.


  • Zangoose@lemmy.worldtoProgrammer Humor@lemmy.mlEvil Ones
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    7 days ago

    This is the case for literally all interpreted languages, and is an inherent part of them being interpreted.

    It’s actually the opposite. The idea of “types” is almost entirely made up by compilers and runtime environments (including interpreters). The only thing assembly instructions actually care about is how many bits a binary value has and whether or not it should be stored as a floating point, integer, or pointer (I’m oversimplifying here but the point still stands). Assembly instructions only care about the data in the registers (or an address in memory) that they operate on.

    There is no part of an interpreted language that requires it to not have any type-checking. In fact, many languages use runtime environments for better runtime type diagnostics (e.g. Java and C#) that couldn’t be enforced at runtime in a purely compiled language like C or C++. Purely compiled binaries are pretty much the only environments where automatic runtime type checking can’t be added without basically recreating a runtime environment in the binary (like what languages like go do). The only interpreter that can’t have type-checking is your physical CPU.

    If you meant that it is inherent to the language in that it was intended, you could make the case that for smaller-scale languages like bash, Lua, and some cases Python, that the dynamic typing makes it better. Working with large, complex frontends is not one of those cases. Even if this was an intentional feature of JavaScript, the existence of TypeScript at all proves it was a bad one.

    However, while I recognize that can happen, I’ve literally never come across it in my time working on Typescript. I’m not sure what third party libraries you’re relying on but the most popular OAuth libraries, ORMs, frontend component libraries, state management libraries, graphing libraries, etc. are all written in pure Typescript these days.

    This next example doesn’t directly return any, but is more ubiquitous than the admittedly niche libraries the code I work on depends on: Many HTTP request services in TypeScript will fill fields in as undefined if they’re missing, even if the typing shouldn’t allow for that because that type requirement doesn’t actually exist at runtime. Languages like Kotlin, C#, and Rust would all error because the deserialization failed when something that shouldn’t be considered nullable had an empty value. Java might also have options for this depending on the serialization library used.


  • As a TypeScript dev, TypeScript is not pleasant to work with at all. I don’t love Java or C# but I’d take them any day of the week over anything JS-based. TypeScript provides the illusion of type safety without actually providing full type safety because of one random library whose functionality you depend on that returns and takes in any instead of using generic types. Unlike pretty much any other statically typed language, compiled TypeScript will do nothing to ensure typing at runtime, and won’t error at all if something else gets passed in until you try to use a method or field that it doesn’t have. It will just fail silently unless you add type checking to your functions/methods that are already annotated as taking in your desired types. Languages like Java and C# would throw an exception immediately when you try to cast the value, and languages like Rust and Go wouldn’t even compile unless you either handle the case or panic at that exact location. Pretty much the only language that handles this worse is Python (and maybe Lua? I don’t really know much about Lua though).

    TLDR; TypeScript in theory is very different from TypeScript in practice and that difference makes it very annoying to use.

    Bonus meme:



  • Zangoose@lemmy.worldtomemes@lemmy.worldHell Yeah
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    29 days ago

    Hey, graduating Gen Z here, where are those mythical high-paying remote jobs? Hell, where’s somewhere that will actually look at my resume? People that got hired during COVID got laid off and now we’re competing with people who have 2-4 years of experience for a junior position, inflation is significantly higher and paying for college and rent didn’t exactly get easier. How can you look at the current situation and say we have it easy, just because you also had it rough?








  • Zangoose@lemmy.worldtomemes@lemmy.worldIts Time
    link
    fedilink
    arrow-up
    3
    ·
    2 months ago

    I’m going to assume no to your first part since a lot of the documents surrounding the project are only being declassified now (and a lot of the details are still classified apparently)

    To your second part, I was paraphrasing but the video I linked also called it a “backyard bomb” so the the project was probably being worked on around the time the terminology for that “scale” was made


  • Zangoose@lemmy.worldtomemes@lemmy.worldIts Time
    link
    fedilink
    arrow-up
    35
    ·
    2 months ago

    ELI5 for people who don’t know what project sundial is because I didn’t know about it until I saw that video:

    In the 1950’s the guy who invented the Hydrogen nuclear bomb made a theoretical design for a bomb that would send the entire planet into a nuclear winter. The bomb would be detonated in somewhere in the US because it was so powerful that both the US and whoever on the globe they were trying to hit would get destroyed either way.

    Here is the video the meme is referencing: https://youtu.be/E55uSCO5D2w








  • To me at least angular makes a bit more sense than React’s way of doing things does. React tries to be functional with its components and yet it seems like they end up basically trying to mimic classes with useState and useEffect. To me Angular’s class-based approach makes a bit more sense (though I am primarily interested in backend development more than frontend so that could be why)

    It does kind of fall into a lot of the traps of Object-Oriented programming though so I can see why a lot of people don’t like it