My experience is - all errors somebody already had and they are solved. This is the one big benefit of mainstream solutions, you can google everything.
Using node/babel/webpack/ts/react is like playing chess: Within 13 steps, you're debugging a unique error no one else in the universe has ever encounteed.
-
-
-
That's definitely the dream. I've just rarely found it to be the case, personally.
Kraj razgovora
Novi razgovor -
-
-
Gotta use them boilerplate repos!
-
Indeed, and then hope and pray that it never, ever breaks!
Kraj razgovora
Novi razgovor -
-
-
My experience is the exact opposite - the only errors are those that I've already seen or I can easily google the solution. I had your experience with
@Reasonml - every half and hour there's an issue that I had to ask about on Discord because I had no idea how to solve it. -
I have a preference for ocaml and bucklescript-tea because of how comprehensible things are comparatively. One wonders if there's some kind of work habit different people have that contributes to not offending one or the other tooling.
- Još 2 druga odgovora
Novi razgovor -
-
-
It takes you 13 steps!?
- Još 1 odgovor
Novi razgovor -
-
-
Me: I think it's time to learn Angular (4) Me: (googles for tutorials) Tutorial 1: Step 1 - install node Me: (skips to next link) Tutorial 2: Step 1 - install node Me: (skips to next link) Tutorial 3: Step 1 - install node Me: (shuts down computer)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I can do it in 9.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.