Can I consent to permanent storage somewhere? I love using the timeline in Google Maps!
HN user
adrianhel
Why bother with jQuery? I don't see the value add anymore.
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. </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.
I did not know that. That's great!
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.
And to elaborate on the other side of the argument: JSX creates plain JavaScript objects instead of exposing an "almost-JS" templating language. Additionally you get an enormous amount of flexibility. For some types of apps that is very important.
It's an unstable feature, but you can use import maps with Deno.
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.
For 7% a P/E of 14.285714285 or less would be good to be very precise.
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.
Scrolling on iOS browsers is an utter pain due to rubber band scrolling. It can be solved with -webkit-overflow-scrolling and hard work.
This was really interesting! Would be interesting to see how this interacts with hemochromatosis.
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.
"Singular marketplace" – there's your problem.
With Android, at least you can download an APK.
That's anti-trust at its worst. Sue Apple.
I like this approach. Personally I wait an hour if I get an invalid response and use timeouts of a few seconds between other requests.
Good strategy. By ensuring good documentation in the early stages, the community will likely follow.
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.
That is not the case anymore. Vendor prefixes are discouraged and seldom needed.
DOM diffing is great for most stuff. When you need anything other than "Replace this with that and don't defocus my input fields", DOM manipulations are great. Drag'n'drop is a great example of this.
There is a lot of potential for the imperative APIs for this though. I even made a proposal:
I just hope it doesn't use a butterfly keyboard. Man, Apple is making home office worse than it needs to be.
In Norway we just slipped from the 2nd most infected per capita to the 3rd after government warnings. If your country has >= 1 infected, you should follow the advice at fhi.no/en.
Take action now.
No. Gambling ads are not allowed though. Neither alcohol or smoking are banned, but ads for them are.
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.
That sounds kind of terrifying.
Do anyone here expose real sql querying capabilities to your users?
Then again, REST/RPC are query languages in their own right.
How would one go about securing this thing anyways?
(I agree with the basic sentiment, but find it somewhat unrealistic)
This depends on the app however. For a landing page? No way. For a module within an app I would not mind, as long as lazy imports are used.