That’s how you should format a date in JS/TS!

I heard Google has prepared an AI for solving competitive programming questions by training models based on problems and solutions from GitHub.
*devil smile*...on my way to flood GitHub with wrong solutions. Ciao!

typescript, I HATE you!

ME: Trying to extend Subject and override Subject.subscribe(PartialObserver<T>)

ME: export class MySubject<T> extends Subject<T> {
subscribe(obs?:PartialObserver<T>): Subscription {
return super.subscribe(obs);
}
}

ME: compile
TS: Compilation error! No such method to override!

ME: load the app -- ERROR

ME: recompile
TS: Compilation error! No such method to override!

ME: load the app -- works perfectly

:confusedjackie:

Make up your mind! So is that class compileable or not???
If not -- how the fuck does it work then???
If yes -- why the fuck do you yell in my face with all those errors???

**Sees a different error after hours of debugging the previous one**

ME (crying inside) - What type of sorcery is this?

CAN 👏 PEOPLE 👏 STOP 👏 ADDING 👏 `/// <reference lib="dom">` 👏 TO 👏 NODE.JS 👏 PACKAGES

It's a Node.JS package, for fuck's sake. But for SOME reason, sometimes to get around the lack of `URL` and `URLSearchParams` in @types/node, people keep including the *entire* DOM typings in their definition files/TypeScript files!

