MJ

@mjackson

Building better websites with

Carlsbad, CA
ಜನವರಿ 2007 ಸಮಯದಲ್ಲಿ ಸೇರಿದ್ದಾರೆ

ಟ್ವೀಟ್‌ಗಳು

ನೀವು @mjackson ಅವರನ್ನು ತಡೆಹಿಡಿದಿರುವಿರಿ

ಈ ಟ್ವೀಟ್‌ಗಳನ್ನು ವೀಕ್ಷಿಸಲು ನೀವು ಖಚಿತವಾಗಿ ಬಯಸುವಿರಾ? ಟ್ವೀಟ್ ವೀಕ್ಷಣೆಯು @mjackson ಅವರ ತಡೆತೆರವುಗೊಳಿಸುವುದಿಲ್ಲ

  1. ಅವರು ಮರುಟ್ವೀಟಿಸಿದ್ದಾರೆ
    2 ಗಂಟೆಗಳ ಹಿಂದೆ

    📝 Wrote some thoughts around how the web’s principles are reflected in modern tools like and

    ರದ್ದುಗೊಳಿಸು
  2. 17 ಗಂಟೆಗಳ ಹಿಂದೆ

    I’ve heard more than one person using say how they were surprised to realize after a while that they were essentially a “backend developer”, which is something that they had never really identified with before. But Remix blurs the lines between the backend and front!

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  3. 17 ಗಂಟೆಗಳ ಹಿಂದೆ

    Locality of reference was a huge factor in the design of our route modules in . Having your component (view) in the same file as the functions that handle reading and writing it’s data (loader/action) eases the transition of primarily front-end devs into full stack.

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  4. 18 ಗಂಟೆಗಳ ಹಿಂದೆ

    I like this idea of “React sprinkles”. You can use as much or as little React as you like in . This helps it meet the needs of really client-heavy apps, but also very minimal apps that don’t need much interactivity. Remix spans the whole spectrum 🌈

    ರದ್ದುಗೊಳಿಸು
  5. 19 ಗಂಟೆಗಳ ಹಿಂದೆ

    This is my favorite week of the year, leading up to Easter Sunday. The message of Easter is redemption, peace, healing, and triumph over death. No matter what is broken, it can be fixed through the atonement of Jesus Christ. Have a great week ❤️ 👉

    ರದ್ದುಗೊಳಿಸು
  6. ಏಪ್ರಿ 9

    If you wanna know where to find me after this tech thing is over, I’ll be in the garden

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  7. ಏಪ್ರಿ 9

    You know what would be really fun? Working in a nursery selling plants. 🌻 You’d just get to sit there all day and help people grow beautiful things and answer their questions about what soil to use and which kinds of plants to pick. No computers. Just plants. 😅

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  8. ಏಪ್ರಿ 9

    I was on a podcast recently where the interviewer was genuinely pretty shocked when I used the words “React” and “web standards” in the same breath. But it isn’t React’s fault if *you* aren’t using web standards and progressive enhancement. That’s your job!

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  9. ಏಪ್ರಿ 9

    For example, nothing about React says that your page needs to be a janky mess with spinners everywhere. But lots of “React sites” are. Why? Take a closer look at your tools. Pop open the network tab. Are your tools getting in the way?

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  10. ಏಪ್ರಿ 9

    Unfortunately I think when some of these people say “React” what they mean is “my React framework”. Like when people in the Rails community said “Ruby” but really meant “Ruby on Rails”. React is very flexible. If it feels busted to you, it might be your framework’s fault.

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  11. ಏಪ್ರಿ 9

    I’ve been seeing more and more people bemoaning the widespread use of React lately. Wishing for something else to come along. Don’t forget: the underlying tech is HTML! Treat React as just a tool for generating and manipulating HTML and you will have a much better time with it.

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  12. ಏಪ್ರಿ 9

    Does support progressive enhancement and server rendering? I couldn’t find anything about it in their docs.

    ರದ್ದುಗೊಳಿಸು
  13. ಏಪ್ರಿ 8
    ರದ್ದುಗೊಳಿಸು
  14. ಏಪ್ರಿ 8
    ರದ್ದುಗೊಳಿಸು
  15. ಅವರು ಮರುಟ್ವೀಟಿಸಿದ್ದಾರೆ
    ಏಪ್ರಿ 8

    Reminder that there is no "Framework War" among the people building the frameworks, nor people trying to "unseat the incumbent". If you love Remix, turn your swords to plowshares and have fun. For our part, all we think about is making your React Router apps even better.

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  16. ಅವರು ಮರುಟ್ವೀಟಿಸಿದ್ದಾರೆ
    ಏಪ್ರಿ 7

    Want to contribute to open source? 1. Go to 2. Try to reproduce bugs in a PR: 3. If you can't, say so, and we'll close it 4. If it's not a bug (feature request/question), say so and we'll transfer it to a discussion.

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  17. ಏಪ್ರಿ 6

    In a world where a single tweet can be used as the basis for costly lawsuits and possibly even public policy, we have to wonder about how an edit button could change the outcomes!

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  18. ಏಪ್ರಿ 6

    And I mean, beyond the physical scaling implications (ie how you would actually *build* it) just think of all the social and legal implications. For example, let’s say Elon tweets about a certain stock being over priced. And then edits his tweet a minute later. What happens?

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  19. ಏಪ್ರಿ 6

    Trying to build an “edit” feature into a massively scaled system that has been optimized for reads over more than a decade seems like a crazy hard task, yet some people seem to think it’s so easy. All depends on perspective, I guess 😅

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು
  20. ಏಪ್ರಿ 6

    I’m not sure how their systems have changed since I worked there a decade ago, but they used to have “fan out” queues to distribute tweets to all your followers. These queues were optimized for reads. Deleting a tweet didn’t really delete it. It just put a “deleted” marker on it.

    ಈ ಥ್ರೆಡ್ ತೋರಿಸಿ
    ರದ್ದುಗೊಳಿಸು

ಲೋಡಿಂಗ್ ಸಮಯ ಸ್ವಲ್ಪ ತೆಗೆದುಕೊಳ್ಳುತ್ತಿರುವಂತೆನಿಸುತ್ತದೆ.

Twitter ಸಾಮರ್ಥ್ಯ ಮೀರಿರಬಹುದು ಅಥವಾ ಕ್ಷಣಿಕವಾದ ತೊಂದರೆಯನ್ನು ಅನುಭವಿಸುತ್ತಿರಬಹುದು. ಮತ್ತೆ ಪ್ರಯತ್ನಿಸಿ ಅಥವಾ ಹೆಚ್ಚಿನ ಮಾಹಿತಿಗೆ Twitter ಸ್ಥಿತಿಗೆ ಭೇಟಿ ನೀಡಿ.

    ಇದನ್ನೂ ಸಹ ನೀವು ಇಷ್ಟಪಡಬಹುದು

    ·