• 0 Posts
  • 39 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle







  • Yeah, absolutely agreed.

    Btw, you probably already know this, but if you don’t. The later versions of Node can run typescript natively. By “run”, I mean, it can run a subset of the language, if your project indirectly or indirectly references a file that has “decorators” or something like that, then you’ll need to use another compiler.

    ts-node or tsx are runners that I use typically if I just want to “run” something. They’re basically zero config runners and I can debug with them with VS Code.


  • I’m a former .NET dev … I stopped quite a few years ago after I joined a Bay Area company. It was quite a change. React 1 was just coming out and I used to just write bad JS on my webpages and I had to rewrite our front-end in React. Also, ES5 or 6 or whatever was getting popular and we had to transition from CoffeeScript.

    The JS world gave me whiplash after doing so many years of Enterprise .NET. The .NET tools felt so much more polished.

    The fundamentals of Node to me were different than .NET. .NET felt like it had a lot more cruft and “magic” at first. With Node it felt deceptively simpler at first. Then when the require syntax was going away and we had imports but then it wasn’t a real import. It was a TypeScript import or a webpack import that did a require behind the scenes. Then I had to understand why we used typescript but then what was the point of tsc vs babel vs webpack vs esbuild what their roles were and I kind got a bit obsessed with understanding what they did and what was happening under the hood. Then Node officially did do import and I had to understand what that was all about and how it affected our compilers or bundlers.

    Sorry I rant pointlessly. Godspeed on your journey!






  • lobut@lemmy.catolinuxmemes@lemmy.worldWhich git branch are you on?
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    9 months ago

    I will just say that things in tech change a lot in general. That’s just the nature of it.

    If I can do one small thing that makes people feel better, then why wouldn’t I do it?

    I don’t necessarily see that as a connection to a measure of competency. It seems you do and you probably have good reasons to believe so and I would say that I haven’t experienced that.


  • lobut@lemmy.catolinuxmemes@lemmy.worldWhich git branch are you on?
    link
    fedilink
    arrow-up
    23
    arrow-down
    3
    ·
    edit-2
    9 months ago

    If it uses master and it’s too much trouble to get people to switch. It stays master until we can coordinate.

    If I’m starting a new project I use main.

    Why?

    It doesn’t take much to do and it avoids any misunderstandings or arguments and we’ve got work to do. I don’t particular care if you guys are “stuck” on master. If that’s what it is and everyone wants to keep it that way, I don’t have enough will to change it. If it’s under my control, I will change it.





  • I use VS Code mainly and I always want to go to the end of a line and beginning. On Mac it’s like CTRL+E and CTRL+A respectively. On Windows, I was like, I guess I could do Windows Key and arrows but it felt off. Installing Vim bindings on VS Code just fixed this all for me. I love it.

    [edit] for non-VIM users, you can skip words and go-to braces (and delete what’s in them) and highlight within quotes very easily … for function search, the built-in VS Code is really good too. I also have Harpoon installed to hop between files. If it doesn’t appeal to you, then that’s cool too! Whatever keeps you in there. [/edit]

    I’ve tried setting up my own vim stuff and I always bail out because I can’t figure something out. I feel like I need to really sit with it and I’d have the perfect set up for me.

    Lastly, I’ve installed vim for zsh and it’s the best. I can hop all around my terminal and highlight and remove things. It’s so beautiful.