Sometimes I upgrade my deps in a Node.JS project and find that DOM typings have been added, causing errors when trying to use the global `URL`/`URLSearchParams` (I've shimmed these so that these (Node.JS versions) are in the global namespace). Then you have to search in all your dependencies for which one is including the DOM definitions.

I'm still using .then().catch() instead of the async await.
So, first of all, Fuck you for calling it a STANDARD now. its nowhere near to be called standard. You wanna get some data from an API? Wanna call it using axios or fetch? What if the server is down? what if there's an error that you don't even know existed? Where do I get that kinda error in async await? try-catch? no thanks :| I'm good -_-

The day I realised There is an AngularJS before Angular 2

In our t ch stack, we have multiple components, most of them are backend, but 2 of them are fronnt end.

The first one is a straight Angular 4 application, and it has the normal angular structure, a ts file, a css file, a js file.

The other component, has a very weird structure I don't understand to this day.

It has a mix of js and html files, sometimes one inside another.

The js file has some "angular.core.shit" and I thought it should be Angular, but nothing in it resembles any angular project.

After much confusion, I finally came across an AngularJS website which is supposed to be deprecated last year.

Then I came to know of the story of Google taking ove rAngular and releasing Angular 2.

WHO THE FUCK THINKS
THIS SHIT
TS:
```
const a = function(callback: (err:any,data:string) => void):void{
callback(null,'balls');
}

a(function(err:any,data:string){
console.log(err,data)
})
```

IS BETTER THAN THIS
ES6:
```
const a = function(callback){
callback(null,'balls');
}

a(function(err,data){
console.log(err,data)
})
```

kys

I had to contact technical support for an API. I’m pretty sure I was emailing with a bot because I was getting all sorts of stupid replies.

Me: I’m using your SDK for language X. It’s returned null for some properties. In the user portal, I can see there are values for those properties for the transaction. I don’t know why I’m not receiving them on my end.

Tech Support: Hi! I see the following was sent in the API response. [Sends api response to me.] You can also go the the portal to see those values.

Me: Yeah, I know. You just repeated everything I wrote to you. I don’t want to go to the portal. I told you I want to figure out why your SDK doesn’t seem to map those properties correctly when I receive the api response.

TS: Let me look at the docs. I think you need to send the properties you want in your request in order to get them back in the reply from the api. Such as <property>value<property> in the xml message.

🤨 The docs do not say that. They don’t even imply that.

Me: What the fuck?! That makes absolutely no sense. We have already established that the api **is** returning values for those properties. I want to troubleshoot why your SDK is mapping them as NULL.

Any backend devs here working with TypeScript? What are the best framework choices right now? I've been looking at Nest.js, but there seems to be a steep learning curve that might hamper onboarding of my (literally fresh graduate) new hires. There's also Ts.ED, which seems like the fat has been trimmed from it.
I know people will recommend something like, just using express / koa / hapi but I don't think we have the time to work with something super lightweight 😬😬😬. And besides, opinionated frameworks will speed things up for now (we have a lot of crap we want to do this incoming 2022)

I did a challenge for an application which consisted of developing a landing page. I figured i wanna hardcode everything and not use any CMS or editor. Fknally i could use SCSS, ITCSS and BEM and it was the most fun i had in a long time. Going for PUG and TS next!

Open question:

Do you and your dev team openly embrace using a formatter for your projects, or do you not? And why?

My senior dev is trying to argue that it creates too much noise for commits, especially on older files and it's driving me nuts because I religiously use it (default TS formatter in VSCode btw, nothing crazy or super opinionated!)

stateofjs survey reminds me of all that's wrong with JavaScript: too many frameworks each of which has to reinvent the wheel and depend on too many node_modules child dependencies, most don't support TypeScript properly (ever tried to convert a node-express-mongoose tutorial to TS?), there is still no proper type support in JS core language, and browser features get added in form of overly complex APIs instead of handy DOM methods.

Instead the community gets excited about micro-improvements like optional chaining which has been possible in other languages for decades.

At least there is something like TypeScript, but I don't like its syntax either, it's overly verbose and adds too much "Java feeling" to JavaScript in my opinion.

Also there is too much JS in web development, as CSS and HTML seem to have missed adding enough native functionality that works reliable cross browser to build websites in a descriptive way without misunderstanding web dev for application engineering.

After all, I'd rather have frontend PHP than more JavaScript everywhere.

Anyway, at least the survey has the option to choose how satisfied or unsatisfied people are about certain aspects of JS. But I already suspect that most respondents will seem to be very happy and eager to learn the latest hype train frameworks or stick to their beloved React in the future.

Behold! This is the first time in my career when Jest and unit testing in general actually helped me 😂

Spent two days moving from a fucking slow piece of crap called Gatsby to Vite, trying to comprehend the difference between TS aliases, Babel aliases and Linaria aliases. Found an answer inside a totally unrelated issue explaining Jest stuff, good job on documentation, Linaria!

Vite is fast. Crazy fast. Forget about Webpack, Parcel and things alike — Vite doesn't even need to bundle JS.

Gatsby was slow to the point of my computer's audio glitching, I'm not even talking about the OS interface lags.

Vite is fast to the point that I don't actually need a new MacBook.

A year ago I built my first todo, not from a tutorial, but using basic libraries and nw.js, and doing basic dom manipulations.

It had drag n drop, icons, and basic saving and loading. And I was satisfied.

Since then I've been working odd jobs.

And today I've decided to stretch out a bit, and build a basic airtable clone, because I think I can.
And also because I hate anything without an offline option.

First thing I realized was I wasn't about to duplicate all the features of a spreadsheet from scratch. I'd need a base to work from.

I spent about an hour looking.
Core features needed would be trivial serialization or saving/loading.

Proper event support for when a cell, row, or column changed, or was selected. Necessary for triggering validation and serialization/saving.

Custom column types.

Embedding html in cells.

Reorderable columns

Optional but nice to have:

Changeable column width and row height.

Drag and drop on rows and columns.

Right click menu support out of the box.

After that hour I had a few I wanted to test.

And started looking at frameworks to support the SPA aspects.

Both mithril and riot have minimal router support. But theres also a ton of other leightweight frameworks and libraries worthy of prototyping in, solid, marko, svelte, etc.
I didn't want to futz with lots of overhead, babeling/gulping/grunting/webpacking or any complex configuration-over-convention.

Didn't care for dom vs shadow dom. Its a prototype not a startup.

And I didn't care to do it the "right way". Learning curve here was antithesis to experimenting. I was trying to get away from plugin, configuration-over-convention, astronaut architecture, monolithic frameworks, the works.

Could I import the library without five dozen dependancies and learning four different tools before getting to hello world?
"But if you know IJK then its quick to get started!", except I don't, so it won't. I didn't want that.

Could I get cheap component-oriented designs?

Was I managing complex state embedded in a monolith that took over the entire layout and conventions of my code, like the world balanced on the back of a turtle?

Did it obscure the dom and state, and the standard way of doing things or *compliment* those?

As for validation, theres a number of vanilla libraries, one of which treats validation similar to unit testing, which seems kinda novel.

For presentation and backend I could do NW.JS, which would remove some of the complications, by putting everything in one script. Or if I wanted to make it a web backend, and avoid writing it in something that ran like a potato strapped to a nuclear rocket (visual studio), I could skip TS and go with python and quart, an async variation of flask.
This has the advantage that using something thats *not* JS, namely python, for interacting with a proper database, and would allow self-hosting or putting it online so people can share data and access in real time with others.

And because I'm horrible, and do things the wrong way for convenience, I could use tailwind.
Because it pisses people off.

How easy (or hard) would it be to recreate a basic functional clone of the core of airtable?

I don't know, but I have feeling I'm going to find out!