HN user

adrianhel

99 karma
Posts2
Comments146
View on HN

Another thing I painfully realized: It that is not a good idea to document HTML in HTML.

<details> <summary> It's not a good idea </summary> really. &lt/details>

It's the snappiest browser at the moment and I love its render as text function and automatic ad blocking on mobile. I've made a permanent switch on mobile, but I tend to miss the Chrome dev tools whenever I use it on a computer.

It's also wonderful that the browser is truly privacy conscious.

There is a lot of land in the world. And definitely have the capacity to build the supply chains. It's just that it's slow and expensive while oil, gas and nuclear is fast and cheap.

We need policy changes. Or in a very ideal world, fusion.

From Node to Deno 6 years ago

I agree. But I do like query builders (Knex for Node). I still write and think in SQL, but don't have to write queries as strings.

There should be a Promise.isThenable or Promise.is. Strictly speaking this library checks if a value is a thenable.

With optional chaining I would however use this check:

    typeof x?.then === 'function'
Or if I was code golfin:
    x?.then?.call
The first case does not account for built in prototype extensions and the second has false positives with certain data structures.

So the function in is-promise should be available as Promise.isThenable or Promise.is.

Agree. It's really missing the point of how this has been used in reality for the sake of promoting semantics in an area where semantics rarely matter.

Just use vanilla JS to begin with. If your app has a lot of interaction, you can use React with create-react-app makes things easier.

You can still use vanilla JS, HTML and CSS. And it's not morally wrong.

Assess the requirements. Lots of moving parts and not a whole lot of time? React or Vue lets you draw the big lines quite simply. Need something simple or with fancy animations? Vanilla may be your best bet.

Personally I use vanilla for simpler stuff and React for more complex apps.

Don't worry, just make cool stuff. Nobody ever cares how you built it, just that it works.

Trello still uses CoffeeScript. It really does not matter as long as it works.

PS: You can combine if and when needed.

Some things I'd have loved to be told to build:

    Simple 2d game
    To do app
    Timesheet app
    Implement a clone of x with something extra of your choosing
    Top Twitter celebrity app using its API
    Building a search engine
    Creating a programming language
An issue with the programming courses at my uni was that none of them used a database. The programs were toy apps by design. Instruct students to use sqlite or MongoDB, and encourage them to use PostgreSQL/MySQL.

Our database class did use databases, but we had no integration of the two subjects.