- Most saliently, you called his framework “React Native Web” over and over again despite him saying “React Native for Web” every single time.
- Whatever you thought the framework’s name was going into the interview, and for whatever reason you thought it, when your guest describes their own work with one name USE THAT NAME.
- For example, he clearly said his problem with the CSS framework replacing the Style object was that it would add overhead, not that it would make low-level styling impossible (no web framework has that power unless it’s malicious).
- His point was that if you’re writing a framework that does low-level CSS operations under one paradigm (React Native for Web), it’s wasteful to load an entirely different framework that does the same work under a different paradigm (CSS framework).
- Please, either listen better, or after the interview ask the interviewee if they’d like you to preamble the podcast with any corrections of what you said.
Download past episodes or subscribe to future episodes of The React Podcast by Changelog Media for free.
Continue reading “The React Podcast by Changelog Media on Apple Podcasts”
- Flutter should have been a predecessor to React Native.Why I think Google should have launched Flutter, a couple years ago.There has been much activity in “Building apps for multiple platforms, using a single code base” camp, in recent years.
- Apple, as we know it, would not have come forward, anyway, under any circumstance, to give developers a framework like React Native or Flutter but Google could have!
- It should have always been like, mobile platforms, act more like web browsers, where they provide us, developers, with a standardized set of APIs, which we can use to write native cross platform apps.
- Facebook, being the company, which has heavy apps, used by billions of people across the globe, faced a problem of maintaining two separate code bases and came up with a solution in the form of React Native.
- Google owns Android, so in my opinion it was better positioned as compared to Facebook to launch a native cross-platform framework, as it could have easily hooked into its operating system.
There has been much activity in “Building apps for multiple platforms, using a single code base” camp, in recent years. Facebook is getting all the love from the developer community and a large…
Continue reading “Flutter should have been a predecessor to React Native.”
- Like a lot of people in this Twitter thread, I didn’t really understand that React Native was even for building on the web.
- I thought it was a way to write React to build native mobile apps.
- Nicolas has a whole “React Native for Web” repo though, explaining otherwise.
- But, if you have a React-based website already, and either have or want a native mobile app, then it seems like this is worth exploring.
How do we convince web developers that React Native has already solved many of the hardest GUI problems for them? Go back in time and release React Native before React DOM? Is there an easier way…— Nicolas (@necolas) March 1, 2018 Like a lot of people in this Twitter thread, I didn’t really understand that
Continue reading “React Native: A Better DOM?”
- A folder for your code, a folder for your demo app (plus dev server and hot loading, yay\o/), a folder that you should use and I didn’t, some build stuff for shipping… – – Basically, it gives you everything you need so you can focus on your component and don’t…
- You need a demo page so you can show off your component in action.
- react-lazyload-fadein, for example, has a demo page that shows off different ways you can use it.
- People will find out about your component in different ways.
- Especially if someone could figure out how to slurp in the README file and make that demo page for you 🤔 – – The React community is a bit silly and loves to invent new patterns to bicker about.
Continue reading “What I learned making my first open source React component”
- Iâve been working with React for almost 3 years now, and it led me to also try other functional languages, so in this sense, React was really helpful for my career.What do you think is the future of web and mobile development?Thatâs difficult to say.
- Whatâs your most awaited feature in testing tools?Obviously, Jest will never be completely automated, on the other hand, if you look at snapshot testing, that kind of is Jest is doing a major part of the job, generating something that you only manage and approve changes.
- I know how difficult it is to organize, how much time and effort you need, and Iâm really grateful that someone experienced is bringing a React conference to Berlin, so Iâm excited.
- I hope itâs gonna be a lot of fun and I get to meet new people, see how they use React in their jobs.Where do you get your inspiration for being an MC?This is not the first time for me, and ever since I was one some time ago, I…
An MC can often make or break a conference, and we couldn’t be more grateful to Robin for taking up this challenge! In the following interview, we discuss his career in software development and his…
Continue reading “Meet our MC 👋 – React Day Berlin – Medium”
- Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
- Already on GitHub?
- Sign in to your account
zipkin – Zipkin is a distributed tracing system
Continue reading “zipkin-ui renovation · Issue #1577 · openzipkin/zipkin · GitHub”
- My first question is what frameworks are people using at work vs for their personal projects.
- From the poll, it seems that slightly more organizations use Angular over React at work.
- However, people seem to prefer React over Angular for their personal projects.
- The survey also showed that most people are happy with their current framework and not wanting to upgrade; but those that did want to upgrade choose React over the alternatives.
- The data shows that the big driver is Angular with only a mediocre number of projects in React using it.
For the past couple of months, I have been talking to people and asking myself a couple of questions in regard to the state of front-end development today. I figured what better way than to create a survey and see if we can’t make some sense out of the current state of things in the community. We had a amazing number (~890) of people who took a minute out of their day and answered these questions so a huge thank you to those who participated!
Continue reading “Front-end Developer Survey 2017”
- The React Native monthly meeting continues!
- Here are the notes from each team: – – Trying to lower the entry barrier for the developers embracing React Native with the following things: – – The next session is scheduled for Wednesday 10, October 2017.
- As this was only our fourth meeting, we’d like to know how do these notes benefit the React Native community.
- Feel free to ping me on Twitter if you have any suggestion on how we should improve the output of the meeting.
The next session is scheduled for Wednesday 10, October 2017. As this was only our fourth meeting, we’d like to know how do these notes benefit the React Native community. Feel free to ping me on Twitter if you have any suggestion on how we should improve the output of the meeting.
Continue reading “React Native Monthly #4”
- Review our standards and practices so that you can be familiar with important topics like milestones, the Elon-Musk-bot, communication guidelines and how NOT to make your team-mates angry.Table of ContentsWhy the Chingu Voyage cohort exists [1 min]Schedule [1 min]Standards + The Builder’s Pledge [3 min]Essential skills to learn before you start [10–200 min]The Build-2-Learn Project Roadmap (Acts+Milestones) [1 min]Why the Chingu-Voyage cohort existsThe Chingu-Voyage cohort exists to give motivated learners a community, environment and challenge to accelerate their skills, be accountable, as well as an opportunity to gain experience in a remote dev team.Why is this important?There are more people learning to code (and competing for jobs) than ever before.
- Put simply: the Voyage cohort is where people build projects.Voyage-2’s ScheduleSeptember 15 — Prep Packet goes outSeptember 21 — Voyage-2 StartsSeptember 24 — Teams launchOctober 3 — Act 1 finished due-dateOctober 10–15 — Sprint 1 due-dateSprints will continue until the project is finished.November 10 — Showcase for finished MVPsSome projects may take more time to complete.
- Those practices (seen below) are now our standards.All members are expected to do a check-in twice a week (NEW TO VOYAGE-2)The check-in style we encourage is:What I did in the last few days?What I’m working on in the next few days?Is there anything blocking my path?I can’t stress enough how important consistent communication is for remote dev projects.
- For anyone new to a Chingu B2L project, this will probably be the biggest skill you learn (regardless of what your team builds).
- The Build-2-Learn Project Roadmap (Acts+Milestones)In Voyage-2, each Build-to-Learn project will have 3 Acts and each act with have 5–10 milestones for the team to complete before they can get to the next act.Act 1 — Project SetupAct 2 — Code sprints (repeat until MVP)Act 3 — Closure+ShowcaseACT 1 = Start button, ACT 2 = the circle, ACT 3 = the mountain-topNote: when the cohort launches you’ll get a document that shows in detail what each milestone is, including any resources we have for that milestone, any examples of the milestone from former teams and due dates for each Act.That’s it, you’re all set!Have fun preparing for the Voyage-2 cohort!
Review our standards and practices so that you can be familiar with important topics like milestones, the Elon-Musk-bot, communication guidelines and how NOT to make your team-mates angry. The Chingu…
Continue reading “Voyage-2 Prep — Overview of what you need to know – Chingu – Medium”
- People practising an unconventional lifestyle, living with lightsome and unwaried optimism; careless about social norms, cheerful.
- Outlawed highwaymen in the 18-19th century; later legendary figures in the public mind, fighting for social justice; today young striplings, taking their own way.
Continue reading “Today I added a @reactjs music player to R1D57 #100DaysOfCode 😬 IT WAS A TOUGH ONE 😬”