lobut

1

Then the Billionaire LeBron James decided to sell a pair of sneakers with MLK Jr's name on it 🤦‍♂️

https://www.si.com/fannation/sneakers/news/nike-lebron-james-criticized-over-mlk-shoes

Yeah, if these tactics were used on the January 6 supporters we'd have Fox News and people screaming about the constitution and amendments and freedom. The Joe Slowgan would spend weeks talking about how creepy this all is and go slippery slope.

1

lobut @lemmy.ca 4d ago

That is a very fair statement.

7

lobut @lemmy.ca 4d ago

Yeah, I mean it's as Carney said in his speech:

We take the world as it is, not as we wish it to be

lobut @lemmy.ca 5d ago

Same. I'm not even patriotic but I will get rid of all the shit I've built up to do this.

1

lobut @lemmy.ca 6d ago

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.

lobut @lemmy.ca 6d ago

According to this CBS article https://www.cbsnews.com/news/one-in-four-workers-in-us-dont-get-any-paid-vacation-time-or-holidays/

1 in 4 workers don't get any paid vacation time. It's from 2019 but it's not like things have gotten better over there since then.

3

lobut @lemmy.ca 6d ago

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.