214 Matching Annotations
  1. Feb 2024
  2. victranslates.blogspot.com victranslates.blogspot.com
    1. 原則上問題不複雜:作者要為書的內容負責,譯者要為翻譯品質負責。但在實際運作上,譯者交出譯稿之後,通常經其他人修改就逕自出版,如何修改不會徵詢譯者的意見。 在此情況下,譯文如果被改壞了或改錯了,我認為譯者沒有理由要概括承受,因為責任就在那個改稿者身上。(真要問責,還可以追究下去,但無論如何都很難說是譯者的責任。)

      有道理!

  3. Jan 2024
    1. DRI: Directly Responsible Individual — A title given to the person who is ultimately responsible for making sure a project or task(s) is completed.
    2. It assigns accountability for the whole project, which means it’s less likely for small details and tasks to “fall through the cracks”, those of which could be missed when responsibility is spread among multiple individuals.
  4. Nov 2023
  5. Aug 2023
    1. Thomas Jefferson’s aphorism ‘Do well by doing good’ is timely and trendy in a way it hasn’t been for centuries. Because that ethos for technology entrepreneurs is increasingly recognized as the only way many people will expect firms offering technology innovations to approach them: humbly and with a broader social mission and accounting not just as a corporate social responsibility afterthought, but as a core value of the products and companies themselves
      • for: quote, quote - Lee McKnight, quote - corporate social responsibility
      • quote
        • Thomas Jefferson’s aphorism ‘Do well by doing good’ is timely and trendy in a way it hasn’t been for centuries.
        • Because that ethos for technology entrepreneurs is increasingly recognized as the only way many people will expect firms offering technology innovations to approach them:
          • humbly and
          • with a broader social mission and
          • accounting not just as a corporate social responsibility afterthought, but -as a core value of the products and companies themselves
      • author: Lee McKnight
        • associate professor, Syracuse University School of Information Studies
  6. Jul 2023
    1. The consequences of our current choices bear not juston us. They bear on the continued evolutionary unfoldingof life in the universe. This marks the scale of our currentresponsibility
      • for: human impacts, MET, major evolutionary transition, progress trap, human responsibility to life, CCE, cumulative cultural evolution, playing God
      • comment
        • Very true, in fact our species is in the unprecedented position that
        • human activity, and specifically our cumulative cultural evolution (CCE) now determines the biological / genetic evolutionary future not only of our own species, but of all life on earth.
        • In other words, of evolution itself! -This is an awkward position as we have nowhere near the wisdom to play God and determine the future direction of evolution!
      • References
  7. Jun 2023
    1. I think we have a responsibility not only to ourselves, but also to each other, to our community, not to use Ruby only in the ways that are either implicitly or explicitly promoted to us, but to explore the fringes, and wrestle with new and experimental features and techniques, so that as many different perspectives as possible inform on the question of “is this good or not”.
    1. One) Successful men realize that the most important decision in their life is the woman they choose, because outside of work, this is what they'll be spending most time on. The woman must understand the man's grand ambition, and support them with it. (Cf. Flow & The Intellectual Life as well). Women should be chosen on personality, not looks. Looks fade (attraction as well), personality "stays".

      Two) Everyone deserves an opinion but not everyone deserves a say. Charlie Munger sums this up right: "I don't ever allow myself to have [express] an opinion about anything that I don't know the opponent side's argument better than they do." Or Marcus Aurelius, who says: "The opinion of ten thousand men is of no value if none of them know anything about the subject." In short: Only state your opinion when you can back it up!; knowledge and experience. The same goes for judging opinion (and advice) from others.

      Three) Successful people buy assets when the money is enough. Assets > Luxury. (See also: Rich Dad, Poor Dad, Robert Kiyosaki). Only buy glamor and other "interests" once your assets are there to secure your financial success.

      Four) Be pragmatic. Do what's practical, not what is "sexy". Notice inefficiencies and solve them. The entrepreneurial mindset.

      Five) The morning sets the tone for the rest of the days. Time is subjective, waking up early doesn't matter as much as waking up later. It depends on the person. Someone who wakes up at 10am can be as successful as someone who wakes up at 6am. Instead, what defines success, is a highly effective morning routine.

      Six) The less you talk, the more you listen. Talking less means less mistakes. In addition, the less you talk, the more people will listen when you do speak. It puts extra weight on your message. Listening means analysis and learning.

      Seven) Pick the right opportunity at the right time. Pick the right vehicle. Do the right things in the right order! The advice "don't do what someone says, do what they do" is bullshit, as you can't do what someone is able to do after ten years of experience.

      Eight) Discipline > Motivation. Motivation, like Dr. Sung says, fluctuates and is multifactorial dependent... When you are lead by motivation you will not be as productive. Don't rely on chance. Rely on what is stable.

      Nine) Once a good career has been made, buy A1 assets and hold on to them to secure a financially successful future.

      Ten) Just because you won, you are not a winner. Being a winner is a continuous process, it means always learning and reflecting as well as introspecting. Don't overvalue individual wins but do celebrate them when appropriate.

      Eleven) Build good relationships with the banks early on. At times you need loans to fund certain ventures, when having a good relation with them, this will be significantly easier. Understand finance as early as possible. Read finance books.

      Twelve) Keep the circle small. Acquintances can be many, but real close relationships should be kept small. Choose your friends wisely. "You become the average of the five people you spend most time with." Privacy is important. Only tell the most deep secrets to the Inner Circle, to avoid overcomplication.

      Thirteen) Assume that everything is your fault. Responsibility. It leads to learning. It requires reflection and introspection. It leads to Dr. Benjamin Hardy's statement: "Nothing happens to you, everything happens for you."

      Fourteen) Work like new money, but act like your old money. Combine the hunger of the new with the wisdom of the old.

      Fifteen) Assume that you can't change the world, but slightly influence it. It prevents disappointments and gives a right mindset. Do everything (that has your ambition) with an insane drive. Aim to hit the stars. To become the best of the best.

      Sixteen) Private victories lead to public victories. The solid maxim is the following: "The bigger the public victory, the more private victories went into it." Work in private. Social media doesn't need to known the struggle. Let your results talk for you. This is also why you should never compare yourself to others, but rather to your own past self.

      Seventeen) After extreme experience, the most complicated task will look elegant and effortless. Unconscious competence.

    1. In the layered architecture pattern, each layer fulfills a specific responsibility and role within the application. Some focus on user interface logic, while others handle the execution of business rules. These layers complement each other's unique purposes, but they aren't explicitly reliant on one another to perform their own tasks.
  8. May 2023
    1. This ensures that GetResponse and our customers comply with Anti-Spam laws.

      IMHO, the customer should be able to opt out of this automatic adding if they want more/full control over the footer. Then they can take on the responsibility themselves.

  9. Mar 2023
    1. hese challenges demand an ethos not of technologicalcleverness, but of social prudence, of acting with humility and cautionwhen confronted by risk and uncertainty. The French philosopherHans Jonas calls this the “imperative of responsibility.”

      // - see also Kevin Anderson's presentation on "The Ostrich and the Phoenix" - https://jonudell.info/h/facet/?max=100&expanded=true&user=stopresetgo&exactTagSearch=true&any=ostrich+and+the+phoenix - humans opt for the just-in-time techno path because we can "kick the can down the road" and procastinate and allow the next generation deal with the problem - As Anderson shows, there isn't enough time for renewable energy to scale to make a difference in the short term and the difficult social problem of massive social behavior change is unfortunately the best way to solve the problem - the allure of technology is that it can fix any problem - the reality is that last generation's technology is unfortunately often the source of this generation's problems - technology not only produces progress, but the unintended consequences produce progress traps which become the inspiration for new technology in an endless cycle of self-created problems giving rise to avoidable solutions

  10. Dec 2022
    1. I have yet to see a Snapd or Flatpak build of Audacity that I'm happy with. Those builds are beyond our control as they are made by 3rd parties. I do find it mildly annoying that Flatpak direct users that have problems with their builds to us.

      annotation meta: may need new tag: the runaround?

    1. I just can’t stop dreaming about a perfect world where I could go back to any of my old JavaScript projects with an ease of mind and knowing that everything just works. A perfect world where my program is going to stand the test of time.

      That's a you-problem. The pieces are there—the language is stable, and there's a ludicrously backwards compatible World Wide Wruntime that you can trust to be around—it's on you if it fails.

  11. Nov 2022
    1. I agree that these fields should be whitelisted by ActiveAdmin automatically as it generates them via the form helpers. Regardless of if you use :raise or :log you wouldn't usually want these causing unnecessary noise.
    1. The second situation would be zombie reaping. If the process spawns child processes and does not properly reap them it will lead to a full process table
    2. For both of these concerns we recommend tini. It is incredibly small, has minimal external dependencies, fills each of these roles, and does only the necessary parts of reaping and signal forwarding.
    3. The first being signal handling. If the process launched does not handle SIGTERM by exiting, it will not be killed since it is PID 1 in the container
    4. highly recommended that the resulting image be just one concern per container; predominantly this means just one process per container, so there is no need for a full init system

      container images: whether to use full init process: implied here: don't need to if only using for single process (which doesn't fork, etc.)

    1. Is whatever process you exec in your entrypoint registering signal handlers? A good way to figure this out might be to check whether your process responds properly to e.g. docker stop (or if it waits for 10 seconds before exiting)
    2. Tini does install explicit signal handlers (to forward them, incidentally), so those signals no longer get dropped. Instead, they're sent to Jenkins, which is not running as PID 1 (Tini is), and therefore has default signal handlers
    3. Tini fixes by "forwarding signals": if you send a signal to Tini, then it sends that same signal to your child process (Jenkins in your case).
    4. A second problem is that once your process has exited, Bash will proceed to exit as well. If you're not being careful, Bash might exit with exit code 0, whereas your process actually crashed (0 means "all fine"; this would cause Docker restart policies to not do what you expect). What you actually want is for Bash to return the same exit code your process had.
    5. When a zombie is created (i.e. which happens when its parent exits, and therefore all chances of it ever being waited by it are gone), it is reparent to init, which is expected to reap it (which means calling wait on it).
    6. In other words, someone has to clean up after "irresponsible" parents that leave their children un-wait'ed, and that's PID 1's job.
    7. Now, unlike other processes, PID 1 has a unique responsibility, which is to reap zombie processes.
    1. Unfortunately most init systems don't do this correctly within Docker since they're built for hardware shutdowns instead. This causes processes to be hard killed with SIGKILL, which doesn't give them a chance to correctly deinitialize things.
    2. According to the Unix process model, the init process -- PID 1 -- inherits all orphaned child processes and must reap them. Most Docker containers do not have an init process that does this correctly. As a result, their containers become filled with zombie processes over time.
    1. When a process loses its parent, init becomes its new parent. init periodically executes the wait system call to reap any zombies with init as parent.
    2. Zombie processes should not be confused with orphan processes: an orphan process is a process that is still executing, but whose parent has died. When the parent dies, the orphaned child process is adopted by init (process ID 1). When orphan processes die, they do not remain as zombie processes; instead, they are waited on by init.
    3. The result is that a process that is both a zombie and an orphan will be reaped automatically.
    1. Let's look at a concrete example. Suppose that your container contains a web server that runs a CGI script that's written in bash. The CGI script calls grep. Then the web server decides that the CGI script is taking too long and kills the script, but grep is not affected and keeps running. When grep finishes, it becomes a zombie and is adopted by the PID 1 (the web server). The web server doesn't know about grep, so it doesn't reap it, and the grep zombie stays in the system.
  12. Sep 2022
    1. What responsibility does a writer bear when construing Utopian or dystopian alternatives to our contemporary world? Are writersof fairy tales unethical and irresponsible when they create false happyendings and delude us into believing that harmony is possible in ourrapidly changing postmodern globalized war-torn world? Is it unethicalto publish fairy tales in all their mass-mediated modes to make as muchprofit as one can by playing with our Utopian desires?

      I never thought about this responsibility! But i think the rest is hyperbolic.. the responsibility does not solely fall on the writer, but also the reader's representation

  13. Jun 2022
    1. Those who are born today are not individu-ally responsible for this burdensome heritage, but we are all respon-sible for the way in which we choose or fail to take it into account inanalyzing the world economic system, its injustices, and the needfor change.

      burdensome heritage [of slavery and colonialism]

  14. May 2022
    1. the underprivileged are priced out of the dental-treatment system yet perversely held responsible for their dental condition.

      How does this happen?

      Is it the idea of "personal responsibility" and "pull yourself up by the bootstraps" philosophy combined with lack of any actual support and/or education?

      There has to be a better phrase or word to define the perverse sort of philosophy espoused by many in the Republican party about this sort of "personal responsibility".

      It feels somewhat akin to the idea of privatize profits and socialize the losses. The social loss is definitely one that is pushed off onto the individual, but who's profiting? Is it really so expensive to fix this problem? Isn't the loss to society and public health akin to the Million Dollar Murray problem?

      Wouldn't each individual's responsibility be better tied to the collective good as well as their own outcomes? How can the two be bound together to improve outcomes for everyone all around?

  15. Apr 2022
    1. Understanding the importance of helping others can also have benefits in your own life, such as reducing your stress. It’s true that you create more responsibility for yourself when you choose to help someone. But this won’t add extra stress to your life. In reality, helping others will allow you to handle stress more easily.

      It's important to understand the valued importance of helping others as it can also help as well especially n the face of reducing your stress. By helping others, you're creating more responsibility, however, this won’t make you feel worse by adding more stress. This is because, helping others allows you to handle stress more easily.

    1. I end up with responsibility (friends complaining to me about this, that, and the other) without control (I can't affect any of those things)

    Tags

    Annotators

  16. Mar 2022
  17. Feb 2022
    1. Remember, our wizard controller is responsible for showing and updating steps, but our top-level controller is still responsible for managing our Pet models.
  18. Jan 2022
    1. ReconfigBehSci. (2022, January 9). Just a thought on this and the general vaccine mandate debate. As a behavioural scientist currently stuck in Germany where this is a live debate, it strikes me that the thoughts below address only part of the population: Those not currently vaccinated. But what about ... 1/2 [Tweet]. @SciBeh. https://twitter.com/SciBeh/status/1480213148032450565

  19. Nov 2021
  20. Oct 2021
    1. Victor Papanek’s book includes an introduction written by R. Buckminster Fuller, Carbondale, Illinois. (Sadly, the Thames & Hudson 2019 Third Edition does not include this introduction. Monoskop has preserved this text as a PDF file of images. I have transcribed a portion here.)

  21. Sep 2021
    1. The willingness to trade other peoples' fundamental rights for preferential tax treatment fits neatly into all three of these, as does the delusion that somehow this can be resolved with sufficient "personal responsibility."

      We know enough about psychology and behavioral economics to know that "personal responsibility" is not going to save us.

      This is in even higher relief when we see laws applied in unclosed systems or where other loopholes exist to help the privileged. Frank Wilhot's idea sums things up fairly well:

      "Conservatism consists of exactly one proposition, to wit: There must be in-groups whom the law protects but does not bind, alongside out-groups whom the law binds but does not protect."

    1. It is also why it's implementation in firefox is completely useless, considering that windows/osx/most linux distros plan to add support for DoH/DoT/DNScrypt resolvers in the near future, so firefox doing it itself will provide no additional benefit.
    1. Users think every Webpack tool/config problem is a problem with a specific package and opens an issue asking for support on the package instead of Webpack. In the past year alone, I’ve had to deal with hundreds of Webpack issues on my repos.
  22. Aug 2021
    1. All answers here which mention scrollHeight/scrollWidth should be adjusted a bit to take body margins into account. Browsers apply default nonzero margins for documents' body element (and it's also applicable to content loaded into frames). The working solution I found is to add this: parseInt(window.getComputedStyle(this.contentDocument.body).margin.
  23. Jul 2021
  24. Jun 2021
    1. Mike: Yeah. I didn't go to school, because my dad thought that if something happened... And I remember one time the cops came to my house, because my little brother was playing outside and it was school hours. And they're like, "What is this kid doing outside?" And I remember him crying outside, because the cops got him. And I was like, "Oh my God, what do I do?"Mike: So I opened the door and my little brother rushes in crying. And then, I don't know, by the grace of God, they left us alone, but they told us that we had to be in school, this and that. And from there we moved. A month later, that's when he got caught up with the thing.Anne: So basically he would go to work, and you would be in charge of the kids?Mike: Yeah.Anne: That's a lot of responsibility to put on—

      Time in the US, Homelife, Parents, Expectations, Siblings, Caring for them

    2. I passed all of them except for my math. My senior year I actually passed it, but I didn't graduate. I just would go to school, literally eat lunch, just get out. It got boring for me and I was really good. I should have never started.

      Time in US - education - dropping out - not graduating

    3. I wanted to do better for myself and for my family, and I felt like that was like a big motivation right there. That push you just need, because you see stuff and you're like, "Dude, I hope that when I have kids, they don't have to go through that." And yeah, that was the push that kind of—

      Time in US - family - having children

    4. Yes. A lot of them. A lot of things. If we didn't do, they probably would have had to do, because if it wasn't me, it would've been the next one. And they did have to go through that stuff too, in a way, because sometimes I couldn't do it, because I'd be in school doing something really, really important.

      Time in US - siblings also take responsibilities - employment

    5. So sometimes I would have to miss school, sometimes I wouldn't go to school. So then it was chaos.

      Time in US - education - employment

    6. I was the only one that talked English, and it was just hard.

      Time in US - learning/speaking English

    7. I used to cry sometimes, because I would wake up at 5:00 in the morning. I'm like, "Dude, I'm a little kid I don't deserve this." You know what I mean?

      Time in US - childhood - memories

    8. I was used to it at least, because growing up my mom didn't have a job so she couldn't provide for us even if she wanted to, because she's illegal. So what we would do is we would make fake CDs, and every morning I would just wake up, go to different little towns and stuff, sell CDs.

      Time in US - homelife - taking care of family - employment - job - responsibility

    1. His wife or his ex-wife was Mexican. He spoke perfect Spanish, so he and my mother were very—they would joke around. It was extremely funny to watch because when other people were around, this big, big figure would joke around with my mom and everyone would be like, "Oh, my God. What's happening?" But my mom was just that kind of person. His sons, I actually grew up with. I know his sons, extremely handsome, very educated people, very, very, very nice. I visited their home quite a few times in Hyde Park. They were great people.

      Time in the US - employment

  25. May 2021
    1. ReconfigBehSci. (2020, November 18). @danielmabuse yes, we all make mistakes, but a responsible actor also factors the kinds of mistakes she is prone to making into decisions on what actions to take: I’m not that great with my hands, so I never contemplated being a neuro-surgeon. Not everyone should be a public voice on COVID [Tweet]. @SciBeh. https://twitter.com/SciBeh/status/1329002783094296577

  26. Apr 2021
    1. The role of the terminal emulator process is:

      Shows the relationship between a "terminal emulator" and a pseudoterminal, as alluded to in the intro:

      is a pair of pseudo-devices, one of which, the slave, emulates a hardware text terminal device, the other of which, the master, provides the means by which a terminal emulator process controls the slave.

    1. Although echo "$@" prints the arguments with spaces in between, that's due to echo: it prints its arguments with spaces as separators.

      due to echo adding the spaces, not due to the spaces already being present

      Tag: not so much:

      whose responsibility is it? but more: what handles this / where does it come from? (how exactly should I word it?)

  27. Mar 2021
    1. The elimination of what is arguably the biggest monoculture in the history of software development would mean that we, the community, could finally take charge of both languages and run-times, and start to iterate and grow these independently of browser/server platforms, vendors, and organizations, all pulling in different directions, struggling for control of standards, and (perhaps most importantly) freeing the entire community of developers from the group pressure of One Language To Rule Them All.
  28. afarkas.github.io afarkas.github.io
    1. Webshim is also more than a polyfill, it has become a UI component and widget library. Webshim enables a developer to also enhance HTML5 capable browsers with more highly customizable, extensible and flexible UI components and widgets.

      And now that it's deprecated (presumably due to no longer needing these polyfills), not only do the polyfills go away (no longer maintained), but also these unrelated "extras" that some of us may have been depending on are now going away with no replacement ...

      If those were in a separate package, then there would have been some chance of the "extras" package being updated to work without the base webshims polyfills.

      In particular, I was using $.webshims.addCustomValidityRule which adds something that you can't do in plain HTML5 (that I can tell), so it isn't a polyfill...

    1. Using ::delegates works exactly like the Forwardable module in Ruby, with one bonus: It creates the accessors in a module, allowing you to override and call super in a user module or class.
  29. Feb 2021
    1. Maintaining the builds of your repositories should be everyone’s job. Instead of relying on that one build person in the team, Travis CI makes infrastructure and configuration a team responsibility.
    1. An endpoint links your routing with your business code. The idea is that your controllers are pure HTTP routers, calling the respective endpoint for each action. From there, the endpoint takes over, handles authentication, policies, executing the domain code, interpreting the result, and providing hooks to render a response.
    1. I am a delegation junkie. Whenever possible, I assign tasks and responsibilities originally assigned to me onto others.
    2. In the classroom, I delegate responsibilities to my students at a rate that astounds people. There is almost nothing that I will not allow my students to do, including teaching my lessons whenever possible. My students take full and complete ownership of the classroom, whether they like it or not, and as a result, they possess great ownership of their learning.
    3. They fail to understand the importance of autonomy when delegating responsibilities.
    4. They lack faith in the capacity of others.
    1. One of the main reasons to work with components is re-usability and portability, but also a delegation of responsibilities. Adding a component should be as easy as simply adding the component without having to know the inner workings (or markup) of this component. A consumer should only be aware of the properties, methods and events of a component. In order to style a child component one has to be aware of the markup as well, which violates this 'delegation of responsibility'-principle.
    1. with ActiveForm-Rails, validations is the responsability of the form and not of the models. There is no need to synchronize errors from the form to the models and vice versa.

      But if you intend to save to a model after the form validates, then you can't escape the models' validations:

      either you check that the models pass their own validations ahead of time (like I want to do, and I think @mattheworiordan was wanting to do), or you have to accept that one of the following outcomes is possible/inevitable if the models' own validations fail:

      1. if you use object.save then it may silently fail to save
      2. if you use object.save then it will fail to save and raise an error

      Are either of those outcomes acceptable to you? To me, they seem not to be. Hence we must also check for / handle the models' validations. Hence we need a way to aggregate errors from both the form object (context-specific validations) and from the models (unconditional/invariant validations that should always be checked by the model), and present them to the user.

      What do you guys find to be the best way to accomplish that?

      I am interested to know what best practices you use / still use today after all these years. I keep finding myself running into this same problem/need, which is how I ended up looking for what the current options are for form objects today...

    2. Trust me, I thought a lot about #validate and its semantics, and I am gonna make it even more "SRP" by making Form#errors and #valid? semi-public. All that happens via #validate reducing the possible wrong usage for users.
    3. About #validate which fill attributes of the form, I think it's a problem of architecture and clarity. If you respect the Single Responsabilty Principle, you must to have two methods. This is wrong. SRP means your class does exactly one thing, which is reflected in a single public method. The more methods you expose, the less SRP you go.
    4. About #validate which fill attributes of the form, I think it's a problem of architecture and clarity. If you respect the Single Responsabilty Principle, you must to have two methods. The validate method do two thing really different.
    1. Now let me ask you, do you write JS for a single page application differently from a "traditional" web application? I sure hope you do! In a "traditional" application, you can get away with being sloppy because every time the user navigates to a new page, their browser destroys the DOM and the JavaScript context. SPAs, though, require a more thoughtful approach.
    2. where's the code that unloads the table-sorter plugin when the page unloads? There isn't any. There didn't need to be back in the day because the browser handled the cleanup. However, in a single-page application like Turbolinks, the browser doesn't handle it. You, the developer, have to manage initialization and cleanup of your JavaScript behaviors.
    3. When people try to port traditional web apps to Turbolinks, they often run into problems because their JS never cleans up after itself.
    4. All Turbolinks-friendly JavaScript needs to: Initialize itself when a page is displayed Clean up after itself before Turbolinks navigates to a new page.
  30. Jan 2021
    1. They can tackle all aspects of a problem, from initial data collection and data conditioning to drawing conclusions. They can think outside the box to come up with new ways to view the problem, or to work with very broadly defined problems: ‘here's a lot of data, what can you make from it?’"

      Data scientists are not just hired to mine and run the data, they are also making the decisions that the data has directed them to. They can do this by making data visuals to show their colleagues that will lead to the best decisions for the company.

  31. Dec 2020
    1. Or maybe a better standard was in the humanitarian world. “There’s a core ethical principle called the responsibility to protect, which is about organizations having a primary responsibility to protect their own personnel,” said Abramowitz. “What’s very clear is that many teachers are distrustful because they have been in deeply unsafe situations for a very long time.” Teachers are asked to deal with school shootings, violent children, aggressive adults, poverty, online bullying—a host of complex social problems that aren’t part of their job description, she said. “Educators are so abandoned, they no longer trust in their own system to protect them.
    1. it focuses on compiling non-standard language extensions: JSX, TypeScript, and Flow. Because of this smaller scope, Sucrase can get away with an architecture that is much more performant but less extensible