283 Matching Annotations
  1. Last 7 days
    1. Configuration style is exactly the same for env_bang and env_setting, only that there's no "ENV!" method... just the normal class: EnvSetting that is called and configured.
  2. Jun 2021
    1. Users who have installed it decided to trust me, and I'm not comfortable transferring that trust to someone else on their behalf. However, if you'd like to fork it, feel free.

      Interesting decision... Seems like the project could have been handed off to new maintainers instead of just a dead-end abandoned project and little chance of anyone using it for new projects now.

      Sure you can fork it, but without a clear indication of which of the many forks in the network graph to trust, I doubt few will take the (massively) extra time to evaluate all options and choose an existing fork as a "leader" (or create their own fork) to go with continuing maintenance...

  3. May 2021
    1. Draft notes, E-mail, plans, source code, to-do lists, what have you

      The personal nature of this information means that users need control of their information. Tim Berners-Lee's Solid (Social Linked Data) project) looks like it could do some of this stuff.

  4. Apr 2021
    1. There is a similar feature in the standard library Logger class, but the implementation here is safe to use with multiple processes writing to the same log file.
  5. Mar 2021
    1. While various shortcomings of the standard run-time library are the obvious, immediate reason for the creation of micro-packages
    2. As to opinions about the shortcomings of the language itself, or the standard run-times, it’s important to realize that every developer has a different background, different experience, different needs, temperament, values, and a slew of other cultural motivations and concerns — individual opinions will always be largely personal and, to some degree, non-technical in nature.
    1. Source maps are on my radar, but i'm playing catchup. See: #124 (comment) for a rundown of where we are right now. Source maps are a pretty big project, it's not li
    1. NOTE: Your strategy should be supported using project management best-practices found within the Management Practices. These practices have been developed by industry, spending billions of dollars each year in projects. Of course, they would want their projects to succeed. Your quality of life is at least this important. Take your efforts seriously and manage your efforts.

      Don't Forget These 10 Project Management Best Practices: https://www.wrike.com/blog/project-management-best-practices-infographic/

  6. Feb 2021
    1. Keeping bootstrap-sass in sync with upstream changes from Bootstrap used to be an error prone and time consuming manual process. With Bootstrap 3 we have introduced a converter that automates this.
    1. note that TRB source code modifications are not proprietary

      In other words, you can build on this software in your proprietary software but can't change the Trailblazer source unless you're willing to contribute it back.

      loophole: I wonder if this will actually just push people to move their code -- which at the core is/would be a direction modification to the source code - out to a separate module. That's so easy to do with Ruby, so this restriction hardly seems like it would have any effect on encouraging contributions.

    1. The great thing about working with reinteractive is you get to work directly with the developers, which is a huge plus. As a technical founder, I find proxying through a project manager adds unnecessary layers of complexity and creates opportunity for human error.
    1. Now if you think about it, PJAX sounds a lot like Turbolinks. They both use JS to fetch server-rendered HTML and put it into the DOM. They both do caching and manage the forward and back buttons. It's almost as if the Rails team took a technique developed elsewhere and just rebranded it.
  7. Jan 2021
    1. A Longform, Media-Rich Narrative

      I think that this would be a neat way to capture and share the experience of work-life balance (or imbalance) of those students who have been instructed to quarantine by capturing their thoughts on trying to continue being a student while living with the stresses of being in quarantine.

    2. A Network Visualization:

      I think that this project type would be useful for examining the politics of citation in journals, topic areas, and/or disciplines. I know this was a topic of discussion at one of the Communication conferences I went to in Fall 2019 and producing a network visualization would be a useful way to help those who disagreed or were skeptical be able to visualize the problem being discussed.

    3. A Gallery of Primary Sources: Making the History of 1989

      I can see myself doing this project type for making a course page based on a syllabus I started for a project in a course I took in the fall. Creating something like this would make the proposal for the class stronger and would be a useful tool in the classroom if I were to get approved to teach the course.

    1. Mobile App for Online Vet Consultations and Prescriptions: A New Frontier for Veterinary Clinics

      When it comes to their pets, humans are extra careful and emotional. They wouldn’t mind zillions of visit to the vets when it comes to keeping their four-legged friends healthy and disease-free .The challenges are numerous, but you cfn overcome many of them with the help of vet app. amd maybe, you are exploring the market and thinking about the prospects of telemedicine app development for vets and pet parents? Get in touch with us to launch your own vet app development project

  8. Dec 2020
    1. Deployment of Project Pages from /docs folder on main branch

      Deployment of Project Pages from /docs folder on main branch.

    1. A perfect web application idea must be a combination of functionalities and amazing designing elements. To make it more clear, let us first discuss what makes a difference between a great web application and an average one.

      it is essential that your web app idea is appropriate in order to achieve your targeted goals. Not only focus on the designing part of your web application, but seamless backend development is important.

    1. Notions, Notes, Ideas and work notes

      My equivalent, as best as I can tell, is:

      • Permanent notes (atomic, linked concepts) = Notions
      • Temporary notes (half-formed thoughts, links, snippets, etc.) = Notes
      • Temporary notes initially, which later become permanent notes = Ideas (see later comment about why)
      • Admin notes (projects, tasks, meetings, etc.) = Work notes
    2. They can be linked to Ideas, Notes or Notions, or may give rise to them, but they serve a purpose firmly rooted in ongoing work. They are always placed within the context, and folder, of a specific project

      Similar to how I've come to think of my "admin" or "operational" notes. They're instrumental in that they serve a purpose that is usually about moving some project forward.

    1. Our team is building open source community tools and Svelte fits our identity as an independent labor of love with an organic community.
    2. With some frameworks, you may find your needs at odds with the enterprise-level goals of a megacorp owner, and you may both benefit and sometimes suffer from their web-scale engineering. Svelte’s future does not depend on the continued delivery of business value to one company, and its direction is shaped in public by volunteers.
  9. Nov 2020
    1. There are actually 3 other libraries that implements material in svelte, i hope this to become the community favorite because using MDC underneath it implements correctly Material guidelines.
    2. @monkeythedev I am curious how do you "organize" your work - You forked https://github.com/hperrin/svelte-material-ui and https://github.com/hperrin/svelte-material-ui is not very active. Do you plan an independent project ? I hope the original author would return at some times, if not, i'll see
    1. In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.
    2. I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)
    1. In July 2010, Microsoft let go Jimmy Schementi, one of two remaining members of the IronRuby core team, and stopped funding the project.[19][20] In October 2010 Microsoft announced the Iron projects (IronRuby and IronPython) were being changed to "external" projects and enabling "community members to make contributions without Microsoft's involvement or sponsorship by a Microsoft employee".
    1. This conflicts in very basic ways with what other engineering disciplines expect. Toyota's stylists might be able to sell their renderings in art galleries, but you can't drive to work in one. In software, you can.

      I don't really understand the sentence. Does it mean that you can't really use a project's design until it's built, in classical engineering, while instead with software all that detailed design is actually the product?

  10. Oct 2020
    1. Industrialization: You can easily chop your form validations into smaller independent pieces that can be developed by separate teams in paralell with no dependencies.
    1. When I say that my experience is that it means it's time to split up your components, I guess I mean that there tends to be a logical grouping between all the things that care about (for example) sqr_n, and in Svelte, logical groupings are expressed as components.
    1. Naptha, its current name, is drawn from an even more tenuous association. See, it comes from the fact that "highlighter" kind of sounds like "lighter", and that naptha is a type of fuel often used for lighters. It was in fact one of the earliest codenames of the project, and brought rise to a rather fun little easter egg which you can play with by quickly clicking about a dozen times over some block of text inside a picture.

      Now if only I could do this with my Hypothes.is annotations! Talk about highlighting!

  11. Sep 2020
    1. Many people recently are complaining about bundler performance. But I don’t think any tool is going to solve performance problems. Bundlers can try innovative ideas such as multi-threading and improved caching, but you’re always going to hit a limit. If you’re having performance problems, it’s more likely because you’re not keeping tabs of what you’re importing, and haven’t considered splitting your project into multiple projects.
    1. Developing software is usually easier if you break your project into smaller separate pieces, since that often removes unexpected interactions and dramatically reduces the complexity of the problems you'll need to solve
    1. The main rationale for this PR is that, in my hones opinion, Svelte needs a way to support style overrides in an intuitive and close to plain HTML/CSS way. What I regard as intuitive is: Looking at how customizing of styles is being done when applying a typical CSS component framework, and making that possible with Svelte.
    1. The more I think about this, the more I think that maybe React already has the right solution to this particular issue, and we're tying ourselves in knots trying to avoid unnecessary re-rendering. Basically, this JSX... <Foo {...a} b={1} {...c} d={2}/> ...translates to this JS: React.createElement(Foo, _extends({}, a, { b: 1 }, c, { d: 2 })); If we did the same thing (i.e. bail out of the optimisation allowed by knowing the attribute names ahead of time), our lives would get a lot simpler, and the performance characteristics would be pretty similar in all but somewhat contrived scenarios, I think. (It'll still be faster than React, anyway!)
    1. It’s become increasingly common to divide code into components, rather than by file type. React, for example, allows for the collocation of a components markup and JavaScript. In Svelte, this is taken one logical step further: the Javascript, markup and styling for a component can all exist together in a single `.svelte`​ file
    1. For a non-monorepo package you can simply point directly to the Github repo. This case is similar, but you want to scope it just to a single package within the repo. For those that make monorepos they don't necessarily need this feature. It's for those that use projects that use monorepos. Telling them to not organize their projects into monorepos doesn't help people who make use of these projects.
    2. If npm installs a git repo, it assumes that the git repo is the package. I don't really know how we could specify a sub-path easily, since all parts of the git url are already used for other things.
    1. This is more a rhetoric question as this seems to be quite hard ;-) There is a long discussion about installing a subfolder of a repository and monorepos in general at the NPM Github issues (yarn misses this feature, too). The thing is that this makes it quite hard to report issues of your project as one can't test the current master easily. Do you recommend a way how to use the latest Github version?
  12. Aug 2020
  13. Jul 2020
    1. Middle School Project: Public Art

      STEAM!!!! Google Maps walking tour, kinetic sculpture to install Teacher Planning Session, connecting learning

      Existing art that students are studying in history Click on art and information they have found about it comes up Applies to real-world--their community Writing proposals for installation of their works of public art

      No "paint by numbers"

      Let students explore the process! The products will be so creative--things you have not even thought about

      "Science fair" or "expo" of ideas

      Students taking ownership of ideas

    1. This process involves the following five phases:

      collaboratively identify interest and a question search and sift through information critically evaluate information (credibility and usefulness) Synthesize what they have learned from multimodal sources Online content construction

  14. Jun 2020